Why it matters
Debugging what Google can see on a site, with URL Inspection, the Page indexing report or Crawl stats, starts with verified access to the site in Search Console.
How to meet it
Add a Domain property (DNS verification) that covers every subdomain and protocol, plus URL-prefix properties for sections or hosts that need separate access, and keep the verification record in infrastructure code so it survives DNS or CMS changes.
How to test it
Search Console lists the Domain property as verified, and every team that ships code has access.
How Regensbot covers it
Regensbot proposes a verdict with the evidence; a person on your team confirms it.
The evidence comes from Search Console, Merchant Center or BigQuery once you connect them.
One consent screen grants read-only Search Console access. Merchant Center and BigQuery are requested separately, only where they apply, and Regensbot only reads from them. URL Inspection samples and Search Analytics add Google's own view of your pages.
Sources
Google documents01
Claims in the knowledge base01
- D2-C306ConsistentWhat is Google friendly JavaScriptSaid on stage
Claim IDs refer to the Search Central Live 2026 knowledge base. The knowledge base (opens in a new tab)
- Consistent
- Google's documentation supports it without stating it.