Blog / WordPress /

A practical review of noindex settings across a WordPress site

A page vanishes from Google. Everyone blames the algorithm. Then someone views the source and finds a noindex tag nobody remembers adding.

A noindex setting keeps a page out of search. That’s useful when you meant it and maddening when it lands on a page that should be found. WordPress sites can combine settings from the platform, SEO plugins, templates, headers and robots.txt rules, so one settings screen never tells you the whole story. I always audit the rendered response and the page’s purpose before I remove a directive. Otherwise a quick fix can expose private or low-value content.

Inventory where directives come from

Start by collecting URLs by template and purpose rather than opening a plugin screen. You want public pages, archives, search results, staging, account pages and utility endpoints in one list. Then inspect the page source or response headers for robots meta tags and X-Robots-Tag.

After that, check the WordPress reading settings, SEO plugin controls, theme logic and server configuration. A robots.txt disallow is not the same as noindex. In fact, blocking a crawler can stop it ever seeing a noindex directive. And don’t assume a setting has the same label everywhere; read the current documentation for the plugins installed on the site.

Compare intent with behaviour

For each group of URLs, write down the search state you intend and the directive you observe. A public service page that should attract traffic must not inherit noindex from a template by accident.

A private account page needs access protection. Noindex is not an access control, and I wouldn’t trust it as one. Check canonical tags and internal links too, because contradictory signals make diagnosis harder. After any change, test representative pages, including rendered output when the directive might be injected dynamically.

Make changes safely

Use a crawl and Search Console inspection, then record the change and the result. A one-line note saying what you changed, when and why saves the next person an hour of detective work. Never switch off noindex sitewide because one valuable page is missing. Fix that page’s cause. The rest of the exclusions are probably there for good reasons.

If a page should be indexed, check first that it returns a successful response, has useful content and is linked from somewhere sensible. If the exclusion is intentional, make sure the user journey still works. A visitor who lands on an excluded page by link shouldn’t hit a dead end.

Put the process into practice

Repeat the audit after plugin, theme or hosting changes, because directives can come from different layers and a new release may bring a new one with it. Crawl with a representative user agent and inspect the response directly when the crawler report is unclear.

Remember that a page blocked from crawling can still have a known URL through links, so blocking isn’t a reliable way to keep a URL private. For sensitive content, use authentication.

Document intentional exclusions, ideally somewhere the editors will see them, such as a shared notes page or a comment in the settings handover. Otherwise a future editor sees a noindex, assumes it’s a mistake and removes it as a routine optimisation.

Close the loop

Check archive, category, tag and pagination templates as well as individual posts. Those are the places where a sitewide setting quietly does the most damage, and nobody looks at them after launch. A global setting can affect a whole class of URLs, while a manual override may apply to one page only.

Keep the purpose of each exclusion on record, and verify after every relevant release that the final response still reflects it.

A final sense check

Keep your notes short: the URL group, the intended state, the directive you found and who owns the fix. Separate what the page demonstrably does from what you suspect explains it. If the evidence is thin, inspect another sample, ask the site administrator or test a reversible change before editing anything.

Revisit the review whenever the site’s templates or business purpose change. Sometimes the right note is simply “monitor, don’t edit”, and that’s a perfectly respectable outcome for an audit.

Which page group would you inspect before changing a sitewide indexation setting?