How Google Indexing Works (and How to Check If a Page Is Indexed)

TL;DR: Indexing means Google has analyzed a page and stored it in its index, making the page eligible to appear in search results. It does not mean the page ranks. Check a specific URL with Google Search Console’s URL Inspection tool, identify the reported exclusion or canonical status, and fix that cause instead of repeatedly clicking “Request Indexing.”

What does indexing mean?

Indexing is the stage where Google analyzes a web page and stores information about it in the Google index. Think of the index as a library catalog for web pages. If your page is absent from that catalog, Google cannot select it as a normal search result.

An indexed page is therefore eligible to appear in Google. It is not guaranteed to appear, and it is certainly not guaranteed to appear on page one.

This distinction prevents a surprising amount of wasted work. A founder searches for a newly published article, cannot find it, and assumes Google has not indexed it. The page may be indexed perfectly well but rank too low for that query. Rewriting robots.txt will not solve a ranking problem (and may create an indexing problem if done carelessly).

Google’s documentation on how Search works separates the process into crawling, indexing, and serving. It also makes the uncomfortable limitation explicit:

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

That is the central rule. A valid sitemap, clean technical setup, and successful live test make a page accessible to Google; they do not create an indexing entitlement. Google still decides whether the page deserves space in its index and whether it deserves to appear for a search.

The three gates between publishing and ranking

1. Crawling: Google fetches the page

Googlebot discovers new and updated URLs by revisiting known pages, following links, and reading sitemaps. It then downloads resources such as text, images, and video.

Google also renders pages and runs JavaScript using a recent version of Chrome. JavaScript-dependent content is not automatically invisible, but rendering introduces another processing step. Server errors, network failures, and robots.txt restrictions can prevent Google from fetching what a browser appears to show normally.

A URL can be discovered without being crawled. Google may know it from a sitemap or an internal link while still not having downloaded the page itself. Search Console can report that state as Discovered, currently not indexed.

2. Indexing: Google processes and stores the page

After crawling, Google analyzes the page’s text, title element, image alt attributes, images, and video. It can also identify signals such as language and usability.

This is where duplicate handling becomes important. Google groups similar pages and chooses a canonical version: the representative URL it considers eligible to appear in results. Your declared canonical is a signal, not an order. Search Console may show that Google selected another URL if your redirects, internal links, sitemap, or content send conflicting signals.

Indexing is therefore more than downloading HTML. The practical question is whether Google stored this URL, consolidated it into another URL, or declined to index it. There is little value in discussing “Google understanding the page” until you know which of those three things happened.

Google states that “Indexing isn't guaranteed; not every page that Google processes will be indexed.” Its documentation identifies low content quality, noindex directives, and site designs that make processing difficult as possible reasons.

3. Serving: Google chooses a result for a query

When someone searches, Google selects results from the index. Relevance, location, language, and device are among the factors that can affect what is served.

Indexing gets a page into the candidate pool. Ranking determines whether it beats the other candidates for an actual query. Ahrefs found that 96.55% of pages in its roughly 14-billion-page study received no traffic from Google. That is a traffic statistic, not an indexing statistic, but it illustrates the gap: being indexed is the floor, not the result.

I have misdiagnosed this myself by treating missing visibility as failed indexation because a page did not appear for the search I happened to run. The correction is unglamorous. Inspect the URL first. Do not infer its index status from one keyword.

How to check if a page is indexed

Use URL Inspection for the reliable answer

Open Google Search Console, choose the correct property, and paste the complete URL into the URL Inspection field. Check the precise protocol, hostname, path, and trailing-slash version you want Google to index.

That precision was not academic during SEOJuice’s migration from seojuice.io to seojuice.com in January 2026. The old-domain URL and new-domain URL represented separate records, with their own crawl and canonical information. Inspecting “roughly the right page” is not enough during a migration (I caught myself doing exactly that more than once).

Google’s URL Inspection documentation says the tool reports information directly from the Google index. Its headline outcomes include:

• URL is on Google: the URL is indexed.
• URL is not on Google: the URL is not indexed.
• URL is on Google, but has issues: the URL is indexed, but Google has identified warnings.

Expand the details rather than stopping at the headline. Check the last crawl, crawl permission, indexing permission, user-declared canonical, and Google-selected canonical. If Google chose another canonical, the inspected URL may not appear even though its content is represented under a different address.

Two caveats matter. First, the report reflects the last indexed version, not necessarily the page currently live on your server. Second, “URL is on Google” does not guarantee that it will appear for a particular query because URL Inspection does not evaluate every serving condition.

Test Live URL performs a fresh Googlebot fetch. It can tell you whether Google can access the current page, but Google says that the test does not update the index. A passed live test means crawlable now, not indexed now. Small distinction. Big debugging consequence.

Use site: as a quick check, not an index audit

You can search Google for site:example.com/page-url. If the URL appears, that is a useful initial signal. If it does not appear, do not immediately conclude that the page is excluded.

Google says the site: operator “doesn't necessarily return all the URLs that are indexed under the prefix specified in the query.” Its own recommendation is to use URL Inspection when a specific URL is absent.

I still use site: because it takes five seconds (sometimes a five-second check is all I need). I would not use it for a migration audit, a client indexation report, or a decision to delete content.

How to interpret the two confusing “currently not indexed” statuses

Discovered, currently not indexed

This means Google found the URL but has not crawled it. Google’s Page indexing documentation says it typically wanted to crawl the page but expected doing so could overload the site, so the crawl was rescheduled.

The operative word is discovered. Google knows the address, perhaps through a sitemap or link, but has not downloaded the current page. Rewriting the article may eventually help its value, but it does not resolve the immediate fetch stage because Google has not seen that rewrite yet.

Start by checking internal discovery, sitemap inclusion, server reliability, and wasteful URL patterns. From what Lida and I see across smaller sites running SEOJuice, weak internal discovery is a far more productive first investigation than crawl-budget theory: an orphan article exists in a sitemap, but no relevant page treats it as important enough to link to. That is an observed pattern, not a universal diagnosis.

Do not default to “crawl budget” for a site with a few hundred pages. Google says active crawl-budget management is mainly relevant to very large sites, including sites with about one million or more unique pages or more than 10,000 pages changing daily. Our guide to crawl budget optimization explains when that diagnosis is warranted and when it is a distraction.

Crawled, currently not indexed

This status means Google fetched the page but did not index it. Google says the page may or may not be indexed later and that there is no need to resubmit it for crawling.

Access worked. Google received the page. The next inspection should focus on distinct value, duplication, canonical selection, and how the page fits into the rest of the site.

John Mueller, Google Search Advocate, has directly connected site quality with how much Google indexes. As reported by Search Engine Journal, Mueller said, “If our systems are seriously worried about the quality of the website, they will reduce the number of pages in the index.” Discussing the two “currently not indexed” states, he added that Google’s systems are effectively saying they know about the URL and, “once we're happy, we will take another look.”

This does not mean every excluded page received a secret quality score of zero. Search Console does not provide that level of diagnosis (I wish it did). It means technical accessibility alone may not solve a pattern of thin, repetitive, or weakly connected pages.

Discovered means not fetched yet. Crawled means fetched but not stored, at least for now. “Currently” matters: neither status is necessarily permanent.

Why a page is not indexed, and what to change

Do not confuse robots.txt with noindex

Robots.txt controls crawling. A noindex directive controls indexing. They are related, but they are not interchangeable.

If robots.txt prevents Google from fetching a page, Google may not see a noindex directive inside that page. Google also explains that a blocked URL can still be indexed without its content if it is discovered through links. If a page must stay out of the index, use Google’s documented noindex method while allowing Google to crawl and read the directive.

SEOJuice has a robots.txt generator for creating the syntax. Review every rule against the paths you actually want crawled; one overbroad disallow can affect thousands of pages (that calculation gets unpleasant quickly).

Canonical and redirect problems

“Alternate page with proper canonical tag” is often an expected exclusion, not an error. If print, filtered, tracking-parameter, HTTP, and HTTPS versions resolve to one preferred URL, you do not need every variation indexed. A lower exclusion count is not automatically a healthier site.

If the excluded URL should be canonical, make its signals consistent. Use an appropriate self-referencing canonical, point internal links and sitemap entries to the preferred URL, and ensure the page is meaningfully distinct. If an old URL has been permanently replaced, redirect it rather than maintaining competing versions. Our guide to 301 vs 302 redirects covers the redirect choice.

Orphan pages and weak internal discovery

Google discovers URLs through links as well as sitemaps. A sitemap says that a URL exists; contextual internal links also show how it relates to the rest of the site and give Google another route to reach it.

Add links from relevant, already-indexed pages. Do not compensate by placing every URL in a giant footer. Internal-link quantity without topical context is usually just clutter. A deliberate structure is more useful, as explained in our guide to content silos for SEO.

For a small site, I would investigate orphaning before server capacity. Manually opening every article works once; it does not work as the site keeps growing. The SEOJuice internal-link finder helps identify internal-link opportunities and is available on the free plan without a credit card. Soft CTA, but also the tool we built because this job is painfully repetitive.

A practical indexing diagnostic sequence

1. Inspect the exact URL. Record its index status, last crawl, declared canonical, and Google-selected canonical.
2. Run Test Live URL. Confirm that Googlebot can currently fetch the page. Remember that this does not update the index.
3. Check indexability. Remove accidental noindex directives, allow necessary crawling, and verify the preferred canonical.
4. Check discovery. Include the URL in an XML sitemap and link to it from relevant, already-indexed pages.
5. Check duplication and value. If Google crawled but did not index the page, compare it with your other URLs. Consolidate near-duplicates or make the page materially more useful.
6. Request indexing once. Put the URL into Google’s crawl queue. Repeated submissions do not repair weak content, conflicting canonicals, or blocked crawling.
7. Recheck the status. Diagnose what Search Console reports next rather than treating every delay as the same failure.

Do not impose a universal 24-hour deadline. Search Engine Land reported Google Search Advocate John Mueller’s guidance that indexing new or updated content can take from “several hours to several weeks.” Mueller also warned that forcing indexing does not mean the page will be shown prominently in Search.

I trust the sequence above more than any precise indexing countdown. Site history, internal discovery, technical access, duplication, content quality, and Google’s scheduling all vary. If someone promises an exact average without a transparent dataset, I would be cautious (or at least ask what their sample contained).

Frequently Asked Questions

What does “indexed” mean on Google?

Indexed means Google has processed a page and stored it in the Google index, making it eligible to appear in search results. It does not mean the page ranks for a specific keyword. Serving is the later stage where Google chooses indexed pages for a query.

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

John Mueller said indexing new or updated content can take from several hours to several weeks. There is no guaranteed timeline. A sitemap, useful internal links, and URL Inspection can improve discovery or put the URL into a crawl queue, but none forces Google to index it.

Why is my page “Crawled, currently not indexed”?

Google downloaded the page but did not store it in the index. Check whether the content is distinct and useful, whether Google selected another canonical, and whether relevant internal pages link to it. Google says the URL may be indexed later and does not need to be repeatedly resubmitted for crawling.

How do I get Google to index my page faster?

Submit an XML sitemap, add relevant internal links from known pages, verify that the URL is crawlable and indexable, and use URL Inspection’s Request Indexing option once. These steps improve discovery and accessibility, but Google does not promise an indexing deadline.

What is the difference between crawling and indexing?

Crawling means Googlebot downloaded the page. Indexing means Google processed and stored the page so it can become a search result. A crawled page is not automatically indexed, and an indexed page is not automatically ranked.

Does robots.txt stop a page from being indexed?

Not reliably. Robots.txt blocks crawling, not indexing. Google can sometimes index a blocked URL without understanding its content if links reveal that URL. To keep a crawlable page out of Google’s index, use a noindex directive that Googlebot is allowed to fetch and read.