Fix “Submitted URL Marked ‘noindex’” in WordPress (Yoast / Rank Math Step-by-Step)

The Search Console error “Submitted URL marked ‘noindex’” means Google received your URL (usually from your sitemap)
That directive can appear as a meta robots tag in HTML or as an HTTP header like
X-Robots-Tag: noindex.This is one of the best errors to fix because it’s usually 100% under your control. Once you remove the noindex directive,clean your sitemap, and request indexing, your page can start appearing in Google.
1) What the error means
2) Where noindex comes from (all common sources)
3) Step 1: Confirm exactly how Google detects noindex
4) Step 2: WordPress “Reading” setting
5) Step 3: Fix noindex in Yoast (page + global)
6) Step 4: Fix noindex in Rank Math (page + global)
7) Step 5: Fix X-Robots-Tag noindex (headers/caching/security)
8) Step 6: Clean your sitemap (don’t submit noindex URLs)
9) Step 7: Request indexing correctly
10) Special cases (categories, tags, attachments, staging, coming soon)
11) Copy/paste checklist
12) FAQs
1) What the error means
Search Console uses your sitemap and site discovery to find URLs. When it says “Submitted URL marked noindex,” it means:
This directive can be:
- Meta robots tag inside the HTML:
<meta name="robots" content="noindex"> - HTTP header:
X-Robots-Tag: noindex - Plugin/theme feature that adds noindex automatically (archives, attachments, etc.)
- Site-wide “discourage indexing” mode in WordPress
The fix depends on where the noindex is coming from — so the first job is to locate the source.
2) Where noindex comes from (all common sources)
Most WordPress noindex problems come from one of these places:
| Source | How it happens | Typical fix |
|---|---|---|
| WordPress Reading | “Discourage search engines” enabled | Disable it |
| Yoast (page-level) | Page set to noindex in Advanced settings | Set to Index |
| Rank Math (page-level) | Robots meta set to noindex | Set to Index |
| Yoast/Rank Math (global) | Archives/taxonomies disabled or noindexed | Index the right types, noindex thin ones intentionally |
| Headers (X-Robots-Tag) | Hosting/security/cache adds noindex header | Remove header rule; purge cache |
| Staging/Coming soon | Maintenance plugin blocks indexing | Disable maintenance/noindex mode |
| Theme code | Theme inserts robots meta tag | Remove or override in functions.php |
3) Step 1: Confirm exactly how Google detects noindex
Open Search Console → URL Inspection for one affected URL. In the details, Google will usually mention where noindex is detected:
either the robots meta tag or the X-Robots-Tag header.
A) Check the HTML source (easy)
- Open the URL in your browser
- Right click → View page source
- Search for:
noindex,robots,x-robots
B) If Search Console says “X-Robots-Tag noindex” but you can’t find it in HTML
Then the noindex is not in your HTML — it’s in your HTTP headers (server or plugin). This happens often with security plugins,
caching layers, CDN rules, or staging configurations.
4) Step 2: WordPress “Reading” setting
This is the first place to check because it can apply site-wide.
- WordPress Dashboard → Settings → Reading
- Find: “Discourage search engines from indexing this site”
- Make sure it is unchecked
- Save changes
5) Step 3: Fix noindex in Yoast (page + global)
A) Yoast page-level noindex (most common)
- Edit the affected post/page
- Yoast SEO panel → Advanced
- Find: “Allow search engines to show this Page in search results?”
- Set it to: Yes (Index)
- Update the post
B) Yoast global settings (archives & taxonomies)
Sometimes the affected URLs are not posts — they’re categories, tags, or author archives.
In Yoast, these may be set to noindex intentionally.
Ask yourself: do you want them indexed?
- If your category pages are strong (intro text + many posts), indexing can be OK.
- If tag pages are thin (1–2 posts), noindex is often better.
Otherwise you will keep getting “Submitted URL marked noindex.”
6) Step 4: Fix noindex in Rank Math (page + global)
A) Rank Math page-level Robots Meta
- Edit the affected post/page
- Rank Math panel → Advanced
- Find Robots Meta
- Ensure “noindex” is NOT selected, and “index” is active
- Update the post
B) Rank Math global settings
Similar to Yoast, Rank Math may noindex archives (tags, author, date) or custom post types globally.
If those URLs appear in your sitemap while noindexed, Search Console flags it.
7) Step 5: Fix X-Robots-Tag noindex (headers/caching/security)
If Search Console says it found noindex in the X-Robots-Tag header, it usually means:
- Your host applied a rule
- A security plugin is blocking indexing
- A cache/CDN layer is injecting headers
- You are on a staging subdomain or “coming soon” mode
A) Quick checks that often solve it
- Disable “maintenance / coming soon” plugin temporarily and re-test
- Purge cache (plugin + server cache + CDN cache)
- Check security plugins for “discourage indexing” options
- If using Cloudflare, review cache rules / transform rules if any
B) Common staging patterns
If your site is on staging.example.com or a temporary host URL, noindex headers are often enabled automatically.
Make sure you’re submitting your real production domain in Search Console.
8) Step 6: Clean your sitemap (don’t submit noindex URLs)
This is a key reason the error persists: your sitemap keeps submitting URLs that are noindexed.
Google sees the sitemap submission and then sees noindex, so it reports the issue again.
What to do
- Decide which URLs you want indexed (posts/pages usually yes)
- Keep noindex on thin pages intentionally (tags, date archives) if needed
- Ensure your SEO plugin sitemap excludes noindex URLs where possible
- Remove unnecessary archives from sitemap if they’re noindexed
Index + keep in sitemap
- Important posts and pages
- Strong categories (optional)
Noindex + exclude from sitemap
- Thin tag pages
- Author/date archives (single-author blogs)
- Attachment pages (often low value)
- Search results pages
9) Step 7: Request indexing correctly
After you remove the noindex directive and clean the sitemap signals:
- Search Console → URL Inspection
- Test Live URL (if available)
- Click Request indexing
10) Special cases (categories, tags, attachments, staging)
A) Category/tag pages
If the affected URLs are category/tag pages, decide based on value:
- Index categories only if they have a good intro + many posts
- Noindex tags if they’re thin (common best practice on new sites)
B) Attachment pages
WordPress media attachment pages are often thin and may be noindexed by SEO plugins. That’s usually fine —
but ensure they’re not being submitted in the sitemap.
C) “Coming soon” mode
If you used a coming soon plugin while building your site, it might still be sending noindex.
Disable it fully, purge cache, then re-test.
D) Conflicting SEO plugins
If you have Yoast + Rank Math + another SEO plugin active, they may generate conflicting robots tags.
Use one SEO plugin only.
11) Copy/paste checklist
- ✅ Check URL Inspection: is noindex from HTML meta or X-Robots-Tag header?
- ✅ WordPress → Settings → Reading: “Discourage indexing” is OFF
- ✅ Yoast (page): “Show in search results” = YES
- ✅ Rank Math (page): Robots Meta = INDEX
- ✅ Remove X-Robots-Tag noindex from server/CDN/cache/security
- ✅ Purge cache (plugin + server + CDN)
- ✅ Sitemap contains only index-worthy URLs (no noindex URLs submitted)
- ✅ Request indexing after fixes
12) FAQs
Why does Search Console say noindex but I don’t see it in my page source?
Because noindex might be in HTTP headers (X-Robots-Tag) or injected by a cache/security layer.
In that case, changing Yoast/Rank Math may not fix it until the header is removed.
Can I keep some pages noindex?
Yes — and it’s often smart (thin tags, date archives, attachment pages).
Just make sure those noindex URLs are not being submitted in your sitemap.
How long until Google indexes after I fix noindex?
It varies, but once noindex is removed and you request indexing, Google usually reprocesses the page faster than normal crawling.
Focus on clean signals + internal links.



