Fix guides · SEO
How to fix “Page is blocked from indexing” (noindex)
A noindex tag or header tells search engines to leave a page out of their results. How to find where it comes from and remove it on Shopify, WordPress, Webflow, Wix, Squarespace and Next.js.
- Time to fix
- 5–20 minutes
- Skill needed
- No code
- Who notices
- Everyone searching for you: the page can't appear in Google
Why it matters
Search engines skip pages that carry <meta name="robots" content="noindex"> or an X-Robots-Tag: noindex header. That's right for login pages, thank-you pages and search results, and a serious problem for pages you want found.
It often happens by accident: a "hide from search engines" setting left on after launch, a staging setting copied to the live site, or a plugin applying noindex too widely.
“Search engines can only show pages in their search results if those pages don't explicitly block indexing by search engine crawlers.”
Before you start
- First decide whether this page should be in search results. If it shouldn't (a cart, account or thank-you page), you can ignore this issue for it.
- Check both places noindex can come from: a meta tag in the page's HTML and an X-Robots-Tag response header from the server.
- After removing it, ask Google to recrawl the page with Search Console's URL Inspection tool.
Fix it on your platform
Shopify
- Check whether the page has an SEO Hidden metafield (seo.hidden) set to 1. Shopify's help center describes it as a way to hide pages, products and blog posts from search engines.
- Check layout/theme.liquid for a <meta name="robots" content="noindex"> that's applied more widely than intended.
- If your online store is still password-protected, search engines see only the password page. Remove the password when you launch.
WordPress
- Go to Settings → Reading and make sure "Discourage search engines from indexing this site" is unchecked. When checked, WordPress adds a noindex tag to every page.
- If you use an SEO plugin, check the page's own indexing setting and the plugin's defaults for its post type.
Webflow
- Open the page's settings and make sure Sitemap indexing is on. Turning it off adds a noindex tag to the page.
- Check site and page custom code for a robots meta tag you added.
- The Staging indexing setting (Site settings → SEO → Indexing) only affects your webflow.io subdomain, not your custom domain.
Wix
- Click Pages & Menu, then the More Actions icon next to the page → SEO basics, and turn on Let search engines index this page.
- If every page is affected, check your site-wide SEO settings: preventing indexing of the entire site overrides the page settings.
Squarespace
- Open the page's settings and check its SEO settings for a hide-from-search option.
- For the whole site, open Settings → Crawlers and make sure "Block Search engine crawlers" isn't checked.
- Also check code injection for a noindex tag you added.
Next.js
- Check metadata.robots in the page and its layouts, and any X-Robots-Tag header set in next.config or middleware. Make sure noindex for preview environments doesn't apply in production.
// SITE_ENV is a variable you set per deployment
export const metadata: Metadata = {
robots: process.env.SITE_ENV === "production" ? undefined : { index: false },
};Any other site
- Remove the robots meta tag from the page, and the X-Robots-Tag header from your server configuration.
<meta name="robots" content="noindex">Check that it's fixed
- View the page source and search for "noindex". In DevTools → Network, check the page's response headers for X-Robots-Tag.
- Re-run your StudioLNC audit, then use Search Console's URL Inspection to request indexing.
Find every issue like this on your site
Free audit of performance, accessibility, SEO and security, with fixes for your platform.