The short answer
First, check whether the decline appears in both GA4 and Google Search Console. Compare equivalent periods, then isolate affected pages, queries, countries, and devices. Review tracking changes and site releases before blaming an algorithm update. Lower demand, changing search results, and technical problems require different responses. Avoid deleting content or redirecting pages until you know what changed.
GA4 organic sessions fall, but Google Search Console clicks remain stable.
Check: Compare Google organic traffic specifically, then review consent settings, tags, reporting scope, and channel classification.
Next: Investigate measurement before changing pages that may still be attracting search visits.
The decline is concentrated in a particular section, device, or country.
Check: Compare equivalent Search Console segments and identify the pages contributing most to the loss.
Next: Narrow the investigation to shared templates, audience differences, and affected search queries.
Search clicks fall after a release or URL change.
Check: Review response codes, redirects, robots rules, noindex directives, canonical URLs, and server availability.
Next: Verify the suspected fault on affected URLs before asking developers to change the wider site.
Impressions or clicks decline without an obvious technical change.
Check: Examine seasonal demand, query patterns, search result changes, and relevant update dates.
Next: Separate demand changes from visibility losses before choosing content or technical work.
Establish whether search visits actually fell
I start by checking whether the reports describe the same problem. GA4 sessions and Search Console clicks measure different events, so their totals should not be treated as interchangeable. In GA4, isolate Google organic traffic rather than comparing every search engine with Search Console. Check the property, hostname, reporting time zone, and date boundaries before interpreting the gap.
My next step would be to place tracking and consent changes beside the decline. A changed consent banner, missing tag, or altered channel classification can affect recorded visits without explaining a search visibility loss. Compare complete periods with matching weekdays, then check seasonal context. I would keep a short evidence note separating confirmed measurement faults from questions that still need testing.
- Check the same hostnames and search source.
- Exclude incomplete reporting days.
- Record consent and tag changes separately.
Find where the loss is concentrated
Search Console lets you compare clicks, impressions, click-through rate, and average position across pages, queries, countries, and devices. These measurements describe different aspects of search performance; a click decline does not automatically mean rankings fell.
I would first identify which page groups account for the missing clicks, then examine their query mix. If impressions hold while click-through rate falls, I would inspect the visible results and competing answers before rewriting the page. If impressions shrink while position appears stable, I would test a demand explanation rather than assume it. An overall average can conceal opposing movements, so compare consistent query and page groups. Save a brief finding for each affected group, including evidence that contradicts your initial explanation.
- Separate branded from nonbranded searches.
- Compare mobile and desktop patterns.
- Keep country filters consistent.
Connect technical symptoms to actual releases
I would review deployment notes against the first visible change, then test affected URLs alongside unaffected examples. Useful checks include server errors, unexpected redirects, robots.txt restrictions, noindex directives, and missing content after rendering. A date match is a lead, not a diagnosis: the suspected change should explain which pages lost traffic and which did not.
After fixing an access or indexing problem, URL Inspection can help check individual pages and request recrawling. A request does not guarantee indexing or immediate processing. For the implementation handoff, I recommend documenting the failing URL, observed behavior, intended behavior, and a verification method. This makes technical SEO work concrete and helps distinguish a WordPress setting change from an issue requiring specialist development.
If affected pages are no longer indexed, follow the website-not-on-Google checks. For broader improvements after the cause is understood, see how to increase organic traffic.
- Test the final destination, not just the redirect.
- Check server behavior during the affected period.
- Verify the fix on representative templates.
Check whether URL changes disrupted the right pages
Redirects and canonical annotations can help consolidate duplicate or similar URLs. Google uses canonical signals when selecting a representative URL; an annotation is not an unconditional instruction. That makes consistency important when a migration or template change introduces competing versions.
My preferred migration check starts with previously valuable landing pages and follows each path to its current destination. Does the destination answer the same need? Do internal links point there? Is a product URL now landing on an unrelated category? I would separate genuine replacements from pages that still serve a distinct purpose. Avoid treating every declining URL as a redirect candidate: first document its role, current status, and relationship to the proposed destination. For larger changes, a reviewed URL map makes developer decisions easier to verify.
- Inspect old and current URL versions.
- Resolve conflicting destination signals.
- Keep useful, distinct pages separate.
Distinguish demand changes from search visibility changes
Google identifies changing search interest and ranking updates among possible causes of traffic drops. An update announcement overlapping a decline does not establish causation. A manual action is different: check Search Console’s Manual Actions report rather than inferring one from traffic.
I would compare affected topics with the site’s seasonal pattern, then inspect results for the same queries and target market. More ads, shopping results, or prominent answers can change the opportunity to earn clicks. Keyword research offers estimated demand, not evidence of your rankings. I would use it as context beside actual search data. If the loss is topic-specific, investigate that topic before commissioning a sitewide rewrite. Save dated observations, since a search result screenshot represents that moment, not every searcher’s experience.
- Compare equivalent seasonal periods.
- Check results in the affected market.
- Label update explanations as hypotheses.
Turn the diagnosis into a focused work plan
Google’s people-first content guidance emphasizes usefulness, trustworthy sourcing, and a clear purpose for the intended audience. If an affected page no longer answers its readers’ needs, improving that answer is a better editorial objective than adding text simply to appear updated.
I recommend a response log that names the problem, supporting evidence, responsible person, proposed change, and review condition. Fix confirmed access or measurement faults before using traffic trends to judge a rewrite. For content problems, decide whether to clarify the answer, replace outdated information, strengthen source checks, or improve contextual links. A focused content strategy should explain what stays as well as what changes. Preserve a baseline and review affected groups separately. Recovery is not guaranteed, and broad changes made together can make later results harder to interpret.
- Prioritize confirmed faults over speculative changes.
- Assign implementation and verification owners.
- Avoid mass deletion without page-level evidence.
Common questions
GA4 traffic dropped, but Search Console clicks did not. Which report should I trust?
Use each report for the question it measures. Search Console describes Google Search performance; GA4 records activity according to your measurement setup. Stable clicks alongside lower recorded sessions make tags, consent, reporting scope, and attribution sensible starting points. They do not prove that everything after the search click is working correctly.
Should I delete pages that lost organic traffic?
Not on that evidence alone. A page may have lost visits because of tracking, demand, a technical fault, or a changed search result. I would first establish its purpose, accuracy, uniqueness, and relationship to other pages. Keep, improve, consolidate, or remove it only when that review supports the decision.
How will I know whether the response is working?
Define a check that matches the diagnosis. A technical fix needs verification of the corrected behavior; a content change needs review of the affected page and query groups. Compare consistent periods and note other changes that could influence the result. A successful implementation and a traffic recovery are related questions, not the same outcome.