Google Search
Verified by Googlebot FCrDNS
SearchIndependent crawler identity control
GateLab sits before your origin, distinguishes Google Search from Google Ads, Meta Ads, Stripebot, and other known crawler families, verifies the source where the provider supports it, and applies one explicit policy per website.
Built-in registry
“Verified” means GateLab found evidence the requester cannot place in a header. When no public verifier exists, the identity remains explicitly “claimed.”
Verified by Googlebot FCrDNS
SearchVerified by Google special-crawler FCrDNS
AdsVerified by published provider domains
SearchVerified through crawl.stripe.com
PaymentVerified through rotating AS32934 prefixes or strict FCrDNS
Ads / preview / AIfwdproxy-*.fbsv.net FCrDNS is retained as a second confirmation path; failure of both remains claimed.Per-site policy
Verified Google Search and Meta Ads crawlers can receive narrow public-page access while their unverified lookalike claims are monitored or denied.
Forward the request with a signed identity decision.
Forward it and retain a privacy-minimized audit event.
Control crawl pressure without blocking the entire provider.
Stop the request before the private origin.
Return a truthful, no-store crawler-access error page.
Product boundaries
GateLab owns your crawler registry, provider verification, site-specific policy, signed origin decision, and identity history. Optional edge evidence remains optional.
A user-agent token identifies what the caller says it is. GateLab promotes that claim only when provider-controlled evidence verifies the source.
Each deployment can allow, monitor, rate-limit, deny, or return a truthful notice by crawler, verification status, path, and method.
Crawler recognition, verification, enforcement, and reporting run inside GateLab. A CDN signal can be added, but Cloudflare is not required.