How to Fix "Excluded by 'noindex' Tag" in Google Search Console

This is one of the more helpful Search Console messages, because it is unambiguous. Google fetched the page, found a directive telling it not to index, and complied. Nothing is broken — something is configured to exclude the page. Your job is to find what.

Confirm it is actually there

Open the page, view source, and search for noindex. You are looking for:

<meta name="robots" content="noindex, follow" />

Also check the HTTP headers, since X-Robots-Tag: noindex does the same job invisibly:

curl -I https://yoursite.com/the-page/

Check as a logged-out visitor — a private window, or curl. Some setups behave differently for logged-in administrators, which is exactly how a noindex can hide from you for weeks.

Source 1: The site-wide discourage-search-engines setting

Check Settings → Reading → Search engine visibility. If "Discourage search engines from indexing this site" is ticked, every page carries noindex.

This is the single most common cause. It gets ticked during development and never unticked at launch. If your whole site is excluded rather than a few pages, look here first — it takes ten seconds to rule out.

Source 2: Your SEO plugin

Yoast, Rank Math, SEOPress and All In One SEO all control indexing per content type and per page:

• Per post or page: the SEO box on the edit screen, under Advanced, has an "Allow search engines to show this page" toggle.
• Per content type: the plugin's search-appearance settings can noindex a whole post type. Tag and author archives are frequently noindexed by default — often correctly.
• By rule: some plugins noindex paginated archives, attachment pages, or thin taxonomy pages automatically.

If a whole category of pages is excluded and you did not do it one by one, this is where to look.

Source 3: The page is not public

A draft, a scheduled post, a private page or a password-protected page will not be indexed, and should not be. Check the status in the editor before assuming a configuration problem.

Source 4: Theme or custom code

Search the theme for noindex. Some themes add it to search results and archives — reasonable — but a hand-added line in header.php from a past developer is not unusual either.

Source 5: A staging site leaking into production

If you cloned staging to live, the staging site's "discourage search engines" setting came with it. Same fix as source 1, but it is worth knowing why it appeared out of nowhere.

After you remove it

1. Verify with view-source that the tag is gone, logged out.
2. Purge every cache. A cached copy of the page will keep serving the old tag to Googlebot, and this is where most people lose another week.
3. In Search Console, use the URL Inspection tool, click Test Live URL, confirm it now says indexing is allowed, then Request Indexing.
4. For many pages, resubmit the sitemap rather than requesting each one individually.

Recrawling takes days to weeks. The "Excluded" count in Search Console will not drop immediately, and that is normal.

When noindex is correct

Do not remove it from everything. These pages usually should not be indexed:

• Internal search results.
• Thin tag archives with one or two posts.
• Thank-you and checkout pages.
• Author archives on a single-author site, which duplicate the blog listing.

Getting excluded pages indexed is only worth doing when those pages deserve to be. Pushing thin pages into the index does more harm than leaving them out.