First confirm whether organic search activity has fallen or only its measurement has changed. Then identify the affected dates, pages and searches, and compare them with website changes and wider demand. Fix a confirmed technical fault promptly, but avoid rewriting the whole site before you know which problem you are trying to solve.
Define the symptom precisely
“Traffic is down” can mean fewer Search Console clicks, fewer analytics sessions or fewer enquiries attributed to search. Those are related observations, but they are not interchangeable.
Record the system, metric, date range and comparison. Check whether reporting filters, consent settings or tracking changed. If only one measurement system shows a sudden break, investigate that difference before assuming the website lost visibility.
Also confirm that the latest period is complete. Comparing a partial week with a full week can manufacture a problem that disappears once the dates are aligned.
Find where the loss is concentrated
Look for the pages and queries responsible for the change. Is it the whole site, a service group or one previously popular article?
Google’s traffic-drop guide recommends examining patterns across pages, queries and other dimensions, alongside possible technical issues and changes in demand.
Build a short list of affected URLs rather than treating every page as equally urgent. Include a few unaffected pages for comparison. If a particular page template is involved, that pattern can help a developer investigate.
Put recent changes on a timeline
Ask what changed shortly before the drop: a redesign, URL move, content removal, hosting change or new plugin. Record the date and the person responsible.
Timing alone does not prove a cause. It gives you a hypothesis to test. For an illustrative site that moved its service pages, check whether the old URLs reach the correct replacements and whether the new pages are accessible.
A written timeline also prevents several people making overlapping fixes without knowing what the others changed. Keep screenshots or exports of the evidence before editing.
Check technical access before rewriting content
Open the affected pages and inspect their status, redirects and indexing instructions. Ask the developer to check whether search engines can reach the intended content and whether the canonical destination is sensible.
Where Search Console is available, review relevant indexing, security and manual-action information. Follow up an actual warning rather than assuming one exists.
If you find a specific fault, describe it precisely. “The replacement service URL returns an error” is an actionable finding. “Google does not like the new site” is not.
Consider demand and the search results
A seasonal service may receive fewer searches outside its busy period. Compare with a relevant earlier period where enough history exists, and check whether the queries themselves show a broader change in interest.
Search results also change. Review the affected questions and the kinds of results now appearing. Does your page still answer the same need, or has the result set shifted towards another format or interpretation?
A reported Google update near the same date is context, not a complete diagnosis. You still need to understand which pages and questions were affected.
Choose the smallest supported action
Write each proposed change beside the evidence that justifies it. Separate confirmed faults from possible content improvements.
- Observation: what the data or test shows.
- Hypothesis: the explanation being investigated.
- Action: the specific change or further check.
- Owner: the person responsible.
- Review: when and how the result will be assessed.
If the problem is one broken template, fix and verify that template. If a guide no longer answers the question well, improve the guide. A site-wide rewrite is a large response that needs stronger evidence than a disappointing graph.
Keep the recovery review honest
After a change, verify that the technical or content issue is actually resolved. Then monitor the relevant pages and queries over an appropriate period. Do not promise that a correction will restore a previous ranking.
Our guide to Search Console measures helps interpret the trend. A content inventory is useful when a redesign or migration is involved.
If the evidence is unclear, our SEO service can help investigate and prioritise the work. The aim is to explain the loss well enough to choose a defensible action, rather than produce a longer list of guesses.