Replit
Missing robots.txt on a Replit app
A Replit deployment is an ordinary website. The page, its same-origin scripts, and the headers from that host are what a visitor receives, and what this scan reads.
A launch file, not a security boundary.
What the scan can see
The scan requests /robots.txt and /sitemap.xml. A 404, or an HTML app shell, counts as missing. A noindex meta tag or X-Robots-Tag on the homepage is a separate finding, because a public launch usually wants to be indexed.
What it does not do
robots.txt does not hide a URL that is already linked. It is not an access control.
The Replit API, the workspace, and secrets that exist only in Replit's server environment are outside the fetch.
What to do next
Serve a plain-text robots.txt and an XML sitemap. Remove noindex from the homepage if the app should be found. Keep noindex on private pages such as this scan report.
Questions
Does this open my Replit project?
No. The Replit API, the workspace, and secrets that exist only in Replit's server environment are outside the fetch.
Can the scan prove missing robots.txt is fully fixed?
robots.txt does not hide a URL that is already linked. It is not an access control.
What should I do if the scan finds it?
Serve a plain-text robots.txt and an XML sitemap. Remove noindex from the homepage if the app should be found. Keep noindex on private pages such as this scan report.
Scan a URL you own
The same free check as the homepage. You confirm the app is yours before it runs.