Search Console: Find and Fix Indexing Problems

Most website problems that affect search traffic are quiet. A template change adds a noindex tag, a redirect sends old posts to the wrong place or a batch of new pages is found but never indexed. Nobody notices until traffic has already dropped. Google Search Console is the free tool that shows how Google crawls, indexes and displays your site, and it is where many of these problems appear first. This guide explains how to use Search Console as a monitoring and troubleshooting tool: which reports to watch, what the common page indexing statuses mean, how to investigate a single URL and how to confirm that a fix has worked.

What Search Console tells you

Search Console is Google's own view of your site. It shows which pages are indexed and why others are not, how often your pages appear in search results and how many clicks they receive, and whether Google can fetch and render individual pages. Because it reports Google's data rather than your analytics, it explains things your own tools cannot, such as pages that are excluded from the index.

Set it up for every version of your site that matters, and give access to the people who own content, development and SEO, so that the right person sees each problem.

The Performance report

The Performance report shows how your site does in Google Search. Its help page defines the main metrics: clicks, the number of times a user clicked through to your site from search results; impressions, how many times your site appeared in results; CTR, clicks divided by impressions; and average position, the average position of the topmost result from your site (Search Console Help: Performance report).

Use it to spot changes. A sharp fall in impressions for a group of pages often points to an indexing or technical problem. A fall in clicks with stable impressions may point to changed titles or descriptions, or to different results appearing above yours.

The Page indexing report

The Page indexing report lists which of your pages are indexed and gives a reason for each page that is not (Search Console Help: Page indexing report). A few statuses come up often:

• Crawled, currently not indexed: Google crawled the page but did not index it. The help page says it may or may not be indexed in the future and there is no need to resubmit it.
• Discovered, currently not indexed: Google found the page but has not crawled it yet. The help page says this is typically because crawling was expected to overload the site, so it was rescheduled.
• Duplicate without user-selected canonical: the page duplicates another, does not indicate a preferred canonical and Google has chosen the other page.
• Page with redirect: a non-canonical URL that redirects to another page and will not itself be indexed.
• Not found (404): the page returned a 404 when requested.

Not every status needs fixing. The help page itself notes that URLs blocked by robots.txt, for example, are probably blocked on purpose. Focus on pages you want indexed that are not.

Investigate one page with URL Inspection

When a specific page is missing or behaving oddly, the URL Inspection tool shows Google's view of it (Search Console Help: URL Inspection tool). Its help page lists what it can do, including showing why Google could or could not index a page, testing a live URL to see whether it might be indexable, requesting indexing for a URL and viewing a rendered version of the page.

Compare the indexed version with the live test. If the live page looks correct but the indexed version does not, Google may simply not have recrawled it yet. If the live test shows a problem, such as a noindex tag or a blocked resource, you have found the cause.

Worked example: a monthly Search Console check

The table below is a hypothetical monthly routine for a B2B company blog. It shows what to look at and what action each finding leads to.

ReportWhat to look forExample findingActionPerformancePages or queries with large dropsImpressions fell for a group of older postsCheck indexing status for those URLsPage indexingRise in any non-indexed statusMore pages marked duplicate without user-selected canonicalMerge near-duplicates and set canonicals or redirectsPage indexingImportant pages not indexedNew service page crawled but not indexedImprove content and internal links; inspect URLURL InspectionLive test versus indexed versionTemplate added noindex to one categoryRemove noindex; request indexingSitemapsErrors or unexpected countsSitemap lists redirected URLsRegenerate with canonical URLs only

Keep notes from each check. Trends over several months reveal problems that a single snapshot hides.

Validate fixes properly

After fixing an issue shown in the Page indexing report, you can ask Google to check the fix. The help page explains that you click Validate fix, and should not click it again until validation has succeeded or failed. Google then rechecks the affected URLs over time. It also notes that you can fix issues without validating, because the counts update whenever Google crawls the affected pages.

Validation is useful for confirming that a sitewide problem, such as a broken template, is resolved. For one-off pages, URL Inspection and a request for indexing are usually enough.

Connect Search Console to your release process

Many indexing problems start with a release: a new template, a change to robots.txt, a migration to new URLs. Add a short Search Console check to your release checklist for significant site changes, and look again a week or two later. Our technical SEO checklist covers the settings worth checking before and after a release, and our guide to the XML sitemap explains how to keep the sitemap in step with the site.

Share the right reports with the right people

Search Console data is useful beyond the SEO team. Developers should see indexing and rendering issues. Content owners should see which pages earn impressions and which are excluded as duplicates. Leadership needs a simple trend of clicks and indexed pages. A short monthly summary, with one or two actions for each group, keeps everyone working from the same evidence.

Frequently Asked Questions

What is Google Search Console used for?

It shows how Google crawls, indexes and displays your site, including search performance, indexing status, page-level inspection and sitemap processing.

What does crawled but not indexed mean?

Google crawled the page but chose not to index it. Search Console's help page says it may be indexed later and there is no need to resubmit it.

How do I check why one page is not indexed?

Use the URL Inspection tool. It shows Google's indexed view of the page, lets you test the live URL and lets you request indexing once the page is fixed.

Do I need to validate every fix?

No. Validation helps confirm sitewide fixes. Search Console also updates counts as Google recrawls pages, even without a validation request.

Catch search problems early

We set up Search Console monitoring, investigate indexing issues and fix the technical causes on your site. See our technical SEO and content publishing service, or talk to us about Search Console.

About the Author

Manav Sharma is the founder of Insyrge and a CRM solutions architect. He works across Zoho, Salesforce, HubSpot, Odoo and more, designing the CRM setups, integrations and automations that keep sales and operations teams working from the same data.