If you use Google Search Console, you’ve likely encountered the “Excluded by ‘noindex’ tag” error at some point. This is a common technical SEO issue that confuses beginners.
This has a direct impact on your website’s ranking and traffic. If this error occurs on important pages, those pages will not be displayed on Google.
In this blog, we’ll explain in detail:
What this error is
Why it occurs
What is its solution
And how can you get your website properly indexed by Google?
What is “Excluded by noindex tag” Error?
“Excluded by noindex tag” means that Google crawled your page, but did not index it.
👉 The reason is simple:
Your page has a noindex tag.
🔑 What is a noindex tag?
Noindex is an HTML meta tag that instructs Google to:
👉 “Please include this page in search results”
Example:
<meta name=”robots” content=”noindex”>
Why Does This Error Occur?
Manually applying a noindex tag to your website.
Sometimes, developers or SEO tools mistakenly apply a noindex to important pages.
Why Your Page Is Not Showing on Google (Noindex Issue Explained Simply)
Have you ever published a page and then waited… but it just never showed up on Google?
Yeah, this happens more often than you’d think.
One of the most common reasons behind this is something called a noindex tag. Sounds technical, but honestly, it’s pretty simple.
Basically, this tag tells Google:
👉 “Don’t include this page in search results.”
And if that instruction is there, Google listens — no matter how good your content is.
So Why Does This Happen?
Let me break this down in a real-world way.
➤ Sometimes It’s Just a Simple Mistake
I’ve seen this a lot — while setting up a page, someone accidentally enables a noindex setting.It could be a developer, or even you while testing things.
➤ WordPress Plugins Can Be Tricky
If you’re using Yoast SEO or Rank Math, there’s a small setting that controls whether a page gets indexed or not.And trust me, it’s very easy to switch it off without realizing.
➤ During Website Setup
When a website is still being built, people often block search engines completely.Makes sense at that stage.But later?They forget to turn it back on.
➤ Not Every Page Is Meant for Google
Some pages are intentionally hidden, like:
Thank you pages
Login pages
Filter-based URLs
And that’s actually a good practice
➤ Hidden Theme or Plugin Behavior
In some cases, your theme or a plugin might add a noindex tag in the background.You don’t see it. But it’s there.
What’s the Real Problem Here?
If this tag is placed on the wrong page — like your blog or product page — then:
Your page won’t appear in Google
You won’t get organic visitors
Rankings won’t improve
And all your SEO work… kind of goes nowhere
It’s like opening a shop but keeping the shutter down.
How Do You Check This?
This part is easy.
Open your page → right-click → click “View Page Source”
Now press Ctrl + F and search for:
noindex
If you see something like:
<meta name=”robots” content=”noindex”>
👉 That’s your issue.
How to Fix It (Step by Step)
If You’re Using Yoast SEO
Go to your page → scroll to Advanced settings
Set: “Allow search engines” → YES
If You’re Using Rank Math
Edit the page → go to Advanced tab
Change Robots Meta to → Index
If You’re Editing Code
Replace noindex with:
<meta name=”robots” content=”index, follow”>
Don’t Forget This Step
After fixing:
Update your sitemap
Go to Google Search Console
Use URL Inspection → Request Indexing
A Few Things Most People Don’t Tell You
Not every page should be indexed
Too many useless pages = bad SEO
Always double-check after publishing
Make it a habit to review Search Console weekly
When Noindex Is Actually Useful
There are cases where you SHOULD use it:
Thank you pages
Login/admin pages
Duplicate content
Internal search result pages
So yeah — noindex isn’t bad.It just needs to be used correctly.
Final Thought
At the end of the day, SEO starts with one simple thing:
👉 If Google doesn’t index your page, it can’t rank it.So before you stress about keywords, backlinks, or traffic…
just make sure your page is actually visible to Google.
Latest Post :
How to Fix Alternate Page with Proper Canonical Tag Issue