Excluded by Noindex Tag: What It Means and How to Fix It

What does excluded by noindex tag mean in Search Console?

"Excluded by noindex tag" is a Search Console status that tells you Google crawled a page, found a noindex directive, and therefore left it out of its index. The directive can sit in a meta tag or in an HTTP header. However, the status is not an error by itself; Google simply followed your instruction.

In other words, Googlebot reached the page, read the content, and saw the note that says do not show this page in search results. So the page stays out of the index. Seeing this line in your report does not mean something broke on your site.

Also, the real question is whether you wanted that. If you did, everything works as planned. If you did not, a page that should earn traffic is invisible in Google, and that needs fixing fast.

In practice, the rest of this guide shows you how to tell the two cases apart, find the source of the directive, and remove it safely.

Where do you find the excluded by noindex tag status?

You find it in the Page indexing report. Open Search Console, go to Indexing in the left menu, and click Pages. The report splits your URLs into indexed and not indexed, and the noindex reason sits in the not indexed table.

Then click the row to see the affected URLs. Then open the URL Inspection tool for any address to see what Google saw on its last visit. The tool states clearly whether the page is indexed and why not.

In addition, if you are new to the reports, start with our guide on what Google Search Console is and how to use it. For other reasons behind missing pages, read how to find unindexed pages in Search Console.

The report also shows a trend chart. A sudden jump in excluded pages usually points to a bulk setting change, so read the chart as a trend and not as a single number.

How does a noindex tag work and how does Google read it?

Noindex is a directive that tells a search engine not to keep a page in its index. You can give it in two ways. The first is a robots meta tag in the page head. The second is an X-Robots-Tag HTTP header that your server sends.

• Meta tag: <meta name="robots" content="noindex"> speaks to all search engines.
• Google only tag: <meta name="googlebot" content="noindex"> speaks to Googlebot alone.
• HTTP header: X-Robots-Tag: noindex works well for PDFs, images, and other non HTML files.

Google sees the directive while it crawls and processes the page. Therefore the page must stay crawlable for the rule to work. Google explains this in its guide on blocking search indexing with noindex.

Note the header route in particular. An X-Robots-Tag never shows up in the page source, so people who only read the HTML often miss it.

Is a page excluded by noindex tag always intentional?

Often it is. Every site has pages that should not appear in search results. You add noindex on purpose because those pages give you no benefit in Google's index.

For example, thank you pages, cart and checkout steps, internal search results, and login screens are typical candidates. Temporary campaign pages and duplicate filter combinations also belong in this group.

Additionally, when these pages show up as excluded, relax. Review the list once, confirm that each address should stay out, and move on. If nothing is missing, the report simply keeps a record for you.

Which pages should carry a noindex tag?

The rule is simple: if a page offers nothing to a visitor who arrives from search, it can be noindex. If it offers value, it belongs in the index. The table below covers the cases we meet most often in the field.

However, do not treat noindex as the first fix for weak content. Improving, merging, or deleting those pages often works better. Read what content pruning is and when to do it for the full reasoning.

What happens when excluded by noindex tag is unintentional?

Unintentional noindex is a silent traffic loss. The page loads, looks fine, and works for visitors, yet it never appears in Google. Most teams notice weeks later, because traffic only drops then.

Moreover, the consequences are clear. Your service page does not rank, so it gets no visitors from the related keywords. So you lean harder on paid ads, because the organic channel does nothing for that page.

Therefore, check the report at regular intervals. Look at it in the first weeks after a launch or a redesign. A page that sits with noindex before Google ever indexes it can stay invisible for months.

Why does unintentional noindex happen?

The root causes repeat with surprising regularity. Most come from a well meant setting or a plugin default.

• A staging setting such as "Discourage search engines from indexing this site" stays on after launch.
• An SEO plugin applies noindex to a whole page type in bulk.
• A theme or template adds noindex to certain category and tag pages.
• A developer copies a test server header to the live server.
• You duplicate a page, and its meta settings travel along with it.

Server headers deserve a special mention. An X-Robots-Tag header does not appear in the HTML source. So anyone who searches the page code for noindex can spend hours hunting for a tag that does not exist.

How do you diagnose excluded by noindex tag step by step?

The goal is to find exactly where the directive comes from. If you follow the order below, you usually catch the source within minutes.

1. Open the noindex reason in the Page indexing report and list the sample URLs.
2. Paste one URL into the URL Inspection tool and run Test live URL.
3. Check the Page indexing section to see where the noindex comes from.
4. Open the page source in your browser and search for the word robots.
5. Look at the response headers in the Network tab for an X-Robots-Tag line.
6. Check plugin, theme, and server settings for a bulk rule.

Also, the live test matters most. The report shows the state Google saw on its last crawl, not your page today. By contrast, the live test reads the response your server returns right now.

Also test with a different device and user agent. Some sites answer mobile and desktop Googlebot differently, so one version may carry noindex and the other may not.

How do you remove a noindex tag?

The removal method depends on where the directive lives. First find the source, because a change in the wrong place does nothing.

• Meta tag in the code: delete the robots tag in the template or change its value to index.
• SEO plugin: switch on the option to show the page in search results.
• WordPress global setting: uncheck the search engine visibility box under Settings, Reading.
• Server header: remove the X-Robots-Tag line from your Apache, Nginx, or CDN configuration.

After the change, run the live test again. If the response shows no noindex, you are done. If you need to write a fresh tag, our meta tag generator makes it easy.

Try the fix on one page first. Confirm it in the live test, then roll it out in bulk. That way you catch side effects early.

How long until Google reindexes the page after the fix?

There is no fixed time. Instead, Google plans crawling according to a page's importance and your site's overall health. Its documentation notes that a revisit can take months for some pages.

To speed things up, do three things. First, confirm a clean live test in URL Inspection. Then click Request indexing. Finally, add the page to your sitemap and strengthen it with internal links.

However, sending the request again and again does not help. Instead, send it once and wait a few days. For the date field in your sitemap, read our note on the sitemap lastmod tag. If you need a new file, the XML sitemap generator helps.

An indexing request is not a guarantee. Google also weighs the quality of the page, so improve the content while you are there.

Can you combine robots.txt and noindex?

No, avoid this pair. Robots.txt stops Google from crawling a page. Noindex needs Google to read the page and see the directive. If crawling is blocked, the directive never gets read.

In practice, the result can backfire. If other sites link to the page, Google may keep the URL in its index without seeing the content. So you think you set noindex, yet the page still appears in search.

In addition, the right path works like this. Do not block the page in robots.txt, leave noindex in place, and let Google see it. After the page drops out, you can close crawling if you still want to. You can read about this and similar errors in common robots.txt mistakes. To build the file correctly, use the robots.txt generator.

What if a sitemap page carries a noindex tag?

A sitemap tells Google which URLs you want indexed. However, noindex says the opposite. When both sit on the same page, Google receives conflicting signals.

Search Console may flag this with its own label: submitted URL marked noindex. The page still stays out of the index. But your report gets noisy, and your real intent becomes hard to read.

Additionally, the fix takes one sentence. If you want the page indexed, remove noindex. If you do not, remove the URL from the sitemap. That way the sitemap lists only pages you want in the index.

Also review your sitemap plugin. Many generators add noindex pages by default, so confirm that the settings exclude them.

How does noindex differ from canonical, robots.txt, and 404?

These methods look similar, but each does a different job. Picking the wrong tool creates a new problem instead of solving the old one.

Moreover, if you choose a redirect, check your chains with the redirect checker.

In practice, follow one rule. Want it crawlable but not indexed? Use noindex. Want it gone? Return 404 or 410. Did the address change? Use a 301.

Does a noindex tag affect link value and crawl budget?

Partly. Google still has to crawl a noindex page, because it can only see the directive by crawling. So noindex does not stop crawling; it only stops indexing.

Over time Google visits pages that always return noindex less often. That shifts crawl resources toward important pages. On large sites, though, thousands of noindex pages still use a share of your crawl capacity.

Link value is a separate matter. If a page stays noindex for a long time, Google may trust its links less. Therefore, never make a noindex page the only route to an important page.

Also, if crawl rate is your real concern, read why Googlebot crawls less. Small business sites rarely face crawl budget problems, but large stores do.

Do noindex pages hurt the rest of your rankings?

No, not directly. Google does not treat noindex pages as a quality penalty. You gave the instruction, and Google followed it.

Indirect effects can still appear. First, if you noindex a valuable page by mistake, it loses its traffic. Second, your internal link flow changes. Third, hiding many weak pages behind noindex only postpones the real problem.

In short, noindex is a tool and not a strategy. Used on the right page for the right reason, it tidies your site. Used in the wrong place, it quietly costs you traffic.

Where does noindex cause trouble in ecommerce?

Online stores generate thousands of URLs, so they suffer noindex mistakes more often. Filter, sort, and pagination URLs multiply, and teams write bulk rules to keep them under control.

In practice, the trouble starts when a rule is too broad. A rule such as noindex every URL with a parameter can also catch an in stock category page that sells well. You only notice when the report opens.

• Do not set noindex on the first page of a category.
• Confirm that the main product URL stays indexable when variants exist.
• Test filter rules against sample URLs before you publish them.
• Use a redirect instead of noindex when a campaign page ends.

Noindex is not the only reason product pages stay out. Our guide on why product pages are not indexed covers the others, and the piece on URL parameters explains filter URLs.

Example scenario: why is your service page missing from search?

The following is an example scenario, not a real client case. Its purpose is to make the diagnosis flow concrete, so you can follow each step.

A business redesigns its site and then notices that its main service page does not rank. The page opens and the content is in place. In Search Console, the page shows as excluded by noindex tag.

At first glance the meta tag looks clean. The live test, however, shows X-Robots-Tag: noindex in the response header. The cause is a server rule from the staging environment that moved to production.

Fixing it takes little effort. The team removes the rule, clears the cache, runs the live test, and requests indexing. Yet the damage depends on how many weeks the page stayed out, so early detection is your best defense.

Noindex, delete, or merge: which decision should you make?

For every page you pick one of three paths. Your choice depends on the value of the page and what it offers users. These questions make it easier.

• When a page serves visitors but has no place in search, use noindex.
• If the page is weak but the topic is valuable, improve it or merge it with another page.
• Once a page has no function anymore, delete it and redirect with a 301.
• If the page duplicates other content, point to the main URL with a canonical.

While you decide, look at inbound links and traffic. If a page earns valuable links, redirecting it beats silencing it with noindex. For Google's own wording, see the robots meta tag documentation.

Also, record the decision. Six months later, you will not remember why you added noindex.

Why does the report still show excluded after you removed noindex?

This happens a lot. Even when you fix the page, the report does not update at once. It reflects the state Google saw on its last visit.

So verify on your side first. Run the live test in URL Inspection. If it shows the page as indexable, the problem is solved, and the rest depends on Google's next crawl.

Sometimes the fix only happened in one place. You deleted the meta tag, for example, but the server still sends an X-Robots-Tag header. Or a cache serves the old version. Clear your CDN and cache plugins as well.

Old URLs can also stay in the list for a few weeks, because Google does not recrawl every address at once. Be patient, but if the live test still shows noindex a week later, the problem is on your side.

How do you audit noindex pages in bulk?

On a site with hundreds of pages, checking one by one is impossible. Export the report first, then filter the list by business priority.

1. Open the noindex reason in Search Console and export the list.
2. Group the URLs by page type: service, product, blog, utility.
3. Flag the URLs in revenue groups and mark them as priority.
4. Use a crawler to collect the real response headers and robots meta values.
5. Record the intentional ones in a document, so you do not ask the same question next time.

For a quick single page check, our SEO checker is enough. Large sites need a full crawl.

Build a small table with URL, page type, intentional or not, owner, and decision. Review it every quarter, because site structure changes and old decisions age.

Which process prevents noindex mistakes?

The way to avoid repeat problems is to make a technical checklist part of your release process. It costs little effort and prevents large losses.

• Before each release, check the robots meta value of new pages.
• Keep test and live settings apart, and protect staging with a password.
• Watch the Page indexing report during the first week after a migration or redesign.
• Document intentional noindex pages and share the list with the team.
• Plan a weekly email alert or a monthly report review.

For high risk periods, our website migration SEO checklist proves useful. For the technical basics, read what technical SEO is and 10 tips.

Finally, add several people to Search Console. If alert emails reach only one person, nobody sees the problem while that person is on holiday.

When should you call in expert help for a noindex problem?

You can fix one page yourself. However, when the problem is bulk, repeating, or of unknown origin, help saves time.

For example, if hundreds of product pages drop out at once, the root cause usually sits in the template or server. One wrong touch can affect the whole site. Therefore, take a backup and test on staging first.

Our team starts such audits with a technical crawl. Then we decide together with you which pages belong in the index, based on your business goals. You can reach us through our SEO consulting page.

What is the quick checklist for excluded by noindex tag?

Let us turn this guide into a short action plan. Each step builds on the previous result and leads you to the right fix.

1. Open the noindex reason in the Page indexing report.
2. For each URL, answer whether it is intentional.
3. If intentional, log it and remove it from the sitemap.
4. If not, find the source: meta tag, plugin, template, or HTTP header.
5. Remove the directive and confirm it in the live test.
6. Request indexing, then update the sitemap and internal links.
7. Check the report again after a few weeks.

In addition, if you follow this list, you keep pages out of search only when you mean to. As a result, a technical status stops being an error and becomes a decision you manage.