Investigate an Unexpected Noindex on a Public Page
Website intelligenceInvestigate an Unexpected Noindex on a Public Page
A noindex directive can be appropriate for private or duplicate content, but it may be harmful when it appears on an important public page by accident. Staging settings and page-builder defaults are common places to investigate.
Confirm the page should be indexable
Check the page's purpose and whether it is intended to appear in search results. A login, account or internal confirmation page may have a different requirement from a public service page or article.
Inspect the actual HTML to confirm the directive exists. Do not make a change based only on a screenshot or an editor switch.
Use the SiteBoost robots value as evidence
SiteBoost reports the robots meta value read from the scanned URL. If it contains noindex unexpectedly, trace the setting in the page editor, global template or publishing system.
Check other pages using the same template. A shared default can cause a sitewide issue, while a page-specific rule may only affect one URL.
- Confirm the page is intended for public search.
- Inspect the live robots meta value.
- Trace the setting that produced it.
- Check related URLs using the same template.
Rescan and monitor indexing separately
After removing an unintended directive, publish the page and rescan it to confirm the value changed.
A successful scan does not guarantee immediate indexing. Use the relevant search engine tools to inspect crawl and index status after the technical correction.
