nnationalparks.org

The URL is declared in robots.txt but does not return a successful response.

Consequence. Crawlers find nothing at the address they were pointed to, so no URLs are submitted. This is worse than declaring no sitemap, because the declaration suggests discovery is covered when it is not.

If that is not intended. Publish the sitemap at the declared URL, or correct the URL to where it lives.

• https://www.nationalparks.org/sitemaps-1-sitemap.xmlL3Responded HTTP 403

Rules name version-control directories, credential files, databases, dumps, archives or logs.

Consequence. If this file is served, it is a critical exposure; listing it here suggests it exists. robots.txt is public and among the first files a scanner reads, and it protects nothing: it only tells readers where to look.

If that is not intended. Check whether these paths answer. Remove the files from the web root or block them at the server, then delete the lines. If a .env file or a .git directory was ever served, rotate every credential it held.

• Disallow: /.envL10Secret file or directory (.env)

All 6 checked search engines are allowed at the site root.

All 4 checked AI answer engines are allowed at the site root.

All 3 checked user-triggered AI fetches are allowed at the site root.

All 5 checked social link previews are allowed at the site root.

All 6 checked AI training crawlers are allowed at the site root.

The page answered HTTP 403 with a bot challenge instead of its content, so its meta robots tags and X-Robots-Tag headers were not read.

Consequence. Nothing is known about whether this page asks to be kept out of search results. Its absence of directives here proves nothing either way.

If that is not intended. Analyse the page again once it answers normally to our bot.

Every line parses as a directive crawlers understand.

Comfortably within the 500 KB that crawlers will read.