How to Check If a Page Is Indexed on Google

To check if a page is indexed on Google, paste its URL into the URL Inspection tool in Search Console, or run a quick site: search for a rough answer. If the page isn't indexed, it can't rank or get organic traffic, however good it is, and it still looks completely normal to anyone visiting it.

Below are four ways to check, from the fastest to the most thorough, plus the reasons a page usually drops out and why a check you ran last month may no longer be true.

Crawled, indexed and ranking are three different states

These words get used interchangeably, and that causes confusion when you read Search Console.

Crawled means Googlebot has fetched the page. Indexed means Google processed it and stored it as eligible to appear in results. Ranking means it actually shows up for searches. Each step depends on the one before, but none guarantees the next. A page can be crawled and never indexed, and an indexed page can rank on page nine.

When you ask whether a page is indexed, you're asking about the middle step. If the answer is no, content and link work on that page won't help until the indexing problem is solved.

Method 1: the site: operator

Search Google for site: followed by the URL, for example site:example.com/pricing/. A result means the page is almost certainly indexed. No result means it probably isn't.

It's a five-second test and nothing more. The operator is not a complete view of the index, it sometimes omits pages that are indexed, and it tells you nothing about why a page is missing. Use it for a quick sanity check, not a diagnosis.

Method 2: URL Inspection in Search Console

For a single URL, this is the authoritative answer. Open the property in Google Search Console, paste the full URL into the inspection bar at the top, and read the verdict: "URL is on Google" or "URL is not on Google".

The useful part is the detail underneath. Under Page indexing you'll see whether crawling was allowed, whether indexing was allowed, the last crawl date, the user-declared canonical and the Google-selected canonical. If the page is excluded, the reason is named, for example:

• Excluded by 'noindex' tag
• Blocked by robots.txt
• Alternate page with proper canonical tag
• Crawled - currently not indexed
• Discovered - currently not indexed

"Test live URL" fetches the page as it is right now, which helps after a fix, since the main report shows the version from Google's last crawl. Once the problem is resolved, "Request indexing" asks Google to recrawl, though it doesn't guarantee inclusion. The limit is that it works one URL at a time, and only for properties you've verified.

Method 3: the Pages report

For a whole site, go to Indexing, then Pages, in Search Console. The chart splits known URLs into indexed and not indexed, and the table below groups non-indexed URLs by reason. Click a reason to see example URLs.

This is where patterns show. A single "Excluded by 'noindex' tag" URL may be deliberate. Three hundred of them appearing in the same week points at a template. The report is also where you'll notice a whole section sitting in "Discovered - currently not indexed". Its drawback is timing: data refreshes on Google's schedule and typically lags by several days. If you see a row that needs work, our guide to fixing index coverage errors in GSC goes through each status.

Method 4: a crawler for the blocking signals

Screaming Frog, Sitebulb and similar crawlers can't tell you what Google has indexed. They can tell you whether each page is allowed to be indexed, by reporting the meta robots tag, the X-Robots-Tag HTTP header, the canonical, and whether robots.txt blocks the URL. On a site with thousands of pages, that's often the fastest way to find the cause behind a group of exclusions.

The catch is that it's a manual run. It shows the state on the day you crawl.

Common reasons a page isn't indexed

A noindex directive is the first thing to rule out. It can sit in the HTML as <meta name="robots" content="noindex"> or arrive as an X-Robots-Tag: noindex response header, which is invisible in page source. The noindex tag, explained covers both.

A robots.txt Disallow stops Google fetching the page. Oddly, a blocked page can still be indexed without its content if other sites link to it, so blocking is not a reliable way to remove a URL. See how to check your robots.txt.

A canonical pointing at another URL tells Google this page is a copy, so the other URL is indexed instead.

Discovery is the quieter problem: nothing links to the page and it isn't in the XML sitemap, so Google hasn't found it or hasn't prioritised it. And "Crawled - currently not indexed" means Google fetched the page and decided not to keep it, often because it looks thin or too similar to another page.

The first three are configuration issues you can usually fix in minutes. The last two take content and linking work.

Why one check isn't enough

An indexing check tells you the state on the day you ran it. After that, a plugin update can add a noindex, a migration can copy a staging robots.txt with Disallow: / to production, or a CMS change can point canonicals at the wrong host. The page was indexed when you looked and isn't now, and Search Console shows it only after Google recrawls and the report refreshes.

On one site you manage closely, repeating the checks now and then is workable. Across a portfolio of client sites where other people deploy, it isn't. Deltio checks the pages in each sitemap on a daily cycle, reads the noindex tag and header, the canonical and robots.txt, notices URLs removed from the sitemap, and sends a Slack or email alert naming the site and the affected pages when something changes compared with the previous check. It reports that a page stopped being indexable, not what Google has done about it yet, so URL Inspection is still the place to confirm the outcome. SEO change alerts explains which changes are worth alerting on.

If you'd like that running on your own sites, you can start a 14-day trial.