Audit my site
How search worksBeginnerChecked against Google docs · Oct 2026

How Google Search works: from crawl to ranking, the full pipeline

Every page that appears in Google has passed through discovery, crawling, rendering, indexing and serving. Learn what happens at each stage, what can stop a page there, and where Search Console shows it.

Author: Eugene Serbin, Head of SEO at Semalt Updated: 30 October 2026 Reading time: 16 min Visuals: 4

In short

Google Search works in three stages: crawling (finding and fetching pages), indexing (understanding and storing them) and serving (choosing and ranking results for a query). Not every page passes every stage, and a page that fails early can never be fixed by work on a later stage. Google does not take money to crawl or rank a site, and it does not guarantee that any page will be crawled, indexed or shown.

The pipeline at a glance

Google describes three stages. Most SEOs split them into five, because two steps that Google files under crawling, URL discovery and rendering, fail for their own reasons and need their own fixes:

  1. Discovery. Google learns that a URL exists, from a link or a sitemap.
  2. Crawling. Googlebot requests the URL and downloads the response.
  3. Rendering. Google runs the page's JavaScript in a browser engine to see the final content.
  4. Indexing. Google analyses the content, groups duplicates, picks a canonical and stores what it learned.
  5. Serving and ranking. When someone searches, Google picks matching pages from the index and orders them.

The reason this model is worth learning first: every search problem belongs to the first stage where the page fails. A page that is never discovered will not be helped by a better title. A page blocked in robots.txt will not be helped by more internal links. Diagnosis always starts at stage one and moves right.

Diagram · The full pipeline, from URL to search result
Google Search pipeline: discovery, crawling, rendering, indexing, serving Five stages in a row. Discovery from links and sitemaps; crawling where Googlebot fetches the URL; rendering where JavaScript runs; indexing where Google analyses the page and picks a canonical; serving where pages are ranked for a query. Under each stage are typical reasons a page drops out: no links or sitemap; robots.txt blocks, server errors or login walls; blocked JavaScript or CSS and script errors; noindex, low quality or duplicate URLs; irrelevance to the query and robots meta rules. A bottom band shows Google's own three stages: crawling covers discovery, crawling and rendering; then indexing; then serving. STAGE 1STAGE 2STAGE 3STAGE 4 STAGE 5 DiscoveryCrawlingRenderingIndexingServing links, sitemapsGooglebot fetchesruns JavaScriptanalyse, canonicalrank for a query Drops out ifDrops out ifDrops out ifDrops out ifNot shown if no internal linksnot in any sitemap robots.txt block5xx, login wall blocked JS / CSSscript errors noindex, low qualityduplicate URL irrelevant to queryrobots meta rules Google's stage: CrawlingGoogle's stage: IndexingGoogle's stage: Serving
Google files discovery and rendering under crawling; SEOs separate them because each one fails for different reasons.

What Google officially says

“Google Search works in three stages, and not all pages make it through each stage”

Google Search Central — In-depth guide to how Google Search works

Google defines the three stages like this:

“Google Search is a fully-automated search engine that uses software known as web crawlers that explore the web regularly to find pages to add to our index.”

Google Search Central — How Google Search works. Google adds that “the vast majority of pages listed in our results aren't manually submitted for inclusion, but are found and added automatically when our web crawlers explore the web.”

“Google doesn't accept payment to crawl a site more frequently, or rank it higher. If anyone tells you otherwise, they're wrong.”

Google Search Central — How Google Search works

“Google doesn't guarantee that it will crawl, index, or serve your page, even if your page follows the Google Search Essentials.”

Google Search Central — How Google Search works

Stage 1: URL discovery

Before Google can crawl anything, it needs a URL. Google is direct about the starting point: “There isn't a central registry of all web pages, so Google must constantly look for new and updated pages and add them to its list of known pages. This process is called "URL discovery".”

Google names three ways a URL becomes known:

A typical case: you publish https://example.com/blog/new-post/. Google finds it because the /blog/ hub now links to it, because an older article links to it, and because your CMS added it to sitemap.xml. Each of these is a separate path in; the more of them a page has, the more reliably it is found.

Sitemaps help, but they are a supplement. About submitting one, the Starter Guide says: “However this isn't required, and you should first focus on making sure people know about your site.” In practice, a page that is only in the sitemap and has no internal links (an orphan page) is usually discovered but crawled rarely, because nothing on the site signals that it matters.

Stage 2: Crawling

Once a URL is known, Google may fetch it. The program that does this is Googlebot. It does not crawl everything at the same pace: “Googlebot uses an algorithmic process to determine which sites to crawl, how often, and how many pages to fetch from each site.”

Crawl rate and your server

Google's crawlers try not to overload a site, and the speed adapts to how the server responds: “This mechanism is based on the responses of the site (for example, HTTP 500 errors mean "slow down").” A slow or failing server therefore gets crawled less. If you see crawling drop, check server errors and response times before anything else.

Recrawling

Crawling is not a one-off event. Google's How Search Works site explains that its crawlers “learn how often content they've seen before seems to change and revisit as needed.” Pages that change often tend to be revisited more often; pages that rarely change are revisited less. The Starter Guide adds that grouping similar topics in directories can help Google learn how often each directory changes on larger sites.

Pages Googlebot will not crawl

“However, Googlebot doesn't crawl all the pages it discovered. Some pages may be disallowed for crawling by the site owner, other pages may not be accessible without logging in to the site.” Google lists the common access problems as:

One distinction trips up many people: robots.txt controls crawling, not indexing. A URL blocked in robots.txt can still appear in the index without its content if other pages link to it. And a noindex rule on a blocked page is never seen, because Google never fetches the page to read it.

# robots.txt on example.com — stops crawling of /cart/, not indexing
User-agent: *
Disallow: /cart/

<!-- in the page itself — stops indexing, but only if the page can be crawled -->
<meta name="robots" content="noindex">

Stage 3: Rendering

The raw HTML is often not the whole page. Google's documentation describes what happens next: “During the crawl, Google renders the page and runs any JavaScript it finds using a recent version of Chrome, similar to how your browser renders pages you visit.” And why it matters: “Rendering is important because websites often rely on JavaScript to bring content to the page, and without rendering Google might not see that content.”

Rendering needs the same resources a browser needs. The Starter Guide warns that if your site hides important components like CSS and JavaScript from Google, it might not understand your pages. Its practical advice: “To check how Google sees your page, use the URL Inspection Tool in Search Console.”

Two practical points:

Stage 4: Indexing

After crawling and rendering, Google tries to understand the page. Indexing includes processing the text and key tags and attributes, such as the <title> element and alt attributes, plus images and videos.

Duplicates and canonical selection

“During the indexing process, Google determines if a page is a duplicate of another page on the internet or canonical.” Google groups pages with similar content into a cluster and picks the most representative one. “The canonical is the page that may be shown in search results.” The other URLs in the cluster are alternates that may be served in specific contexts, for example to mobile users or to someone looking for that exact page.

Signals collected for later

Google also stores signals about the canonical page for the serving stage. “Some signals include the language of the page, the country the content is local to, and the usability of the page.”

What may not be indexed

Google is clear that this stage is selective: “Indexing isn't guaranteed; not every page that Google processes will be indexed.” The common reasons it gives:

Add to that the duplicate case: a URL that Google treats as an alternate of another canonical is not indexed on its own. That is normal and usually fine, as long as the canonical is the URL you want.

Stage 5: Serving and ranking

When someone types a query, Google searches its index for matching pages and returns the results it believes are the highest quality and most relevant. Two statements frame this stage: “Google doesn't accept payment to rank pages higher, and ranking is done programmatically.” And: “Relevancy is determined by hundreds of factors, which could include information such as the user's location, language, and device (desktop or phone).”

Google's How Search Works site groups the key signals into five areas:

Overview · Google's five key Search signals
Meaning

What the query is really asking: intent, spelling, synonyms.

Relevance

Whether the page contains information that answers that query.

Quality

Which relevant pages show expertise, authoritativeness and trustworthiness.

Usability

Whether the page is accessible and easy to use, for example on mobile.

Context

The searcher's location, past Search history and Search settings.

The five names are Google's own; the one-line explanations summarise its How Search Works page.

What Google says about each, in its own words:

The layout of the results page also changes with the query. Google's example: a search for bicycle repair shops will likely show local results and no image results, while a search for a modern bicycle is more likely to show images. Which features appear, including AI Overviews, is covered in the next lesson of this module.

Indexed but not visible

Search Console may say a page is indexed while you never see it in results. Google gives three reasons:

What Google does not do

A lot of bad advice comes from misunderstanding these limits. Google states each of them directly.

Changes are also not instant. The Starter Guide says: “Some changes might take effect in a few hours, others could take several months.” Its advice is to wait a few weeks before judging whether a change worked.

Where each stage shows up in Search Console

Every stage leaves a trace in Search Console. Knowing which report belongs to which stage turns a vague complaint (my page is not on Google) into a precise question.

Table · Pipeline stage → Search Console report
StageWhere to lookWhat it tells you
DiscoverySitemaps report; Page indexing status Discovered – currently not indexed; URL Inspection, Discovery sectionWhether Google read your sitemap, which URLs it knows but has not crawled yet, and which sitemap or referring page led to a URL
CrawlingCrawl stats report (Settings); robots.txt report (Settings); URL Inspection, Crawl sectionRequests over time, response codes, host problems, whether robots.txt was fetched and whether a URL is allowed
RenderingURL Inspection, live test (View tested page)Rendered HTML, screenshot, page resources that could not be loaded and JavaScript console messages
IndexingPage indexing report; URL Inspection, Indexing sectionIndexed and not indexed URLs with a reason for each, such as Crawled – currently not indexed, plus the user-declared and Google-selected canonical
ServingPerformance report (Search results)Queries, pages, impressions, clicks, CTR and average position
Start in the row of the earliest stage that looks wrong; problems further right are often just a consequence.

A quick outside check is the site: operator, for example site:example.com/blog/. The Starter Guide suggests it to see whether Google has found your content at all. Treat it as a rough sign of presence, not as an index count; URL Inspection is the reliable answer for a single URL.

What can stop a page at each stage

When a page is missing from search, go down this list in order and stop at the first stage that fails.

Cheat sheet · Blockers per stage and the first check
StageWhat can stop the pageFirst check
DiscoveryNo internal links (orphan page), not in any sitemap, links only in forms or scripts Google cannot follow, sitemap with errorsURL Inspection: is the URL known? Sitemaps report: was the sitemap read?
Crawlingrobots.txt Disallow, 5xx errors or timeouts, network or DNS problems, login wall, a slow server that reduces crawl raterobots.txt report, Crawl stats response codes, URL Inspection live test
RenderingCSS or JavaScript blocked in robots.txt, script errors, content that only appears after user interaction, different content for the crawler's locationLive test: compare the screenshot and rendered HTML with what users see
Indexingnoindex in a meta tag or X-Robots-Tag header, low-quality or thin content, URL treated as a duplicate of another canonical, design that makes the content hard to processPage indexing report reason; Google-selected canonical in URL Inspection
ServingContent not relevant to the queries you expect, low quality compared with competing pages, robots meta rules that prevent serving, poor usabilityPerformance report: does the page get impressions, and for which queries?
The first failing stage is the one to fix; later symptoms usually disappear with it.

See where your pages stop in the pipeline

OurSEO Tools crawls up to 1,000 pages and records the status code, canonical, indexability and load time of every URL, alongside a 69-point checklist that covers indexation, rendering and internal linking.

69-point checklistTechnical crawlContent analysis

Common mistakes

Where this course goes deeper

This lesson is the map; each stage has its own lessons later in the course:

StageLessons that go deeper
DiscoveryXML sitemaps; Internal linking and orphan pages; Structure from keywords: hubs and depth
Crawlingrobots.txt and AI crawlers; Crawl budget; Server log analysis; Status codes, soft 404, 410; Redirects and site migrations
RenderingJavaScript SEO and rendering; Mobile-first indexing
IndexingMeta robots and X-Robots-Tag; Canonical tags; Duplicate URLs; Crawled vs Discovered – currently not indexed; Page indexing report: every status
Serving and rankingClassic results, AI Overviews, AI Mode, Discover; Ranking systems, core updates and spam policies; Search intent and SERP analysis; Helpful content in practice; E-E-A-T: the four pillars; Core Web Vitals: LCP, INP, CLS
Measuring all stagesSetting up Search Console; Performance report: filters, regex, comparisons; Why traffic dropped: a diagnostic method

FAQ

How long does it take Google to find and index a new page?

There is no fixed time. A page linked from your home page or a busy hub is usually found sooner than an orphan listed only in a sitemap. Google itself says changes can take anywhere from a few hours to several months.

Does Google crawl every page on my site?

No. Googlebot decides algorithmically which sites to crawl, how often and how many pages to fetch, and it skips pages blocked by robots.txt or hidden behind a login.

Can I pay Google to crawl or rank my site more?

No. Google does not accept payment for crawling, indexing or rankings. Buying ads gets you a labelled ad, not a better organic position.

Why is my page crawled but not indexed?

Usually because of quality, a noindex rule, or because Google sees it as a duplicate of another canonical. The Page indexing report gives the reason for each URL.

Is a sitemap required to get indexed?

No. Google primarily finds pages through links. A sitemap is useful, especially for large or new sites, but it does not replace internal links.

How do I check how Google sees one page?

Use URL Inspection in Search Console. It shows whether the URL is known, crawled and indexed, which canonical Google picked, and with a live test, the rendered HTML and a screenshot.

Sources

Quotes checked against the official pages on 30 October 2026.