# Google index checker: is this page indexed, and why not, from the URL Inspection API

Connect the Search Console property you already own and your agent can ask Google, per URL, the question the UI answers one click at a time: is it indexed, when was it last crawled, which canonical did Google choose, and if it is not indexed, which bucket it sits in. It runs on your own Google account, so treg.to never meters it, and it is the same URL Inspection data the Search Console panel shows, without the clicking.

## What's the best way to ask ChatGPT?

Setup line (paste into any agent): `set up treg — https://treg.to/llms.txt`

Then ask: "Using treg, take every URL in our sitemap, inspect each one in Search Console, and give me a table of the ones that are not indexed with the coverage state, last crawl date and the canonical Google picked."

- **Connect once** One OAuth click for the property you own. treg.to holds the token, not you.
- **Give it the property string** The URL must sit under the property you name, sc-domain or URL-prefix. A mismatch is a permission error, not a result.
- **Mind the quota** Google allows 2,000 inspections per property per day, and nothing lifts it. A 5,000-page site is three days.
- **It costs nothing** Your own account, so the call is never metered.

## Why go through treg.to

- **One key, not 9 accounts** treg.to holds the provider keys. Neither you nor the agent sees them.
- **Price before the call** The provider's own rate, $0.000 markup, from a prepaid balance.
- **No subscription, no seats** Charged per call. $1.00 free per new team, no card to start.
- **Your own keys are free** Already pay Hunter? Register it and those calls are never metered.
- **Switch by changing a word** Another provider is a different word in the prompt, not a new integration.
- **Nothing to integrate** No SDK, no OAuth dance per vendor, no seats.

## How it works

One provider does this job: Google Search Console (`google-search-console.url_inspection`), on the account you already own. You connect it once, treg.to keeps the token server side, and the call is never metered.

    treg call google-search-console.url_inspection --data '{"inspectionUrl":"https://example.com/","siteUrl":"sc-domain:example.com"}'

Endpoints:

- `google-search-console.url_inspection`: treg call google-search-console.url_inspection --data '{"inspectionUrl":"https://example.com/","siteUrl":"sc-domain:example.com"}'

## What people actually struggle with

Indexing is a queue of people waiting on Google and a shelf of tools promising to jump it: about a dozen index-checker and indexing-service pitches sat among ~70 on-topic Reddit and X posts in August 2026. These four are people checking their own pages.

**The two Search Console reports disagree**

> "URL Inspection says Indexed, but Page Indexing says 'Crawled – currently not indexed.'... Which status should we trust more?" (r/SEO, 12 points: https://www.reddit.com/r/SEO/comments/1ume4w0/)

What this page can do about it: The inspection side is the fresher one, and it is what the API reads. A scripted pass over the affected URLs gives you the current verdict per page instead of a report that updates on its own schedule.

**Crawled, not indexed, for months, and validation never finishes**

> "Crawled - currently not indexed for almost 2 months. Validation Started - Started: 5/29/26 and still nothing." (r/TechSEO, 70 points: https://www.reddit.com/r/TechSEO/comments/1uzt1t0/)

What this page can do about it: No API makes Google decide faster, and this page will not claim one does. What it gives you is the per-URL state, the last crawl date and the canonical Google chose, kept over time, so you can see which pages moved and which did not.

**The Indexing API turns out to be for job postings**

> "Google Search API can not be used because it only supports categories related to broadcasting and job postings." (r/SEO, 32 points: https://www.reddit.com/r/SEO/comments/1robehb/)

What this page can do about it: Correct, and it is why the most-searched term for this job names the wrong API. The URL Inspection API is the one that answers 'is this indexed', for any page on a property you own.

**The 2,000 a day quota is the whole constraint**

> "The big limitation of the insufferable URL inspection API is the 2,000 daily quota." (@iannuttall on X: https://x.com/i/status/1734591329953276340)

What this page can do about it: It is, and it is per property, set by Google. treg.to relays the call as it is, so the quota is yours to spend well: inspect the pages that changed, not the whole site every morning.


## What actually differs

- The quota is Google's and it is hard: 2,000 inspections per property per day. treg.to does not pool, rotate or route around it, and the forum's tales of getting past it involve multiple properties or policy violations. Inspect the pages that matter, keep the verdicts, and diff them week to week; that is where the tool earns its place.
- This is the fresher of the two Search Console answers. The Page Indexing report lags and its validations can sit for months, which is why people see it disagree with the URL Inspection panel. The API reads the inspection side, so a scripted check gives the per-URL answer without waiting for the report to catch up.
- Two things this page does not do. It does not request indexing: that button has no API and its own small daily limit. And it is not the Indexing API, which Google restricts to JobPosting and BroadcastEvent pages; using it for anything else is against policy and returns a cheerful 200 that changes nothing.

## What is the URL Inspection API?

The URL Inspection API is the Search Console endpoint behind the URL Inspection tool. For one URL on a property you own it returns Google's index verdict, the coverage state (indexed, crawled but not indexed, discovered but not indexed, and the rest), the last crawl date, the robots and indexing state, the canonical you declared against the one Google chose, and the mobile and rich-result checks. It is a read. It does not ask Google to index anything, and it is not the Indexing API, which is a different endpoint restricted to job postings and live-broadcast pages.

## Questions

**Does this cost anything?** No. Search Console runs on your own Google account, so treg.to relays the call and meters nothing. Only calls on treg.to's own provider keys are billed.

**Can it make Google index my page?** No. The URL Inspection API reads Google's verdict; it does not submit anything. It tells you which bucket a page is in and why, which is the part you can act on.

**Is this the Google Indexing API?** No. The Indexing API is for job postings and live-broadcast pages only. Most people searching for it want what this page does: check whether a URL is indexed, in bulk, and see the reason when it is not.

**How many URLs can I check a day?** 2,000 per Search Console property per day, set by Google. The agent can loop a sitemap and stop at the quota, then carry on the next day.

HTML version: https://treg.to/use-cases/is-this-page-indexed-and-why-not