Google indexing is the processing stage in which Google analyzes a fetched page, evaluates its content and signals, groups duplicate representations, and may store a canonical representation in its index. An indexed page is eligible to appear in Search, but indexing does not guarantee ranking or traffic. Use this hub to move from discovery and crawling to the correct evidence workflow.
What are crawling, indexing and serving?
| Stage | Question it answers | Evidence to inspect |
|---|---|---|
| Discovery | How could Google learn that the URL exists? | Internal links, sitemap declarations and known referring pages |
| Crawling | Could Googlebot request and fetch a representation? | Recorded crawl, live fetch, response, robots access and host status |
| Rendering | What main content and directives were available after processing? | Rendered HTML, resources, visible content and robots directives |
| Indexing/canonicalization | Which representation, if any, was selected for storage? | Page Indexing status, user-declared canonical and Google-selected canonical |
| Serving | Could the indexed representation be selected for a particular query? | Query-dependent Search performance; indexing alone is insufficient |
Start with crawling versus indexing versus ranking when these stages are being treated as one outcome. For the complete sequence, read how Google indexing works from discovery to serving.
Which evidence source should you use?
| Question | Best available route | Important boundary |
|---|---|---|
| What does “indexed” mean? | Indexing definition and state model | Indexed does not mean guaranteed to rank |
| What did Google record for my URL? | URL Inspection workflow | Requires access to the relevant property |
| How is the property behaving overall? | Search Console indexing guide | Report examples are not a complete export of every affected URL |
| Can the official API submit this page type? | Google Indexing API eligibility | A notification is not an indexing verdict |
| Why is a page not indexed? | Indexing Problems diagnostic hub | The same symptom can have different causes |
| What was observed for a third-party backlink? | Bulk public index observation | External observation is not private Search Console data |
How does Google discover a URL?
A URL needs a discoverable path before it can be crawled. Useful discovery declarations include crawlable internal links and canonical URLs in an XML sitemap. A sitemap helps Google discover preferred URLs but does not guarantee crawling or indexing. Follow the sitemap submission and validation workflow when a property’s important URLs are missing from discovery evidence.
What does a successful fetch prove?
A successful live fetch establishes that the tested representation was accessible under the conditions of that test. It does not prove that Google has already replaced an older crawl record, selected the same canonical, stored the page, or will serve it for a query. Keep the current test and recorded indexing state as separate observations.
Google’s How Search Works documentation describes crawling, indexing and serving as related but distinct processing stages. The Page Indexing documentation explains that important canonical pages are the ones expected to be indexed, while duplicate or alternate URLs may correctly remain outside the index. Documentation last checked: August 2, 2026.
How should a site owner measure index coverage?
- Define the eligible cohort: the canonical URLs that should be indexable.
- Remove redirects, intentional duplicates, noindex pages and unavailable checks from the eligible denominator where the reporting definition requires it.
- Record the measurement date and evidence source.
- Separate indexed canonical pages from excluded, duplicate, unavailable and unresolved outcomes.
- Compare like-for-like cohorts over time instead of dividing arbitrary Search Console totals.
This denominator-first approach prevents utility URLs and expected duplicates from making a healthy site look broken. The IndexVero measurement methodology documents the corresponding exact, alternate/canonical, not-observed and unavailable classes for public observations.
How should backlink providers use this knowledge?
For a provider or seller, the source page usually belongs to a third party. Use this evidence chain:
delivered URL → reachable final page → expected link present → dated public index observation → later recheck
Do not translate a missing external observation into “Crawled – currently not indexed,” “Soft 404,” or another private property status. If the source cannot be fetched, report it as unavailable. If an alternate URL is observed, preserve it separately from the submitted URL. Campaign processing remains a separate action from observation.
What should you do next?
- If the URL has no reliable discovery path, inspect internal links and the sitemap.
- If fetching fails, use the server/access and robots branches in the Indexing Problems hub.
- If Google selected another representation, inspect the canonical cluster.
- If the page is indexed but does not rank, stop treating indexing as the remaining diagnosis.
FAQ
Is crawling the same as indexing?
No. Crawling retrieves a representation; indexing is later processing and possible storage of a canonical representation.
Does an indexed page automatically rank?
No. Indexing makes a representation eligible for Search. Serving and ranking depend on the query and other systems.
Can a sitemap force indexing?
No. It declares preferred URLs for discovery. Google still determines crawling, canonicalization and indexing.
Can providers use Search Console reasons for third-party backlinks?
Only when they have authorized access to the relevant property. Otherwise report dated public observations and their limits.