Comparison · Official GSC API

CheckIndex.io vs IndexProbe: a yes/no on credits, or the official verdict with the reason

CheckIndex.io answers yes or no: the page is indexed, or it isn't, for one credit per check — without saying how that answer is obtained. IndexProbe asks Google's official API and reports the full record: the status, the non-indexing reason, the selected canonical, Googlebot's last visit. And recurring monitoring is part of the subscription, with no credit meter.

No commitmentNo credit card requiredSearch Console connected in 2 clicks
IndexProbe URLs table: official index status, non-indexing reason, Google-selected canonical and last crawl for each URL
The official verdict, field by field. IndexProbe view.

Their product

What CheckIndex.io does, described honestly

CheckIndex.io bundles three credit-based bricks: an index check with a binary verdict (1 credit per URL), an HTTP status checker with redirect chain and loop detection (1 credit per URL), and a URL submission service through external indexing providers (30 credits per URL, 150 on the priority queue). Around them: projects, sitemap imports that re-sync automatically, scheduled checks, alerts and a documented REST API. A coherent product, built around a one-bit answer: indexed, or not.

One point deserves to be stated calmly, because it is verifiable: their site and their API documentation, read in full, nowhere indicate how the indexing verdict is obtained. No Search Console connection appears anywhere in the product, and a URL's record is limited to: indexed yes/no, an HTTP code, a geo-restriction heuristic — which they themselves label “a heuristic, not a verified 200” — and the date of the last check.

This is not a transparency detail, it is a difference in kind: without property access, a tool can only observe an absence — your page doesn't show up in Google. It cannot read the decision — what Google concluded about that page, and why.

The split

Where the two models diverge: the reason, and the meter

Two gaps decide the choice. First: a yes/no opens an investigation, the official verdict closes it — “Crawled - currently not indexed”, Soft 404 or a reassigned canonical don't call for the same fix, and only the official API tells them apart. Second: at CheckIndex.io, every re-check consumes credits — the more you monitor, the more you pay; at IndexProbe, recurring analyses and alerts are part of the subscription.

The credit model has an arithmetic consequence worth facing squarely: monitoring 10,000 URLs every week consumes about 43,000 credits a month — their Pro pack at $79 a month, for yes/no answers. Monitoring becomes a cost line that grows with frequency, which mechanically pushes toward checking less often, or fewer pages.

IndexProbe takes the opposite stance: recurrence is the core of the product, not a consumption. A scheduled analysis re-runs over the whole list every week, suspected regressions are inspected first, and the email alert fires when a page leaves the index — with no meter counting anything down.

The value

What you get for your money

At every price point, the same subscription buys the full official record, monitoring without a meter, and an analysis layer a binary check cannot carry.

1

The full official record, not a boolean

For every URL: the exact status among the Search Console statuses, the reason when the page isn't indexed, the canonical Google actually selected versus the one you declare (with a difference badge), the date of Googlebot's last visit. That is the data that drives the fix, not just the observation.

2

Monitoring included, meter removed

Recurring analyses, email alerts, the side-by-side Comparison view, a history of 5 to 30 analyses per project depending on the plan: everything is in the subscription. Re-checking costs nothing extra, whatever the frequency.

3

An analysis layer above the verdicts

Segmentation generated by AI or hand-written (editable regex), status, noindex, robots.txt and canonical pies, statuses crossed by segment and by date, a Referring URLs column for internal linking. And a crawl reading drawn from Google's own data: 30-day crawl rate, average frequency, HTTP codes as seen by Googlebot — where a classic HTTP checker only shows what its own robot encounters.

4

Where CheckIndex.io stands out

Their URL submission service is real, and IndexProbe offers none: reading the official outcome is our job, pushing for indexing is not. Their public REST API is properly documented — IndexProbe has no public API today (CSV export covers reporting integrations). And like any checker without property access, they can check URLs you don't manage — backlinks, third-party placements — ground closed to us by design: the Search Console authorization we require is exactly what unlocks the official data.

Side by side

Line by line

The same comparison, laid out. Their column reflects observed capabilities — their site and API documentation as read on 2026-08-08.

CheckIndex.io (observed capabilities)IndexProbe
MethodNot disclosed (no Search Console connection)Official URL Inspection API, on your properties
Per URLIndexed yes/no, HTTP code, geo heuristicOfficial status, non-indexing reason, selected canonical, last crawl
Re-checking1 credit per URL, every passIncluded: recurring analyses with no meter
Monitoring 10,000 URLs weekly≈ 43,000 credits/month, Pro pack $79/monthStarter $19/month, reasons included
How URLs get inSitemap (re-synced), manual add, APISitemap, CSV, paste, Search Console import by clicks / impressions / regex
Speed leversAccelerated mode (impressions without quota), regressions first, multi-property aggregation
Top-tier capacityAgency $169 / 130,000 checksAgency $99 / up to 1.8M distinct inspections a month, deduplicated domain view
SegmentationAI or manual, editable regex
ChartsIndexed / not-indexed countersStatus, noindex, robots.txt and canonical pies; statuses by segment and date; crawl charts
CrawlHTTP codes seen by their robotHTTP codes seen by Googlebot, 30-day crawl rate, frequency per segment, no logs
URL submissionReal: 30 credits/URL, VIP 150Out of scope, by design
Public APIDocumented REST APINo public API (CSV export)
Third-party URLs (backlinks)Yes, no property access neededNo: authorized properties only
Trial100 free credits10 days, no credit card

Pricing

CheckIndex.io pricing vs IndexProbe pricing

CheckIndex.io sells credits with 30-day validity: Starter $19 / 10,000, Medium $39 / 25,000, Pro $79 / 60,000, Agency $169 / 130,000 (read from their pricing API on August 8, 2026 — check their page for current rates; annual −15%). IndexProbe sells subscriptions: $19, $49 or $99 a month, recurrence included.

The deal, spelled out: at the same entry price — 19 — the two products don't deliver the same thing. There: 10,000 yes/no answers, consumed once. Here: 3 projects, 30,000 URLs per analysis, analyses that repeat with no meter, and for every URL the reason, the canonical and the crawl. At the top: their Agency at $169 exhausts 130,000 checks; our Agency at $99 opens up to 1.8 million distinct inspections a month, aggregated by domain. Monitoring is not a consumption, it is the product.

CheckIndex.io packs

As read from their pricing API on August 8, 2026 — check their page for current rates: Starter $19 / 10,000 credits · Medium $39 / 25,000 · Pro $79 / 60,000 · Agency $169 / 130,000 · 30-day validity, annual −15% · 1 credit = 1 index or HTTP check · submission 30 credits/URL, VIP 150 · 100 free credits at signup.

IndexProbe plans

Starter $19/month, 3 projects, 30,000 URLs per analysis · Pro $49/month, 10 projects, 60,000 URLs, AI segmentation · Agency $99/month, 3 Search Console accounts, 30 projects, 100,000 URLs per analysis, add-ons (+10 projects, +1 account). Recurring analyses and alerts on every plan. Free 10-day trial, no credit card.

Honest framing

What IndexProbe does, and does not do

IndexProbe reads the official verdicts of the Search Console API on the properties you are authorized on. The honest comparison covers what surrounds that data — and what stays outside our scope.

100% official data

The same verdicts as Search Console's URL inspector, non-indexation reason included, with no scraping and no estimates.

Your lists, not a crawl

Search Console export, CSV, sitemap, or paste, up to 100,000 URLs per analysis. IndexProbe does not discover URLs by following links.

Google's quota, turned into an implementation detail

Google caps official inspection at 2,000 URLs per day per property, but IndexProbe gets you past that limitation. The accelerated inspection mode counts pages that received recent impressions, or whose indexing was recently confirmed, without touching that quota: it runs through an API whose quota is separate. The cap applies per property, not per site — so IndexProbe aggregates the projects of a single domain: 10 prefix properties in your Search Console, and at least 20,000 URLs are processed per day, more than 140,000 distinct URLs in a week, often more still once the accelerated mode is at work. On the Agency plan, 30 projects multiply that ceiling up to 60,000 daily inspections — enough to potentially cover 1.8 million distinct URLs in a month before the accelerated mode even counts. Whatever overflows a day rolls over to the next ones on its own.

A scope we stand by

No URL submission, no third-party URL checking: those trades exist, CheckIndex.io practices them, and ours is elsewhere — reading Google's decision, in bulk, continuously, with the why.

FAQ

Frequently asked questions

Do CheckIndex.io and IndexProbe use the same data?

No. IndexProbe reads Google's official URL Inspection API on properties you are authorized on: status, reason, canonical, crawl information. CheckIndex.io does not disclose its checking method; its documentation mentions no Search Console connection and its result is limited to indexed yes/no, alongside an HTTP code collected by its own robot.

What does IndexProbe show that a yes/no cannot?

The exact reason when a page isn't indexed (duplicate page, different canonical selected by Google, Soft 404, crawled without indexing…), the canonical actually chosen versus the one you declare, and the date of Googlebot's last visit. Two “not indexed” pages can call for two opposite fixes; the reason is what tells them apart.

How does the cost of regular monitoring compare?

At CheckIndex.io, every check consumes a credit: monitoring 10,000 URLs weekly represents about 43,000 credits a month, their Pro pack at 79 dollars. At IndexProbe, recurring analyses are included in the subscription: the Starter plan at 19 dollars a month covers 3 projects and 30,000 URLs per analysis, reasons included, whatever the frequency.

Can IndexProbe submit URLs for indexing?

No, by design. CheckIndex.io offers that service through external providers (30 credits per URL, 150 on priority). IndexProbe focuses on the other half of the job: reading what Google decided, with the reason, and detecting regressions — resubmitting a page Google set aside doesn't change its decision, fixing the reason does.

I check backlinks and URLs I don't manage. Which tool?

Not IndexProbe: the official API requires being authorized on the Search Console property, and that requirement is what unlocks the official data. For third-party URLs, a checker without property access like CheckIndex.io is a relevant choice — the two tools complement each other on this point.

How fast does IndexProbe cover a large site?

The official quota is 2,000 inspections per day per property, but it multiplies: 100,000 URLs are covered in 2 days with 30 prefix properties, in about 5 days with 10, and faster still with the accelerated mode, which counts pages with recent impressions without consuming that quota. Subsequent analyses re-cover the list without limit.

The official verdict, with the reason

Connect your Search Console, import your list. Status, reason, canonical, last crawl — in bulk, continuously, with no credit meter. From $19/month, 10 days free, no card.

Start the free 10-day trial
No commitmentNo credit card required
CheckIndex.io Alternative: The Official Verdict, With the Reason | IndexProbe