There’s only one source that truly knows whether one of your URLs is on Google: Google itself. Everything else — searching with “site:”, guessing from traffic, inspecting your HTML — is just an approximation. The real data lives in Search Console, and getting it has never been the problem: the problem is getting it for an entire catalog without burning an afternoon URL by URL.
The data only Google has
Search Console’s URL Inspection tool gives you the official verdict: whether the URL is indexed, and if not, why — blocked, noindex, canonical pointing elsewhere, discovered but queued. No tool that analyzes your site from the outside can give you that: it can form an opinion about your HTML, but it has no idea what Google actually decided.
The manual method and its limit
In Search Console you paste a URL into the inspection bar, wait a few seconds, and get the verdict. Perfect for a single URL. For a catalog of 300 product pages, it’s an entire afternoon of copying, pasting, and logging results in a spreadsheet — one that’s already outdated the following week. The aggregate coverage report helps you see the forest, but cross-referencing it with YOUR list of important URLs is still manual grunt work.
Manual inspection
URL by URL in Search Console, logging results in a separate sheet. Hours of work that nobody repeats as often as they should.
Bulk coverage checks from the back office
The real status of a sample of your catalog, queried against Google’s API in batches, with every problem URL listed along with its cause.
What we’re building: Zeyvro Faro
With Search Console connected, Google’s URL Inspection API can be queried in batches across a sample of your catalog, respecting its quotas: there is no public “coverage API,” and anyone who tells you otherwise is selling you smoke. Bringing that into the back office, with Google’s reason for each URL, is what we’re building with Zeyvro Faro.
Faro isn’t on sale yet: if you want to know when it launches, join the waiting list.
💡 Before querying Google, make sure your own store isn’t the problem: the technical audit for robots, sitemap, noindex, and canonical — free, with nothing to connect.
What to do with the verdict
- Blocked or noindex — a configuration error: fix it in robots.txt or on the page itself, then request reindexing.
- Canonical pointing elsewhere — decide which URL is genuinely the right one and align the canonical with that decision.
- Discovered, not indexed — Google is waiting for stronger signals: improve the page, its internal linking, and how differentiated the content is.
- Indexed but invisible — the problem is no longer indexing, it’s ranking: a different battle, fought with different weapons.
Frequently asked questions
Is there a Google API to see the coverage of my entire site?
There’s no public “Index Coverage API.” What does exist is the URL Inspection API, which checks the real status URL by URL — it can be used in batches across a sample of the catalog, respecting its quotas.
Doesn’t “site:mydomain.com” tell me the same thing?
Not reliably: the site: operator is an approximation that neither lists everything indexed nor confirms what’s missing. The official verdict, cause included, only comes from Search Console’s URL Inspection tool.
Will Faro use Zeyvro Connections?
That’s the plan: connect Google once in the free Zeyvro Connections hub and let the other Zeyvro modules inherit it. Faro is still in development.
What does the AI diagnosis tell me that Search Console doesn’t?
Search Console gives you the technical status; the AI diagnosis translates it into plain language and prioritizes: why this URL isn’t indexing, and which one to fix first.
Google’s real verdict on your catalog, right inside your back office — with the reason behind every URL.
Notify me when Zeyvro Faro launches →Zeyvro builds PrestaShop 8 modules from a real store running in production. Unobfuscated code.