How to Check If a Page Is Indexed on Google: 5 Methods Compared (2026)

The URL Inspection tool in Google Search Console is the authoritative way to check if a page is indexed: it returns Google's own verdict for the exact URL, the canonical Google selected, and the last crawl date. Every other method — site: searches, the Pages report, bulk checker tools, traffic signals — trades some of that accuracy for speed or scale.

The trade matters because the authoritative method has hard limits: it works only on verified properties you own, one URL at a time. Checking a client site without access, five hundred URLs at once, or backlinks pointing at you from domains you will never verify requires the other four methods. This guide compares all five — how each works, what its answer proves, and where it fails — and ends with a decision table matching each situation to its best method.

TL;DR — Quick Summary

• URL Inspection gives the authoritative per-URL verdict — but only for your own verified properties, one URL at a time
• The site: operator is the fastest check and works on any domain, but its results are an estimate: absence does not prove a page is unindexed
• The Pages report shows indexed versus not-indexed for your whole site, with the reason behind every exclusion
• Bulk index checkers cover what Search Console cannot: many URLs at once, and URLs on domains you don't own — backlinks above all
• Impressions and organic referrals confirm indexing indirectly — good for monitoring, useless for proving a page is missing
• A "not indexed" answer splits into two states with different fixes: never crawled versus crawled and declined

---

Method 1: The "site:" Search Operator

A site: search restricts Google results to one domain or one URL: site:example.com lists pages Google returns for the domain, and the exact-URL form site:example.com/page checks a single page. It is the fastest possible check — no account, no setup, and it works on any domain, including domains you don't own.

How to run it: paste site: plus the full URL into Google with no space between them: site:example.com/blog/post-name. A result for that exact URL means the page is in Google's search index — search results are served from the index, not the live web, so appearing in any result requires index membership.

Why it is unreliable as a final answer:

• Results are an estimate. Google assembles site: output as a sample, not an inventory — the operator exists for triage, and its result count is not your indexed-page count.
• Absence proves nothing. site: output omits indexed pages under URL variants — trailing slash, parameters, www — and filters results it considers redundant, so pages that URL Inspection confirms as indexed still come back empty.
• Presence can overstate health. A page can appear in site: results while on its way out of the index through an upcoming quality re-evaluation.

Use site: as the ten-second triage, and treat only URL Inspection as the verdict.

---

Method 2: The URL Inspection Tool in Google Search Console

The URL Inspection tool returns Google's own record for a URL: a "URL is on Google" or "URL is not on Google" verdict, the Google-selected canonical, the last crawl date, and how the URL was discovered. It is the only method whose answer is Google stating its index contents directly.

How to run it:

1. Open your property in Google Search Console
2. Paste the full URL into the search bar at the top
3. Read the verdict — "URL is on Google" means indexed and eligible to appear in results
4. Expand the Page indexing panel for the selected canonical, the last crawl date, and the referring sitemap or page
5. Click Test live URL to compare the indexed snapshot against the page as it exists right now

The detail fields answer the follow-up questions the verdict raises: a Google-selected canonical that differs from your URL explains why this exact address is absent from results, and the last crawl date tells you whether your latest changes have even been fetched yet.

The limits: the tool works only on properties you have verified — you cannot inspect a URL on someone else's domain — and it inspects one URL at a time, which makes it exact and unscalable in equal measure.

---

Method 3: The Pages Report in Google Search Console

The Pages report (Indexing → Pages) is the bulk view of your own site: a count of indexed pages over time, plus a "Why pages aren't indexed" table listing every exclusion reason with its URL list. It is where per-URL checking turns into site-level diagnosis.

How to read it:

1. Open Indexing → Pages in Search Console
2. Check the indexed count and its trend — a falling line signals deindexing; a flat line while you publish signals new pages are not being accepted
3. Scroll to "Why pages aren't indexed" and sort the reasons by page count
4. Click any reason to see its URLs, and export the list for the ones you intend to fix

Two states dominate most exclusion tables, and they split cleanly by pipeline stage: "Discovered - Currently Not Crawled" means Google knows the URL but has never fetched it — a crawl-side problem — while "Crawled - Currently Not Indexed" means Google fetched the page, evaluated it, and declined it — a quality-side problem. Each linked guide covers the causes and fixes for its state.

The report's constraint is freshness: its data carries a processing delay of 2–3 days, so it shows where your site was earlier this week, not this minute. For a URL you changed today, URL Inspection is current and the Pages report is not.

---

Method 4: Bulk Index Checker Tools

Bulk index checkers answer the two questions Search Console cannot: whether URLs on domains you don't own are indexed, and whether hundreds of URLs are indexed without inspecting them one at a time. Backlink checking is the defining case — a backlink passes value only after Google indexes the page it sits on, and you can never verify someone else's domain in Search Console to check it there.

Checking up to 50 URLs in the browser: the free Google Index Checker automates site: checks for a list. Paste up to 50 URLs, one per line, and the tool opens a Google site: search for each URL in its own tab, spaced with a delay to avoid rate limiting. A result in a tab means that URL is indexed; "No results found" means it is not. The checks run entirely in your browser, with no account required.

Checking unlimited URLs from the desktop: the Free Google Index Checker page ships IndexCheck, a free, open-source desktop app for Windows and Linux. It imports URLs from paste, CSV, or a sitemap, runs unlimited bulk checks, and exports the results. Its Search Console mode uses your own Google credentials to validate index status against your verified properties — bulk scale with URL Inspection-grade accuracy for the sites you own. The export of unindexed URLs is the input for the fix step: submission.

---

Method 5: Indirect Signals — Impressions and Referral Traffic

Impressions and organic referrals prove indexing as a by-product: a URL that records an impression in the Search Console Performance report appeared in results, and appearing in results requires being in the index. Google-organic sessions in your analytics tool carry the same implication.

How to use them:

1. Open the Performance report, switch to the Pages tab, and filter for the URL — any impression count above zero confirms the page is indexed
2. In your analytics tool, segment sessions by Google organic source and check whether the URL receives entrances

The logic runs in one direction only. Zero impressions is not evidence of non-indexing: an indexed page that ranks for no query records no impressions, and both data sources lag by days. That one-way property makes indirect signals a monitoring layer — a portfolio-wide pulse that flags when indexed content stops appearing — and disqualifies them as verification for any single URL.

---

Which Method Should You Use? Decision Table

Match the method to the situation: ownership decides whether Search Console is available, URL count decides whether per-URL tools scale, and the stakes decide how authoritative the answer must be.

---

What Should You Do When the Page Is Not Indexed?

First identify which of the two not-indexed states applies, because their fixes do not overlap. Run the URL through URL Inspection — or find it in the Pages report — and read the reason Google gives:

• "Discovered - currently not indexed" — Google has never fetched the URL, so the fixes are crawl-side: internal links from frequently crawled pages, sitemap hygiene, server speed, and direct submission. Work through the guide to fixing "Discovered - Currently Not Crawled".
• "Crawled - currently not indexed" — Google fetched the page and declined it, so the fixes are quality-side: content depth, deduplication, stronger internal linking, and a re-crawl request after the improvements. Work through the guide to fixing "Crawled - Currently Not Indexed".

The mechanism behind both states — what happens between discovery and the index, and where each state sits in the pipeline — is covered in our pillar guide to how Google indexing works. The short version: search engine indexing is selective, Google indexes a subset of what it crawls, and the checking methods above only tell you which side of that selection your page landed on — the fix content tells you how to change it.

---

Frequently Asked Questions

Is the site: operator a reliable way to check indexing?

It is reliable in one direction. A site:example.com/page result proves the page is in Google's index; an empty result proves nothing, because site: output is an estimate that omits indexed URL variants and filtered results. Confirm every empty site: result with URL Inspection before treating the page as unindexed.

How do you check if backlinks are indexed?

With site: checks or a bulk index checker — backlinks live on domains you cannot verify in Search Console, so URL Inspection and the Pages report are unavailable. Paste the backlink URLs into the Google Index Checker for batches up to 50, or run unlimited checks in the IndexCheck desktop app and export the unindexed list.

Why does Search Console say "URL is on Google" but the page gets no traffic?

Because indexed means eligible, not ranking. Ranking is computed per query at serving time, and an indexed page that wins no query records no impressions. The page has passed the indexing pipeline; visibility now depends on relevance, content quality, and links.

Can a page be indexed today and gone next month?

Yes. Pages leave the index through noindex directives, 404/410 responses, redirects, canonical consolidation, and quality re-evaluation. One-time checks decay for exactly this reason: verify important URLs after publishing, then let Performance-report impressions act as the continuous monitor that flags drops.