Check if your pages are indexed
Paste your URLs and check them with the site: operator — no API key, no daily limit. Batch-safe against the CAPTCHA, and you see the live SERP as a searcher does.
Opening several search tabs at once is exactly what pop-up blockers stop. One click confirms you’re set before you paste a long list.
Walk your open tabs and mark each one. Anything you mark CAPTCHA goes back in the queue — solve it in the tab, then hit Retry CAPTCHA to reopen just those.
No saved lists yet. Name a list and hit Save, or park the not-indexed ones and re-check them next week.
Ctrl+Enter to open the next batch · Ctrl+S to save the list · Alt+R to reset
Built for the way SEOs actually check indexing
See the real SERP, not a verdict
An index-checking API returns yes or no. Opening the search shows you the page as a searcher meets it — the title Google chose, the description it wrote, and whether your schema earned a rich result.
No API key, no daily limit
The tool opens searches in your own tabs, so you are just searching Google yourself. Nothing is metered, nothing expires, and there is no quota to top up mid-audit.
Batches that dodge the CAPTCHA
Open 10–15 at a time instead of firing a hundred searches in a burst. The batch size, the delay between tabs and a resume cursor are all yours to steer, so a long list stays survivable.
Retry only what got blocked
When a CAPTCHA does land, mark those URLs and reopen just them. No re-running the whole list and no losing your place — the ones you already read stay read.
Walk away with a CSV
Mark each URL indexed or not as you go and export the lot — URL, query, verdict, engine and date. That is the client deliverable, not a screenshot of forty tabs.
Your list stays yours
No backend and no uploads. URLs, marks and progress live in your browser's local storage — which also means a refresh mid-audit costs you nothing.
How it works
-
1
Paste your URLs
One per line, or separated by commas or spaces. The tool builds a
site:query for each and shows you the first one, so you can see exactly what will be searched. -
2
Open a batch
Ten by default. The tabs open with a small gap between them; you read each SERP and mark it indexed, not indexed, or CAPTCHA.
-
3
Retry, then export
Solve any CAPTCHA and reopen just those URLs. When the list is done, export a CSV of every verdict.
Tips & detailed help
Why 10–15 and not 50
Google rate-limits the search results, not your site. A burst of searches from one IP reads as automation and you get a CAPTCHA — sometimes on most of the tabs at once, which is worse than useless, because you then solve fifteen puzzles to read fifteen results. Ten to fifteen per batch, with a half-second gap, is the range that stays quiet in practice. Above 15 the tool warns you; it won't stop you.
A CAPTCHA is not a penalty
It says nothing about your pages, your site's health, or your rankings. It means Google wants to know you're a person. Solve it in the tab and the result is right there behind it. Mark those URLs CAPTCHA, solve them, then Retry CAPTCHA reopens exactly that subset. If it keeps happening, drop the batch size and raise the delay.
Park the not-indexed and come back
Indexing is a moving target, so the useful list is never the one you just pasted — it's the pages that didn't show up. Save the not-indexed ones as a named list and re-run it next week to see which have landed. Same for anything a CAPTCHA blocked: park it, load it back, and check it properly. Saved lists live in your browser, so they're there next time you open the tool.
Why not just use Search Console?
Use both — they answer different questions. Search Console is the official record, but Coverage and URL Inspection lag, so a page indexed this morning can still read as missing this afternoon. That lag is the whole reason this method exists: site: shows the live index right now. Search Console is the verdict on one URL; this is a fast read across forty.
Read the snippet while you're there
The tab is open — get more than a yes/no from it. Is Google using your title or rewriting it? Is the description the one you wrote, or scraped from the body? Did your FAQ or product schema actually earn a rich result? This is the part no index-checking API can give you, and it's often where the real finding is.
Pop-ups must be allowed
Opening a batch of tabs is precisely what a pop-up blocker exists to stop, so the first run may open one tab and silently drop the rest. The panel at the top of the tool tells you where you stand — hit Check pop-ups before pasting a long list. If a batch gets blocked partway, nothing is lost: allow pop-ups and carry on from where it stopped.
Frequently asked questions
Why does Google show a CAPTCHA when I check lots of URLs?
Firing many site: searches in a short burst from one IP looks automated to Google, so it asks you to prove you are human. It is not a penalty and it says nothing about your site — it is rate limiting on the search results, not on your pages. Solve it once and carry on. Opening a smaller batch and leaving a delay between tabs makes it happen less often.
How many URLs should I open at once?
Ten to fifteen is the sweet spot, which is why the tool defaults to 10 and flags anything above 15 as risky. Much beyond that and Google starts serving CAPTCHAs, so you spend more time solving them than reading results. There is no hard limit — the batch size is yours to set — but bigger batches are usually slower overall, not faster.
Is the site: operator the same as Google Search Console?
No, and they answer different questions. Search Console is authoritative but its Coverage and URL Inspection data lags, sometimes by days, so a page you published this morning can look missing when it is already indexed. A site: search reflects what is in the live index right now. Use site: for a fast read on many URLs, and Search Console when you need the official verdict on one.
Does a site: search show every page Google has indexed?
Not exactly — site: results are approximate rather than a guarantee. For a single URL, which is all this tool checks, it is dependable in practice: if site:example.com/page returns that page, it is indexed. If it returns nothing, that is strong evidence it is not, and worth confirming with Search Console's URL Inspection before you act on it.
Does this tool use an API, and are there daily limits?
There is no API and no limit. The tool builds the search URLs and opens them in your own tabs, so you are simply searching Google yourself, the way you would by hand. Nothing is metered and there is no key to buy. The only practical ceiling is the CAPTCHA, which is what the batch size is there to manage.
Why can't the tool read the results and mark them automatically?
A web page cannot read another site's search results — the browser's same-origin policy blocks it, and scraping Google from a page would break its terms anyway. Reading the tab yourself is the honest way to do it, and it has a real upside: you also see the title, description and any rich result exactly as a searcher would, which no index-checking API tells you.
Do my URLs leave my browser?
No. The tool is a single static page with no backend. Your list, your marks and your progress live in your browser's local storage and are never uploaded, logged or shared. You can check the network tab, or turn off your connection — the page keeps working offline right up until it opens a search tab.
Install Indexing Checker