How to Fix a Page That Cannot Be Indexed

What the flag means

This flag means Crystal Ball found an indexing directive, crawl restriction, access failure, or uncertain response that needs review. A noindex directive asks supporting search engines not to include a page in results. A robots.txt rule controls crawling; it does not reliably remove a known URL from an index and can prevent a crawler from seeing the page-level directive.

Treat this as high priority when the page should appear in search, but confirm the exact signal before changing it. Login screens, internal results, staging pages, and private resources may be intentionally excluded.

Common causes

Common causes include staging settings left on after launch, page-level SEO controls, plugin or template directives, robots rules, password protection, security filters, or an intermittent server response. The scanner may also be blocked even when a normal visitor can load the page.

How to fix it

Confirm the warning first and make a backup before editing the live site. If the change involves templates, code, DNS, redirects, or server settings, switch to Intermediate or ask for help before proceeding.

• Custom HTML/static: Remove accidental noindex tags, check HTTP headers, and make sure robots.txt is not blocking the page. Start with Google's noindex guide and robots.txt guide.
• WordPress: Check Settings → Reading and uncheck "Discourage search engines." If an SEO plugin is active, review the page's advanced/indexing setting. See WordPress Reading Settings.
• Shopify: Review theme code and robots.txt.liquid before changing anything. Shopify documents hiding pages from search engines and editing robots.txt.liquid.
• Wix: Open the page SEO settings and make sure search engines are allowed to index the page. Wix explains preventing or allowing indexing.
• Webflow: Check Site settings → SEO indexing, page-level custom code, and staging indexing settings. Webflow documents indexing controls and robots.txt rules.