Why Google Won't Index Your Pages: A Plain-English Breakdown of GSC's 4 Most Common Errors

If you have been inside Google Search Console recently and clicked into the Pages report (previously called Index Coverage), you may have seen a section titled "Why pages aren't indexed." That list tells you exactly which URLs Google found on your site but chose not to add to its search index, and the reason for each one.

This is not abstract SEO theory. Pages that are not indexed cannot rank. If Google is excluding pages from your site, you are losing search visibility you should have, and the reason is usually fixable once you understand what Google is actually telling you.

This post covers the four most common "not indexed" statuses small business websites encounter, what each one means in plain terms, and the exact steps to resolve it.

1. Page With Redirect

What it means: Google followed one of your URLs and landed on a different URL because a redirect was in place. The original URL is not indexed. Only the final destination URL is eligible to be indexed.

This status is usually caused by one of three things:

• Old URLs still listed in your XML sitemap that have since been redirected (common after a site redesign or domain migration)
• HTTP versions of pages listed in your sitemap when the live site runs on HTTPS
• Trailing-slash inconsistencies, where your sitemap lists yoursite.com/page but the server redirects to yoursite.com/page/

The redirect itself is not necessarily a problem. A 301 redirect is the correct way to permanently move a page. The issue is that Google's crawler is spending time and crawl budget following chains to find the real URL, and your sitemap or internal links are pointing to the wrong address.

How to fix it:

Open the flagged URLs in the Pages report and note where each one redirects. Then make those two changes:

1. Update your XML sitemap to list the final destination URL directly, removing any URL that redirects instead of serving a page.
2. Find all internal links pointing to the old URL and update them to point to the final destination.

Once both are done, resubmit your sitemap through GSC and request re-indexing of the destination URL using the URL Inspection tool. The redirect URLs will typically clear from the report within the next few crawl cycles.

If you are on Next.js, check your next.config.js redirects array and your sitemap generation logic. A common mistake is having sitemap.ts export the pre-redirect version of a URL rather than the canonical final version.

2. Alternate Page With Proper Canonical Tag

What it means: Google found this page, crawled it, and saw that it contains a canonical tag pointing to a different URL. Google is respecting your instruction and indexing the canonical URL instead. This page intentionally is not indexed.

The canonical tag (<link rel="canonical" href="..." />) is how you tell Google: "This URL exists, but this other URL is the authoritative version. Index that one." It is commonly used for:

• Paginated content (page 2, page 3 of a blog index)
• Product pages accessible through multiple URL paths (filter or sort parameters)
• Content syndicated to multiple URLs

In most cases, this status is expected and correct. If the page Google is flagging truly is a duplicate or an alternate version of another page, and the canonical tag points to the right primary URL, no action is needed.

Where this becomes a problem:

The issue arises when the canonical tag is wrong. For example:

• A canonical tag accidentally points to a 404 URL
• A canonical tag points back to the same page (self-referencing canonical, which is fine) but the intent was to point to a completely different primary page
• A developer added a canonical to a page that should actually be indexed independently, blocking it unintentionally

How to fix it:

Use the URL Inspection tool in GSC to inspect the flagged URL. Look at the "Google-selected canonical" field. If it shows a URL you recognize as the correct primary version, this status is working as intended.

If the canonical target is wrong, locate the canonical tag in your site code (for Next.js, this is typically in the metadata.alternates.canonical export for each page) and correct the URL. After fixing the tag, request re-indexing of the corrected page through URL Inspection.

3. Crawled: Currently Not Indexed

What it means: Google crawled the page successfully. It was not blocked, it returned a 200 status code, and Google read the content. Then Google decided, based on its own quality assessment, not to add it to the index.

This is one of the more frustrating statuses because there is no explicit error to point to. Google's systems evaluated the page and concluded it was not worth including. The reasons Google makes that call typically come down to content quality signals:

• Thin content: The page has very little text or substantive information. A service page with two short paragraphs, no details about the service, and no original perspective is a common culprit.
• Duplicate or near-duplicate content: The page is substantially similar to another page on the same site or elsewhere on the web.
• Low engagement signals: Historical user data suggests visitors do not find the page useful.
• No inbound links: Google has not seen any other sites or pages linking to this URL, making it harder for Google to assess its relevance and authority.

How to fix it:

Start by inspecting the flagged URLs in GSC and reviewing the actual pages. Ask honestly whether each one provides something useful that a visitor could not get from a hundred similar pages. If the answer is no, that is your starting point.

For each flagged page:

1. Expand the content. Add original depth: specific details, practical steps, examples, data, or your business's direct perspective. A service page should explain what the service includes, who it is for, how it works, and what outcomes to expect, not just two sentences and a call-to-action button.
2. Add internal links pointing to the page from related posts or other pages on your site. Internal linking signals to Google that the page is part of your site's content structure.
3. If the page genuinely cannot be expanded (a standalone landing page, for example), consider whether a noindex tag is more appropriate than leaving it in a permanent "crawled but not indexed" limbo.

After making content improvements, use the URL Inspection tool to request re-indexing. Give Google a few weeks to re-evaluate before drawing conclusions.

"Crawled, currently not indexed is Google's way of telling you the page exists but is not earning its place in the index yet. The solution is almost always adding more value to the page itself."

4. Discovered: Currently Not Indexed

What it means: Google found out about this URL (through your sitemap, a link from another page, or both) but has not yet crawled it. It is in the queue, but Google has not gotten to it.

This status is less urgent than the others because no quality judgment has been made yet. Google simply has not visited the page. The reason for the delay is usually crawl budget. Every site is allocated a certain amount of crawl activity based on its authority and server responsiveness. Sites with lower domain authority or infrequent content updates get crawled less often, meaning new pages can sit in the queue for days or weeks.

How to fix it:

The fastest path is the URL Inspection tool. Look up the flagged URL and click "Request Indexing." This puts the URL at the front of Google's crawl queue and typically results in a crawl within a day or two for most sites.

Beyond the immediate request, the longer-term fix is improving the signals that tell Google your site deserves more frequent crawling:

• Add internal links to the new page from existing, already-indexed pages. A link from an indexed page gives Google a path to discover and prioritize the new one.
• Make sure the URL is included in your submitted sitemap. GSC's Sitemaps report shows whether the URL was included and whether it was processed.
• Publish content consistently. Sites that update regularly train Google's crawlers to return more often.

The Validation Workflow: After You Fix an Issue

After resolving any of these statuses, GSC lets you formally submit the fix for validation. In the Pages report, open the specific issue category and click "Validate Fix." Google will then re-crawl the affected URLs to confirm the problem is resolved.

Validation takes time. For small sites, expect the process to take one to four weeks for a full resolution. The status will move from "Started" to "Passed" once Google confirms the fix across all affected URLs.

Do not re-validate before the underlying issue is actually fixed. Submitting a premature validation request and having it fail can reset the validation timeline and delay resolution.

Putting It Together: The Indexing Audit Workflow

If you open the Pages report today and see URLs in any of these categories, here is the sequence to work through them:

1. Identify every flagged URL for each status category.
2. For each URL, use the URL Inspection tool to see what Google knows about it, including the last crawl date, the canonical Google selected, and any detected issues.
3. Apply the fix appropriate to the status: update the sitemap and internal links for redirects, verify or correct canonical tags for alternate page issues, expand content for crawled-not-indexed pages, and request indexing for discovered-not-indexed pages.
4. Resubmit your sitemap after making changes.
5. Submit the validation request in GSC and monitor the status over the following weeks.

The Pages report in GSC is one of the most actionable reports in SEO precisely because every entry represents a specific, identifiable problem with a specific fix. None of these errors are permanent if you understand what they are telling you and address them methodically.

If you are still early in your Google Search Console setup and want a full walkthrough of the tool before diving into the error reports, our earlier guide covers the complete GSC interface from setup through the Performance, Coverage, Core Web Vitals, and Links reports: Google Search Console Explained.