Audited Prerender Buddy edge and developer integration code recognizes crawler user-agent families and routes eligible requests to rendered HTML. This reference separates request detection, routing, controlled tests, and independent verification so those terms are not treated as the same proof.
Recognition makes a crawler eligible for the rendered-response path. It does not authenticate the operator or guarantee indexing, ranking, citation, or recommendation.
Registry reviewed 2026-07-13
29
Request-agent entries detected and routed in audited integration code.
Managed-DNS proxy detection was not separately audited in the available repositories.
5
Agents with a dated controlled crawler-style production test.
No operator verification claimed
A supplied user agent can be spoofed. Authentication requires operator-specific verification.
How to read the status
Four terms, four different claims.
Detected
The request user-agent matches a documented family in the audited integration code.
Routed
A detected request is eligible for the rendered-response path in that integration.
Tested
Prerender Buddy can send a controlled request using that user-agent token.
Verified
A dated test authenticates or otherwise proves the stated relationship. None is currently claimed here.
Search and AI agents
Keep each crawler purpose distinct.
Search crawlers, AI-search agents, model-development crawlers, and user-requested fetchers can come from the same operator but serve different purposes and use separate robots controls.
Google
Googlebot
Search
Crawls pages for Google Search and related Google Search features.
Request-agent token or family
Googlebot
Detected and routedControlled test: 2026-07-13Not independently verified
Googlebot follows Google Search robots.txt controls. User-agent strings can be spoofed; Google documents IP and reverse-DNS verification.
The available test uses a supplied Googlebot user agent. It does not authenticate Google or prove indexing.
Link previews, advertising crawlers, public-web datasets, and archival agents can also request public pages. Detection does not guarantee how their downstream product will use or display the response.
Google
Google advertising crawlers
Advertising
Fetches pages for Google advertising and publisher products.
Request-agent token or family
AdsBot-GoogleMediapartners-Google
Detected and routedNo controlled test presetNot independently verified
Special-case Google crawlers can have product-specific robots behavior.
These are not Google Search indexing crawlers and should not be described as AI-search agents.
Covered through Google’s crawler ecosystem, not a separate Gemini crawler.
Google documents Google-Extended as a robots.txt product token for certain Gemini uses. It has no separate HTTP request user agent; crawling is performed with existing Google agents.
Product visibility without an unverified crawler claim.
The audited routing configuration does not contain a distinct Grok or xAI request-agent token, and no current official crawler identity was verified for this reference. Grok is therefore not labelled as detected or routed.
Status: crawler identity not independently verified
What this page does not promise
Detection does not authenticate who sent a request.
Routing does not guarantee crawling or indexing.
Indexing does not guarantee rankings or traffic.
AI crawler access does not guarantee citation or recommendation.
Robots.txt permission does not force an operator to retrieve a page.
Controlled tests simulate user agents; they do not impersonate verified operators.
Test what a crawler-style request receives.
Compare the raw response first. If the important content is missing, inspect the rendered result before choosing a setup path.