To fix Google Search Console errors, open the report that flags the problem, click an affected URL to run the URL Inspection tool, and read the exact reason Google gives. Then correct that root cause on the live page, whether it is a noindex tag, a 404, a redirect, a server fault, or thin content, and click Validate Fix so Google recrawls and confirms the issue is gone.
That single loop covers almost every warning you will meet. The rest of this guide walks through the most common Search Console errors one by one, explains what actually causes each, and gives you the precise steps to clear it. Every threshold and definition below comes from Google Search Central, so you are fixing to Google's own spec, not guesswork.
Before you touch a single line of code, know that nearly every fix follows the same five steps. Google Search Central frames the whole process around inspect, diagnose, correct, and validate, and it applies whether the error is an indexing problem, a redirect, or a Core Web Vitals failure.
The two tools you will live in are the Page indexing report (Indexing, then Pages in the left menu) and the URL Inspection tool (the search bar at the top). The report tells you which URLs are affected and groups them by reason. The inspection tool tells you why a single URL is stuck and lets you run a live test against the current version of the page after you fix it. If you are still learning what the surrounding numbers mean, our explainer on what impressions mean in Search Console pairs well with this guide.
Here is a reference table you can scan when an error appears. Each row names the status exactly as Google shows it, the usual cause, and the concrete fix. Definitions and the five-redirect limit come from Google Search Central.
| Error or status | Likely cause | Exact fix |
|---|---|---|
| Server error (5xx) | Server returned a 500-level response when Googlebot requested the page | Check the Crawl Stats host status, fix hosting or rate limiting, add capacity, then validate |
| Not found (404) | The URL is gone or never existed, but something links to it or it sits in your sitemap | Restore the page or 301 redirect it to the closest live page; remove dead URLs from the sitemap |
| Soft 404 | The page returns a 200 status but shows an empty or "not found" message | Return a real 404 or 410 for missing pages, or add genuine content if the page should exist |
| Redirect error | A redirect loop, a chain longer than five hops, or a malformed target URL | Point each redirect straight to the final URL in one hop; replace 302s with 301s where permanent |
| Blocked by robots.txt | A robots.txt rule disallows the URL | Remove or narrow the Disallow rule; use the robots.txt tester to confirm Googlebot is allowed |
| Excluded by 'noindex' tag | A noindex meta tag or X-Robots-Tag header sits on the page | Remove the noindex directive from the template, plugin, or header, then request indexing |
| Crawled - currently not indexed | Google fetched the page but judged it not worth indexing | Improve depth and uniqueness, consolidate duplicates, add internal links, then re-request |
| Discovered - currently not indexed | Google found the URL but has not crawled it yet | Strengthen internal links and the sitemap; raise overall site quality so crawl demand grows |
| Duplicate without user-selected canonical | Two similar URLs with no clear canonical signal | Add a self-referencing canonical to the version you want indexed and differentiate the content |
| Sitemap "Couldn't fetch" | Google cannot read the sitemap file | Confirm the URL loads, unblock it in robots.txt, fix XML errors, then resubmit |
These two look similar but need different fixes. "Discovered - currently not indexed" means Google knows the URL but has not crawled it yet, usually a crawl-budget or site-quality signal. "Crawled - currently not indexed" means Google fetched the page and chose to leave it out, which is almost always a content-quality or duplication signal. Google Search Central describes both as normal states that can resolve on their own, but on pages you care about you should act.
For "Crawled - currently not indexed", resist the urge to keep hitting Request Indexing. Google will simply re-evaluate the same weak page and reach the same verdict. Instead, make the page worth indexing: deepen the content so it fully answers the query, merge or remove near-duplicate pages competing with it, and add internal links from stronger, already-indexed pages so Google sees it as part of a real topic cluster. Only then request indexing again.
For "Discovered - currently not indexed", the lever is crawl demand. Add the URL to your XML sitemap, link to it from your main navigation or a high-traffic page, and stop flooding the site with thin, near-identical URLs that eat crawl budget. If a whole section is stuck, that is a sign your site-wide quality or internal linking needs work, which is exactly the kind of thing our SEO audit checklist is built to surface.
These are status-code problems, and they are usually the fastest wins because a single fix can clear many URLs at once. A "Not found (404)" only needs attention when you linked to the URL or listed it in a sitemap. Google Search Central is clear that an intentionally removed page returning a 404 is fine and does not need fixing.
Work through them like this:
After correcting a batch, use the live test in URL Inspection to confirm the new status code before you click Validate Fix. Fixing the code but forgetting to verify it is the most common reason a validation later fails.
Both of these mean you are actively telling Google to stay away, so the fix is to remove the instruction if the page should rank. "Excluded by 'noindex' tag" means Google found a noindex directive, either a robots meta tag in the HTML or an X-Robots-Tag in the HTTP header. "Blocked by robots.txt" means a Disallow rule stops Google from crawling the URL at all.
For a stray noindex, find where it comes from. On most sites it is a CMS setting, an SEO plugin toggle, or a staging rule that shipped to production by accident. Remove the directive, then run the live test in URL Inspection to confirm the noindex is gone before requesting indexing. For a robots.txt block, edit the file to remove or narrow the Disallow line, and use the robots.txt tester to confirm Googlebot is now allowed. One caution from Google Search Central: robots.txt does not reliably keep a page out of the index, because a URL linked from elsewhere can still appear. If you genuinely want a page hidden, use noindex and allow crawling so Google can see the noindex, rather than blocking it in robots.txt.
The Core Web Vitals report grades your URLs on real user experience, not lab tests. Google Search Central sets the "Good" thresholds at LCP under 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1, and a group of URLs only turns green when at least 75% of visits meet all three at once.
Match the fix to the failing metric. If LCP is slow, speed up the largest element on screen: compress and correctly size the hero image, serve it in a modern format, and remove render-blocking scripts and fonts. If INP is poor, the culprit is usually heavy JavaScript blocking the main thread, so defer or split non-critical scripts and cut third-party tags. If CLS is high, reserve fixed dimensions for images, ads, and embeds so nothing jumps as the page loads. Mobile Usability problems, where that report is present, tend to be text too small to read, tap targets too close together, or content wider than the screen, all fixed with a responsive layout and a correct viewport meta tag. Fix the underlying pages, wait for fresh field data to accumulate, then click Validate Fix.
"Couldn't fetch" means Google could not retrieve the sitemap file at all. Google Search Central lists the usual causes: the sitemap URL returns a 404, robots.txt blocks it, the server was briefly unavailable, low crawl demand delayed the read, or an unresolved manual action stopped sitemap processing entirely.
Diagnose it in order. First, open the sitemap URL in your browser to confirm it actually loads and returns valid XML. Second, run it through URL Inspection and check that "Crawl allowed?" says Yes and "Page fetch" says Successful. Third, remove any robots.txt rule blocking the sitemap path. Fourth, if the file is malformed, fix the XML, since Google will reject a sitemap with invalid syntax, wrong date formats, or a file over 50MB uncompressed. Once the file loads cleanly, resubmit it in the Sitemaps report. If you are building or rebuilding the file, our guide on how to make a sitemap covers the correct format so it validates the first time.
Fixing the page is only half the job. You still have to tell Google and wait for confirmation. After you correct every instance of an error, open the issue in the Page indexing report and click Validate Fix. Google Search Central explains that this recrawls the affected URLs and checks the problem is gone, and it emails you as the state moves from Started to Passed or Failed. Validation usually takes up to about two weeks, though it can run longer on large sites.
Two things speed this up. First, actually fix every affected URL before validating, because Google checks sample pages immediately and stops the whole run if it still finds the issue. Second, keep your sitemap tight: submit one that contains only your most important pages, then filter the report by that sitemap before requesting validation so Google prioritises the URLs that matter. If you want to understand which report reflects fixes and which reflects live traffic, our comparison of Google Search Console vs Google Analytics clears up where each number lives.
How do I fix errors in Google Search Console? Open the report showing the error, click a flagged URL to run the URL Inspection tool, and read the reason Google gives. Fix that root cause on the live page, whether it is a noindex tag, a 404, a redirect, a server fault, or thin content, then click Validate Fix. Google Search Central says validation recrawls the affected URLs and confirms the issue is gone, usually within about two weeks.
Why does Google Search Console say "Crawled - currently not indexed"? It means Google fetched the page but decided not to add it to the index, which is almost always a quality or duplication signal rather than a technical fault. The fix is to make the page genuinely more useful, remove or consolidate near-duplicate URLs, add internal links from related indexed pages, then request indexing again in the URL Inspection tool.
How do I fix "Discovered - currently not indexed"? This status means Google knows the URL exists but has not crawled it yet, often because it sees limited crawl value or reaches a crawl-budget limit. Strengthen internal links to the page, make sure it is in your XML sitemap, improve overall site quality so crawl demand rises, and avoid publishing large numbers of thin or near-identical URLs that dilute your crawl budget.
What does "Excluded by 'noindex' tag" mean and how do I fix it? It means Google found a noindex directive on the page, either a robots meta tag or an X-Robots-Tag HTTP header, so it kept the page out of the index. If you want the page indexed, remove the noindex directive from the page template, plugin, or server header, confirm it is gone using the live test in URL Inspection, then request indexing. If the page should stay hidden, no action is needed.
How do I fix a "Page with redirect" or redirect error? A plain "Page with redirect" status is informational and usually needs no action, because the redirect target gets indexed instead. A true redirect error means a loop, a chain longer than the five hops Google follows, or a malformed target URL. Fix it by pointing each redirect straight to its final destination in a single hop and replacing temporary 302 redirects with permanent 301s where the move is permanent.
How do I fix the sitemap "Couldn't fetch" error? Google Search Central lists a few causes: the sitemap URL returns a 404, robots.txt blocks it, the server was temporarily unavailable, or an unresolved manual action stopped sitemap reading. Open the sitemap URL in a browser to confirm it loads, test it with URL Inspection so Crawl allowed shows Yes and Page fetch shows Successful, remove any blocking robots.txt rule, then resubmit the sitemap.
What does "Validate Fix" do and how long does it take? Validate Fix tells Google you have resolved an issue so it recrawls the affected URLs and confirms the problem no longer appears. Google Search Central states validation usually takes up to about two weeks but can run longer, and it emails you as the state moves from Started to Passed or Failed. If Google finds the issue on a sample page, validation stops so you can fix the remaining pages.
How do I fix Core Web Vitals issues in Google Search Console? The Core Web Vitals report groups URLs as Poor, Needs improvement, or Good using real user data. Google Search Central sets the Good thresholds at LCP under 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1, and a URL group only earns Good when at least 75% of visits meet all three. Fix LCP by speeding up the main content, INP by trimming heavy JavaScript, and CLS by reserving space for images and ads, then click Validate Fix.
Do I need to fix every error in Google Search Console? No. Some statuses like "Alternate page with proper canonical" and "Page with redirect" are working as intended and need no action. Prioritise true Errors that block important pages, then warnings on pages you want ranked. Deliberately excluded, redirected, or canonicalised URLs can be left alone, so focus your time on pages that should be indexed but are not.
Start with the errors blocking pages you actually want to rank, work down the table above, and validate each fix before moving on. If a whole section of your site is stuck on "Crawled - currently not indexed" or your Core Web Vitals stay red no matter what you try, the problem is usually structural rather than a single page. That is where a full technical review pays off. Our complete SEO site audit traces every indexing and crawl issue back to its root cause and hands you a prioritised fix list, or request a free SEO audit from Rankite and we will show you which Search Console errors are costing you the most traffic first.
Get a free, no-obligation SEO audit and a 30-minute strategy session. We'll show you exactly where the growth is hiding.
Fill out the form and we'll get back to you within one business day. Prefer email? Write to us directly at contact@rankite.com.
