How to Fix Accidental Noindex Tags on Key Pages
A noindex directive, either in a robots meta tag or an X-Robots-Tag HTTP header, tells search engines to drop a page from their index. This guide shows you how to find every noindexed page, separate intentional ones from mistakes, remove the accidental directives at their source, and confirm the pages can be indexed again.

Why it matters
A noindexed page cannot rank, cannot appear in Google or Bing results, and is usually skipped by AI answer engines that rely on search indexes. One leftover staging setting can remove an entire site from search within days. Our audit fails the check when 10% or more of crawled pages carry noindex.
It always fails if the homepage is noindexed, because that usually means a sitewide switch was left on.
What you need
Step-by-step fix
Find where each noindex comes from
For every flagged URL, check both places a noindex can live: the HTML <meta name="robots"> tag and the X-Robots-Tag response header. Bot-specific forms count too, such as <meta name="googlebot" content="noindex"> or X-Robots-Tag: googlebot: noindex. Start with the homepage, because a noindex there almost always points to a sitewide setting.
# Check the HTTP header curl -sI https://example.com/ | grep -i x-robots-tag # Check the meta tags in the HTML curl -s https://example.com/ | grep -io '<meta[^>]*name="\(robots\|googlebot\|bingbot\)"[^>]*>'
Decide which pages should actually rank
Sort the flagged URLs into two groups: keep noindex, and remove noindex.
- Usually fine to keep noindexed: cart, checkout, account, login, internal search results, thank-you pages, and filtered or sorted duplicates.
- Should never be noindexed: the homepage, category and collection pages, product and service pages, blog posts, and landing pages you advertise.
Intentional noindex pages still count toward the 10% threshold. If they make up a large share of your crawlable pages, consider why so many utility URLs are linked internally.
Turn off any sitewide noindex switch
If the homepage or most of the site is noindexed, look for a global setting before editing pages one by one. Common culprits:
- WordPress Settings > Reading > Search engine visibility
- A staging environment variable copied to production
- A password or "coming soon" mode
- A layout template that hard-codes the robots tag
Search your codebase for the string so you catch every template.
grep -rni "noindex" ./templates ./themes ./src ./app 2>/dev/null
Remove page-level robots meta tags
For individual pages, change the robots setting in your CMS or SEO plugin, or edit the template. You can either delete the tag, because indexing is the default, or set it to index, follow. Never leave noindex alongside other values such as max-snippet.
<!-- Before --> <meta name="robots" content="noindex, follow"> <!-- After (or delete the tag entirely) --> <meta name="robots" content="index, follow, max-image-preview:large">
Remove noindex X-Robots-Tag headers
Headers are set in server config, .htaccess, CDN rules, or application middleware.
- Search your Nginx or Apache config for
X-Robots-Tagand delete or scope any rule that applies noindex to pages that should rank. - Keep header-based noindex only where it is meant, such as PDFs you want hidden or a staging hostname.
- Reload the server after editing.
# Find the rule
grep -rn "X-Robots-Tag" /etc/nginx/ /etc/apache2/ .htaccess 2>/dev/null
# Nginx: limit noindex to the staging host only
server {
server_name staging.example.com;
add_header X-Robots-Tag "noindex, nofollow" always;
}
# ...and make sure the example.com server block has no such add_header
# Then test and reload
sudo nginx -t && sudo systemctl reload nginxClear caches and make sure crawlers can reach the pages
Purge your CDN and page cache so the old HTML and headers stop being served. txt does not Disallow the fixed URLs. A blocked page cannot be recrawled, so Google never sees that the noindex is gone.
Add the fixed pages to your XML sitemap if they are missing.
curl -s https://example.com/robots.txt
Verify the fix and request reindexing
Re-run the curl checks from step 1 on each fixed URL and confirm neither the header nor the meta tag contains noindex. In Google Search Console, open URL Inspection, click Test live URL, and confirm "Indexing allowed? Yes".
Then click Request indexing for your most important pages. Finally, re-run the audit to confirm the noindex share is under 10% and the homepage is clear.
for u in https://example.com/ https://example.com/products/ https://example.com/blog/; do echo "== $u" curl -sI "$u" | grep -i x-robots-tag curl -s "$u" | grep -io '<meta[^>]*noindex[^>]*>' done
Platform-specific notes
WordPress
First uncheck Settings > Reading > "Discourage search engines from indexing this site". This setting outputs a sitewide noindex robots tag. Then check per-page settings: in Yoast, open the Advanced tab of the Yoast sidebar and set "Allow search engines to show this content in search results?" to Yes. In Rank Math, open the Advanced tab and set Robots Meta to Index. Also check Yoast > Settings > Content types and Taxonomies, where a whole post type can be set to noindex.
Shopify
Shopify adds noindex while the store is password-protected. Remove the password under Online Store > Preferences. A product or page with the metafield seo.hidden = 1 also gets noindex, so delete that metafield on pages that should rank. Finally, search theme.liquid for a custom robots meta tag added by an app or developer.
Wix
For each page, go to Pages & Menu, click the ⋯ next to the page, open SEO basics, and turn on "Let search engines index this page". For sitewide control, open the SEO dashboard and check that the site is set to be indexed and connected to Google.
Webflow
The *.webflow.io staging domain is noindexed by default, and that is correct. Make sure your custom domain is published and set as the default. Webflow has no simple per-page index toggle, so look in each page's Settings > Custom code > Inside <head> tag, and in Site settings > Custom code, for a pasted noindex meta tag.
Next.js
In the App Router, check every exported metadata object and generateMetadata function for robots: { index: false }. Pay particular attention to app/layout.tsx, where it applies to every page. Also search next.config.js headers() and middleware.ts for an X-Robots-Tag noindex header, which is often added for preview deployments and accidentally shipped to production.
Check that it worked
✅ How to verify
- Run curl -sI https://example.com/ | grep -i x-robots-tag and confirm the output contains no noindex.
- View the page source (Ctrl+U or Cmd+Option+U) and search for "noindex". There should be no match on pages meant to rank.
- In Google Search Console, use URL Inspection > Test live URL and confirm "Indexing allowed? Yes".
- Re-run the audit and confirm the homepage is not flagged and fewer than 10% of crawled pages carry noindex.
⚠️ Common mistakes
- Removing the meta tag but missing a noindex X-Robots-Tag header set at the server or CDN, so the page stays excluded.
- Blocking the page in robots.txt at the same time. Google cannot recrawl it to see that the noindex was removed.
- Copying a staging configuration or environment variable to production, which pushes a sitewide noindex live during a launch or migration.
- Forgetting to purge the CDN or page cache, so the old noindexed HTML keeps being served after the fix.
Is this still an issue on your site? Run a free audit — ZORO checks this and 294 other SEO, AI-visibility, accessibility and security signals, with fixes for your platform.
Check my site freeFAQ
How long does it take for Google to reindex a page after removing noindex?
Usually a few days to a few weeks, depending on how often Google crawls your site. Requesting indexing in Search Console URL Inspection speeds it up for priority pages. Including the URLs in your sitemap also helps.
What is the difference between noindex and blocking a page in robots.txt?
Noindex lets Google crawl the page but keeps it out of results. Robots.txt Disallow stops crawling, but the URL can still appear in results without a description. If you want a page removed from results, use noindex and do not block it in robots.txt, or Google will never see the tag.
Which pages should I keep noindexed?
Typical candidates are cart, checkout, account and login pages, internal site search results, thank-you pages and thin filtered duplicates. Content you want people to find through search should not be noindexed. That includes the homepage, categories, products, services and articles.
Why does my page show noindex when I can't find it in the HTML?
It is probably coming from an X-Robots-Tag HTTP header set by your server, CDN or framework, or from a robots tag injected by JavaScript after the page loads. Check the response headers with curl -sI and inspect the rendered DOM in browser DevTools.
How to Fix a Missing Viewport Meta Tag on Every Page
How to Fix Generic Page Titles Like "Home" and "Untitled"
How to Fix a Missing Call-to-Action Above the Fold
How to Fix Nofollow on Internal Links (Step-by-Step)
How to Add a Table of Contents to Long Pages and Articles
How to Fix Broken Outbound Links (404, 410 and 5xx Errors)