How to Check If a Page Is Indexed on Google

A page that isn't indexed cannot rank, cannot get traffic, and cannot earn a single click, no matter how good it is. The frustrating part is that an unindexed page looks completely normal to a visitor. Here is how to check whether a page is actually in Google's index, the fastest methods to the most authoritative, and why the answer can quietly change after you stop looking.

Deltio watches the indexing signals on your client sites every day and alerts you on Slack when a page stops being indexable. From £20 a month.

Indexed is not the same as crawled or ranking

Before checking, it helps to be clear on what "indexed" means, because three different things get muddled together.

• Crawled means Google's bot has fetched the page.
• Indexed means Google has processed the page and stored it as eligible to appear in search results.
• Ranking means the page is actually showing up for queries, ideally near the top.

A page can be crawled but not indexed. A page can be indexed but rank nowhere useful. When you check "is this page indexed?", you are asking the middle question: is this page even eligible to appear at all? If the answer is no, nothing else you do to it matters until you fix that.

Method 1: a site search (fast and rough)

The quickest gut check is to search Google for site: followed by the exact URL, for example site:example.com/your-page. If the page comes back, it is indexed. If nothing comes back, it probably is not, though this method is a rough signal rather than a guarantee. It is perfect for a five-second check on a single page, and useless for understanding why a page is missing.

Method 2: URL Inspection in Search Console (authoritative)

Google Search Console's URL Inspection tool is the definitive answer for a single page. Paste the URL, and it tells you plainly whether the page is on Google, and if it is not, why. It will name the reason: "Excluded by noindex tag," "Blocked by robots.txt," "Alternate page with proper canonical tag," "Crawled, currently not indexed," "Discovered, currently not indexed," and so on. This is the tool to reach for when a page should be indexed and isn't, because it turns a mystery into a named cause. The tradeoff is that it is one URL at a time.

Method 3: the Pages report for the whole site (bulk)

For the portfolio view, the Pages report in Search Console (sometimes called the Indexing or Coverage report) groups every URL Google knows about by status: indexed, or not indexed with the specific reason. This is where you spot patterns, a whole section excluded by a canonical, a batch of pages "Discovered, currently not indexed," a template that quietly went noindex. It is the best single screen for understanding indexing health across a site, though it updates on Google's schedule, not yours.

Method 4: a crawler for the blocking signals

A crawler like Screaming Frog fetches every page and reports the signals that decide indexing: the meta robots tag, the X-Robots-Tag header, the canonical, and the robots.txt rules. It will not tell you what Google has actually indexed, but it will tell you whether a page is even allowed to be, which is often the faster route to the cause. Great for a full sweep; it is a manual job you have to remember to run.

Why a page might not be indexed

When a page you care about is missing, the reason is usually one of these:

• A noindex tag, in the meta tag or the HTTP header. We cover this in depth in the noindex tag, explained.
• Blocked in robots.txt, so Google never crawls it. See how to check your robots.txt.
• A canonical pointing elsewhere, telling Google another URL is the real version, so this one is dropped in its favour.
• Not discovered yet, because nothing links to it and it isn't in the sitemap.
• Judged thin or duplicate, shown as "Crawled, currently not indexed," where Google saw the page and chose not to keep it.

The first three are technical and fixable in minutes once you know they are there. The trick is knowing.

The catch: indexing is not a one-time check

Here is the part that undoes most manual checking. You can confirm a page is indexed today, close the tab, and be completely wrong about it next week. A plugin update adds a noindex. A migration copies a staging robots.txt to production. A CMS change points the canonical at the wrong URL. The page was indexed when you checked and isn't now, and nothing tells you.

That is the difference between checking and monitoring. Checking answers "is this page indexed right now?" Monitoring answers "did anything just change that will drop this page?" and pushes the answer to you.

How Deltio keeps this from surprising you

Deltio checks the pages in your sitemap on a daily cycle and reads the exact signals that decide indexing: the noindex meta tag and header, the canonical, robots.txt, and whether URLs are still present in the sitemap. When a page that was indexable yesterday stops being so today, you get a plain alert on Slack naming the page and the site. Across a portfolio of client sites you do not control, that turns indexing from something you have to remember to audit into something you are simply told about. If you want to see how these alerts are scoped, read SEO change alerts.

The short version

To check one page fast, use a site: search; to know for certain and why, use URL Inspection; for the whole site, use the Pages report; to see the blocking signals directly, run a crawler. Then remember that any answer you get is only true for that moment. On sites you are responsible for, the answer worth having is the one that reaches you the day it changes.

Add your first client site, connect Slack, and Deltio starts watching the same day. Start your 14-day trial and stop finding out from the traffic graph.