How to Check If a Page Is Indexed on Google
After you publish, a page exists in two worlds at once. It is live on your server, where you control everything about it. And it may or may not be in Google’s index, where you control nothing. Those are separate facts, and only the second one produces traffic. This guide covers how to check if a website is indexed: four methods, what each can actually tell you, and the traps in reading the results.
The check is worth doing properly because everything downstream depends on it. A page that is not indexed earns no impressions, no clicks, and no credit for the links pointing at it. If a page is underperforming, indexing status is the first thing to verify, before you touch the content, the links, or anything else covered in the full guide to Google indexing. Google’s own documentation on how Search works is blunt about the sequence: a page is crawled, then possibly indexed, then possibly served. Checking tells you how far along that sequence your page actually got.
Method 1: the site: search
The fastest check requires nothing but a browser. Search Google for site:example.com/your-page, using the full URL of the page in question. If the page comes back as a result, it is indexed. You can also run site:example.com on its own to browse what Google returns for the whole domain.
The catch is in the negative case. The site: operator is a search filter, not a lookup into the index itself. A page that appears is genuinely indexed, but a page that does not appear is not necessarily absent from the index. The operator abbreviates, omits, and reshuffles, especially on larger sites. Treat a positive result as reliable and an empty result as a reason to check properly, not as a verdict.
There is a second trap: the operator says nothing about ranking. A page can be indexed and still sit far beyond any position that earns clicks. Indexed means eligible, nothing more.
Method 2: the URL Inspection tool
For a single URL, the authoritative answer lives in Google Search Console. The URL Inspection tool reports whether a specific URL is on Google, when it was last crawled, which URL Google chose as canonical, and what blocked indexing if anything did.
This is the strongest evidence available, because it comes from the same system that made the decision. Its limits are practical ones. You need a verified Search Console property, which means proving ownership of the site, so you cannot inspect a domain you do not control. It handles one URL at a time, which makes it tedious past a handful of pages. And the indexed version it describes can trail the live page, so a page you updated this morning may be reported as it stood last week.
Method 3: the Page indexing report
Where URL Inspection answers for one page, the Page indexing report in Search Console answers for the whole site. It splits your known URLs into indexed and not indexed, and groups the excluded pages by reason: noindex, redirect, duplicate, crawled but not indexed, discovered but not crawled, and the rest.
This is the right tool for spotting patterns. If four hundred product pages share the same exclusion reason, that is one problem, not four hundred. Its weakness is timing: the report refreshes on Google’s schedule, not yours, and it says nothing about pages Google has not discovered at all. It is a census, taken periodically, of the URLs Google already knows about.
How to check if a website is indexed without Search Console
All three methods above either scale badly or require ownership proof. That leaves a gap: checking many URLs, or URLs on a site you cannot verify, such as pages that link to you. Index checkers fill it by querying live Google results for each URL and recording what comes back. The trustworthy ones show their evidence; the buyer’s guide to index checker tools covers how to tell the difference.
This is also where AIndexify sits. You paste URLs or upload a CSV, and each URL is checked against live Google results on a fixed schedule over the following days, with no Search Console connection or ownership proof required. Each check records what Google returned on that date, so the answer you get is “indexed as of the 14th” or “not indexed as of the 14th”, rather than a tick that merely means the URL was received.
Reading the answer
Whichever method you use, three distinctions keep the result honest.
Submitted is not indexed. Handing a URL to Google, through a sitemap, a request, or a pipeline, is a request, and its success says nothing about the outcome. The two are separate events, and the gap between them is where most confusion lives; the difference costs you money if you read the first event as the second.
Indexed is not permanent. Google revisits its decisions. A page indexed in March can quietly drop out in June, which is why a check is a snapshot with a date on it, not a property of the page. Anything you rely on deserves rechecking, not a single verdict filed away.
Absent has many causes. “Not indexed” is a symptom with a dozen possible diagnoses, from a stray noindex tag to thin content to a canonical pointing elsewhere. The check tells you where you stand; it does not tell you why. The why is its own investigation.
A sensible routine
For one page, run the site: check first because it costs nothing, then confirm through URL Inspection if the result is empty or the stakes are high. For a site you own, read the Page indexing report monthly and after every large release. For volume, or for pages outside your Search Console, use a checker that queries live results and stamps a date on what it finds.
However you check, insist on evidence over inference. A green tick means whatever the tool decided it means; a dated observation of Google’s results means exactly one thing. If you want the second kind of answer for your own pages, submit your URLs and see where they actually stand.