How to Check If Google Has Indexed Your Site (And Force Faster Indexing)
You published a page a week ago. It is not showing up in Google. You search for your own brand name plus the page title and get nothing. Is something broken, or is Google just slow?
Indexing problems are one of the most common and most frustrating technical SEO issues, largely because they are invisible. A page can look perfect, load fast, and read well — and still be entirely absent from Google’s index because of a single line in a robots file or a stray meta tag.
This guide shows you how to verify exactly what Google has indexed, diagnose why specific pages are missing, and use the methods that genuinely accelerate indexing.
site:yourdomain.com/page-url/. If a page is not indexed, diagnose the blocker (noindex tag, robots.txt rule, canonical, thin content, or no internal links), fix it, then use Request Indexing and add internal links from already-indexed pages.Key Takeaways
- Crawling and indexing are different — a page can be crawled and still not indexed.
- Google Search Console’s URL Inspection tool is the only authoritative source for indexing status.
- The
site:operator gives an approximate picture, not an exact index count. - Most indexing failures trace back to a noindex tag, a robots.txt rule, or a canonical pointing elsewhere.
- Internal linking is the single most underrated accelerator of indexing for new pages.
- Requesting indexing prioritises a crawl but never overrides a blocking directive.
Crawling vs Indexing: Why the Distinction Matters
These two terms get used interchangeably, and that confusion causes a lot of wasted troubleshooting.
- Crawling is Googlebot fetching your page and reading its content.
- Indexing is Google deciding to store that page in its index so it can appear in search results.
A page can be crawled and then rejected for indexing — Google read it and decided it was duplicate, thin, or not worth storing. Conversely, a page can be indexed without being fully crawled if Google has strong external signals about it but is blocked from reading the content itself.
This distinction determines your fix. A crawl problem means Googlebot cannot reach the page. An indexing problem means Googlebot reached it and declined. Different causes, different solutions.
Three Ways to Check Indexing Status
1. The site: Search Operator (Quick Check)
Search Google for site:yourdomain.com to see an approximate list of indexed pages from your domain. To check a specific page, use site:yourdomain.com/specific-page-url/.
What this tells you: whether Google has that URL at all. What it does not tell you: the exact index count (the number Google displays is a rough estimate), why a page is missing, or when it was last crawled.
Use a Google Index Checker to run this check across multiple URLs at once rather than searching them individually — useful when auditing a batch of new posts.
2. Google Search Console URL Inspection (Authoritative)
This is the definitive method. In Google Search Console, paste any URL from your verified property into the inspection bar at the top.
The report tells you:
- Whether the URL is on Google
- When Googlebot last crawled it
- Which URL Google selected as canonical (this may differ from yours)
- Whether crawling was allowed and indexing was allowed
- Any detected structured data or mobile usability issues
If the page is not indexed, this report names the specific reason — which is exactly what you need to fix it.
3. The Pages Report (Site-Wide View)
In Search Console, go to Indexing → Pages. This splits your URLs into indexed and not-indexed, with a reason listed for every excluded page.
| Status Reason | What It Means | Action |
|---|---|---|
| Excluded by noindex tag | The page carries a noindex directive | Remove the tag if the page should rank |
| Blocked by robots.txt | A disallow rule prevents crawling | Edit robots.txt to allow the path |
| Alternate page with proper canonical | Working as intended — a duplicate pointing to its canonical | Usually no action needed |
| Duplicate, Google chose different canonical | Google overrode your canonical choice | Strengthen the intended canonical with internal links |
| Discovered — currently not indexed | Google knows the URL but has not crawled it | Add internal links, improve content depth |
| Crawled — currently not indexed | Google read it and declined to index | Improve content quality and uniqueness |
| Soft 404 | Page returns 200 but looks empty to Google | Add real content or return a proper 404 |
| Page with redirect | URL redirects elsewhere | Expected — ensure the target is indexed |
Why Pages Do Not Get Indexed: Diagnosis
The Noindex Tag
A <meta name="robots" content="noindex"> tag in the page head tells Google explicitly not to index the page. This is the most common cause of unexpected indexing failure, and it usually gets applied accidentally — a staging site setting carried into production, or WordPress’s “Discourage search engines” checkbox left enabled after launch.
Check it in WordPress under Settings → Reading, and verify the rendered output with a Meta Tags Analyzer.
Robots.txt Disallow Rules
A disallow rule in robots.txt blocks Googlebot from crawling a path entirely. Note the important nuance: a blocked page can still be indexed if other sites link to it — Google just cannot read the content, so it indexes a bare URL with no description.
Review your rules against our guide to robots.txt rules, examples, and common mistakes, and verify what crawlers actually see using a Search Engine Spider Simulator.
Canonical Tags Pointing Elsewhere
If page A carries a canonical tag pointing to page B, you have told Google that B is the version worth indexing. A will typically be excluded. This is correct behaviour when intended and a serious problem when it is a templating error applying one canonical across many pages.
Thin or Duplicate Content
“Crawled — currently not indexed” usually means Google read the page and judged it insufficiently valuable or too similar to existing content. The fix is editorial, not technical: add depth, original insight, and genuine differentiation. See our content quality checklist and our guide to duplicate content and SEO.
No Internal Links (Orphan Pages)
Googlebot discovers URLs primarily by following links. A page with no internal links pointing to it — an orphan page — may sit undiscovered indefinitely, even if it is listed in your sitemap. Sitemaps assist discovery; internal links drive it.
Server Errors and Slow Response
If Googlebot encounters 5xx errors or extremely slow responses, it reduces crawl frequency to avoid overloading your server. Check your server response with a Server Status Checker and address speed issues using our guide on how to fix slow page speed.
How to Force Faster Indexing
Ranked by actual effectiveness:
1. Add Internal Links from Indexed Pages (Most Effective)
Link to the new page from pages Google already crawls frequently — your homepage, a high-traffic blog post, or a category hub. This is consistently the fastest and most reliable way to get a new URL discovered and indexed.
2. Request Indexing in Search Console
Use the URL Inspection tool and click Request Indexing. This adds the URL to a priority crawl queue. There is a daily quota, so reserve it for genuinely important pages. It prioritises a crawl but will not override a noindex tag or robots.txt block.
3. Keep Your XML Sitemap Clean and Current
Your sitemap should list every URL you want indexed and nothing else — no redirects, no noindexed pages, no 404s. A sitemap full of errors reduces the trust Google places in it. Generate a clean one with an XML Sitemap Generator and resubmit it in Search Console after major content additions.
4. Improve Crawl Efficiency
Every crawl request Googlebot spends on a redirect chain, a parameter duplicate, or a broken link is a request not spent on your real content. Fix redirect chains, consolidate duplicates with canonicals, and remove low-value URLs from your sitemap.
5. Earn External Links
A link from an external site that Google crawls frequently is a strong discovery signal. This is slower to arrange than internal linking but valuable for important pages.
6. Ping Search Engines (Minor)
An Online Ping Tool notifies services that your content has updated. The effect is minimal compared to the methods above, but it costs nothing. Treat it as a supplement, never a strategy.
Checking Google’s Cached Version
A cached copy confirms Google successfully crawled and stored your page, and shows you the version it holds. If the cache is weeks old on a page you have recently updated, Google has not recrawled since your changes — requesting indexing will refresh it.
Use a Google Cache Checker to see the cache date for any URL. If no cache exists at all, the page is very likely not indexed.
Common Mistakes
- Assuming the site: count is exact. It is a rough estimate. Use Search Console’s Pages report for accurate numbers.
- Requesting indexing repeatedly instead of fixing the blocker. If a noindex tag is present, you can request indexing a hundred times and nothing will change.
- Leaving the WordPress search-engine discouragement setting on after launch. This single checkbox blocks an entire site from indexing and is one of the most common launch mistakes.
- Submitting a sitemap full of redirects and 404s. This wastes crawl budget and lowers the trust Google places in your sitemap.
- Panicking about tag and archive pages not being indexed. Google filtering low-value archive pages is normal and usually desirable.
- Ignoring orphan pages. If nothing links to a page, it will struggle to get indexed regardless of how good the content is.
Expert Tips
- Link every new post from an existing indexed page on publish day. Make this a standard step in your publishing workflow — it consistently cuts indexing time.
- Audit the Pages report monthly. Watching the not-indexed reasons over time reveals systemic issues (a templating error, a bad canonical rule) far earlier than waiting for traffic to drop.
- Check the Google-selected canonical, not just your own. URL Inspection shows both. When they disagree, Google has overridden you — and that is worth investigating.
- Use Request Indexing after significant content updates, not just for new pages. It prompts a recrawl so your improvements are reflected in the index sooner.
- Watch for a rising Discovered — currently not indexed count. A growing number here usually signals crawl budget strain from too many low-value URLs.
Indexing Action Checklist
- ☐ Run
site:yourdomain.comfor a directional index check - ☐ Inspect key URLs individually in Google Search Console
- ☐ Review the Indexing → Pages report and note all exclusion reasons
- ☐ Verify no unintended noindex tags are present on important pages
- ☐ Confirm WordPress search engine visibility setting is enabled
- ☐ Review robots.txt for overly broad disallow rules
- ☐ Check canonical tags resolve to the intended URLs
- ☐ Confirm the XML sitemap contains only indexable, live URLs
- ☐ Resubmit the sitemap in Search Console
- ☐ Add internal links to any orphan pages
- ☐ Request indexing for high-priority pages
- ☐ Verify server returns 200 with acceptable response times
Frequently Asked Questions
How do I check if Google has indexed my page?
The most reliable method is the URL Inspection tool in Google Search Console — paste the exact URL and it reports whether the page is indexed, when it was last crawled, and any blocking issues. For a quick check without Search Console, search site:yourdomain.com/page-url/.
How long does it take Google to index a new page?
It varies from a few hours to several weeks. Established sites that publish frequently and link internally often see pages indexed within 24–48 hours. New sites with few backlinks may wait several weeks. Requesting indexing and adding internal links both accelerate the process.
Why is my page not being indexed by Google?
The most common causes are a noindex meta tag, a robots.txt disallow rule, a canonical tag pointing to a different URL, a redirect, thin or duplicate content Google chose not to index, or no internal links pointing to the page so Googlebot never discovered it.
What does “Discovered — currently not indexed” mean?
Google knows the URL exists but has not crawled it yet, usually due to crawl budget prioritisation or a judgement that the page is unlikely to add value. Fix it by strengthening internal links, improving content depth, and ensuring the page is in your sitemap.
Does requesting indexing in Search Console guarantee it?
No. Requesting indexing adds the URL to a priority crawl queue, but Google still decides whether to index based on content quality, duplication, and crawl budget. If a blocking issue such as a noindex tag exists, requesting indexing will not override it.
How many pages should Google have indexed?
Ideally every page you want in search results and none that you do not. Compare your indexed count against your sitemap URL count. A large gap suggests either indexing problems or that Google is filtering low-value pages such as tag archives and parameter variants.
What is the difference between crawling and indexing?
Crawling is Googlebot fetching and reading a page. Indexing is Google storing and organising that page so it can appear in results. A page can be crawled but not indexed if Google judges it duplicate, thin, or low value. Both must happen for a page to rank.
Does pinging search engines still help indexing?
Pinging has minimal effect compared to Search Console’s Request Indexing and a properly maintained XML sitemap. It costs nothing and does no harm, but should never be your primary indexing strategy.
Conclusion
Indexing problems are usually simple once diagnosed — a single tag, one robots.txt line, or a missing internal link. The difficulty is that they are silent. Nothing on the page looks wrong; it simply never appears in search.
Make indexing verification a routine step, not an emergency response. Check the Pages report monthly, inspect important URLs after publishing, and always link new content from an existing indexed page on day one.
If your pages are not getting indexed and you cannot identify why, EW Marketings can run a full technical audit covering crawlability, indexation, and server health. Request a free consultation to get a clear diagnosis.
Summary
- Use Search Console’s URL Inspection tool for authoritative indexing status;
site:is only a quick check. - Crawling and indexing are separate — identify which one is failing before attempting a fix.
- Most indexing failures trace to a noindex tag, robots.txt rule, canonical conflict, or thin content.
- Internal linking from already-indexed pages is the most effective way to speed up indexing.
- Request Indexing prioritises a crawl but never overrides a blocking directive — fix the blocker first.