ssiteinspire.com

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.siteinspire.com/sitemap.xmlL55Responded HTTP 403
• https://www.siteinspire.com/websites/sitemap.xmlL56Responded HTTP 403
• https://www.siteinspire.com/profiles/sitemap.xmlL57Responded HTTP 403
• https://www.siteinspire.com/websites/categories/sitemap.xmlL58Responded HTTP 403
• https://www.siteinspire.com/inspiration/sitemap.xmlL59Responded HTTP 403
• https://www.siteinspire.com/profiles/expertise/sitemap.xmlL60Responded HTTP 403
• https://www.siteinspire.com/profiles/location/sitemap.xmlL61Responded HTTP 403

A broader rule of the same type already covers these paths.

Consequence. These lines change nothing. They are harmless, but they add length to a file that has a size limit, and they make the real policy harder to read.

If that is not intended. Remove the redundant rules, or narrow the broader rule if it is catching more than intended.

• allow: /api/mcpL9Already covered by "allow: /" on line 8
• allow: /_next/static/L10Already covered by "allow: /" on line 8
• allow: /_next/static/L45Already covered by "allow: /" on line 44
• allow: /websites/categories/sitemap.xml$L46Already covered by "allow: /" on line 44

Blocked: Google-Extended.

• Google-ExtendedGoogleL41

  Google AI Overviews and Gemini grounding

  "Disallow: /" blocks Google-Extended.

If that is the intention. If your intention is to keep the site out of AI-generated answers, the current configuration achieves that for these crawlers — the rest of the group is still allowed.

Consequence. The site cannot be cited as a source in AI-generated answers. Unlike training crawlers these send referral traffic, so blocking them forfeits those visits.

If that is not intended. Remove the matching Disallow rule, or allow these agents on the sections you want cited.

Blocked: GPTBot, ClaudeBot, Bytespider, meta-externalagent, CCBot, Amazonbot.

• GPTBotOpenAIL41

  OpenAI model training

  "Disallow: /" blocks GPTBot.

• ClaudeBotAnthropicL41

  Anthropic model training

  "Disallow: /" blocks ClaudeBot.

• BytespiderByteDanceL41

  ByteDance model training

  "Disallow: /" blocks Bytespider.

• meta-externalagentMetaL41

  Meta model training

  "Disallow: /" blocks meta-externalagent.

• CCBotCommon CrawlL41

  Common Crawl, widely redistributed as training data

  "Disallow: /" blocks CCBot.

• AmazonbotAmazonL41

  Amazon model training and Alexa

  "Disallow: /" blocks Amazonbot.

If that is the intention. If your intention is to prevent this content being used as model training data, the current configuration achieves that.

Consequence. These crawlers cannot retrieve content from the site, so it will not be collected as training data. They send no traffic back, and blocking them does not affect search rankings.

If that is not intended. Remove the site-wide block, or replace it with narrower path restrictions.

All 6 checked search 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.

The page answered HTTP 403, 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.