Google indexer: see which pages Google left out, and why
Content Hub asks Google's URL Inspection about your pages, tells you why an article was left out, and re-sends your sitemap to Google every time you publish (with Search Console connected with full access).

Google's own indexing tools, in numbers
Plenty of tools sell faster indexing. This is what Google's documentation says about its Indexing API, and about the inspection API we use.
Tell Google. Then check. Then say why.
Sending a URL is the easy half. The work is knowing which pages never made it in, and what is stopping them.
You publish
Sitemaps go back to Google through the Search Console API; with our WordPress plugin or Cloudflare, IndexNow too.
Google sitemap
Bing IndexNowoptionalWe ask Google
Day 2 after publishing, a forced check around day 14; in between, every 3 days while out, every 7 once in.
URL InspectionYou see why
Not indexed? We check noindex, canonical, sitemap, links and Google’s verdict.
noindex · canonical · linksYou get a warning
A red card counts the published articles Google doesn’t have, one click from the list.
Command Center alert
Indexing status for every page, in one tab
Check any page against Google
Your Search Console pages, with Google's verdict next to clicks and position. One button inspects a URL; another sends it to Google's Indexing API, best effort.
- On Google and In sitemap columns from the latest inspection
- Re-scan coverage inspects up to 50 pages with impressions in the period
- Last crawl, robots.txt, indexing, fetch and rich results per URL

Not indexed, and the reason
For each published article we test the page itself, not just Google's verdict, and pick the problem that weighs most.
- ✓Loads (HTTP 200)
- ✓No noindex (meta or header)
- ✓Canonical points to itself
- ✓Listed in your sitemap
- ✓robots.txt doesn't block it
- ✕Sitemap never submitted to Google
- ✕No page links to it
Google has never found it. Submit your sitemap and link to it from your home or blog page.
Then the status is Unknown, unless the page itself blocks Google: a noindex, an error, or a canonical pointing elsewhere.
A signal on every publish, logged
Each publish re-submits your sitemaps to Google. With our WordPress plugin or Cloudflare, it also pings IndexNow and sends a 30-day “fresh” sitemap.
- Sitemaps go through the Search Console Sitemaps API. Google retired the old sitemap ping (Google)
- Send history: what went to Google and to IndexNow, with errors
- Send now to repeat it without publishing

The Index button is a nudge, not a guarantee
It sends a URL_UPDATED notice to Google's Indexing API. Google may ignore it.
- Google documents that API only for job postings and livestreams
- Also sent when you redirect a page or republish an off-line article from the Topical Map
- Only after one of your actions, never the publish pipeline or autopilot. Keep it for a handful of URLs
Pages that go quiet
An indexed article with 7 days in a row without impressions is inspected again first. Our own “GEO for e-commerce”:
- Impressions stop, before any inspection shows it
- Google recrawls it
- Still “Crawled - currently not indexed”
What this can't do
- Nobody can force Google to index a page.
A crawl request “does not guarantee that inclusion in search results will happen instantly or even at all” (Google).
- “Crawled, not indexed” is Google’s call.
Google read it and passed; it “may or may not be indexed in the future; no need to resubmit this URL for crawling” (Google).
- Search Console is required.
Inspections, sitemap resubmits and the Index button use it. Resubmits need full access, not read-only; the Index button, a verified owner.
- Inspections have a ceiling.
2,000 URL Inspection calls a day per property, shared by every check. The coverage scan inspects up to 50 pages with impressions; new articles are checked anyway by the hourly job.
Nobody can force Google to index a page.
A crawl request “does not guarantee that inclusion in search results will happen instantly or even at all” (Google).
“Crawled, not indexed” is Google’s call.
Google read it and passed; it “may or may not be indexed in the future; no need to resubmit this URL for crawling” (Google).
Search Console is required.
Inspections, sitemap resubmits and the Index button use it. Resubmits need full access, not read-only; the Index button, a verified owner.
Inspections have a ceiling.
2,000 URL Inspection calls a day per property, shared by every check. The coverage scan inspects up to 50 pages with impressions; new articles are checked anyway by the hourly job.
Four ways to tell a search engine about a page
What each one is for, per the people who run it, and what Content Hub does with it.
| Method | Google Indexing API | |||
|---|---|---|---|---|
| What it is | ||||
| Read by GoogleGoogle is not on the IndexNow list of participating engines. | Yes | No | Yes | Yes |
| Meant for any kind of page | Yes | Yes | NoJobPosting and BroadcastEvent only | Yes |
| Published limit | No per-site cap; 200/min per user (Google) | None we found | 200 per project by default | A quota; number not published |
| In Content Hub | ||||
| Sent on every publish | Yes (Search Console with full access) | With our WP plugin or Cloudflare | Never in the publish pipeline or autopilot | No (you do it by hand in Search Console) |
| On demand | Send now | Send now | Index button (also sent on redirect or republish): off-label for ordinary pages, best effort | Not available |
Sitemap, IndexNow, Google Indexing API and Search Console's Request Indexing compared
- What it is
- Read by Google
- Yes
- Meant for any kind of page
- Yes
- Published limit
- No per-site cap; 200/min per user (Google)
- In Content Hub
- Sent on every publish
- Yes (Search Console with full access)
- On demand
- Send now
- What it is
- Read by Google
- No
- Meant for any kind of page
- Yes
- Published limit
- None we found
- In Content Hub
- Sent on every publish
- With our WP plugin or Cloudflare
- On demand
- Send now
- What it is
- Read by Google
- Yes
- Meant for any kind of page
- NoJobPosting and BroadcastEvent only
- Published limit
- 200 per project by default
- In Content Hub
- Sent on every publish
- Never in the publish pipeline or autopilot
- On demand
- Index button (also sent on redirect or republish): off-label for ordinary pages, best effort
- What it is
- Read by Google
- Yes
- Meant for any kind of page
- Yes
- Published limit
- A quota; number not published
- In Content Hub
- Sent on every publish
- No (you do it by hand in Search Console)
- On demand
- Not available
Yes yesNo no, per the documentation
Checked on in Google's and IndexNow's own documentation.
Method and sources (6)
Content Hub rows: what the product does today, checked in our own code. IndexNow and the fresh sitemap need our WordPress plugin or Cloudflare; other setups only get the regular sitemap re-submitted. Two tips from Google: with many URLs, send a sitemap, “an important way for Google to discover URLs on your site”; and requesting the same URL again “won’t get it crawled any faster” (Google).
Questions people ask
What is a Google indexer?
Can I use the Google Indexing API for any page?
How do I check if a page is indexed by Google?
site: search is only a rough signal. Content Hub runs URL Inspection for you and keeps the result per page.How long does Google take to index a new page?
Does IndexNow work with Google?
Why is my page “Crawled - currently not indexed”?
Find the pages Google is missing
Content Hub, with the Search Console + Indexer tab, is included from Brand ($349/mo) and in every Agency plan. Connect Search Console and every article you publish is checked on its own.