Agent-friendly 404s

A missing page must answer 404 or 410. Returning a 200 tells an agent the page exists.

Standard
Established

Who supports it

No agent or browser has announced support yet.

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

What it checks

The extension requests a path that will not exist on any real site, /sitebulb-agent-readiness-404-probe, and records the status code it gets back after following redirects. The path is fixed rather than random, so you can request it yourself and see the same response.

An agent trusts the status code. If a missing page answers 200, the agent treats whatever came back as real content, and may cite or act on an error page.

Results

Status When
Pass The missing path answers 404 or 410
Pass The missing path answers another 4xx status, which still tells an agent it is not a resource
Fail The missing path answers a 2xx or 3xx status, including when it redirects to a page that answers 200
Unmeasured The request failed or the server answered with a 5xx error

How to fix

Return a real 404 (or 410 for pages removed permanently) for paths that do not exist. Do not redirect unknown paths to the homepage, and make sure a single-page app’s catch-all route sets the status code rather than rendering a “not found” view with a 200.

You can check what your site does with:

curl -sI https://example.com/sitebulb-agent-readiness-404-probe | head -1

A good 404 page also helps an agent recover. Link to your sitemap or /llms.txt from it.

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.

No agent or browser has announced anything about this yet.

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

Adoption on the top 100 sites

80 of 93 measured sites implement it

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

9 Oct 2026: 84%12 Oct 2026: 85%23 Oct 2026: 86%
9 Oct 2026 84% → 23 Oct 2026 86%
Sites implementing it80
  1. #1 google.com
  2. #2 cloudflare.com
  3. #3 aws.amazon.com (via amazonaws.com)
  4. #5 gstatic.com
  5. #8 googleapis.com
  6. #9 microsoft.com
  7. #12 apple.com
  8. #15 mail.ru
  9. #16 x.com (via twitter.com)
  10. #18 linkedin.com
  11. #23 googletagmanager.com
  12. #24 azure.microsoft.com (via azure.com)
  13. #29 amazon.com
  14. #32 github.com
  15. #37 fastly.com (via fastly.net)
  16. #39 whatsapp.com (via whatsapp.net)
  17. #42 bing.com
  18. #44 triplinkintl.com
  19. #45 googleusercontent.com
  20. #48 gandi.net
  21. #50 marketingplatform.google.com (via doubleclick.net)
  22. #53 icloud.com
  23. #55 wordpress.org
  24. #56 teams.live.com (via skype.com)
  25. #57 cloudflare.net
  26. #59 goo.gl
  27. #60 digicert.com
  28. #61 adobe.com
  29. #67 domains.google (via googledomains.com)
  30. #68 zoom.com (via zoom.us)
  31. #69 uk.yahoo.com (via yahoo.com)
  32. #71 endpoints.news
  33. #72 api.whatsapp.com (via wa.me)
  34. #75 roblox.com
  35. #76 opera.com
  36. #77 open.spotify.com (via spotify.com)
  37. #80 baidu.com
  38. #81 tiktokv.com
  39. #83 ya.ru (via yandex.net)
  40. #84 nginx.org
  41. #85 ntp.org
  42. #86 msn.com
  43. #90 vimeo.com
  44. #91 primevideo.com (via amazonvideo.com)
  45. #93 bunny.net (via b-cdn.net)
  46. #94 blogger.com (via blogspot.com)
  47. #95 mozilla.org
  48. #96 f5.com
  49. #101 wordpress.com
  50. #107 letsencrypt.org (via lencr.org)
  51. #109 ui.com
  52. #110 european-union.europa.eu (via europa.eu)
  53. #114 st.okcdn.ru (via okcdn.ru)
  54. #116 bitly.com (via bit.ly)
  55. #117 ipify.org
  56. #120 samsung.com
  57. #121 office365.com
  58. #122 intuit.com
  59. #123 aliyuncs.com
  60. #127 openai.com
  61. #128 one.one.one.one (via cloudflare-dns.com)
  62. #130 registrar-servers.com
  63. #131 pages.github.com (via github.io)
  64. #132 dropbox.com
  65. #133 skybridge.click
  66. #135 discord.com (via discord.gg)
  67. #136 developer.adobe.com (via adobe.io)
  68. #139 apache.org
  69. #140 android.com
  70. #141 nih.gov
  71. #144 vk.ru
  72. #150 t-online.de
  73. #151 archive.org
  74. #153 webex.com
  75. #154 snapchat.com
  76. #156 godaddy.com
  77. #158 kaspersky.co.uk (via kaspersky.com)
  78. #159 firebase.google.com (via crashlytics.com)
  79. #160 tumblr.com
  80. #161 nytimes.com

Overview

6/9

Gaining traction

Real support exists and adoption is growing.

How this rating is worked out6 of 9 points
FactorPointsWhy
Vendor support0 / 30 vendors supporting, 0 partly or planned
Top-100 adoption3 / 386% 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.