Why Google Analytics Might Not Be Showing Your Website Data

The short version: Google Analytics usually goes quiet because of a broken or missing tracking code, a filter or consent setting blocking the data, a mismatch between your property and your website, or you're simply looking at the wrong date range or the wrong GA4 view. Nine times out of ten it is not Google's fault. It is a setup mistake, and most of them take under ten minutes to fix once you know where to look.

I've had this exact panic call from clients more times than I can count. "Lilach, my traffic has vanished." Three weeks ago it was a boutique candle brand in Kent who rang me convinced Google had "switched off" her account overnight. Her sessions had gone from around 400 a day to zero. Nothing. Not a dip, a total flatline. She'd already emailed Google support (which, by the way, does not really exist for free GA accounts, there is no phone line and barely a help centre form that gets answered). The actual cause took me four minutes to find: her web developer had updated the site the week before and the new template had wiped the GA4 tag from the header entirely. The site was working fine. Google Analytics just wasn't there anymore to see it.

That's the pattern I see again and again. The website is fine. The traffic is probably fine. Analytics just stopped watching, or it's watching the wrong thing, or you're reading it wrong. Let's go through the real reasons, in the order I check them when a client says their numbers have disappeared.

The tracking code isn't on the page anymore

This is the single most common cause I see, easily more than half of the "my data disappeared" cases I've troubleshooted over the past few years. It happens when:

• A site redesign or theme change strips out the header code without anyone noticing
• A plugin that was inserting the GA4 snippet gets deactivated or updated and loses its settings
• Someone migrates the site to a new host and forgets to move the tracking script over
• A caching plugin serves an old cached version of the page that predates the tag being added

The fix: go to Google Tag Assistant (a free Chrome extension from Google) or just open your site, right click, "view page source," and search for your Measurement ID, the one that looks like G-XXXXXXX. If it's not there, that's your answer. Nothing else matters until you get that tag back on every page, not just the homepage.

You set up the property but never checked the data stream

GA4 splits everything into properties and then data streams underneath those properties. I've seen people create a shiny new GA4 property, get given a Measurement ID, paste it in, and never notice that the data stream itself is pointing at the wrong URL, sometimes a staging domain, sometimes a URL with a typo, sometimes an old domain from a previous site version. Go to Admin, then Data Streams, and check the exact URL listed matches your live site exactly, including whether it's the www or non-www version and whether it's http or https. This sounds pedantic. It isn't. Google Analytics treats www.yoursite.com and yoursite.com as different things unless you've told it otherwise, and I've watched traffic "disappear" simply because someone changed which version of the domain redirects to which.

You're on the wrong Google Analytics account or property entirely

This one's embarrassing but common. If you run more than one website, or you've ever handed access to a developer or agency, there's a real chance you're logged in and staring at a different property than the one connected to the site you're worried about. I wrote a full piece on this because it trips up so many small business owners who assume one Google Analytics account covers every website they own, when each site needs its own property set up correctly and you can easily be checking property A while property B is the one connected to your live domain.

Consent mode or a cookie banner is blocking the data before it fires

Since the UK's rules under GDPR and PECR tightened up how cookie consent banners behave, plenty of sites now only fire the GA4 tag after a visitor clicks "accept." If your consent banner is broken, badly coded, or defaults to "reject," Google Analytics simply never fires for most visitors. I've seen sites where the cookie banner button itself was broken on mobile, meaning nobody on a phone could ever click accept, which meant nobody on mobile was ever tracked. That's not a small gap either. Mobile traffic on most UK small business sites now sits somewhere between 55 and 70 percent, depending on the sector. If your consent tool is broken on mobile, you could be blind to well over half your real traffic and never know it.

Test this yourself: open your site in an incognito window, click through the cookie banner exactly as a visitor would, then check GA4's Realtime report (Reports, then Realtime) to see if your own visit shows up within about 30 seconds. If it doesn't, the problem is almost certainly consent related.

Filters are quietly excluding your own traffic, or worse, everyone's

GA4 lets you set internal traffic rules to exclude your own IP address, or your team's, from the data, which is sensible so your own daily visits don't inflate the numbers. The uncomfortable truth nobody likes to admit is that these filters are often set up carelessly, based on an IP address range rather than a single exact IP, and if that range is broader than intended it can end up excluding a chunk of genuine visitors who happen to share part of that IP block, particularly anyone on the same office network, coworking space, or even the same mobile network provider. I've seen a filter meant to exclude one marketing agency's five staff end up blocking an entire IP range used by a regional broadband provider, quietly erasing a slice of real customers from the reports for months before anyone noticed the numbers looked oddly low for that region. Go to Admin, then Data Settings, then Data Filters, and read what each filter excludes rather than assuming it's doing what you think.

You're looking at the wrong date range, comparing against the wrong period, or checking too soon

GA4 processes standard reports with a genuine delay. Realtime data shows within seconds. Standard reports, though, can take 24 to 48 hours to fully process and settle, so if you're checking yesterday's numbers first thing this morning and they look thin, that's often just processing lag, not missing data. I've had clients panic on a Tuesday morning about Monday's "terrible" numbers, only for the report to fill back in by Wednesday afternoon once Google finished processing it. Also check the basics: is the date range set to what you think it is? GA4's default view sometimes reverts to "last 7 days" or "last 28 days" after you've navigated elsewhere in the interface, and it's easy to misread a chart because the comparison period changed without you noticing.

Ad blockers are hiding more of your audience than you'd expect

This is the part most articles on this topic skip entirely, because it's an uncomfortable one for Google Analytics itself: a meaningful share of your real visitors are never counted at all, and there is nothing wrong with your setup. Ad blockers, privacy browsers like Brave, and browser extensions like uBlock Origin block Google Analytics scripts from loading in the first place, by design. Studies over the past few years have put ad blocker usage somewhere between 25 and 40 percent of desktop users in markets like the UK and US, higher among younger, more tech-savvy audiences. That means even a perfectly configured GA4 setup is structurally undercounting your actual traffic, sometimes by a third or more, and no amount of troubleshooting fixes that because it isn't broken, it's just how the tool works. I mention this because I think small business owners deserve to know their "real" traffic is almost always higher than the dashboard says, not lower, and that gap isn't a sign something needs fixing on your end.

Server-side issues and redirects are eating the tag before it fires

If your site uses a redirect chain, say an old URL redirecting to a new one which redirects again to a final page, the GA4 tag on the intermediate pages sometimes never gets the chance to fully load and fire before the browser jumps again. This shows up as pages with disproportionately low pageviews compared to what you know is happening, particularly on campaign landing pages that have been renamed or moved more than once. Check your redirects with a tool like Screaming Frog and count the hops; more than one redirect in a chain is worth fixing regardless of Analytics, because it also slows the page down and affects your actual conversion rate, not just how it gets measured.

You've got GA4 and Universal Analytics data mixed up in your head

Universal Analytics stopped processing new data back in mid 2023, and a lot of business owners still have the old UA property bookmarked, or are looking at historical exports and comparing them against fresh GA4 numbers as if they're the same metric. They're not. GA4 counts sessions and engagement differently to how UA did, so a like-for-like comparison between an old UA screenshot and today's GA4 report will often look like a dramatic drop even when nothing has changed. If you're benchmarking against old numbers, make sure you're benchmarking GA4 against GA4, ideally from the same month a year ago rather than against a UA report from 2022 or earlier.

What I'd check first, in order

• View source on your live site and confirm the Measurement ID is present and matches your GA4 property
• Open Realtime reports and visit your own site in an incognito window to confirm the tag fires
• Check Data Streams in Admin to confirm the URL is exactly right, www vs non-www, http vs https
• Read every active data filter under Data Settings and confirm it isn't excluding more than intended
• Test your cookie consent banner on mobile specifically, not just desktop
• Confirm your date range and give standard reports 24 to 48 hours before panicking about a single day

This is exactly the kind of thing that eats up a business owner's Tuesday afternoon and, honestly, it's also exactly the sort of granular setup issue that quietly costs you weeks of decision-making based on wrong or missing numbers. If you're regularly making marketing or budget calls off a GA4 dashboard that might be lying to you, it might be worth getting someone to audit the setup once rather than firefighting it every few months; I cover what that kind of audit and consultant support typically costs for a small business, and it's usually a lot cheaper than the bad decisions made on broken data.

Worth saying too: even a perfectly working GA4 setup only tells you half the story now. It shows you who found your site through search and clicks, but it does nothing to show whether ChatGPT or Perplexity are quoting your business to someone who never clicks through at all, which is a growing chunk of how people research businesses in 2026. I wrote about discovering my own site was essentially invisible to those tools despite ranking fine on Google, in a post about how my small business site was invisible to ChatGPT until I changed how it was structured. Analytics and AI visibility are two separate problems and fixing one doesn't fix the other.

Once I sorted the candle brand's missing tag, her numbers came straight back the next day, right back around that 400-session mark, nothing sinister, just a code that had gone missing during a template update. It's rarely more dramatic than that. If you want the fuller picture of what GA4 is recording about each of those visitors once the tracking is working, I've broken that down in what data Google Analytics really collects, and if you want proof that fixing the boring technical stuff moves the needle on revenue, not just on a dashboard, that's the story I told in the month my website started paying me again.

Related: data analytics (this site).

Related: ai consultant vs ai agency small business for small businesses.

Frequently asked questions

Why did my Google Analytics data suddenly drop to zero overnight?

The most common cause is a website update, template change, or migration that removed the GA4 tracking code from your site's header without anyone noticing; check "view page source" on your live site for your Measurement ID before assuming anything else is wrong.

Why does Google Analytics show fewer visitors than I know I'm getting?

Ad blockers and privacy browsers stop the GA4 script from loading for somewhere between 25 and 40 percent of users depending on your audience, plus cookie consent banners that default to "reject" or are broken on mobile can silently block over half your traffic from ever being counted, meaning your real numbers are almost certainly higher than the dashboard shows.

How long does it take for Google Analytics data to show up?

Realtime reports update within about 30 seconds, but standard GA4 reports can take 24 to 48 hours to fully process, so a thin-looking report from yesterday or today is often just processing lag rather than a genuine drop in traffic.

Could a filter in Google Analytics be hiding my real traffic?

Yes, internal traffic filters set up to exclude your own team's IP address are sometimes configured too broadly, excluding an entire IP range rather than a single address, which can quietly filter out genuine visitors who share part of that range; check every active filter under Admin, Data Settings, Data Filters to see exactly what it's excluding.

Further reading

• the ICO's guidance on cookies and similar technologies