Visual semantics

What Is Cost of Retrieval?

Cost of retrieval is the computing a search engine spends to crawl, render, segment and evaluate a page, and fewer, cleaner pages cost less and reach the ranking stages that matter.

Cost of retrieval, illustrated
Cost of retrieval as five stages: crawl, render, segment, evaluate with cheap signals, and a shortlist where expensive rerankers run

Cost of retrieval is the compute a search engine spends to understand a page, from the first fetch to the final evaluation.

The work runs in stages: the crawler fetches the HTML, the renderer executes scripts and builds the DOM, the segmenter splits the page into blocks and the extractor pulls the primary content.

Koray Tuğberk Gübür put cost of retrieval in the denominator of his topical authority formula. Cost of retrieval is not a term in any published Google document. The verified part is narrower: Google runs cheap signals on many pages and expensive models on few.

How does Google's shortlist turn cost of retrieval into a gate?

Google runs cheap signals on many documents and expensive rerankers on a shortlist, so a page that fails early is never read in depth.

Pandu Nayak's testimony in the DOJ trial describes the funnel. Core topicality, PageRank and localization signals take tens of thousands of documents down to a shortlist, and new pages without clicks are judged on topicality first.

RankBrain, by the same testimony, looks at the top 20 or 30 documents only, because it costs more than some other ranking components. Depth of content matters after that point, not before.

Google's filing on its generative search describes summarizing a handful of documents per query and names saving compute as one reason to return a standard results page.

What do cheap first-pass signals read on a page?

A cheap pass reads the title, the H1, the first characters after the H1, the first blocks, the heading skeleton and the rendered dimensions.

A title written as the query matches on the first read, and a heading skeleton that names entities lets passages score without a full reading. A page that hides its entity until the fourth paragraph pays for a deeper read it rarely receives.

Contextless labels such as Share, Print, Updated, Read time and Tags inside the content area add tokens with no entity, and across a thousand pages they become thousands of tokens of noise. One template fix cleans every page.

The Content Warehouse API leak shows Google storing a page's rendered dimensions and DOM. A render without layout shift keeps those block positions consistent between crawls.

How do rendering and DOM size raise cost of retrieval?

Every script that builds primary content after load, and every empty node around it, adds work before the page is read.

Primary content belongs in the initial HTML response. Content that appears only after a click, scroll or hover is unsafe for the first pass, while tabbed content passes when it sits in the DOM on load.

Render-blocking resources in the head delay everything below them. Third-party scripts, inline SVG bloat, base64 images and large inline scripts raise file size. Empty spacer divs render as blocks with no content, and Google's layout-aware encoder patent lists padding as one of its block types. Lean markup with shallow nesting costs less to parse and render.

How does page count change cost of retrieval?

Page count is a cost, because every URL is crawled, rendered and evaluated, and pages without a distinct intent add cost without adding coverage.

Google's ranking systems guide states that deduplication hides very similar pages and shows only the most relevant, so two near-duplicates earn one listing while the site pays to crawl and evaluate both.

The same guide states that site diversity generally limits a site to two listings in the top results. A third page on the same query competes with the site's own two listings and adds cost without a listing.

Query deserves a page decides page, section or sentence for each query variation, and cost of retrieval is the reason that decision matters. A dental clinic with one page per treatment and one per staffed office costs less than one with a page per suburb.

When does pruning lower cost of retrieval?

Pruning lowers cost when a page's intent has no distinct results page type, or when the page sits too close to a sibling.

The audit reads every indexable URL against the live results for its query. A page whose query returns the same results page type as a sibling's merges into that sibling, and a page with no demand and no distinct entity folds into a section.

Search Console statuses mark candidates. Crawled, currently not indexed means Google fetched the page and declined it; Discovered, currently not indexed means Google knows the URL and has not crawled it.

Merges redirect to the surviving page, which absorbs anything unique. We ship one structural change per cycle and judge it after a full crawl cycle.

Questions about cost of retrieval

Is cost of retrieval the same as page speed?
No. Page speed and Core Web Vitals measure how fast a page loads for a person; cost of retrieval covers the compute to fetch, render, segment and understand it. A fast page with a script-built main component still costs a lot to understand.
Is there a size limit for a page's HTML?
A 2 MB limit has been claimed in published case material. We have not verified it against Google's documentation, so we do not quote it. Lean HTML is the rule regardless of the exact limit.
Does a large site automatically carry a high cost of retrieval?
No. Cost is judged against what the pages return. A large site where every page answers a distinct intent carries its size; a small site with ten near-duplicates carries more waste per page.
How is cost of retrieval measured?
No single metric exists. The proxies are crawl stats in Search Console, raw HTML compared with rendered HTML, and DOM node counts per template, and each proxy points at the template where the fix lands.
Does moving a section to a subdomain lower cost of retrieval?
No. Google states that subdomains are generally treated as the same site, and site-wide classifiers still apply. A subdomain isolates measurement and leaves the crawl and render cost unchanged.
Does cost of retrieval matter for a single-page site?
Yes, at the page level. A single-page site with a script-built main component pays the full render cost on its only URL.
Which platform has the lowest cost of retrieval?
None by default. WordPress, Shopify and Next.js all output lean or heavy HTML depending on theme, plugins and rendering mode, so the rendered output decides the cost.
Does removing pages hurt topical coverage?
No, when the removed pages held no distinct intent. Coverage counts intents answered, not URLs, and a merged page carries the merged content as a section.
Does longer content raise cost of retrieval?
Length raises cost when it adds tokens without facts. Google's layout-aware encoder patent describes truncating each block at a maximum token length, and a 2026 study on LLM rerankers found readability padding ranked worse than no added text.
How often is cost of retrieval reviewed?
Cost of retrieval is reviewed every 90 days, per template, from crawl stats and rendered output. A template change between reviews gets its own check after release.
Who fixes cost of retrieval issues, SEO or development?
Both, split by layer. The audit names the template, the block and the cause; development ships the rendering, markup and script fixes, and the strategist decides the merges and prunes.
Book a callWhatsApp