What noindex means on a website page
Noindex tells supporting search engines not to include a page in their index after they can read the instruction. It can appear in the page’s HTML or its response headers. It is useful for non-search pages, but an accidental setting can also hide a genuine service page.
Useful context
- Identify the exact URL and what a visitor would use it for.
- Decide whether it is public information or a customer-specific utility.
How it works
Decide whether exclusion is sensible
A public plumbing-services page should usually be eligible for search. A basket, protected brief or password-recovery page should not. Make that distinction before asking to remove every noindex setting merely because an indexing report lists excluded URLs.
Find the source of the setting
Your platform may expose an indexing option, while a custom website may set it in code or hosting headers. Ask the person responsible to identify the actual source. Changing one screen may not override a separate instruction elsewhere in the delivery chain.
Correct only the intended page group
If a finished service page is blocked accidentally, authorise the relevant public-page correction and retain a record of the previous setting. Keep preview environments and customer utilities separately controlled. Do not treat privacy-sensitive URLs as useful extra search landing pages.
Verify after publishing the change
Check the live result, then use a live URL inspection where available. Google’s indexed report can lag behind a recent correction. Keep the inspection date and result so you can distinguish an old report from a setting that remains wrong.
What to check
- You have an explicit reason for indexing or excluding the page.
- A live check confirms the intended instruction after the change.
- Private records still require appropriate customer access.
Sources and further reading
Platform features can change. Check the provider’s current guidance before changing a live service.