Google Search Console is the most direct window into how Google sees your website. One of its most useful features is the Pages report, which shows which URLs are indexed and which are not, along with the reasons. Some reasons are perfectly normal, while others point to real problems that prevent important pages from appearing in search.
This guide explains the most common crawl and indexing issues, which ones you need to worry about and how to fix them step by step.
Where to Find Crawl Errors
In Search Console, go to Indexing and then Pages. You will see a chart of indexed and not indexed pages and a table listing reasons why pages are not indexed. Click any reason to see example URLs. Use the URL Inspection tool to check an individual page in detail, including whether it is indexed, its canonical and how Google rendered it.
Common Issues and How to Fix Them
| — | — | — |
|---|---|---|
| Not found (404) | The URL returns a 404 error | Only if the page should exist or has links |
| Server error (5xx) | Server failed to respond properly | Yes, investigate quickly |
| Redirect error | Redirect loop, chain too long or broken | Yes |
| Blocked by robots.txt | Crawling is disallowed | Only if the page should be crawled |
| Duplicate without user-selected canonical | Google sees duplicates with no canonical | Add canonical tags |
| Crawled – currently not indexed | Google crawled but chose not to index | Often a quality signal |
| Discovered – currently not indexed | Google knows the URL but has not crawled it yet | Often normal for new pages; check site quality and links |
| Soft 404 | Page looks empty or like an error but returns 200 | Yes, fix content or status code |
Fixing 404 Errors
404 errors are normal when pages are deleted, but they matter when:
- Other pages on your site link to the missing URL
- External sites link to it
- It was an important page that should still exist
Fix internal links pointing to 404 pages. If the page moved or has a close replacement, set up a 301 redirect. If it was removed intentionally and has no replacement, a 404 or 410 status is fine.
Fixing Server Errors (5xx)
Server errors mean Googlebot could not access the page because your server failed. Common causes include overloaded hosting, plugin conflicts, firewall rules blocking bots or temporary outages. Check your hosting status and error logs, deactivate problematic plugins, review security settings and consider upgrading hosting if errors are frequent.
Fixing Redirect Errors
Redirect errors occur when redirects loop back to themselves, chain through too many URLs or point to broken destinations. Use a redirect checker to trace the path of the problem URL. Update redirects so each old URL points directly to its final destination and update internal links to the final URL.
Fixing Noindex Problems
If important pages are excluded by noindex, check your SEO plugin settings for that page, its post type and taxonomy. Also check the WordPress Reading setting that discourages search engines. Remove the noindex and request indexing through URL Inspection.
Fixing Robots.txt Blocks
If key pages are blocked by robots.txt, edit the file to remove the incorrect rule. Use the robots.txt report in Search Console to confirm Google has fetched the updated version.
Fixing Soft 404s
A soft 404 happens when a page returns a normal 200 status but looks like an error or has almost no content. Examples include empty category pages, “no results” pages or thin product pages. Either add meaningful content or return a proper 404 or 410 status. Redirect if there is a clear replacement.
Dealing with “Crawled – Currently Not Indexed”
This status means Google visited the page but decided not to index it, at least for now. Common reasons include:
- Thin or low-value content
- Content very similar to other pages
- Weak internal linking suggesting the page is unimportant
- Overall site quality concerns
Improve the page by adding depth and unique value, merge it with similar content, strengthen internal links from relevant pages and make sure it is included in your sitemap. Then request indexing.
Dealing with “Discovered – Currently Not Indexed”
Google knows the URL exists but has not crawled it yet. For new sites, this is common and often resolves over time. If it persists, improve internal linking, reduce low-value URLs that waste crawl resources and focus on publishing high-quality content that earns links.
Validating Fixes
After fixing an issue, return to the Pages report, open the issue and click “Validate fix”. Google will recheck the affected URLs over the following days or weeks and report whether the problem is resolved.
A Monthly Search Console Routine
- Check the Pages report for new or growing issues
- Review the Core Web Vitals and HTTPS reports
- Look at Manual Actions and Security Issues
- Inspect a few important new pages to confirm indexing
- Review Performance for sudden changes in clicks or impressions
Frequently Asked Questions
Do 404 errors hurt my rankings?
Not by themselves. They only matter if important pages or links lead to them.
Should I redirect every 404 to the homepage?
No. Redirect only to a relevant replacement. Redirecting unrelated pages to the homepage can be treated as a soft 404.
How long does validation take?
It can take from a few days to several weeks depending on the number of URLs and how often Google crawls your site.
Why are my new pages not indexed?
New pages may need time. Make sure they are linked internally, included in the sitemap and offer unique value.
Is “Page with redirect” an error?
Usually not. It simply reports that the URL redirects elsewhere.
Can I force Google to index a page?
You can request indexing through URL Inspection, but Google still decides whether the page is worth indexing.
Conclusion
Crawl errors are signals, not disasters. Focus on the URLs that matter, fix technical blockers such as server errors, redirect problems, noindex mistakes and robots.txt blocks, and improve content that Google chooses not to index. Check Search Console regularly, and your site will stay healthy and visible.
