How to Check If a Page Is Indexed by Google

The only authoritative way to verify whether Google has indexed a web page is using the URL Inspection tool inside Google Search Console. While public search operators like site: provide rough approximations that fluctuate constantly, URL Inspection queries Google’s internal index database directly. It reveals the exact crawl timestamp, indexation state, and canonical URL selected by Google’s indexing systems.

The only authoritative method

Website owners frequently rely on third-party ranking tools, scraping software, or browser search queries to determine whether their content is indexed. These secondary methods observe external search engine results pages, which reflect filtered, personalized, and sampled projections rather than database realities. A page may be completely indexed inside Google’s database but fail to appear for a specific user query due to geographic filters or safe-search settings.

The URL Inspection tool inside Google Search Console bypasses all external presentation filters. Because Google Search Console connects directly to Google’s primary indexing database, the inspection interface displays the actual system record for that URL. It confirms whether the address is stored in the inverted index, identifies the crawler user-agent that fetched it, and reports whether any canonicalization rules altered its serving status.

To inspect a URL, log into Google Search Console, select your verified domain property, and paste the full destination URL into the top search bar. Within seconds, the tool queries Google’s indexing infrastructure and returns a comprehensive status dashboard. If the tool displays the green confirmation badge stating “URL is on Google,” the document is officially stored in the index.

Reading the URL Inspection result field by field

The URL Inspection report is divided into several technical data cards that disclose exactly how Googlebot evaluated the page during its most recent visit. Interpreting these fields correctly allows developers to pinpoint indexing blockers with precision. The table below explains each data field displayed in the report:

The distinction between user-declared canonical and Google-selected canonical is one of the most critical diagnostic indicators in the report. If your declared canonical URL does not match Google’s selected canonical, Google treats the inspected address as an unindexed duplicate. All ranking credit, anchor signals, and search impressions are transferred to Google’s chosen URL. You can study how canonical selection operates in our guide to the search engine indexing pipeline.

Live test versus indexed version

The URL Inspection tool features two distinct diagnostic views that serve opposing operational functions: the cached indexed view and the live test view. Understanding the difference between these two states prevents engineers from misdiagnosing recently resolved technical issues.

When you first inspect a URL, Google Search Console presents the cached indexed record. This screen displays what Googlebot observed during its last recorded crawl, which may have occurred hours, days, or weeks prior. If you updated a canonical tag, removed a noindex directive, or fixed a server error yesterday, the indexed view will still report the old error until Googlebot schedules and completes a fresh crawl.

To evaluate your live server response, click the “Test Live URL” button in the upper-right corner of the interface. This command initiates an on-demand HTTP request, dispatching a live headless browser to fetch and render the page in real time. The live test checks whether your current server configuration returns a valid status code, verifies structured data syntax, and renders page resources cleanly.

+-------------------------------------------------------------------+
| INDEXED VERSION (Default)   | LIVE TEST VERSION (Button)          |
+-------------------------------------------------------------------+
| Historical database record  | Real-time on-demand HTTP fetch      |
| Shows last crawl date       | Shows current server configuration  |
| Decides current SERP state  | Previews next crawl outcome         |
| Cannot be updated instantly | Executes in 30 seconds              |
+-------------------------------------------------------------------+

If the live test reports that the URL is eligible for indexation, you can click “Request Indexing” to queue the address for prioritized recrawling. This manual submission bypasses normal crawl queue intervals, encouraging Googlebot to fetch the updated page promptly.

The site: operator, and why the number is wrong

The most common method beginners use to check indexing is typing site:example.com/page into Google search. While this query operator is convenient, using it to audit indexation yields unreliable, misleading conclusions. The public search interface is engineered for query serving performance, not database auditing.

The primary flaw of the site: operator is result estimation. When you execute a broad search like site:example.com, the number displayed at the top of the search results page represents an approximate statistical projection generated by distributed query servers. It does not perform a precise count of index records. If you navigate to page five of the results, the estimated count often drops or fluctuates wildly because the query server recalculates its projection across different cache tiers.

Furthermore, search engines filter search results pages based on personalization, query relevance, and duplicate clustering. If Google considers five URLs on your domain substantially similar, it may collapse them under a single representative result, hiding the others from the site: operator view. Those hidden pages remain fully indexed in the database, but Google’s search algorithms suppress them to preserve searcher diversity.

The site: operator remains useful for basic sanity checks, such as confirming whether a newly migrated brand name returns any results at all. However, it should never be used as a definitive measurement of site-wide indexation. For accurate diagnostics, rely exclusively on first-party reporting platforms like Search Console.

Checking many URLs at once

Inspecting URLs individually through the search bar is practical for single articles, but inspecting an e-commerce catalog or enterprise publishing site requires automated bulk workflows. Google Search Console provides three methods to evaluate indexation across thousands of documents simultaneously.

The first method is the Page Indexing report inside Google Search Console. This report aggregates your entire domain into two primary categories: “Indexed” and “Not indexed”. Clicking into the report reveals detailed sub-reports that group unindexed pages by specific technical failure reasons, such as 404 errors, redirect loops, or noindex tags. You can review how diagnostic tools track these coverage metrics in our guide to search engine diagnostic tools.

The second method is using sitemap-scoped coverage filters. Rather than viewing site-wide metrics that include legacy redirects and parameter URLs, select your submitted XML sitemap from the dropdown filter at the top of the Page Indexing report. This view isolates your declared canonical URLs, revealing exactly how many of your preferred pages are successfully indexed versus excluded.

The third method is using the Google Search Console URL Inspection API. The API allows developers to submit programmatic inspection requests for up to two thousand URLs per day per property. You can integrate the API with desktop crawlers like Screaming Frog or custom Python scripts to automate daily index verification across your most important landing pages.

What the statuses mean and what to do about each

The Page Indexing report categorizes excluded URLs into standardized technical buckets. Understanding the exact mechanical trigger behind each status allows teams to apply targeted technical fixes rather than guessing at causes. The table below details the most common indexing exclusions:

The status “Crawled - currently not indexed” represents the most frequent quality hurdle for modern websites. Unlike technical errors that return broken status codes, this state confirms that your server responded perfectly and Googlebot read your code. Google simply decided that the document did not provide sufficient unique value to justify storage costs in its index.

Checking Bing

While Google dominates global search volume, auditing your index presence on Microsoft Bing is essential for capturing desktop and enterprise search traffic. Microsoft provides Bing Webmaster Tools, an authoritative first-party portal that mirrors Google Search Console’s diagnostic capabilities.

Bing Webmaster Tools features a dedicated URL Inspection tool located in the left navigation sidebar. Pasting a URL into this tool returns real-time indexing status, last crawl dates, discovered structured data, and code rendering snapshots captured by Bingbot. Bing also provides an explicit Indexing report that tracks discovered URLs and index coverage over time.

Additionally, Bing supports the IndexNow protocol, an open standard that allows websites to notify participating search engines instantly whenever content is published, updated, or deleted. Submitting URLs through IndexNow bypasses standard crawler discovery delays, accelerating indexation across Bing, Yandex, and participating search engines.

Third-party index checkers: what they can and cannot know

A thriving ecosystem of commercial SEO tools and browser extensions advertise automated index checking capabilities. Understanding the technological boundaries of these third-party platforms prevents site owners from acting on inaccurate diagnostic data.

Third-party index checkers cannot query private search engine index databases. Because Google and Microsoft do not allow external software to query their internal index shards directly, third-party checkers simulate user searches. They execute automated headless browser queries using site: search operators or quoted URL searches, scraping the resulting search pages to see if your link appears.

Because these services rely on automated scraping, their findings inherit all the inaccuracies of the public search interface. A third-party tool may report a page as deindexed simply because Google’s bot protection blocked the scraper, or because search results personalized the layout. While third-party tools provide convenient competitive rank tracking, they cannot replace first-party data. Authoritative index verification always requires Google Search Console and Bing Webmaster Tools.

Frequently asked questions

What is the fastest way to check if a page is indexed?

The fastest authoritative method is pasting the complete URL into the Google Search Console search bar to run URL Inspection. The tool queries Google internal database immediately and returns a definitive status card stating whether the address is currently indexed on Google or excluded.

Why does site: show a different number every time?

The site: search operator does not perform an exhaustive database count. Instead, Google search serving clusters execute a fast statistical estimation across distributed index shards to return a quick query approximation. Navigating through pages of results forces the query engine to recalculate this estimate, causing totals to fluctuate.

My page is indexed but does not rank. Why?

Indexing and ranking are completely separate pipeline phases. Indexing simply means Google parsed your text and stored it in an inverted index. Ranking requires your content to defeat competing documents based on topical relevance, search intent satisfaction, content quality, and domain authority signals during live query scoring.

What does “URL is not on Google” mean?

This status indicates that the URL is not currently stored in Google search index and cannot appear in search results. It may occur because Googlebot has not discovered the URL, blocked it via robots.txt, encountered an error during fetching, or evaluated the content as duplicate or low-quality.

Can I check indexing without Search Console?

You can check public indexing by searching the exact URL string or unique title text in Google search, or by executing a site: query for that specific address. However, these public checks are secondary indicators; only Google Search Console provides direct telemetry on crawl dates and canonical assignments.

How often does the Page Indexing report update?

The Page Indexing report in Google Search Console updates every few days rather than in real time. Because Google aggregates crawl logs and indexing databases across billions of URLs, data visible in coverage reports typically reflects the state of your website from two to three days prior.

Why does Google show a different canonical than mine?

Google treats user-declared canonical tags as suggestions rather than strict commands. If your declared canonical URL has poor internal linking, redirects elsewhere, differs substantially in content, or serves conflicting mobile versions, Google indexing algorithms will override your tag and select an alternative URL as the authoritative version.

Does an indexed page always appear in search results?

An indexed page is stored in Google database, but it is not guaranteed to appear for every search. Google filters results based on geographic location, searcher query relevance, safesearch filters, and duplicate document clustering. If a query matches millions of stronger candidates, an indexed page may not be displayed.