How to Check If a Page Is Indexed on Google (4 Methods)

Why Checking Indexing Status Matters

Google's index is the pool of pages eligible to appear in search results. If your page is not in that pool, no amount of keyword optimization or link building will help — the page simply does not exist from Google's perspective.

Common scenarios where you need to verify indexing:

• After publishing new content and you want to confirm it was picked up
• After a site migration or redesign to ensure old URLs are replaced correctly
• When organic traffic drops unexpectedly and you suspect deindexing
• When auditing a client site as part of an SEO engagement
• After fixing "Discovered — currently not indexed" or "Crawled — currently not indexed" issues

Method 1: The site: Search Operator

The simplest way to check indexing is the site: operator in Google Search. Type site:yourdomain.com/page-url into Google and see if the URL appears.

Step-by-Step

1. Open google.com in your browser
2. In the search bar, type site:https://yourdomain.com/your-page
3. Press Enter
4. If the URL appears in results → the page is likely indexed
5. If "Your search did not match any documents" → the page is not indexed

site:https://example.com/blog/my-article

Pros & Cons

Method 2: Google Search Console URL Inspection

The URL Inspection tool in Google Search Console provides the most authoritative, real-time answer for a single URL. It tells you whether the page is in the index, when it was last crawled, and whether any issues exist.

Step-by-Step

1. Log in to Google Search Console
2. Select the correct property (domain or URL prefix)
3. Paste the full URL into the inspection bar at the top
4. Click Enter and wait for results
5. Look for the "URL is on Google" green checkmark — this confirms indexing
6. Click "Test Live URL" for a real-time crawl snapshot

The inspection result will show one of several states:

• URL is on Google — Page is indexed and eligible to appear in results
• URL is on Google, but has issues — Indexed but with warnings (e.g., missing structured data)
• URL is not on Google — Not indexed, with a specific reason (noindex, crawl anomaly, etc.)

Limitations

You can only inspect URLs for properties you own and have verified. There is a daily quota (roughly 50 inspections per day per property). This method is excellent for spot-checking but impractical for large-scale audits.

Method 3: Google Search Console Coverage Report

The Pages report (formerly "Coverage") in GSC gives you a aggregated view of all indexed and non-indexed URLs on your site. It groups URLs by status and reason, making it ideal for identifying patterns.

Step-by-Step

1. Open Google Search Console and navigate to Indexing → Pages in the left sidebar
2. Review the "Indexed pages" tab for successfully indexed URLs
3. Click the "Not indexed" tab to see excluded URLs
4. Click on any specific reason (e.g., "Discovered — currently not indexed") to see affected URLs
5. Export the list for further analysis by clicking the export button

Key statuses to watch for:

• Submitted and indexed — Your best-case scenario for important pages
• Indexed, not submitted in sitemap — Indexed but you should add it to your sitemap
• Discovered — currently not indexed — Google knows about it but hasn't crawled yet
• Crawled — currently not indexed — Google crawled but decided not to index
• Page with redirect — URL redirects; no action needed
• Excluded by 'noindex' tag — Intentionally excluded

Method 4: IndexLens Bulk Index Checker

When you need to check hundreds or thousands of URLs at once, manual methods break down. IndexLens lets you paste a list of URLs (or upload a CSV) and get batch indexing status in seconds — no GSC property access required.

Step-by-Step

1. Navigate to the IndexLens Index Status Checker
2. Paste your URLs (one per line) or upload a CSV file
3. Click Check Index Status
4. Review the results table showing indexed / not indexed for each URL
5. Export results as CSV for reporting or further action

Method Comparison

Choosing the right method depends on your use case. Here is a quick summary:

Frequently Asked Questions