Google Search Console errors can look intimidating, especially when you see long lists of indexing problems, server errors, or soft 404s in your reports. But the reality is that most Google Search Console “errors” and “warnings” are status messages, not emergencies.
A lot of our clients are puzzled by the error and page indexing reports in Google Search Console, particularly things like server errors, soft 404 errors, and “crawled – currently not indexed”. They raise important questions:
- Is this hurting my organic search visibility?
- Which Google Search Console errors actually matter?
- What should I fix now vs. monitor over time?
The good news? Not every error, such as a one-off 5xx server error, is cause for concern, though repeated 5xx errors can affect crawling and visibility if left unresolved. In many cases, you can safely ignore informational entries unless they relate to important pages or critical technical issues that users and search engines depend on.
By the end of this guide, you’ll have clarity on:
- what these Google Search Console errors are,
- which ones matter, and
- how to handle common errors effectively.
We’ll walk through the most common GSC errors and exclusions, using our own website as a real-life example.
1. Common Google Search Console Errors
1.1 Pages with Redirects
At first glance, seeing “pages with redirects” under the Page Indexing report might induce panic—“1,210 pages not indexed due to redirect errors!? How can I fix this error to improve my page’s performance in Google search?
Take a deep breath. Most redirected URLs are normal and expected, especially after content updates, URL changes, or migrations. “Page with redirect” simply means Google found a URL that now redirects elsewhere, so it’s not going to index the old version, which can be checked via Google Search Console.
Think of it as a housekeeping note from Google, not a disaster.
“All these pages are basically Google saying, ‘We used to see a post or page here, but now it redirects somewhere else,’ which can sometimes be associated with soft 404 errors if redirects aren’t set up correctly.”
How to check and fix “Page with redirect”
Use the URL inspection tool in Google Search Console to verify that the redirect is working and points to the right page.
- Enter the URL in the search bar at the top of Google Search Console.
- Check the “Page with redirect” status and view the final URL.
- Confirm the final URL:
If that’s all true, you may need to identify and fix the issues you don’t need to “fix” these errors — Google is just documenting the redirects.
1.2 Alternative Page with Proper Canonical Tag
Another common entry in Google Search Console is “Alternative page with proper canonical tag.”
Canonical tags act as markers telling Google which version of similar or duplicate pages is the “master” version for indexing. This helps prevent duplicate content and consolidates ranking signals.
When you see this status, it usually means:
- Google found multiple versions of similar content (e.g. with tracking parameters, print views, or HTTP vs HTTPS).
- A canonical tag is present pointing to the preferred URL.
- Google is indexing the canonical page, and treating this alternative version as a non-indexed duplicate.
There’s nothing inherently problematic here — this is Google doing its job efficiently, as long as the canonical really does point to the right version.
“Google is saying, ‘We’ve seen this content on more than one page, and we’ve chosen another page with a canonical tag as the primary version.’ This page is treated as a duplicate and isn’t indexed on its own.”
When to review canonical-related issues
- If an important page is showing as an alternative, double-check your canonical tag setup and internal linking.
- Make sure the canonical URL is indexable, returns a 200 status, and matches the content you want to rank.
1.3 Excluded by ‘noindex’ Tag
Many sites, especially WordPress sites use plugins like Rank Math, SEOPress or Yoast which can help optimise your site for better performance in Google search results. Those plugins will naturally have some pages excluded by a noindex tag.
Common examples:
- Author archives
- Date-based archives
- Tag or category archives you don’t want indexed
- Thank-you pages or utility pages
Having a noindex tag isn’t inherently bad—it’s a strategic exclusion that helps Google focus on your important content.
What to do
- In Google Search Console, review the “Excluded by ‘noindex’ tag” report.
- Make sure any URL with issues is monitored within Google Search Console to find and fix errors and that the noindex reported page is not a key landing page you expect to rank.
- If a key page is mistakenly set to noindex, remove the tag and then click “Request indexing” in GSC to re-crawl it.
Key takeaway: Regularly check for technical issues and misconfigured noindex tags so you don’t accidentally prevent your best content from appearing in search.
1.4 Blocked Due to Access Forbidden (403)
You might also see statuses like “Blocked due to access forbidden (403)” or resources blocked by robots.txt.
This commonly occurs when:
- You have membership or logged-in sections,
- Protected client areas, or
- Files and pages that are intentionally restricted.
For private or members-only content, it’s perfectly fine for these URLs to be blocked or return 403/401 errors in Google Search Console. They shouldn’t be indexed if they trigger errors in Google Search Console.
Just confirm that:
- Public-facing content that should be indexed isn’t accidentally returning 403,
- Your robots.txt isn’t blocking key sections that you want Google to crawl.
1.5 404 Not Found
A 404 (Not Found) indicates that a page no longer exists at that URL.
This might happen when:
- You delete old blog posts or landing pages.
- Users remove profiles or user-generated content.
- URLs change without redirects.
A 404 isn’t automatically a problem for search engine crawlers. If the removal was intentional, it may lead to errors in search results. However, there are best practices:
- If there’s a clear equivalent or updated page, implement a search engine optimisation strategy 301 redirect from the old URL to the new one.
- If the content is genuinely gone and there’s no relevant replacement, a proper 404 status is acceptable. Pro tip: Use the URL inspection tool to check how Google sees the URL and confirm whether it’s returning a 404 or being handled as a potential error occurs that may affect indexing.
Pay attention when:
- You see a sudden spike in 404s after a migration or slug changes as this can indicate missing redirects.
- Important pages were deleted unintentionally or changed by someone without SEO oversight.
1.6 Crawled – Currently Not Indexed
When you see “Crawled – currently not indexed”, it means Google has crawled the page but decided not to index it (for now). This can be due to:
- Quality signals (thin or low-value content).
- Perceived duplication or lack of uniqueness.
- Google simply deciding the page isn’t useful enough to merit inclusion yet.
A few related statuses:
- “Discovered – currently not indexed” indicates that Google may not have crawled your page yet. – Google knows about the URL but hasn’t crawled/indexed it yet, sometimes due to crawl budget or site performance.
- “Duplicate, Google chose different canonical than user” – Google has selected a different URL as the primary canonical version.
What to watch for
If these are errors in Google Search Console pages you want to rank, and after a month or more they’re still not indexed, you should:
- Review the content depth and uniqueness.
- Check internal linking and sitemaps.
- Ensure there’s no conflicting noindex, canonical, or redirect setup.
Google is increasingly selective: only high-quality content gets crawled and indexed just because a page exists doesn’t mean it will be indexed. Pages that are too thin, duplicative, or not helpful might never be indexed.
Google’s focus on helpful, people-first content (aligned with E‑E‑A‑T principles) means you’ll get better indexing if your content demonstrates expertise, experience, authority, and trustworthiness.
2. Google Search Console Errors for Videos
Google Search Console can also report video indexing issues, such as when it can’t determine the prominent video on a page or shows “Video not found on host service,” which may affect search engine visibility.
Common causes:
- The video was removed or made private from the hosting platform.
- The video is buried in the layout and not considered “prominent” enough.
- Technical or rendering issues prevent Google from loading the video during crawl.
Example: “Video not found on host service”
This specific error usually means:
- The video ID or URL no longer exists on the host, or
- It’s on a private/unreachable hosting service.
What to do
- Visit the video on the hosting platform (e.g. Google) to find and fix any related issues. Vimeo, Wistia, YouTube) using the ID or URL.
- If it’s gone or private, Update your page to fix this error and improve its visibility in Google search results. to either:
- Embed a working video, or
- Remove the broken embed so Google isn’t trying to index a non-existent asset.
3. Page Experience Issues in Google Search Console
3.1 Core Web Vitals (LCP, INP, CLS)
Core Web Vitals are now a standard part of page experience reporting in Google Search Console, focusing on:
- LCP (Largest Contentful Paint) – loading speed
- INP (Interaction to Next Paint) – responsiveness
- CLS (Cumulative Layout Shift) – visual stability
Issues like error occurs can be identified and resolved through Google Search Console reports. “CLS issue: more than 0.1” may be reported within Google Search Console. indicate that layout elements are shifting as the page loads, especially on mobile.
Example: An image, ad, or dynamic block causes content to jump on screen as it loads, which can frustrate users and degrade the experience during a Google crawl. page experience scores.
Sometimes these issues are:
- Transient – caused by a test, plugin, or design tweak that later gets reverted.
- Or they may not be indexed due to errors in Google Search Console. It could signal deeper technical problems, like improperly sized images or injected elements.
How to approach Core Web Vitals fixes
- Use the Core Web Vitals report in GSC to identify affected URL groups.
- Drill down into specific URLs and run them through PageSpeed Insights for detailed diagnostics.
- Prioritise high-traffic, important pages and fix issues like large images, slow server responses, and layout shifts.
3.2 Other Page Experience Concerns
Text too small to read
This is straightforward: font sizes and line heights on mobile are too small, creating poor usability. Fix by:
- Increasing visibility in search results requires addressing crawl errors base font size.
- Ensuring sufficient contrast and spacing.
Clickable elements too close together
This is common on DIY or older designs:
- Buttons, links, or icons are stacked with tiny touch targets, especially social buttons or navigation links.
- Users struggle to tap the right element, which GSC flags as a mobile usability issue.
You can improve this by:
- Increasing spacing and padding around touch targets.
- Following recommended minimum touch target sizes in your design system.
These adjustments improve user experience, and over time, support better performance in search.
4. Ongoing Monitoring: We Check Google Search Console for You
If this all feels like a lot to stay on top of every month, you’re not alone. Google Search Console errors, Core Web Vitals warnings, and indexing issues are exactly the kinds of things most business owners don’t have time to monitor regularly.
As part of our monthly WordPress website care plans, we:
- Keep an eye on Google Search Console errors and warnings
- Monitor indexing issues, 404s, and redirect problems
- Watch for Core Web Vitals and page experience changes
- Flag and fix issues before they start affecting your organic search visibility
We have WordPress Care and maintenance plans starting from $65.00 plus GST per month. If you’d like us to take this off your plate, you can learn more on our WordPress Website Care Plans page.
5. Final Thoughts: How to Think About Google Search Console Errors
It’s important not to panic when you see Google Search Console errors, exclusions, or warnings. Many entries are:
- Normal by-products of redirects, canonical tags, and noindex rules.
- Signals that Google is documenting how it sees your site, not that your SEO is broken.
Use Google Search Console mainly to:
- Confirm that critical pages are indexed and error-free.
- Spot patterns, like spikes in 404s, crawled – currently not indexed, or Core Web Vitals issues that might indicate deeper problems.
- Track whether your fixes are being validated and recognised over time.
Most “errors” can be as benign as a page redirect, a member-only URL, or a duplicate that’s correctly handled by canonical tags.
The key is to focus your attention on:
- Important URLs that should be indexed but aren’t,
- Technical issues blocking access to key content, and
- User experience problems that make the site slow or hard to use.
If you want to check a page is indexed without errors, remember that you can always use the fetch as Google option in Google Search Console to check how your page is being indexed.
6. Key Takeaways
- Not all Google Search Console errors are urgent. Many are informational and reflect expected behaviour like redirects, canonicalisation, or noindex rules.
- Prioritise critical pages. Focus on issues affecting pages that drive traffic or revenue: persistent “not indexed” states, major 404 spikes, or server errors.
- Use the URL inspection and Core Web Vitals reports. They’re your best tools for verifying how Google sees a page and spotting real technical issues.
- Think in terms of patterns, not single URLs. Spikes in 404s or “crawled – currently not indexed” can reveal migrations gone wrong, hacks, or quality issues.
7. Frequently Asked Questions About Google Search Console Errors
Here’s answers to the most common questions we get about Google Search Console Errors.
How serious are Google Search Console errors for SEO?
Not all Google Search Console errors are serious. Many are informational and simply describe how Google is handling certain URLs (for example, redirects, canonicals, or noindex tags). Focus your attention on errors that affect important, traffic‑driving pages — such as persistent server errors, widespread 404s, or pages that should be indexed but aren’t.
Which Google Search Console errors should I fix first?
Prioritise:
- Server errors (5xx) on key pages
- Accidental noindex on important landing or service pages
- Critical Core Web Vitals issues on high‑traffic URLs
- Large spikes in 404s after a redesign or migration
Less critical items — like alternative pages with canonical tags or excluded archives — can usually wait or be monitored.
Why does Google say “Crawled – currently not indexed” for my page?
“Crawled – currently not indexed” means Google has seen the page but chosen not to store it in the index (at least for now). Common reasons include:
- Content that’s too thin or similar to other pages
- Weak internal linking
- The page not being particularly helpful or unique
If a page still isn’t indexed after a few weeks and you want it to rank, review the content quality and internal links, then consider improving or consolidating it.
Should I worry about “Alternative page with proper canonical tag”?
Usually, no. “Alternative page with proper canonical tag” tells you that Google:
- Found duplicate or very similar content, and
- Is using the canonical URL you specified (or chose) as the primary version
You only need to worry if an important page you expect to rank is treated as an alternative rather than the main canonical. In that case, review your canonical tags, internal links, and duplicate content.
What’s the difference between a 404 error and a soft 404 in Google Search Console?
- A 404 error is a genuine “page not found” server response—normal if content has been intentionally removed.
- A soft 404 happens when the page technically returns a 200 OK status, but Google believes there’s no useful content (or it looks like a “not found” page), so it treats it like a 404 anyway.
If a page should exist and be indexed, make sure it:
- Has useful, unique content, and
- Returns a proper 200 response rather than mimicking an error page.
Do I need to fix every 404 error in Google Search Console?
No. You don’t need to fix every 404, especially for:
- Old, irrelevant URLs you no longer care about
- Deleted user profiles or temporary content
You should fix 404s when:
- They involve important pages
- They result from URL changes or migrations without proper redirects
In those cases, use 301 redirects to send users (and Google) to the most relevant new page.
Why does Google say my video “is not found on host service”?
This usually means the video:
- Was deleted,
- Set to private, or
- Moved to a different URL or host
on the video platform (e.g. YouTube, Vimeo, Wistia). Update the embed to a working video or remove the broken embed so Google isn’t trying to index something that no longer exists.
How do Core Web Vitals errors in Google Search Console impact my rankings?
Core Web Vitals (LCP, INP, CLS) are part of Google’s page experience signals. Poor scores won’t necessarily destroy your rankings on their own, but they can:
- Make it harder to compete in tougher niches, and
- Harm user experience, which indirectly affects performance
It’s wise to fix Core Web Vitals issues on high‑value pages to keep your site fast, stable, and user‑friendly.
Why does Google say “Clickable elements too close together” on mobile?
This means buttons, links, or interactive elements (like icons) are too close, making it hard for users to tap the correct one—especially on smaller screens. You can fix this by:
- Increasing spacing and padding around touch targets
- Ensuring each clickable element has a reasonable tap area
This improves both mobile usability and your page experience signals.
How often should I check Google Search Console for errors?
For most small‑to‑medium businesses, checking once a week or once a fortnight is enough. You’ll want to look more frequently when:
- You’ve just launched a new site or redesign
- You’ve migrated URLs or changed site structure
- You’re actively pushing new content and want to confirm indexing
The goal is consistency: spot issues early, fix what matters, and don’t obsess over every minor warning.
