URL Marked Noindex in Search Console
This status means Google found a noindex directive on a page, in a meta tag or an HTTP header, so it did not index it. This guide shows how to tell whether that is intended, where the directive hides, and the exact steps to remove it and get the page indexed.
- Meta tag and header
- Intentional or not
- Remove and request indexing
- WordPress causes
<meta name="robots"
content="noindex">
or header:
X-Robots-Tag: noindexGoogle found a noindex directive, in a meta tag or an HTTP header, and did not index the page. Google’s label in the report is URL marked ‘noindex’. If you want the page indexed, remove the directive, confirm it is gone with a live test in URL Inspection, then request indexing. If you do not want it indexed, no action is needed.
What the status means
A noindex directive tells search engines not to show a page in results. When Google crawls the page and sees it, the page is left out of the index. The directive can be a robots meta tag in the HTML or an X-Robots-Tag HTTP header. See the noindex tag guide for background.
Is it intentional?
| Page type | Should it be noindex? |
|---|---|
| Thank-you, cart, account, internal search | Usually yes (my own judgement) |
| Thin tag or date archives | Often yes (my own judgement) |
| A blog post or service page you want to rank | No, remove it |
| Staging or development copy | Yes |
Where a noindex can hide
Robots meta tag
Inside the head of the page.
X-Robots-Tag header
Set by the server, so it is not visible in the page source.
A page setting
For example a visibility checkbox in an SEO plugin (my own note).
Discourage search engines
A WordPress setting that applies to the entire site (my own note).
Find it
Open the URL Inspection tool for the page. It shows whether indexing is allowed. Then run a live test to see the current state.
<meta name="robots" content="noindex, follow"> X-Robots-Tag: noindex
Remove it
| Source | How to remove |
|---|---|
| Page setting in an SEO plugin | Set the page to index; see Yoast SEO settings |
| Hard-coded meta tag in the theme | Edit the template and remove it |
| HTTP header from the server | Remove the header rule in server config |
| Site-wide visibility setting | Untick the discourage option |
Fix it step by step
Do you want it indexed?
If not, you are done. No action is needed.
Confirm in URL Inspection
Check the page for the noindex reason.
Find the source
Check the meta tag, headers, plugin settings and site-wide option.
Delete the directive
Remove it at its source and purge caches.
Run a live test
Confirm the directive is gone.
Request indexing
Use request indexing, then validate if many pages are affected.
Do not combine noindex with a robots.txt block
If robots.txt blocks a page, Google cannot crawl it and so cannot see the noindex tag. Google’s own advice on blocked pages is to remove the block and use noindex when you want a page kept out of search. See Blocked by robots.txt.
Notes for WordPress sites
- Reading settings. A site-wide discourage option can noindex everything. Check it first (my own note).
- Staging copies. A staging site pushed live can keep its noindex.
- Plugin defaults. Some plugins noindex certain post types or archives by default. See archives: index or noindex.
- Caching. Old cached HTML can keep serving the tag after you remove it.
Troubleshooting
| Symptom | Likely cause (my own diagnosis) | Fix |
|---|---|---|
| Tag gone from source, still noindex | HTTP header | Check response headers |
| Whole site noindex | Site-wide setting | Change visibility setting |
| Live test still shows noindex | Cache | Purge caches |
| One post only | Per-page plugin setting | Reset to index |
Checklist
Decide
- List affected URLs
- Mark which should index
- Leave intended ones alone
- Note patterns
Find
- Check meta tag
- Check headers
- Check plugin settings
- Check site-wide option
Fix
- Remove directive
- Purge caches
- Run live test
- Request indexing
Prevent
- Audit after launches
- Check staging copies
- Document intended noindex pages
- Review monthly
What Google’s page does not say
Google does not give a date by which a page will be indexed after you remove noindex and request indexing. A request does not guarantee indexing, and Google does not list every plugin that sets noindex.
Key terms
- Noindex
- A directive telling search engines not to index a page.
- Meta robots
- A tag in the page head with crawl and index instructions.
- X-Robots-Tag
- The HTTP header version of the directive.
- Live test
- A fresh fetch of the page in URL Inspection.
Common mistakes
Removing noindex but blocking in robots.txt
Google cannot see changes.
Forgetting headers
Source looks clean.
Leaving staging noindex live
Whole site hidden.
Not purging cache
Old tag persists.
Fixing intended pages
Pollutes the index.
Skipping the live test
You cannot confirm.
Related guides
Noindex status questions
What does this status mean?
Google found a noindex directive in a meta tag or HTTP header and did not index the page.
Do I need to fix it?
Only if you want the page indexed. If not, no action is needed.
How do I confirm the directive?
Use URL Inspection, then run a live test to check whether it still exists.
What do I do after removing it?
Request indexing.
Why can’t I see it in the source?
It may be an HTTP header rather than a meta tag.
Can robots.txt hide noindex from Google?
Yes. If crawling is blocked, Google cannot read the tag.
Is the report label different?
Yes. Google labels it URL marked ‘noindex’.
Can WordPress noindex my whole site?
Yes, via a site-wide visibility setting (my own note).
The status definition, fix steps and the robots.txt advice come from Google’s pages. The intended-pages table, where-it-hides list, WordPress notes, troubleshooting table and checklists are my own.