A downward line in a traffic report can make every recent website decision look suspicious. Was it the new homepage, the article you edited, or something Google changed? The quickest way to create more confusion is to change everything before you know what happened.
Begin by describing the drop precisely. Search clicks, website sessions and enquiries are different measures. Write down which one fell, when it started and how you noticed it. That turns a worrying impression into something you can investigate.
- 01 - ConfirmCheck the metric, dates and filters
- 02 - NarrowFind the pages or searches that changed
- 03 - InvestigateTest a cause before choosing a correction
Check that you are comparing like with like
Confirm the website, date range and filters in the report. Avoid comparing an unfinished week with a full week, or a busy seasonal period with an ordinary one. If your business is usually quiet at weekends, include comparable weekdays.
Use Search Console to investigate Google Search activity and your analytics system to investigate recorded website visits. They measure different things, so their totals do not need to match. Our guide to Search Console and Analytics explains how to read them together.
If analytics traffic falls but Search Console clicks remain broadly similar, check whether tracking or consent settings changed. That pattern is a clue, not proof of a tracking problem. Ask the person responsible for analytics to verify data collection before you change the site’s content.
Find out whether the drop is broad or concentrated
Look at the pages that lost the most clicks, then the searches associated with them. Check whether the change is limited to one device, country or search type. A decline in image-search traffic is not the same problem as a decline across your main service pages.
Keep the investigation short enough to act on. Select a few affected pages and write a plain-English observation for each: this service page lost clicks, this guide stayed steady, this product page was recently removed. Avoid treating a site-wide total as a diagnosis.
Google recommends examining traffic patterns, comparable periods and possible seasonal demand. Check a longer historical view where data is available. A recurring quiet period may call for planning, not emergency technical changes.
Make a timeline of recent changes
Ask your team about deployments, page moves, navigation changes, tracking updates and outages around the time of the decline. Record what actually happened, not what someone vaguely remembers might have changed.
For example, a fictional shop might discover that a useful buying guide moved to a new address while old internal links were left behind. That gives the team a specific journey to test. It does not establish that every lost visit came from that change.
Do not automatically blame a search update because its date is nearby. Timing can suggest an investigation, but it cannot establish cause on its own.
Check the affected pages directly
Open the important URLs on desktop and mobile. Do they load? Is the main content present? Can visitors use the navigation and contact or purchase controls? Ask your developer to check unexpected errors or redirects.
For indexing concerns, use Search Console’s URL Inspection and the page’s current technical evidence. Our Indexability Checker can help review observable signals, but cannot confirm Google’s indexing decision. A successful page load also does not prove that a page is indexed.
Check Search Console for any reported security issue or manual action. If one exists, follow its specific guidance rather than making unrelated design changes. If the evidence remains unclear, keep that uncertainty in your notes.
Choose one response supported by evidence
A useful task describes the symptom, the suspected cause, the evidence and the check that will confirm the correction. Fixing a broken destination is testable. Restore all traffic is an outcome you cannot guarantee.
If no defect is established, continue monitoring and investigate the affected content and audience demand. Avoid deleting useful pages or adding repeated keywords simply because a chart moved down.
Keep a small incident note: dates, affected URLs, observations, changes made, owner and next review. Our SEO reporting service can help frame the questions to investigate. The immediate aim is a reliable explanation and a proportionate response, not a rushed redesign.