Google index checker: check if your pages and links are indexed

This guide covers all three methods, where each one falls short, and what to do with the pages Google hasn't indexed.

What an index checker does

An index checker is a tool or method that asks Google whether a given URL is stored in its index and records the answer. That's it. A good indexing check gives you a clear yes or no per URL, the date it was checked, and a way to repeat the check later so you can see change over time.

Why does this matter? Google's process runs in stages: it discovers a URL, crawls it, processes it and then decides whether to store it in the index (Google: How Search works). Only indexed pages can be shown in results. If you want the background on those stages, start with how Google indexing works. An index checker sits at the end of that pipeline and tells you whether a page made it.

What an index checker does not tell you:

• Why a page isn't indexed. For your own site, the page indexing report in Search Console groups unindexed URLs by reason.
• Where a page ranks. Indexed and ranking are different things.
• Whether a link passes value. For backlinks, being indexed is a precondition, not a guarantee.

People use the phrase "Google index checker" for everything from a single browser search to an API that processes thousands of URLs. The underlying question is always the same, so the methods below are ordered from quickest to most scalable.

Indexation vs indexability

Indexation is whether Google has actually stored a page; indexability is whether the page is technically allowed to be indexed. A page can be perfectly indexable and still not indexed, and the two need different checks.

Indexability problems are usually yours to fix and fully within your control. A noindex tag, a robots.txt disallow, a 404 or 5xx response, or a canonical tag pointing elsewhere will each keep a page out of the index. Search Console lists these as separate reasons, such as "URL marked 'noindex'", "URL blocked by robots.txt" and "Server error (5xx)" (Google: Page indexing report).

Indexation problems are Google's decision. The two statuses that frustrate people most, "Crawled - currently not indexed" and "Discovered - currently not indexed", describe indexable pages Google has chosen not to store yet. For the first one, Google's help page says the page "may or may not be indexed in the future; no need to resubmit this URL for crawling."

The practical rule: check indexability first (it's cheaper to fix), then check indexation to see whether Google followed through. Our noindex and indexability checker guide walks through all five indexability checks for one URL, with a script you can run.

Method 1: site: search, and why it's unreliable

A site: search is the fastest way to check Google indexing, but it's a sample, not a complete list. Type site:example.com/your-page into Google and see whether the URL appears.

It's useful for a quick look. It's not useful as proof, and Google says so directly. Its documentation for the operator states that "the list of URLs returned is not always exhaustive", that "bigger sites shouldn't expect to see all their URLs in the results", and that an indexed URL "can show up" in site: results but it's "not guaranteed" (Google: site: search operator). If a URL doesn't appear, Google recommends using the URL Inspection tool instead.

Where site: searches go wrong:

1. False negatives. An indexed page doesn't show, so you conclude it's missing and waste effort pushing it.
2. Result counts are estimates. The "About X results" number for site:example.com is not a count of indexed pages. Don't report it to a client as one.
3. Manual and slow. Checking 50 backlinks one search at a time takes an afternoon, and repeated automated queries to Google Search aren't something you should script yourself.
4. No history. You get a snapshot with no record of what changed since last week.

Use site: when you want a ten-second sense check on one URL. For anything you'll act on or report, use one of the next two methods.

Method 2: URL Inspection in Search Console

URL Inspection is Google's own index check for a single URL on a property you've verified in Search Console, and it's the most reliable answer you can get. Paste the URL into the search bar at the top of Search Console and it reports whether the URL is on Google (Google: URL Inspection tool).

What it shows that other methods can't:

• Index status from Google's own data, not inferred from search results.
• Crawl details, including when Google last crawled the page and whether crawling was allowed.
• Canonical information: the canonical you declared and the one Google selected. A mismatch explains a lot of "missing" pages.
• A live test of the current URL, which tells you whether the page is indexable as it stands today. A passing live test doesn't mean the page is indexed; it means nothing on the page is blocking it.
• Request indexing, which asks Google to recrawl the URL.

The limits are just as important:

• Ownership required. You must have access to the property, so it can't check a backlink on someone else's site.
• One URL at a time. There's no bulk mode in the interface.
• Request indexing is capped. Google says "there's a quota for submitting individual URLs", and that "requesting a recrawl multiple times for the same URL won't get it crawled any faster" (Google: Ask Google to recrawl your URLs). Google also notes that crawling "can take anywhere from a few days to a few weeks."

For site-wide patterns rather than single URLs, the page indexing report groups URLs by status. Its example lists are capped at 1,000 URLs per status and Google says they aren't guaranteed to show every affected URL, so for an exact list of specific pages you still need a URL-level check.

Method 3: bulk index checkers

A bulk index checker runs the same yes-or-no indexing check across a list of URLs and returns a result for each one. It's the only practical way to check indexed pages at scale, whether that's 300 product pages after a migration or 2,000 backlinks across a client roster.

What separates a useful tool from a noisy one:

Treat results with appropriate humility. Index checkers ask Google whether each URL is in its index and record what comes back at that moment. Results can vary between runs, so a single "not indexed" result is a reason to re-check, not to panic. Our bulk index checker guide covers how to run a check across thousands of URLs and how to read disagreements between runs.

This is where a tool like FreshlyCited's visibility check fits: it checks each URL, marks it as seen by Google or invisible, and keeps the result so you can compare it with the next run.

Checking backlinks on sites you don't own

To find out whether a backlink is indexed, you check the page that contains the link, not your own page. If that linking page isn't in Google's index, Google has no stored copy of your link.

You can't use URL Inspection here because you don't own the linking site. Search Console's Links report shows "Top linking sites" and other link data for your property (Google: Links report), but it doesn't tell you whether each individual linking page is indexed today. That leaves site: searches (unreliable, as above) or a bulk check of the linking URLs.

A sensible workflow for link builders and agencies:

1. Collect the exact URLs of the pages that host your links, not the root domains.
2. Run them through an index checker.
3. Separate the indexed links from the unindexed ones.
4. Look at the unindexed pages: are they live, do they still contain your link, are they blocked from indexing?
5. Push the eligible ones and re-check later.

There's more detail on this in our guide to how you check if backlinks are indexed, including what "indexed" does and doesn't tell you about a link's value.

What to do with pages that aren't indexed

Pages that aren't indexed need a diagnosis before they need a push. Asking Google to recrawl a page that is blocked or weak usually produces the same result.

Work through this order:

1. Confirm the result. Re-check after a few days, or use URL Inspection if it's your property. One run is a data point, not a verdict.
2. Check indexability. Look for noindex, robots.txt rules, non-200 status codes, redirects and canonical tags that point elsewhere. Fix these first.
3. Check the status reason. On your own site, the page indexing report tells you whether Google hasn't crawled it yet ("Discovered") or crawled it and passed ("Crawled").
4. Improve the page if Google passed on it. Thin, duplicate or low-value content is the common cause. Add what's missing rather than changing the date.
5. Strengthen discovery. Link to the page from pages Google already crawls often, and keep it in an accurate XML sitemap.
6. Ask Google to look again. Use Request indexing for a handful of owned URLs, or a push service for larger lists and third-party pages.
7. Re-check. Only a fresh check tells you whether the push worked.

There's one thing to avoid: pushing everything regardless of status. Checking first and sending only the invisible URLs is cheaper, and it avoids asking Google to recrawl pages it already has. In FreshlyCited a standard check costs one check credit per link, and with check-first on, links Google already sees aren't pushed, so no index credit is reserved for them.

Why does this matter beyond rankings? AI answers cite what's been crawled, and they lean toward pages that are kept current. FreshlyCited helps Google discover and index the pages, posts and backlinks you publish or update sooner, so they become eligible for Google Search, AI Overviews and AI Mode, then re-checks and shows you what Google has indexed. Google's documentation says a page "must be indexed and eligible to be shown in Google Search with a snippet" to appear as a supporting link in AI Overviews or AI Mode (Google: AI features and your website). Read more on why indexing decides AI search visibility. Indexing is the first step; being cited still depends on quality, authority and relevance.

Index checking as a routine for agencies and SaaS teams

Index checking works best as a scheduled routine rather than a one-off audit, because pages and links enter and leave the index over time. A routine turns "I think it's indexed" into a dated record you can act on and show to others.

For SEO agencies and link builders

• Check every new batch of backlinks a week or two after they go live, then again a few weeks later.
• Re-check paid links on a regular schedule, since linking pages can drop out of the index.
• Report results per link, with before and after, rather than a single percentage. Clients trust a list of URLs they can open.
• Keep a record per client so you can show progress over a campaign.

See index checking for agencies for how this fits client reporting.

For SaaS and content teams

• Check new pages after each release or content batch, especially programmatic or templated pages, which are the most likely to sit in "Discovered - currently not indexed".
• Check updated pages too. If you refresh a pricing or comparison page, the version Google stores is the one search results and AI answers work from until Google recrawls it.
• Watch the page indexing report for sudden jumps in any "not indexed" reason after a deploy. A spike in "URL marked 'noindex'" or "Server error (5xx)" usually points to a release bug.

A simple cadence

Whatever the cadence, keep the same loop: check, fix, ask Google to look, re-check. If you want to see where your own pages and links stand today, check your own links free.