# How do I check whether Google has indexed my pages?

For one URL, paste it into Search Console's URL Inspection tool and read the verdict: URL is on Google means it is indexed and eligible, not guaranteed to appear. For the whole site use the Page indexing report. For batches, the URL Inspection API allows 2,000 inspections per day per property. Searching for the exact URL on Google is the definitive test.

By SEOBolt. Published 13 November 2026, updated 13 November 2026.

## Why this happens
Indexed does not mean ranking, and crawled does not mean indexed. Google discovers a URL, may crawl it, and then decides whether to add it to its index. A page can be fetched successfully and still left out, which Search Console reports as Crawled - currently not indexed. A page can also be indexed but never shown for any query.

Several different problems sit behind the same "not indexed" label: the page is blocked by robots.txt, has a noindex directive, returns an error, redirects, or has a canonical pointing to another URL that Google prefers. Each needs a different fix, so the first job is to read the exact status, not to resubmit the URL.

Two Google caveats are worth knowing. URL Inspection shows the most recently indexed version, not the live page, so you must run a live test to see current state. And URL is on Google does not guarantee the page appears in results; Google's help page says the definitive test is to search for the URL itself.

## How to check, step by step

1. **Inspect a single URL.** Paste the full URL into the search bar at the top of Search Console. The URL must belong to the property you are in. Read the overall status: URL is on Google, URL is on Google but has issues, or URL is not on Google.
2. **Read the reason, not just the verdict.** Expand Page indexing. It shows how Google discovered the URL, the last crawl, whether crawling and indexing were allowed, the user-declared canonical and the Google-selected canonical. A mismatch between the two canonicals is a common cause of a page being left out.
3. **Run a live test for current state.** The indexed report is from the last crawl. Use the live test to see whether the page is fetchable and indexable now, especially after you fix something.
4. **Use the Page indexing report for patterns.** Open Indexing, then Pages, to see counts by reason across the property, and click a reason to list affected URLs. Fix by cause rather than URL by URL.
5. **Check batches through the API.** For many URLs, the URL Inspection API enforces 2,000 queries per day and 600 per minute per site, so spread large audits across days and prioritise key pages.
6. **Search for the URL.** Search Google for the exact URL. Google's URL Inspection help calls this the definitive test of whether a URL appears, and its Page indexing help suggests site: searches (for example site:example.com/page) as the quick check for sites under about 500 pages.
7. **Fix the cause and validate.** Fix the underlying issue, then use Validate fix in the Page indexing report; Google says validation typically takes up to about two weeks. Requesting indexing does not override a quality decision. Not every URL needs to be indexed: duplicates, blocked and removed pages are fine.

## Index status and the usual fix
Common reasons a URL is not indexed and the first check for each (Search Console Help, read 13 November 2026)

| Status | Meaning | First check |
| --- | --- | --- |
| Blocked by robots.txt | Google was not allowed to fetch it | Test the URL against robots.txt; remove the rule if unintentional |
| Excluded by noindex | The page says do not index | Remove the noindex tag or header if unintentional |
| Crawled - currently not indexed | Fetched, then left out | Improve or merge the page and strengthen internal links |
| Alternate or duplicate with different canonical | Google chose another URL as canonical | Make canonical, internal links, sitemap and redirects agree |
| Not found (404) or server error | The URL does not return a good page | Fix the status or redirect to the right page |

## When to use SEOBolt for this
seo_gsc_index_coverage uses the Search Console URL Inspection API with your connected property. Pass up to 50 URLs (they must belong to the property), or omit them and it inspects the project's top crawled pages by Search Console impressions. Each URL is placed in a bucket: indexed, not_indexed_crawled, canonical_elsewhere, noindex, blocked_robots, error_404_5xx or unknown, with a suggested fix. It stops and returns a partial result when the daily quota is reached and suggests changes only.

It needs Search Console connected and a plan that includes the integration; /pricing shows which. Without a connection, the free Indexability Checker at /tools/indexability-checker explains one URL's status, X-Robots-Tag, meta robots, canonical, redirects and robots.txt rules for Googlebot as a plain verdict.

MCP tools involved: `seo_gsc_index_coverage`, `seo_issues`.

**When SEOBolt is not the right tool:** It reports what Google's index says; it cannot make Google index a page. If a page is thin or duplicated, the fix is the content, not another inspection.

## Prompt to give your AI assistant

With the SEOBolt MCP server connected (https://seobolt.app/mcp-seo):

```text
Assign to SEOBolt: for sc-domain:example.com run seo_gsc_index_coverage on my top crawled pages, group the results by bucket, and for each non-indexed page give the cause and the fix. This tool only reads data. Show me what you did so I can approve the changes.
```

## FAQ
### Is URL is on Google the same as ranking?
No. Google says it means the URL is eligible to appear in results, not guaranteed to appear. Search for the URL to confirm.

### How often can I inspect URLs through the API?
Google lists 2,000 queries per day and 600 per minute per site for URL inspection.

### Does Request indexing force indexing?
No. Google's help describes it as a request that a URL be crawled. It does not override Google's decision about the page, so the cause of a not-indexed status still has to be fixed.

### Why is a crawled page not indexed?
Google decided it was not worth adding, often because of thin or duplicate content or weak internal links. See our guide to Crawled - currently not indexed for a triage table.

## Sources
- [Search Console Help: URL Inspection tool](https://support.google.com/webmasters/answer/9012289), read 13 November 2026
- [Search Console Help: Page indexing report](https://support.google.com/webmasters/answer/7440203), read 13 November 2026
- [Search Console API: Usage limits](https://developers.google.com/webmaster-tools/limits), read 13 November 2026
- [Google Search Central: Introduction to robots.txt](https://developers.google.com/search/docs/crawling-indexing/robots/intro), read 13 November 2026

## Related
- [Crawled - currently not indexed: causes and fixes](https://seobolt.app/blog/crawled-currently-not-indexed)
- [How do I test whether my robots.txt blocks Googlebot or AI crawlers?](https://seobolt.app/solutions/test-robots-txt-googlebot-and-ai-crawlers)
- [Why did my page lose Google traffic?](https://seobolt.app/solutions/page-lost-traffic)
- [Indexability Checker (free tool)](https://seobolt.app/tools/indexability-checker)
- [All problems and solutions](https://seobolt.app/solutions)

HTML version: https://seobolt.app/solutions/check-if-google-indexed-my-pages