When a client reports that their Google rankings dropped, we start by checking the evidence. The next decision is whether the change needs work, and who should own it. Editing the page before answering those questions leaves your team acting on an assumption.
Confirm whether Google rankings dropped
Say a client’s service page slips from position 6 to 11 for its main term. We’ll use that example throughout. We first record the query, page, date, country and device behind the alert.
A rank tracker gives you a snapshot for its configured location and device. Search Console shows recorded performance from what searchers saw. We check both, keeping their different views clear, rather than expecting the numbers to match exactly.
Has only that keyword moved? Check the page’s other queries and whether the change persists across comparable checks. Keep mobile and desktop separate, and check the country the client serves. Check clicks and impressions alongside position. If both fell, work through the possible causes below. Your team needs to know whether it’s investigating one tracked result or a broader drop in Google rankings.
Google recommends comparing previous and year-on-year periods, with up to 16 months available in Search Console. Filter by query, page, country, device and search appearance, and examine search types separately. Those checks come from Google’s guide to debugging drops in Search traffic.
We also check the Search Status Dashboard for an update in progress and record any relevant dates. An overlapping rollout belongs in the investigation notes. We don’t treat timing alone as proof of the cause.
Find the scope and likely cause
Before commissioning a rewrite, establish which pages are affected. The same guide recommends the Pages table to distinguish one page, a group or the whole site, then the Page indexing report for site-wide issues and URL Inspection for individual pages.
For our service page, start with nearby service pages and the rest of its query set. If they’ve held steady, keep the investigation focused. If the same pattern appears across a template, expand the checks to that group.
Check what changed on your side
Read the change record and ask the people who maintain the site. We want dates and specific changes:
- Page edits, including changes to the service explanation and title.
- Template releases affecting the page or its wider group.
- Site moves or migrations.
- Changes to indexing instructions, including noindex.
- Internal links added, removed or moved.
Google lists technical faults, security issues, spam issues or manual actions, changing demand and migrations among possible causes, alongside algorithmic updates. Check relevant Search Console reports, including Manual Actions. Working through that list stops the team settling on the first explanation.
A page edit made around the drop is something to investigate. Keep the earlier version available while you compare it. You may still lack enough evidence to separate the effect of that edit from other changes.
Check what changed in the results
Look at the pages now ranking above the service page. Compare the questions they answer, how they explain the service and the evidence they provide. Record a specific gap that matters to a prospective client before proposing new copy.
If impressions held but clicks fell, Google advises checking titles, snippets and competing rich results. It also points to Google Trends for changes in interest. Note new results-page features alongside your observations.
Let the SEO lead choose the response
The SEO lead decides whether to monitor, fix or commission work. The delivery lead then agrees the priority and capacity. If a wider review changes the client programme, bring the agency owner or account lead into that decision.
We use four possible responses:
- Monitor: leave the page alone where the shift is small and the wider evidence doesn’t justify a change. Give monitoring an owner and review date.
- Fix a technical problem: assign a confirmed fault to the person who can correct it, with a check that the repair worked.
- Update the page: commission a brief around a specific weakness supported by the page review and the results now ranking.
- Review content more widely: assess affected pages together when the evidence supports a broader problem.
Google’s guidance on core updates says these updates don’t target individual sites. Other pages may now serve searchers better. Small shifts usually need no major action, while a sustained, substantial drop across the site calls for a wider assessment of helpful, reliable, people-first content.
For our service page, position 6 to 11 alone doesn’t choose the response. We need the query pattern, traffic evidence and page checks.
If a core update overlaps the drop, Google recommends waiting until it finishes, then at least a week before comparing Search Console data with the week before rollout began. It also advises against quick fixes and treats deletion as a last resort. We still assign a confirmed technical fault for prompt repair.
Turn the decision into a scoped task
A task called “improve rankings” leaves the work undefined. The owner needs work they can complete and a reviewer needs something they can assess.
If the service-page investigation supports a content update, attach the brief and record:
- Reason: the position change, affected query and evidence from the comparison.
- Scope: the sections to review and the specific gaps to address.
- Owner: the person responsible for producing the update.
- Deadline: the date the draft is due for review.
- Follow-up: who will check performance again and on what date.
Include the investigation notes so the writer can understand the decision without repeating the checks. Keep any unresolved cause clearly labelled. The brief should explain why the proposed change is useful to the reader.
A ranking alert needs a decision before it needs an edit.
The deadline applies to the work we control. Draft review, approval and publication still need their own decisions. If client input is required, name it on the task and agree who will obtain it before promising a delivery date.
Tell the client what moved and what happens next
Keep the client update plain. For our illustrative service page, explain that the main tracked term moved from 6 to 11, then describe what the wider checks showed.
Cover what moved, what you checked, the chosen response and when you’ll look again. If you’re commissioning an update, explain the specific issue the brief addresses. If you’re monitoring, say why you’re leaving the page alone and who owns the next check.
Don’t promise recovery by the task deadline. Your agency can commit to completing the investigation and agreed work. Where the cause remains uncertain, say so, and explain what further evidence you’re waiting for.
Keep the follow-up attached to the work
At the follow-up, reopen the original evidence and use the same filters and comparison periods. Record what changed, what stayed stable and whether the next decision is to continue monitoring or investigate further.
Google says effects can take days to months and advises waiting a few weeks before re-analysis after changes. Improvement isn’t guaranteed.
In Doxa’s workspace, rankings and Search Console data sit beside the client’s work. The drop, the task and its follow-up can stay connected, with the brief and review attached to the task. People make the decisions about scope, quality and publication.
Get in touch at hello@doxaseo.com to talk about the platform or how your agency works.