Get found

Google traffic dropped. Check these things in order

A calm investigation sequence for a search traffic decline, from report freshness and tracking to affected pages and search demand.

START HERE

Confirm the drop in complete data, identify the affected pages and separate a search decline from a recording problem before changing content.

A downward line is uncomfortable, especially when the website brings enquiries or sales. Start by identifying what actually fell. Search impressions, search clicks and recorded sessions are related, but they answer different questions.

Confirm the dates and the shape

Exclude a partial reporting day. Compare equal periods and check whether the change is a single-day wobble or a sustained pattern. Note holidays, campaigns, website releases and tracking changes without immediately deciding that one caused the drop.

Google's traffic-drop investigation guide covers technical issues, changing demand, ranking changes and other possible causes. Use those as investigation branches, not a ready-made diagnosis.

Find the pages responsible

Sort by lost clicks in a page comparison. A small site can lose much of its traffic when one seasonal article stops attracting interest. That calls for a different response from hundreds of pages disappearing after a deployment.

Illustrative example: overall clicks fall from 600 to 420. One seasonal page accounts for 150 of the 180 lost clicks. Investigate that page and its queries first. Rewriting the entire site would spread effort across pages that may be working normally.

Compare the two sources

If Search Console clicks are steady while GA4 sessions collapse, inspect measurement and consent behaviour. If both decline on the same pages, investigate search visibility and the website itself. The sources do not need to have equal counts to provide useful directional evidence.

Open a few affected URLs. Check the actual response, visible content and intended next step. Use Search Console's indexing and inspection tools for pages that may have become inaccessible or excluded. Ask a developer to inspect recent releases if the timing and page group match.

Look at the question people are asking

Compare affected query groups. Has demand fallen for the subject? Has the page become outdated? Does the page still answer what people expect from that search? Google Trends can help with context, but its relative interest figures are not a replacement for your own traffic counts.

Avoid copying a competitor simply because its page currently appears above yours. Identify the useful answer or evidence your page lacks. Sometimes the right action is updating an expired offer or removing a recommendation that no longer fits.

Make a reversible first move

Fix confirmed technical faults promptly. For content, record the problem and choose a focused update. Save the previous version. A ranking change with no clear page defect deserves more investigation before a sweeping rewrite.

AbstractMetrics helps you compare periods and inspect page activity beside search metrics. Next actions can highlight a related concern, but it does not automatically determine the cause of a traffic drop. Ask ChatGPT to list the strongest evidence and the next verification step separately.

What to watch afterwards

Track the affected group separately from the whole site. Record recovery timing and other changes that could explain it.

Take this to ChatGPT

Investigate my search traffic drop using connected reports. Identify the affected pages, compare search clicks with recorded Google organic activity, and give the next verification step without inventing a cause.

You choose what to share. Copying does not send anything or connect an account.

Sources and further reading

Official guidance checked on 16 October 2026. Examples and suggested workflows are our own.