Google SEO: the documentation Google publishes itself, what each document settles, and the order to read it

Google SEO has one feature that makes it unlike almost any other marketing discipline: the company that owns the rules writes them down and publishes them for nothing. Most arguments you will have about SEO are already settled in a document on Google Search Central, and most of the bad advice in circulation is a blog post about a document nobody involved had read. There are about ten documents that matter. Google Search Essentials is the rulebook, the SEO starter guide is the practical introduction, the spam policies say what gets a site demoted, Search Console Help explains every number you will be asked about, and the structured data pages set out what qualifies for a rich result. Read the primary source first and the commentary afterwards.

This page is a map of what Google publishes, what each document settles, the order to read them, and the arguments the documentation already closes. For the practice itself, start with what SEO is in plain English.

The documents, and the question each one answers

Everything in the table below lives under Google Search Central at developers.google.com/search, with two exceptions noted in the rows themselves.

Document	What it settles
Google Search Essentials	The closest thing to a rulebook. Three parts: the technical requirements a page has to meet to be eligible at all, the spam policies, and the key best practices. If somebody tells you Google requires something, this is where it either is or is not.
SEO Starter Guide	The practical introduction for a site owner: get indexed, write useful titles and descriptions, organise a site, use images properly. Short, and it covers the ground most paid courses charge for.
How Search Works, at google.com/search/howsearchworks	Crawling, indexing and serving explained for a general reader, plus how the results page features are assembled. The document to send to a board or a client.
A guide to Google Search ranking systems	The systems Google is willing to name, and which of them are automated and continuous rather than manual actions. Useful mainly for what it does not contain.
Spam policies for Google web search	What gets a site demoted or removed: cloaking, scaled content abuse, link spam, site reputation abuse and the rest. Read it before you buy anything from anybody who promises links.
Search Console Help	What each report counts and what each number means, including how average position and impressions are defined. Nearly every reporting disagreement ends here.
Structured data general guidelines, plus one page per feature	Which markup is eligible for which result type, the required properties, and the technical and quality rules. Eligibility is not a promise of display, and the documents say so themselves.
The crawling and indexing set: robots.txt, meta robots, canonicalisation, redirects, JavaScript basics, crawl budget	The mechanics of access and duplication. These are the pages a developer should be handed at the start of a build rather than after a traffic drop.
Google Search ranking updates, and the Search Status Dashboard at status.search.google.com	A dated record of confirmed core and system updates, and a live record of current incidents. Both are how you tell a Google event from your own mistake.
Do you need an SEO?	Google's own guidance on hiring: the questions to ask, the warning signs, and its plain statement that nobody can guarantee a number one ranking.

The order to read them in

• First hour. Search Essentials, then the SEO starter guide. Those two give you the shape of the whole subject and the vocabulary everything else uses.
• First week. Search Console Help for the three reports you will actually open, which are Performance, Pages and URL Inspection. Our guide to the Search Console reports is the same ground with the practical order on top.
• Before you buy anything. The spam policies and the hiring page. Twenty minutes here saves the cost of a bad supplier.
• Before a build or a migration. The crawling and indexing set, handed to whoever writes the templates.
• As needed. The structured data pages, feature by feature, only for the features you are actually trying to earn.
• Once a quarter. The ranking updates page, so your own traffic chart has dates to sit against.

If you would rather be taught than read, our note on picking an SEO class that teaches the work covers what a course should contain. The documentation is still the thing a good course is teaching from.

Six arguments the documentation already closes

• There is no Google authority score. Domain Authority and Domain Rating are third party metrics built by tool vendors from their own link indexes. They are useful for comparing two sites inside one tool and they are not a number Google holds. Our page on what domain authority is and what it is not covers how to use them without misquoting them.
• The meta keywords tag does nothing for Google Search. This has been documented for well over a decade, and it is still being sold as a service.
• There is no keyword density figure to hit. No Google document states a percentage, because no percentage exists. Write for the reader and use the words the query uses.
• A sitemap is not a requirement for being indexed. It helps discovery on large sites, new sites and sites with poor internal linking. A small, well linked site can be fully indexed without one.
• Paying for Google Ads changes nothing in organic results. The two systems are separate, Google says so plainly, and anybody who implies otherwise in a sales call has told you something useful about themselves.
• Nobody can promise a position. That sentence is on Google's own hiring page, which makes it the most quotable line in the entire documentation set when you are reading a proposal.

What the documentation deliberately does not tell you

It describes mechanics. It does not describe weightings, thresholds, or why one specific page outranks another specific page, and it never describes what is coming. So the documentation settles every question of the form "is this allowed, and how does it work", and it settles no question of the form "will this beat the page above me". That second kind is answered by looking at the results page for your query, reading the pages that currently rank, and testing on your own site.

Knowing which kind of question you have is the skill. Teams waste weeks looking for a documented answer to a competitive question, and they publish confident claims about mechanics they never looked up.

How to use a Google document in an argument

• Quote the sentence, not the summary. Paste the line and the page address into the ticket or the email. A paraphrase of a paraphrase is how the myths got started.
• Write the date you read it. These pages are edited, and Search Central publishes a list of documentation changes, so a quote without a date ages badly.
• Separate documentation from commentary. A Google employee's remark in a video or on social media is informed, and it is not the documented position. Both are worth knowing, and only one of them belongs in a policy.
• Re-check after a confirmed update. When the ranking updates page records a core update, that is the moment to re-read the parts of the documentation your plan depends on.

Google SEO: the questions behind the search

Does Google publish official SEO rules?

Yes, in Google Search Essentials, which sets out the technical requirements, the spam policies and the key best practices. It is not a ranking formula, and it is a real set of rules with real consequences: the spam policies describe behaviour that gets a site demoted or removed.

Does Google publish its ranking factors?

No, and the ranking systems guide is the nearest thing. It names a set of systems and explains what each is broadly for, without weightings or thresholds. Treat any list of two hundred ranking factors as somebody's reconstruction rather than a document.

Is there an official Google SEO certification?

Not for organic search. Google's training programmes certify people on Google Ads and on Analytics, which are advertising and measurement products. A certificate in either is evidence somebody studied those tools, and it says nothing about organic search skill.

How do I report a spam problem or a wrong result to Google?

Google provides forms for reporting search spam, paid links and legal removal requests, linked from Search Central and from Search Console. For a page about your own business that is simply wrong, the faster route is usually fixing the source: the page itself, your business profile, or the third party site carrying the error.

Is Google SEO different from SEO for Bing or other engines?

The fundamentals are shared, because every engine crawls, indexes and ranks. The differences are in the detail: Bing documents its own guidelines and offers its own console, and Bing's index also feeds several AI assistants. In practice a site built properly for one is close to correct for the others, and the gap is worth a few hours rather than a separate programme.

Where should somebody completely new start?

Search Essentials and the SEO starter guide, then verify the site in Search Console and read the Pages report. That sequence costs nothing, takes an afternoon, and puts you ahead of most people selling the service.

The engine that documents itself, and the ones that do not

The reason this page can exist is that Google writes its rules down. That is now unusual. When a buyer asks ChatGPT, Gemini or Perplexity to recommend a company in your category, there is no equivalent document: no eligibility list, no spam policy, no starter guide for being named in an answer. What exists instead is observation, which means asking the question repeatedly and recording which companies get named and which sources the answer leaned on. Our study of what assistants actually cited across 597 readings is that method applied at some scale, and it is the closest thing to documentation this part of search currently has.