v0
Missing robots.txt on a v0 app
v0 generates UI you then deploy, often on Vercel. The scan starts at the deployed URL. It sees the shipped page, not the v0 chat that produced the components.
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.
A component that was generated but never deployed is not part of the check.
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 v0 project?
No. A component that was generated but never deployed is not part of the check.
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.