Loading…
Every URL in your sitemap, checked against Google's index in one run. The same verdicts Search Console gives you, without pasting URLs one at a time.
Google's limit per property. It is charged to your account, so you never queue behind other people using this page.
The checker reads indexing data straight from Google's URL Inspection API, so the verdicts are the same ones you see inside Search Console. That means it only works on properties you have already verified.
Read only access. We never store your Google token, and we cannot change anything in your account.
Two of these read almost identically and need opposite fixes. That is the single most expensive misreading in technical SEO.
At 2,000 inspections per property per day, site size decides everything. This is why the checker sorts newest first and gives you a URL filter: on a large site you are choosing which 2,000 pages are worth today's quota.
One legitimate way to double it. A domain property and a URL prefix property for the same site each carry their own 2,000 per day.
You should, and this reads the identical data from the identical API. What changes is throughput.
| Search Console | This page | |
|---|---|---|
| URLs per run | One at a time | Your whole sitemap |
| Freshness | Report lags by days | Live, on request |
| Export | Capped at 1,000 rows | Full CSV |
| Ordering | Not sortable by publish date | Newest published first |
Paste the page URL into Search Console's URL Inspection tool, or run this checker to test every URL in your sitemap at once. Both read the same source: Google's URL Inspection API. A verdict of PASS means the page is in the index and can appear in search results.
Google allows 2,000 URL inspections per property per day, and 600 per minute. That quota belongs to your Search Console property, not to this tool, so you are never queuing behind other people. A site with more than 2,000 URLs takes several days for a full pass, which is why the checker orders by newest first.
Google fetched the page, evaluated it, and decided not to index it. It is almost never a technical fault. The usual causes are thin or duplicated content, a page that closely resembles others on the site, or weak internal linking that signals the page is not important. Improving the page itself is the fix, not resubmitting it.
Discovered means Google found the URL but has not fetched it yet. Google's own definition is specific about why: it wanted to crawl the URL but expected that to overload the site, so it rescheduled the crawl. That points at server capacity and response times, not at the crawl budget explanation usually given. Crawled means Google did fetch the page and chose not to index it, which points at content. The two look almost identical in reports and need opposite fixes.
No. Google's URL Inspection API only returns data for properties the signed-in account has verified in Search Console. Tools that claim to check any site are scraping search results with the site: operator, which is unreliable and does not return complete index data.
No. The access token stays in your browser tab for the session and is sent with each request so we can call Google on your behalf. We never write it to disk, we never ask for a refresh token, and closing the tab discards it. The permission requested is read only, so nothing in your Search Console can be changed.
Internal linking, crawl paths, duplication at scale, or rendering Google never sees. We do technical SEO and GEO work on exactly this.