Fix Excluded by Noindex Tag Error

When you are trying to get a new blog post to show up in search results, seeing the "Excluded by ‘noindex’ tag" status in Google Search Console can be incredibly frustrating.

​Unlike errors where Google decides your content is too thin, or where your server crashes, this status means your website is actively telling Googlebot to go away. A "noindex" tag is a piece of hidden code that acts like a "Do Not Enter" sign. It specifically commands search engines to keep a page out of their public search results.

​If an important article is getting flagged with this status, you have a configuration issue hiding your content. Here is exactly why this happens and how to remove the roadblock.

​Key Takeaways

• ​A noindex tag is an intentional command telling Google to hide a page.
• ​Googlebot will crawl the page, see the tag, and respect your wishes by excluding it.
• ​This is often caused by accidentally clicking the wrong setting in your dashboard.
• ​You can fix this by adjusting your Blogger settings and removing the restrictive tag.

​Why This Status Appears

​When search engines read a webpage, they look at the invisible HTML code behind the text. If they see a line of code that says <meta name="robots" content="noindex">, they will instantly drop the page from their database.

​Often, website owners use this tag on purpose for pages they want to keep private, like an admin login page or a thank-you page after a user signs up for a newsletter. However, if your main blog posts are getting this error, it usually means a setting was accidentally toggled on in your website builder.

​Quick Note: If you are confused about why Googlebot can see the page but still refuses to show it, read our complete breakdown on the differences between crawling, indexing, and ranking.

​How to Fix the Noindex Error

​You do not need to know how to code to fix this. You just need to flip the correct switch in your dashboard so Google is allowed to display your work.

​1. Check Your Blogger Robot Tags

​If you are using Blogger, you control these tags in your main settings. Go to your Blogger dashboard and click on Settings. Scroll down to the Crawlers and indexing section.

​Look for the setting called "Enable custom robot header tags." If this is turned on, click into your "Home page tags," "Archive and search page tags," and "Post and page tags." Ensure that the noindex switch is turned off for your main posts and pages. You want "all" or "index" selected instead.

​2. Inspect the Live URL

​Once you have updated your settings, you need to verify that the "Do Not Enter" sign is actually gone. Open Google Search Console, click on the error in your report, and select the affected URL.

​Click the "Test Live URL" button at the top of the screen. When the test finishes, open the "Availability" section. If you fixed the issue correctly, the "Indexing allowed?" line will now say "Yes."

​Important Detail: If the tag is removed but your page is still invisible, you might be dealing with a different delay. Check out our troubleshooting steps for when a website is not showing on Google.

​3. Validate the Fix

​Now that the page is fixed and the live test is successful, you want Google to process the updated page so it can finally appear in search results.

​Next Steps: Do not wait for the crawler to wander back to your site naturally. Follow our quick guide on how to reindex a page fast in Google to push your clean URL back into the system today.

​Frequently Asked Questions (Q&A)

​Does a noindex tag permanently ruin my page?

No. A noindex tag is completely reversible. As soon as you remove the tag and Google recrawls the page, it will be eligible to show up in search results again.

​Should I use noindex tags on my blog?

Yes, but only strategically. It is smart to use noindex tags on thin, unhelpful pages like author archives or generic tag feeds so Google only focuses on your high-quality written articles.

​How long does it take for the error to disappear?

Once you fix the settings and request indexing, it can take anywhere from a few days to a few weeks for your Google Search Console dashboard to clear the error from your report.