Sitemap available

A sitemap gives agents a list of the pages worth reading or indexing.

Standard
Established

Who supports it

  • CopilotSupported (announced)

    Published 31 Jul 2025 · last checked 9 Oct 2026: Keeping Content Discoverable with Sitemaps in AI Powered Search (Bing Webmaster Blog)Bing (which grounds Copilot) says 'sitemaps remain a foundational signal for ensuring comprehensive URL coverage' in AI-powered search. Written by Fabrice Canel and Krishna Madhavan.

  • CCBotSupported (announced)

    Undated · last checked 9 Oct 2026: Common Crawl FAQ'The crawler supports the Sitemap Protocol and utilizes any Sitemap announced in the robots.txt file.'

25 others: no evidence yet. See every agent and browser

What it checks

The extension first looks for Sitemap: lines in robots.txt. If there are none, it fetches /sitemap.xml and checks that the body contains a <urlset> or <sitemapindex> element. A sitemap saves an agent from having to discover pages by following links.

Results

Status When
Pass robots.txt declares one or more sitemaps
Pass /sitemap.xml exists but is not declared in robots.txt (with a recommendation to declare it)
Fail No sitemap is declared in robots.txt and /sitemap.xml was not found

How to fix

Publish an XML sitemap and reference it from robots.txt, so agents find it without guessing the path:

Sitemap: https://example.com/sitemap.xml

A sitemap index works too, if you split your sitemap into several files:

<?xml version="1.0" encoding="UTF-8"?>
<sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <sitemap>
    <loc>https://example.com/sitemap-pages.xml</loc>
  </sitemap>
</sitemapindex>

See also robots.txt present & valid and Sitemap freshness (lastmod).

Support by agent and browser

Announced means the vendor’s own docs or announcement say so. Published is the date on the vendor’s own page, where it has one. Checked is the last time our weekly research found that page still saying so.

AgentStatusSource
AI assistants
Copilot MicrosoftSupported (announced)

Keeping Content Discoverable with Sitemaps in AI Powered Search (Bing Webmaster Blog) Published · Checked Bing (which grounds Copilot) says 'sitemaps remain a foundational signal for ensuring comprehensive URL coverage' in AI-powered search. Written by Fabrice Canel and Krishna Madhavan.

AI crawlers
CCBot Common CrawlSupported (announced)

Common Crawl FAQ Undated · Checked 'The crawler supports the Sitemap Protocol and utilizes any Sitemap announced in the robots.txt file.'

No evidence yet25
  • ChatGPT
  • Claude
  • Gemini
  • Perplexity
  • Meta AI
  • ChatGPT Atlas
  • Comet
  • Dia
  • Gemini in Chrome
  • Edge Copilot Mode
  • Claude Code
  • Cursor
  • Codex
  • GitHub Copilot
  • Windsurf
  • Applebot
  • Amazonbot
  • Bytespider
  • Cohere
  • Mistral
  • DuckAssist
  • Chrome
  • Edge
  • Firefox
  • Safari

Adoption on the top 100 sites

64 of 99 measured sites implement it

Scanned 23 Oct 2026 with the Sitebulb Labs extension, against the Tranco list (tranco-56Z8N). 1 sites couldn’t be measured (bot challenge or timeout) and are left out of the share.

9 Oct 2026: 62%12 Oct 2026: 62%23 Oct 2026: 65%
9 Oct 2026 62% → 23 Oct 2026 65%
Sites implementing it64
  1. #1 google.com
  2. #2 cloudflare.com
  3. #3 aws.amazon.com (via amazonaws.com)
  4. #4 facebook.com
  5. #9 microsoft.com
  6. #11 youtube.com
  7. #12 apple.com
  8. #13 instagram.com
  9. #16 x.com (via twitter.com)
  10. #20 dzen.ru
  11. #24 azure.microsoft.com (via azure.com)
  12. #32 github.com
  13. #37 fastly.com (via fastly.net)
  14. #39 whatsapp.com (via whatsapp.net)
  15. #42 bing.com
  16. #43 netflix.com
  17. #44 triplinkintl.com
  18. #48 gandi.net
  19. #50 marketingplatform.google.com (via doubleclick.net)
  20. #52 uk.pinterest.com (via pinterest.com)
  21. #53 icloud.com
  22. #55 wordpress.org
  23. #60 digicert.com
  24. #61 adobe.com
  25. #68 zoom.com (via zoom.us)
  26. #69 uk.yahoo.com (via yahoo.com)
  27. #70 sso.myfritz.net (via myfritz.net)
  28. #71 endpoints.news
  29. #75 roblox.com
  30. #76 opera.com
  31. #77 open.spotify.com (via spotify.com)
  32. #83 ya.ru (via yandex.net)
  33. #84 nginx.org
  34. #85 ntp.org
  35. #86 msn.com
  36. #87 qq.com
  37. #90 vimeo.com
  38. #93 bunny.net (via b-cdn.net)
  39. #96 f5.com
  40. #99 store.epicgames.com (via epicgames.com)
  41. #101 wordpress.com
  42. #106 sentry.io
  43. #107 letsencrypt.org (via lencr.org)
  44. #109 ui.com
  45. #110 european-union.europa.eu (via europa.eu)
  46. #112 chatgpt.com
  47. #116 bitly.com (via bit.ly)
  48. #117 ipify.org
  49. #120 samsung.com
  50. #122 intuit.com
  51. #127 openai.com
  52. #131 pages.github.com (via github.io)
  53. #132 dropbox.com
  54. #135 discord.com (via discord.gg)
  55. #136 developer.adobe.com (via adobe.io)
  56. #140 android.com
  57. #141 nih.gov
  58. #151 archive.org
  59. #153 webex.com
  60. #154 snapchat.com
  61. #158 kaspersky.co.uk (via kaspersky.com)
  62. #159 firebase.google.com (via crashlytics.com)
  63. #160 tumblr.com
  64. #161 nytimes.com

Overview

8/9

Established

Widely supported and widely deployed.

How this rating is worked out8 of 9 points
FactorPointsWhy
Vendor support2 / 32 vendors supporting, 0 partly or planned
Top-100 adoption3 / 365% of measured sites
Spec maturity3 / 3Published standard

8 or more points is Established, 5 to 7 is Gaining traction, 2 to 4 is Speculative and under 2 is Stalled. A feature is also Stalled when more vendors have said no than yes. Read the spec.

Community insights

No community insights for this feature yet.

Quotes are from public posts, checked against the original before they appear here. Suggest an insight, or ask for yours to be removed.