What is indexing in SEO?

Indexing is the stage in which Google analyses page content and may store information about it in its search index. It follows fetching and is separate from serving a result for a particular query. Google’s Search overview distinguishes crawling, indexing and serving results, with URL discovery within the crawling stage.

Publishing a page does not guarantee any of those outcomes. For a page missing from search, establish its actual state before deciding whether to change content, navigation or a technical setting.

Indexing and ranking answer different questions

“Has Google indexed this page?” concerns its place in the search index. “Does it appear for this customer’s query?” also involves the query and the serving decision. An indexed page is not guaranteed to appear for every relevant search.

A useful audit identifies which URLs are intended search destinations. A moved address, an intentionally excluded confirmation page and a current service page should not all have the same expected status. Treating every non-indexed URL as an error can lead to removing a deliberate exclusion or undoing a correct move.

How a URL becomes a possible search result

  1. Discovery. Google learns that the address exists, for example through a link or a sitemap.
  2. Crawling. It may fetch the URL when access and serving conditions allow.
  3. Indexing. It processes the content and metadata, considers duplicates and canonical selection, and may store the information.
  4. Serving. It selects information relevant to a user’s search.

This is a reading aid for Google’s documented process, not a guaranteed sequence completed for every submitted URL. Canonicalization also matters: several addresses can represent substantially similar content without all being separate search destinations.

Rendering is part of the technical investigation

Google’s JavaScript SEO guidance explains crawling, rendering and indexing. When the initial HTML lacks the main content, rendering can be needed to see it. Providing useful content in the initial HTML helps access, but it does not guarantee indexing or eliminate every processing delay.

Read the indexing reason before choosing a fix

Selected states, not an exhaustive list of Search Console reasons
Observed reasonWhat it tells youUseful next check
Discovered, currently not indexedThe URL is known but has not yet been crawled.Review discovery context and serving availability.
Crawled, currently not indexedIt was fetched but is not indexed.Inspect the page and its context; do not infer a word-count diagnosis.
URL marked noindexAn exclusion instruction was encountered.Confirm whether exclusion was intended.
Page with redirectThe inspected address redirects elsewhere.Inspect the intended destination separately.
Duplicate or canonical-selection reasonAnother representative URL may have been selected.Compare the pages and canonical details.
Blocked by robots.txtCrawl access is restricted.Check the applicable rule and the desired outcome.

The Page indexing report provides the exact reason descriptions. “Crawled, currently not indexed” is an observation, not proof that a page is thin. Google also says that reason does not require repeatedly resubmitting the URL for crawling.

Illustrative investigations for different page states

A new menu page that has not been fetched

A restaurant checks the exact menu URL, confirms that it is public and links to it from relevant navigation. The owner also inspects the sitemap entry and serving response. These checks address discovery and access; they do not establish that an added link will produce indexing by a particular day.

A service page with an unintended exclusion

The owner finds a noindex header on a page that should be a search destination. They identify which template or delivery layer supplies it, correct that setting, and inspect the resulting response. They then compare the change with Google’s later observation. Removing the rule makes consideration possible; it does not complete Google’s indexing decision.

A moved article

The old address redirects to the current article. Inspect both addresses and confirm that the destination contains the intended information. The old URL’s redirect state can be correct even if the destination needs a separate investigation. None of these examples describes a measured customer outcome.

Crawling is a fetch. Indexability describes whether the observed technical conditions allow a page to be considered. Indexing is the actual inclusion decision. A successful HTTP response or live inspection addresses part of the process, not its whole outcome.

Use robots.txt to understand crawl access and noindex to understand search exclusion. A block that prevents Google reading a new exclusion instruction is not evidence that the URL has disappeared from search.

Investigate one intended search destination

  1. Identify the exact address. Record the URL and whether it should be indexed, excluded or redirected.
  2. Inspect the stored observation. In authorised Search Console access, note the indexing details, selected canonical and last crawl information.
  3. Inspect current output. Compare the response status, content, robots instructions and relevant resources with the stored observation.
  4. Check discovery. Confirm useful navigation and the correct sitemap entry without inventing an internal-link quota.
  5. Correct the identified issue. Keep the change recoverable and record the setting or content that changed.
  6. Observe again. Allow for the difference between a fresh deployment and Google’s earlier view before attributing a result.

Google’s sitemap guidance describes a discovery aid, not an indexing guarantee. Its recrawl guidance says repeated requests for the same URL do not make it crawl faster. Requesting indexing is not a processing deadline.

Do not mistake a live test for an indexed result

The URL Inspection documentation separates Google’s stored view from a live test. The live test does not evaluate every indexing condition, including some duplicate and canonical questions. A successful result cannot guarantee inclusion.

A site: query is also not a complete index inventory. Google’s operator documentation says results can omit indexed URLs. Use the query as a clue, then inspect the exact URL and the applicable reason.

Do not rewrite to a word-count target simply because a page is not indexed. Identify the missing explanation or inaccurate content first. A longer article that repeats the same information does not resolve a crawl block, an unintended exclusion or a different selected canonical.

How long should I wait before taking action?

There is no universal indexing deadline. If inspection identifies an unintended exclusion or a serving failure, investigate that issue rather than waiting for a promised indexing date. If the page is accessible and still awaiting a decision, keep the observations and review its purpose and content. Repeated submission is not a way to accelerate crawling.

Sources and editorial note

Official Google references are linked beside the relevant explanations and were checked on October 12, 2026. AI assisted this revision. Scenarios are illustrative, not customer cases. No private Search Console property, indexing experiment, customer gain or named expert approval was tested. The existing publication date remains, with its historical provenance unresolved.