Indexing
How to Check If a Page Is Indexed on Google (and When to Stop)
How to check if a page is indexed on Google with the site: operator, Search Console, and Screaming Frog, plus the accuracy limits that decide build-vs-buy.
You can check if a page is indexed on Google in about ten seconds. The hard part isn't the check: it's trusting the result, and noticing the day a page silently falls out of Google's index. This guide covers the three real methods SEOs use (site: operator, Google Search Console, Screaming Frog), what each one is actually accurate for, and the honest build-vs-buy line where manual checking stops being enough.
No fluff on "what is indexing." If you're here, you already know.
The fastest way to check if a page is indexed
To check if a page is indexed on Google, search site: followed by the full URL, for example site:example.com/pricing. If the page appears in the results, it's indexed. If nothing shows up, it isn't. For a definitive answer, paste the same URL into the URL Inspection Tool in Google Search Console, which queries Google's index directly.
That's the 90-second version. Now the part the quick guides skip: how much you can trust each method.
Method 1: the Google site: operator (fast, but approximate)
The site: operator is the reflex move, and it's genuinely useful for a one-page yes/no. Type site:yourdomain.com/page into Google; a result means the page is in the index.
Where it breaks is precision. Google's John Mueller has stated plainly that "a site: query is not meant to be complete, nor used for diagnostics purposes." The operator samples the index and shows an approximate count: the "About 1,240 results" number is an estimate, not an audit. So site:yourdomain.com is the wrong tool for "exactly how many of my pages are indexed," even though people use it that way constantly. Treat it as a smoke test, not a source of truth, and move to Search Console when the answer matters.
Method 2: Google Search Console (the source of truth, with a lag)
The URL Inspection Tool is the most reliable single-page check available, because it reads Google's actual index rather than sampling the SERP. Enter a URL and it reports whether the page is indexed, when Googlebot last crawled it, the canonical Google chose, and any coverage problems.
For site-wide totals, the Page Indexing report (under Indexing → Pages) buckets your URLs into indexed and not-indexed with reasons like "Crawled – currently not indexed" or "Discovered – currently not indexed." It's authoritative, but it has two limits worth respecting: it covers one verified property at a time, and the data typically lags real index status by a few days. By the time a dropped page shows up in the report, it may have been gone for most of a week. (We unpack the most common stuck state in why pages get crawled but not indexed.)
Method 3: Screaming Frog (scale, with a caveat)
Screaming Frog is the desktop crawler most technical SEOs already own, and it scales the check far past one URL. But there's a distinction that trips people up: a default crawl reports indexability, not indexation. The "Indexability" column tells you whether a page is crawlable and not blocked by noindex, robots.txt, or a canonical: what Googlebot could index, not what it did.
To get real index status, connect the Google Search Console URL Inspection API (Config → API Access → Google Search Console → enable URL Inspection). Screaming Frog then pulls live index data alongside the crawl, and surfaces problem URLs under the "Indexable URL Not Indexed" filter: pages you meant to rank that Google left out. The catch: the API is capped at roughly 2,000 URLs per property per day, and it's still a manual, point-in-time desktop crawl. You run it, you read it, you close the laptop. Nothing watches the URLs after that.
The honest comparison: where each method actually fits
Each tool is good at something. None of them does everything, and the gaps line up neatly:
| Capability | site: operator |
Screaming Frog + GSC API | Search Console UI | Scheduled monitoring |
|---|---|---|---|---|
| Exact index status | Approximate | Yes | Yes | Yes |
| Scales past a handful of URLs | No | ~2,000/day | Sampled | Yes |
| Point-in-time vs continuous | Point-in-time | Point-in-time | Lagged snapshot | Continuous |
| Alerts when a page drops | No | No | No | Yes |
| Cost | Free | Tool license | Free | Subscription |
The pattern is clear. The site: operator and Screaming Frog answer "is it indexed right now?" well enough. Not one of them answers "tell me the moment it stops being indexed." That's not a flaw in the tools: it's just outside what a search operator or a manual crawler is built to do.
If you only manage a handful of pages and check them by hand, the free tools are the right call: stop reading and go run a site: query. The build-vs-buy line shows up when you have more URLs than you'll honestly re-check on a schedule. (Our how to monitor index status at scale guide walks through that workflow in depth.)
The gap all three methods share: nobody tells you when it drops
Here's the failure mode that catches even careful SEOs. A page is indexed when you check it on Monday. A content edit, a Google update, or a quality reassessment quietly drops it on Thursday. The site: operator won't tell you: you'd have to think to re-run it. Screaming Frog won't: you'd have to launch another crawl. Search Console will, eventually, a few days later. By then the traffic is already gone.
Manual checking has no memory and no heartbeat. Monitoring does. A scheduled tool re-checks every URL on a cadence you set, keeps a history so you can see when status changed, and pushes a deindexing alert the moment a page falls out, so you find out from a notification, not a panicked look at Analytics three weeks later.
So do you actually need a tool?
Be honest about your situation:
- A few pages, checked occasionally → the
site:operator and Search Console are plenty. Don't buy anything. - Hundreds of URLs, or revenue tied to staying indexed → manual point-in-time checks will eventually miss a drop, because nobody re-runs them forever.
- You want history and alerts, not snapshots → that's monitoring, and it's the one job none of the free methods do.
SearchOptimo is the boring, reliable version of that monitoring layer: campaigns of URLs, automatic re-checks, retained history, bulk index checking, and alerts on drop. It's deliberately positioned as a Google Search Console alternative for the one thing GSC doesn't do: watch your URLs continuously and tell you the instant something changes.
If you're weighing the trade-off, see whether SearchOptimo is worth it for your case, or just start free and watch your own URLs (100 URLs/month, no card) before you decide to pay for anything.
Frequently asked questions
- Is the site: operator accurate for checking if a page is indexed?
- Not reliably. Google's John Mueller has said a site: query 'is not meant to be complete, nor used for diagnostics purposes.' It samples results and gives approximate counts, so it's fine for a quick yes/no on one page but wrong for exact index status or totals.
- Can Screaming Frog tell me if a page is indexed by Google?
- Yes, when you connect the Google Search Console URL Inspection API. Screaming Frog's own crawl only reports whether a page is indexable (crawlable, not blocked), not whether Google actually indexed it. The API adds real index status but is capped at about 2,000 URLs per property per day.
- How do you check if a page is indexed online?
- Two quick ways. Open Google Search Console and click the Pages report under Indexing to see which pages are indexed and which aren't, or run the URL Inspection Tool on a single URL for a direct read of Google's index. Faster still, type site: followed by the page URL into Google: if it appears in the results, it's indexed. The Search Console methods are the most reliable because they query Google's index directly rather than sampling the SERP.
- How long does it take Google to index a new page?
- Usually a day or two to a couple of weeks, though it can stretch to a month or more for new or low-authority sites. If a page still isn't indexed after that, check it in the Search Console URL Inspection Tool: it will tell you whether Google has discovered, crawled, or skipped the URL, rather than leaving you to guess from a site: query.
- Why didn't I notice my page was deindexed?
- Because manual checks are point-in-time. The site: operator, Screaming Frog, and even Search Console only tell you status at the moment you look. A page can drop out the next day, and you won't know until traffic falls, unless something re-checks on a schedule and alerts you.
Monitor your index status automatically
SearchOptimo re-checks your URLs on a schedule and alerts you when something drops. Start free — no credit card.
Start freeKeep reading
Indexing
"Discovered – Currently Not Indexed"? Fix or Wait [Tree]
Discovered – currently not indexed means Google found your URL but hasn't crawled it. Use this decision tree to know when to wait, fix crawl issues, or prune.
Indexing
"Crawled – Currently Not Indexed": What It Means and How to Fix It
Google crawled your page but left it out of the index. Here's what that status actually means, the real reasons it happens, and a practical fix checklist.
Indexing
How to Check If Multiple URLs Are Indexed (Free, Fast)
Check if multiple URLs are indexed at once, free, no 5-URL cap. Compare bulk checkers vs GSC, then monitor pages so you catch deindexing fast.