fleetline.ai's robots.txt returns a 500 server error on both www and the bare domain, and so does /sitemap.xml (each checked twice). Google's documentation says that when robots.txt returns a 5xx error, Google stops crawling the site for the first 12 hours, and that it stops crawling if the site still looks unavailable after 30 days. Underneath that, the homepage and /support read as a single word, "Fleetline", to any reader that doesn't run scripts; the product sentence about simulating billions of fleet plans only appears after scripts run. A site:fleetline.ai search returns no pages from fleetline.ai itself, only directories and marketplace listings. A fleet executive who hears about Fleetline and searches for it, or asks an AI assistant, gets someone else's description of the company.
First action
Publish a plain robots.txt and sitemap.xml and confirm both return status 200 from www and the bare domain.
How to measure it
Indexed pages and branded clicks
- Now
- –
- Target
- All public pages indexed; fleetline.ai is the first result for "Fleetline dispatch"
- By
- 30 days
Steps
Fix robots.txt
Static file: User-agent *, Allow /, Sitemap line. Confirm a 200 status on www and the bare domain.
Founding Engineer 1 hour
Fix the sitemap
List the homepage, /support, /privacy and /terms; confirm a 200 status.
Founding Engineer 1 hour
Write the copy
H1, two-sentence description, three sections, demo link, page title and meta description.
Co-founder, CEO 1 day
Render it as text
Real Framer text layers, not text inside a script or canvas. Check with a text-only fetch.
Founding Engineer 1 day
Fill /support
Setup steps for the Google Chat app and the Motive connection, plus a contact route.
Co-founder, CTO 1 day
Submit to Google
Verify in Search Console, submit the sitemap, request indexing of the homepage.
Founding Engineer 1 hour
Monitor
Weekly check that robots.txt returns 200 after each publish; track branded queries.
Co-founder, CEO weekly
Why it works
Serve a static robots.txt (allow all, with a Sitemap line) and a static sitemap.xml listing the homepage, /support, /privacy and /terms, and confirm both return 200. Then put the pitch into the page's HTML: an H1, a two-sentence description (AI load planning and dispatch for mid-to-large trucking fleets, working with your TMS and ELD), three short sections (plan the week, re-plan in plain language, integrations with Motive and Google Chat), a demo link, a page title and a meta description. In Framer, that means real text layers, not text drawn by an embedded script or canvas. Fill /support with setup steps for the Google Chat app and the Motive connection. Verify the site in Google Search Console, submit the sitemap and request indexing, then confirm with a text-only fetch that the pitch is readable.
Every channel Fleetline uses (YC, the Motive marketplace, the Google Workspace listing, investor and job-board profiles) ends with a buyer typing the name into Google or an assistant. Right now that search can't land on fleetline.ai. Fixing it takes about a day and makes the company's own words the first answer, ahead of third-party directories.
Ready to use
ChecklistFindability launch list
[ ] robots.txt returns 200 on www and the bare domain [ ] sitemap.xml returns 200 and lists every public page [ ] Homepage H1 and description readable without scripts [ ] Page title and meta description set [ ] /support has real setup and contact text [ ] Search Console verified, sitemap submitted [ ] Text-only fetch of the homepage shows the pitch
Risks and how to handle them
A later publish brings the error back
Set robots and sitemap in Framer's site settings and re-test after every publish.
Copy reads like a pitch deck
Use the fleet's own words: loads, drivers, hours of service, empty miles, revenue per truck.
Evidence
- Your websiterobots.txt returns HTTP 500 (server error) at both www.fleetline.ai and fleetline.ai, and /sitemap.xml also returns 500 (each checked twice on November 9, 2026). Google Lighthouse flags "robots.txt is not valid".Source
- Google Search CentralWhen robots.txt returns a 5xx error: "For the first 12 hours, Google stops crawling the site but keeps trying to fetch the robots.txt file." For the next 30 days Google uses the last good copy, or assumes no restrictions if it has none; after 30 days, if the site has general availability problems, Google stops crawling it.Source
- Your websiteHomepage, read three times on November 9, 2026 without running scripts: the whole page reads as one word, "Fleetline", with no readable headline, description or links. The product sentence ("Fleetline simulates billions of possible ways to plan a fleet over a week and s…") appears only after scripts run, in Google's PageSpeed render. /support also reads as the single word "Fleetline", while /privacy and /terms (both "Last updated: January 1, 2025") are readable.Source
- Web presenceDomain registered June 25, 2025 and built on Framer; a web search restricted to site:fleetline.ai returned no pages from fleetline.ai itself, only directories and the Motive and Google Workspace listings; no Hacker News mentions and no news mentions in the last 30 days.Source