Did Website Traffic Drop, or Did Analytics Stop Tracking It?

Website traffic suddenly drops.

GA4 shows fewer users. Organic sessions are down. Conversions are down. Someone opens the monthly report and immediately starts looking for an SEO problem.

Sometimes there really is a traffic problem.

Other times, the visitors are still coming and the website has simply stopped measuring some of them.

This happens more often than many businesses realize, especially after:

• A website redesign
• A theme change
• A migration
• A new cookie consent banner
• A Google Tag Manager update
• A checkout or booking platform change
• A new form
• A domain change
• A developer deployment
• A change to GA4 or Google Ads tracking

Before changing SEO strategy, rebuilding pages, or trying to recover rankings, confirm what actually dropped.

The first comparison should usually be GA4 versus Google Search Console.

GA4 and Search Console measure different parts of the visit

Google Search Console reports what happens in Google Search.

It can show:

• Impressions
• Clicks
• Queries
• Landing pages
• Average position
• Click-through rate

GA4 begins measuring after the visitor reaches the website and the analytics setup successfully records the visit.

That distinction is extremely useful during troubleshooting.

A person can click your result in Google and reach the website while GA4 fails to record the session.

Search Console may therefore show stable search traffic while Analytics reports a large decline.

When those two systems suddenly begin disagreeing around the same date, investigate measurement before assuming Google rankings collapsed.

Start with the date the decline began

Find the first date where the numbers clearly change.

Do not begin with a vague comparison like “traffic seems lower this month.”

Look for a specific point in time.

Then ask what changed around that date.

A sudden decline that starts on the exact day of a website launch, tracking deployment, cookie banner update, or hosting migration deserves very different investigation from a gradual six-week decline in Search Console impressions.

The shape of the graph can tell you a lot.

A sharp drop on one specific day

This often points toward a technical or measurement change.

Check tracking, templates, tags, consent, domain configuration, redirects, and any deployment that occurred around the same time.

A gradual decline over several weeks

Look more closely at rankings, impressions, affected pages, search demand, indexing, content changes, and competition.

Traffic drops to almost exactly zero

Start with tracking.

Large websites rarely lose nearly all legitimate traffic overnight without some other major symptom.

One section drops while the rest of the website remains normal

Investigate the templates and tracking used by that section.

A blog, ecommerce checkout, landing-page system, or booking platform may use completely different code from the rest of the site.

Compare Search Console clicks with GA4 organic traffic

This is one of the fastest ways to narrow the problem.

Suppose GA4 shows organic sessions dropping by 40 percent.

Now open Search Console and compare Google Search clicks over the same period.

Search Console clicks are also down

You may have a real search traffic decline.

Continue investigating:

• Pages that lost clicks
• Queries that lost impressions
• Average position
• Indexing
• Redirects
• Canonicals
• Internal links
• Content changes
• Search demand
• Google updates
• Competitor movement

Search Console clicks are stable

Tracking moves much higher on the list.

Google is still reporting users clicking through from search.

Now determine why GA4 stopped seeing some of them.

Search Console clicks increased while GA4 organic traffic decreased

That is an especially strong reason to review measurement.

The search engine is reporting more visits from Google while the website analytics system is reporting fewer.

That gap deserves investigation before anyone starts rewriting pages.

Do not expect GA4 and Search Console to match exactly

These platforms use different definitions and collection methods.

You should expect some difference between them.

Search Console records Google Search activity.

GA4 records website activity after Analytics successfully loads and processes the visit.

Differences may result from:

• Consent
• Tracking prevention
• JavaScript
• Session attribution
• Time zones
• Data processing
• User behavior
• Duplicate or missing tags
• Cross-domain navigation

The important signal is a meaningful change in the relationship between the systems.

For example, if Search Console and GA4 generally followed the same trend for a year and suddenly separated after a redesign, that change is worth investigating.

Confirm GA4 is actually loading

Open the website and confirm the GA4 measurement setup still exists.

Depending on the site, analytics may be installed through:

• Google Tag Manager
• A WordPress plugin
• Shopify
• Theme code
• A custom integration
• A consent management platform
• Google’s direct gtag.js implementation

Check more than the homepage.

Test representative pages such as service pages, articles, landing pages, thank-you pages, product pages, and any templates involved in the reported decline.

A redesign can preserve tracking on one template while removing it from another.

Check GA4 Realtime

GA4 Realtime is useful for a quick controlled test.

Open the website in a separate browser or device and navigate through several pages.

Then look for your activity in Realtime.

If nothing appears, investigate further.

If the visit appears normally, that confirms at least some traffic is still being recorded.

Realtime does not prove the entire implementation is correct, but it is a useful first check.

Use Google Tag Manager Preview when GTM is involved

If the website uses Google Tag Manager, Preview mode provides much more detail.

You can see:

• Whether the container loaded
• Which tags fired
• Which tags did not fire
• Which triggers activated
• Consent status
• Event names
• Variables
• Page navigation
• Form interactions

This becomes especially important after a redesign.

A GTM container may still be installed while the triggers inside it depend on elements that no longer exist.

For example, a form submission trigger may have relied on:

form_submit_success

The redesigned form might now use:

form_confirmation

The website works.

The lead submits.

The tracking trigger never fires.

A theme or template change may have removed the tracking code

Analytics code is sometimes installed directly inside:

• header.php
• functions.php
• A theme options panel
• An Elementor integration
• A page builder
• A custom template
• A code-snippet plugin

Replacing the theme can remove that code.

A new developer may also rebuild the site without realizing that the previous theme contained:

• GA4
• Google Tag Manager
• Google Ads conversion tracking
• Meta Pixel
• Call tracking
• Custom event scripts

The redesigned site may look completely correct while measurement quietly disappears.

Duplicate tracking can also corrupt the numbers

Missing tracking receives most of the attention, but duplicate tracking causes its own problems.

A redesigned site may accidentally contain GA4 through:

• Google Tag Manager
• A WordPress plugin
• Theme code
• A hosting integration

at the same time.

This can produce:

• Duplicate page views
• Duplicate events
• Inflated sessions
• Inflated conversions
• Strange engagement metrics

The problem may become visible later when one of the duplicate implementations is removed.

For example, traffic may appear to fall 30 percent after a redesign because the previous site had been overcounting activity.

That is still important to understand.

The new measurement may actually be more accurate.

Check whether the GA4 property changed

Sometimes the website still sends analytics data, just to the wrong property.

This can happen during:

• A rebuild
• An agency transition
• A staging deployment
• A new Google account setup
• A tag replacement
• A Shopify migration
• A copied GTM container

Confirm the actual GA4 Measurement ID used by the live website.

Then compare it with the property you are reviewing.

A perfectly functioning analytics implementation provides no useful data if everyone is looking at a different property.

Check the Google Tag Manager container ID

The same problem can happen with GTM.

A developer may accidentally install:

• The staging container
• An old container
• A new empty container
• A container owned by a previous agency

Confirm that the live website is using the expected production container.

Then confirm that the published container version actually includes the current GA4 setup.

Cookie consent can significantly change reported traffic

A new consent banner is one of the first things I would investigate when GA4 falls after a website update but Search Console remains relatively steady.

Modern consent systems can control whether analytics and advertising tags are allowed to run.

Problems can occur when:

• Analytics is blocked until consent
• The banner never properly records consent
• Tags remain denied after the visitor accepts
• Different pages use different consent settings
• The consent tool loads after GTM
• A template excludes the consent script
• Consent Mode is configured incorrectly
• Geographic rules change tracking behavior
• A plugin update resets configuration

A reduction in measured traffic may also be legitimate if the previous site tracked visitors before consent and the new site handles consent more carefully.

That context matters when comparing periods.

Test with consent accepted and denied

When a consent platform is involved, perform controlled tests.

Test the website:

1. Before interacting with the banner
2. After accepting analytics cookies
3. After rejecting optional cookies
4. In a fresh private browsing session

Watch what happens in:

• Tag Assistant
• GTM Preview
• GA4 Realtime
• Browser network requests

You want to understand what the website actually does under each consent state.

Browser privacy features can affect measurement

Some visitors block or restrict analytics through:

• Browser privacy settings
• Tracking protection
• Ad blockers
• Network-level filtering
• Corporate security tools

That is normal.

The goal is not to force every browser to report analytics data.

The useful question is whether something changed that suddenly caused a much larger portion of legitimate traffic to go unmeasured.

Check whether one device category changed

Break the traffic decline down by device.

Compare:

• Desktop
• Mobile
• Tablet

If desktop remains normal while mobile traffic suddenly collapses, look for something specific to the mobile experience.

Possible causes include:

• Mobile consent behavior
• Responsive templates
• JavaScript errors
• Missing tracking code
• Mobile redirects
• Different navigation
• Embedded content
• Browser-specific issues

Search Console can also help determine whether Google Search clicks declined on the same device.

Check browser differences

A problem may affect:

• Chrome
• Safari
• Firefox
• Edge
• Mobile Safari
• Android browsers

Safari deserves particular attention because its privacy protections can make measurement behavior different from Chrome.

A redesign may also introduce code that fails in one browser while appearing normal in another.

Compare the decline by browser if the available analytics data allows it.

Check landing pages

Do not look only at the sitewide traffic total.

Sort organic traffic by landing page.

Ask:

• Which pages lost the most sessions?
• Did every page decline?
• Did one template decline?
• Did blog posts remain stable?
• Did service pages disappear?
• Did ecommerce pages change?
• Did the homepage remain normal?

Then compare those pages in Search Console.

If a page lost GA4 traffic but Search Console clicks stayed stable, tracking on that page becomes a strong suspect.

If both systems show a similar decline, investigate the page’s search visibility.

Tracking can break on specific page templates

This is particularly common with WordPress and custom development.

A website might have separate templates for:

• Pages
• Posts
• Products
• Locations
• Landing pages
• Custom post types
• Checkout
• Thank-you pages

One template can be missing the tag while the others continue reporting normally.

The overall traffic drop may therefore reflect a technical problem affecting only one part of the site.

Embedded systems require extra attention

Many websites rely on embedded third-party platforms for:

• Forms
• Booking
• Ecommerce
• Payments
• Applications
• Scheduling
• Quoting

A user may begin on the main website and complete the important action inside:

• An iframe
• A subdomain
• Another domain
• A vendor-hosted checkout
• A booking platform

A redesign or vendor update can affect cross-domain measurement.

The website may still receive the visitor.

The transaction may still happen.

Analytics may lose continuity once the visitor crosses into the external platform.

Check cross-domain tracking

Cross-domain tracking is important when users move between domains as part of one journey.

Without proper configuration, GA4 may:

• Start a new session
• Assign the referral incorrectly
• Lose the original source
• Treat the external platform as a referral
• Fragment the customer journey

This can make organic traffic appear weaker even when lead or sales volume remains stable.

Check whether the redesign changed:

• Booking providers
• Checkout domains
• Payment pages
• Subdomains
• Embedded forms
• Referral exclusions
• Cross-domain configuration

Redirects can change attribution

URL redirects can also affect measurement.

A user might click:

https://example.com/old-service/

and be redirected to:

https://example.com/new-service/

That is usually fine when implemented properly.

More complicated redirect chains can introduce:

• Tracking parameters being stripped
• Cross-domain jumps
• Referral changes
• Lost UTM parameters
• Broken campaign attribution

Test the complete URL path rather than only the final destination.

Check whether UTMs are surviving

Paid campaigns, email campaigns, social campaigns, QR codes, and partner links often rely on UTM parameters.

A redesign may introduce redirects that remove them.

For example:

?utm_source=google&utm_medium=cpc

may disappear before the visitor reaches the final page.

GA4 can then classify the session differently.

Campaign traffic appears to drop even though the visitors still arrived.

Organic traffic can be misclassified

GA4 traffic channels depend on attribution rules.

A change to:

• Redirects
• Cross-domain configuration
• Referral exclusions
• Consent
• Landing pages
• Campaign parameters
• Session handling

can move visits into different channels.

Look for corresponding increases in:

• Direct
• Referral
• Unassigned
• Paid Search
• Organic Social

Sometimes the traffic did not disappear.

It moved into another reporting bucket.

Compare total users, not only organic sessions

Suppose Organic Search falls significantly.

Now look at total users.

If total users remain relatively stable while another channel suddenly grows, attribution may have changed.

If total users fall by a similar amount, missing tracking becomes more plausible.

Then compare Search Console to determine whether Google still sent the visitors.

No one metric provides the entire answer.

Check conversions separately

Traffic tracking can work while conversion tracking fails.

A redesigned form may still receive visitors while the old GA4 event no longer fires.

For example, the old site may have tracked:

generate_lead

after a successful form submission.

The redesigned site may show the same confirmation message but never send that event.

GA4 reports:

• Stable traffic
• Fewer conversions
• Lower conversion rate

The business may still be receiving the leads.

Check the real system of record:

• Form entries
• CRM
• Orders
• Booking system
• Phone calls

Then compare those outcomes with GA4.

Google Ads conversions can fail separately from GA4

A business may also report that “website conversions dropped” when the issue exists only inside Google Ads.

Check whether conversions are tracked through:

• Google Ads directly
• GA4 imports
• Google Tag Manager
• A CRM import
• Enhanced conversions
• A third-party booking platform

Confirm:

• The action still fires
• The correct action is marked Primary
• The Ads account uses the expected conversion goals
• GA4 events are imported correctly
• The conversion action is active
• Attribution windows did not change

Paid campaign performance should not be judged from a broken conversion action.

Check whether the form actually stopped working

When conversions decline, perform a real test.

Submit the form.

Then follow it.

Confirm:

• The form displays success
• The entry saves
• The notification sends
• The CRM receives the lead
• The correct salesperson receives it
• GA4 records the event
• Google Ads records the conversion when applicable

A functioning website can have broken tracking.

A functioning tracking setup can also record a conversion for a lead that never reached the sales team.

Those should be tested independently.

Compare Analytics with business data

Analytics should be compared with the systems that actually run the business.

Useful sources may include:

The more systems agree, the more confidence you can have in the diagnosis.

If GA4 reports a 40 percent decline while Search Console, CRM leads, orders, and server traffic remain stable, the evidence points strongly toward measurement.

If all of them decline at roughly the same time, the business likely has a real acquisition problem to investigate.

Server logs can help when analytics is questionable

Server logs record requests made to the website independently of GA4.

They can help answer whether real traffic to the server changed.

Server logs are especially useful when:

• Analytics disappeared completely
• JavaScript tracking is unreliable
• A redesign changed the tag setup
• Bot traffic needs to be separated
• There is disagreement between platforms

Log analysis is more technical, but it provides another source of evidence when browser-based measurement cannot be trusted.

Check for JavaScript errors

GA4 and GTM rely heavily on JavaScript.

A JavaScript error can interrupt:

• Tag loading
• Event handling
• Form tracking
• Consent management
• Ecommerce tracking
• Dynamic navigation

Open browser developer tools and review the console.

Test:

• Homepage
• Service pages
• Forms
• Ecommerce
• Mobile navigation
• Embedded systems
• Thank-you pages

Errors introduced during a redesign may affect tracking without visibly breaking the page.

Single-page applications require special handling

Some modern websites change content without performing a traditional full page load.

GA4 may need additional configuration to correctly track those virtual page changes.

Without it, visitors can browse several screens while Analytics records only the initial view.

If a redesign introduced React, Vue, another JavaScript framework, or app-style navigation, confirm that route changes are being measured correctly.

AJAX forms can break old tracking methods

Older form tracking often depends on a thank-you page.

A redesigned form may submit through AJAX and display a message without changing URLs.

The form still works.

The previous conversion trigger may have depended on visiting:

/thank-you/

That visit never happens anymore.

Tracking needs to listen for the successful form event instead.

This is one of the most common ways a redesign can break conversion reporting while leaving the actual form intact.

Check whether thank-you pages still exist

If your analytics or advertising setup depends on a thank-you page, confirm:

• The form still redirects there
• The URL did not change
• The page is accessible
• The conversion tag still loads
• The page is not being visited before conversion
• Refreshing the page does not create duplicate conversions

A page-view-based conversion should only be used when reaching that page reliably represents the completed action.

Call tracking may have changed

Websites that use dynamic number insertion can lose call attribution after:

• Theme changes
• JavaScript changes
• Consent changes
• Call-tracking script removal
• Phone number markup changes
• A provider account change

The displayed phone number may still work while call attribution disappears.

Compare:

• Actual phone volume
• Call tracking
• GA4 call events
• Google Ads call conversions

Ecommerce tracking can break while sales continue

A redesigned ecommerce site may still process orders correctly while GA4 loses:

• add_to_cart
• begin_checkout
• purchase
• Revenue
• Product data
• Transaction IDs

Compare GA4 with the ecommerce platform.

If Shopify or WooCommerce reports normal orders while GA4 purchases disappear, investigate tracking before questioning the sales funnel.

Also watch for duplicate purchase events caused by confirmation pages being reloaded.

Look for changes in hostname reporting

Domain and subdomain changes can create confusing analytics behavior.

Check whether traffic is being recorded under:

• www.example.com
• example.com
• shop.example.com
• booking.example.com
• A staging domain
• A vendor hostname

A redesigned system may send data from a new hostname that filters or reports exclude.

Filters can hide valid traffic

GA4 data filters can exclude:

• Internal traffic
• Developer traffic
• Test traffic

Incorrect rules can exclude legitimate visitors.

Review filters when the decline coincides with:

• Office IP changes
• VPN deployment
• Network changes
• New internal traffic definitions
• Analytics configuration changes

Be cautious when activating filters because some filtering decisions cannot be applied retroactively.

Reporting changes can create an apparent decline

Sometimes the website and tracking remain unchanged.

The report changed.

Check whether someone modified:

• Date ranges
• Channel definitions
• Comparisons
• Explorations
• Filters
• Audiences
• Attribution settings
• Looker Studio data sources
• Dashboard connectors

A broken dashboard can create a very convincing traffic emergency.

Always compare the underlying source data before troubleshooting the website based on one report.

Search Console can have reporting quirks too

Search Console provides excellent diagnostic data, but it also needs context.

Query data can vary because of:

• Privacy filtering
• Search appearance
• Country
• Device
• Search type
• Date range
• Reporting delays

Use trends rather than expecting GA4 and Search Console totals to reconcile perfectly.

The value comes from determining whether Google Search activity changed in the same direction.

Traffic may genuinely have dropped

After verifying measurement, there may still be a real traffic problem.

Possible causes include:

• A redesign
• URL changes
• Missing redirects
• Removed content
• Incorrect canonicals
• noindex directives
• Robots restrictions
• Lost internal links
• Search intent changes
• Ranking losses
• Seasonality
• Lower search demand
• Competitor improvements
• Google search updates
• Server availability problems

At that point, SEO investigation makes sense.

Our guide on why search traffic drops after a website redesign goes deeper into those causes and how to diagnose them.

A practical diagnostic sequence

When someone tells us traffic dropped, I would work through the evidence in roughly this order:

1. Identify the exact date the decline began.
2. Compare GA4 with Search Console.
3. Determine which pages, devices, and channels changed.
4. Confirm GA4 and GTM are present on the affected templates.
5. Test tracking in Realtime and Tag Assistant.
6. Review consent behavior.
7. Confirm the correct GA4 property and GTM container.
8. Look for changes in Direct, Referral, and Unassigned traffic.
9. Check real leads, orders, bookings, and phone calls.
10. Test important conversion actions.
11. Review cross-domain tracking and external platforms.
12. Check server logs when browser analytics remain questionable.
13. Investigate SEO only after confirming the search traffic itself declined.

That order avoids spending hours “fixing SEO” when the original problem was a missing analytics tag.

When the decline followed a website redesign

A redesign deserves special attention because several systems may change at the same time.

The project may involve:

• New templates
• New code
• New forms
• New URLs
• New hosting
• New cookie consent
• New Tag Manager setup
• New tracking events
• New checkout behavior
• New third-party integrations

Document the exact launch date and compare it with the first date the analytics trend changed.

Then separate the investigation into two questions:

Did fewer people reach the website?

Use Search Console, server data, rankings, paid clicks, and other acquisition sources.

Did fewer visits get recorded?

Use GA4, Tag Assistant, GTM Preview, consent testing, browser tools, and template comparisons.

Both problems can happen at the same time.

Do not immediately replace the analytics setup

When reporting looks wrong, rebuilding GTM or replacing every tag can make diagnosis harder.

First determine:

• What currently fires
• What used to fire
• Which pages are affected
• When the behavior changed
• Whether the business data also changed

Then correct the confirmed failure.

Preserving evidence is particularly important when several developers or agencies have worked on the website.

Document the working setup after the repair

Once tracking works correctly, document:

• GA4 property ID
• GTM container ID
• Who owns each account
• How consent is configured
• Which conversions are tracked
• What triggers each conversion
• Cross-domain settings
• Important referral exclusions
• Ecommerce configuration
• CRM imports
• Google Ads conversion sources

This makes future redesigns and migrations considerably safer.

A developer should not have to reverse-engineer the entire analytics setup every time the website changes.

When a technical website assessment makes sense

A broader review can help when:

• GA4 and Search Console disagree significantly
• Traffic dropped after a redesign or migration
• Nobody knows how tracking was originally installed
• Several analytics implementations are present
• Conversions disappeared
• Forms and CRM data disagree with GA4
• A cookie consent change coincided with the decline
• Cross-domain tracking is involved
• An outside booking or ecommerce platform is involved
• Several developers or agencies have changed the setup
• SEO and tracking problems may be happening simultaneously
• Previous troubleshooting has produced conflicting explanations

Kismet’s Technical Website Assessment can review the website, tracking configuration, Search Console data, templates, integrations, redirects, and connected systems to identify what changed and what the evidence actually supports.

For problems specifically involving form submissions, CRM delivery, lead routing, or conversion tracking, our Website Lead Workflow Assessment can trace one complete lead path through the connected systems.

—

Find out whether the traffic disappeared or the measurement did

A traffic graph can show that something changed.

It cannot always tell you what changed.

Kismet can review the website, GA4, Google Tag Manager, Search Console, consent setup, conversion tracking, and connected systems to determine whether the decline reflects real traffic loss, broken measurement, or a combination of problems.

Request a Technical Assessment

Or

Website Lead Workflow Assessment

—

Written by Joey Zuccarini
COO at Kismet Creative Co.