Watch search performance in context
Review important landing pages and queries regularly. Look at trends rather than reacting to one ranking observation. Changes in demand, competitors, reporting and your own site can all affect what you see.
The original transcript described a redesign that removed an earlier change. The useful lesson is to keep a change log: compare the timing of a performance shift with theme updates, migrations and content edits. Form a hypothesis from the data, then inspect the actual site before acting.
Investigate unexpected indexing changes
Use Search Console’s indexing reports alongside a crawl and your sitemap. A search using site: can surface unexpected URLs, but its result count is not a reliable inventory. Different tools report different scopes and can update at different times.
Unexpected pages can indicate duplicate URLs, a configuration mistake or compromised content. Inspect examples before removing anything. If you find a compromise, address the security cause and remove unauthorised content; hiding URLs from search alone does not secure the site.
Keep a record of the response
An earlier WordPress incident described a plugin unexpectedly creating broken paths. After a plugin or theme change, check important URLs and internal links directly, and compare any new errors with the change log. Do not rely on a search-service email to detect every fault. Fix the cause and verify the affected paths, rather than assuming that the timing alone proves a ranking impact.
Record what changed, who fixed it and what you expect to observe. Choose a review cadence appropriate to the site’s activity, and allow for reporting delays. No single count or ranking proves the cause or guarantees recovery.
See our SEO work and redesign checklist.