Google Search Central

What it is

Search Central is the canonical source for how Google says its crawling, indexing, ranking and rich result systems work, and what it considers acceptable practice. It includes the technical reference for every supported structured data type, guidance on robots.txt, sitemaps, JavaScript rendering and site moves, and the spam policies that govern manual actions. Search Console help documentation and developer guidance for Google's crawlers and user agents sit alongside it.

Why it matters

Most SEO advice in circulation is second hand, and the primary documentation is where you settle disputes about what is actually required or merely rumoured. It is also where Google publishes changes to rich result eligibility, crawler behaviour and policy, which can materially affect what appears in results and in AI-generated answers. Citing the documentation in recommendations makes it far easier to get engineering and legal sign-off.

How it works

Teams use it as the reference when implementing structured data, validating markup against the eligibility requirements for each rich result type, planning migrations, or resolving indexing problems. Many follow the Search Central blog and release notes so that policy and feature changes are picked up early, and use the office hours recordings and forum for edge cases. In practice it works best as a checklist step in technical SEO tickets rather than something read end to end.

When it applies

Use it whenever a technical or policy question needs a definitive answer, before shipping structured data or crawl directives, and during audits, migrations and penalty diagnosis.

Examples

• A developer checks the Product structured data documentation to confirm which properties are required for merchant listing eligibility.
• An SEO lead links to the Search Essentials spam policies in a brief to stop a partner agency buying links.
• A technical team follows the site move documentation to plan redirects and Search Console change of address for a domain migration.

How it is measured

• Percentage of structured data implementations validated against the current documentation before release
• Rich result errors and warnings reported in Search Console after each deployment
• Time between a documented policy or feature change and the corresponding site update
• Number of technical recommendations supported by a primary documentation reference