Skip to content

The problem list is free. A fix prompt for each one is $9.

See pricing

Cursor

Missing robots.txt on a Cursor app

Cursor writes the repo on your machine. Visitors see the host you deployed to. A key in a local .env is invisible here. A key compiled into the deployed JavaScript, or returned at /.env, is not.

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 scan does not open the Cursor workspace, the chat, or git history on your laptop.

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 Cursor project?

No. The scan does not open the Cursor workspace, the chat, or git history on your laptop.

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.

Free public scan