Updated · 31 Aug 2026
Short answer.
Separate three states first: the page cannot be crawled; it can be crawled but the engine selected another canonical; or it is accessible but has not been selected for the index. A plugin can test technical access and directives, but only the search engine’s data confirms indexing.
Check first
Evidence before change.
- HTTP status and final URL after every redirect.
- X-Robots-Tag, meta robots, and robots.txt rules for the intended user agent.
- The page canonical and whether that canonical is accessible/indexable.
- Presence in the current sitemap and its modification date.
- Ordinary internal HTML links to the page.
- Duplicates across parameters, slashes, case, protocol, and similar templates.
- The exact URL inspection in Yandex Webmaster and Google Search Console.
Safe sequence
Move in small verifiable steps.
- Inspect one exact URL. Do not use a `site:` query as the only evidence.
- Remove contradictions. Sitemap, canonical, robots, and internal links should express one intention.
- Select the primary version. Technical duplicates should not compete for one document.
- Improve the useful page. Metadata alone cannot fix a document that answers no distinct need.
- Request recrawl. Submit the priority URL after correction and wait for new processing.
Common mistakes
What usually increases risk.
- Opening utility, filter, and stage pages merely to increase an index count.
- Changing URLs without redirects and updated internal links.
- Treating a sitemap as an indexing guarantee.
- Publishing synonym pages that answer the same question.
320px Site Audit
What can be checked automatically.
Site Audit crawls accessible pages and reviews status, robots directives, canonical, metadata, sitemap, and selected duplicate patterns. It does not report rank or prove index presence; webmaster tools are required for that.
When help is useful
A concrete next step.
Technical indexing causes and safe changes are covered by WordPress SEO support without promising a particular position.
Continue
A related guide and the full collection.
01
What to do when a WordPress site is hacked
First actions after suspected WordPress compromise: contain damage, preserve state, rotate secrets, restore trusted code, and verify again.
Tell us what the site needs.
A goal, the current difficulty, and an optional website address are enough. Do not send passwords, keys, or private exports.