Submitting a sitemap to Google doesn't guarantee your pages will be indexed. Google decides whether to index a page based on its quality, crawl budget, and technical signals — and there are at least a dozen reasons it might decline. The good news is that Google Search Console tells you exactly what's happening for every URL. This guide walks through each issue category and how to fix it.
Start With the Page Indexing Report
In Google Search Console, go to Indexing → Pages. This report shows every URL Google has found on your site and groups them into why they are or aren't indexed. In 2026, the interface organises issues into three main categories under "Why pages aren't indexed". Click any category to see the specific URLs affected.
Use the URL Inspection tool (type any URL in the search bar at the top) to get a per-page diagnosis. It shows the last crawl date, whether the page is indexed, and any specific reason it's not.
Issue 1 — "Discovered — Currently Not Indexed"
Google found the URL (from your sitemap or by following a link) but has chosen not to crawl it yet. This is usually a crawl budget issue. Google doesn't have infinite crawl budget — on large or low-authority sites, it deprioritises pages it considers less important.
What to do:
- Make sure the affected pages are linked from other indexed pages on your site. Orphan pages (no internal links pointing to them) get deprioritised.
- Remove low-quality or thin pages from your sitemap so Google doesn't have to evaluate as many URLs. A smaller, cleaner sitemap improves crawl efficiency.
- Check your overall site health — a high percentage of 404s and redirects in your sitemap signals poor site quality and reduces the budget Google allocates to you.
- Use the URL Inspection tool → Request Indexing for high-priority pages. This puts them into Google's crawl queue faster, though it's not instantaneous.
Issue 2 — "Crawled — Currently Not Indexed"
Google crawled the page but decided not to index it. This is a content quality signal — Google visited the page and judged it wasn't worth indexing. Common causes:
- Thin content — pages with very little substantive text, boilerplate copy, or low information density. Add meaningful content that answers a real question.
- Duplicate content — the page is substantially similar to another page on your site or elsewhere on the web. Consolidate or differentiate, and use canonical tags to signal the preferred version.
- Soft 404 — the page returns HTTP 200 but the content says something like "no results found" or "out of stock" with very little other content. Either enrich the page or return a proper 404 for truly empty pages.
- Crawled too recently — sometimes this resolves on its own as Google re-evaluates the page. If content is genuinely good, wait a few weeks and check again.
Issue 3 — "Blocked by robots.txt"
A Disallow rule in your robots.txt is preventing Googlebot from accessing the page. This is only a problem if the page is in your sitemap and you want it indexed — having it in both is a contradiction.
Fix: Either remove the Disallow rule from robots.txt (if the page should be indexed) or remove the URL from your sitemap (if the page should remain blocked). Never include a blocked URL in your sitemap.
Issue 4 — "Page with Redirect"
The URL in your sitemap redirects to a different URL. Google indexes the destination, not the source. If the redirect is intentional, update your sitemap to list the destination URL directly. If you see a large number of these, your sitemap is likely outdated — regenerate it from a fresh crawl.
Issue 5 — "noindex Tag Detected"
A <meta name="robots" content="noindex"> tag is on the page. Google found it and respected it. If the page should be indexed, remove the tag. This often happens after a migration where staging environment noindex tags weren't removed before going live.
Issue 6 — "Alternate page with proper canonical tag"
Google treats this URL as a duplicate and is indexing a different canonical version instead. Check the rel="canonical" tag in the page source. If it points to a different URL intentionally, this is expected behaviour — remove the duplicate from your sitemap and list only the canonical URL.
Issue 7 — Server Blocking Googlebot
If Googlebot is being blocked at the server or CDN level (firewall rules, security plugins, Cloudflare settings), your pages will never get crawled regardless of your sitemap. Use the URL Inspection tool to "Test Live URL" — if it returns an error like "Couldn't fetch", the issue is server-side. Check your firewall and security plugin settings to ensure Googlebot's IP ranges are not blocked.
A Faster Route to Indexing
Beyond fixing errors, there are a few things that speed up Google's discovery and evaluation:
- Internal links — pages with more internal links pointing to them get crawled faster. Link to important new content from your homepage, navigation, or related posts.
- External links — a link from a high-authority external site is the fastest known way to get a new page indexed.
- Accurate lastmod in your sitemap — when Google sees a recent, accurate lastmod date on a URL, it prioritises re-fetching it.
- Clean sitemap — remove 404s, redirects, and noindex pages so Google spends all its budget on the pages that matter.