Products SEO & GEO Agent Paid Ads Agent Website Agent Conversion Agent
How it works Pricing FAQ Blog Book a call

Technical SEO audit with Google Analytics: what GA4 reveals

Updated · 7 min read

Short answer GA4 can't crawl your site, but it shows where real visitors hit technical trouble. Check five things: search landing pages whose visits collapsed, error pages people reach, pages much worse on phones, browsers with oddly low engagement, and visits on the wrong hostname. Then confirm each suspect in Search Console or on the page itself.

Want help applying this to your business? Talk it through on a free 30-minute call.

Book a call

What GA4 can and can't tell you in a technical audit

GA4 records people, not search engines. Its tag runs in a visitor's browser, and it drops bots on purpose:

"In Google Analytics properties, traffic from known bots and spiders is automatically excluded." (Analytics Help: Known bot-traffic exclusion)

So Googlebot never shows up in GA4. Whether Google can crawl and index a page is Search Console's job. GA4's job is the human side: a page that loads broken on phones, an error page people keep landing on, a page whose search visits suddenly stopped. Google's own split:

"The source of truth for Search performance will always be Search Console, while the source of truth for behavior inside your site will be Google Analytics." (Google Search Central: Using Search Console and Google Analytics data for SEO)
GA4 can showOnly Search Console (or a crawler) can show
Search landing pages that lost their visitsWhy: noindex, redirect, robots.txt block, not indexed
Error pages real people reach, and from whereThe HTTP status code a page returns
Pages that do much worse on phones or one browserHow Googlebot renders the page
Visits landing on a staging site or old domainWhich version Google treats as the main one (canonical)
Speed for real visitors, only with extra setupCore Web Vitals, with no setup

GA4 is free ("free of charge", per Google's Analytics page). If you have only an hour, start with Search Console: the reports to read. GA4 adds the "where do people get stuck" half.

Before you start: clean data

Two checks so you don't chase ghosts:

  1. Your own visits. Exclude your office IP address under Admin > Data streams > Configure tag settings > Define internal traffic, then turn the data filter on. Google warns the effect "is permanent", and you need the Editor role (Analytics Help: Filter out internal traffic).
  2. Calls and forms counted. Otherwise "engaged but no leads" can't be read. See GA4 key events.

Use at least three months of data: on a small page, one visit swings the rates.

Check 1: search landing pages that lost their visits

A page that drops from steady search visits to almost none usually has a technical cause, not a content one.

  1. Open Reports > Engagement > Landing page (Analytics Help: Landing page report).
  2. Add a filter: Session default channel group, exactly matches, Organic Search.
  3. Compare the last 28 days with the 28 days before, or with the same weeks last year if your business is seasonal.
  4. List every page that fell to near zero while similar pages held steady.

Then paste each one into Search Console's URL Inspection tool. Common causes: a redesign changed the address with no redirect, a noindex tag left on, or the page fell out of the index. See traffic dropped after a redesign and crawled or discovered, not indexed.

If every page fell on the same day, suspect the tag before Google. Search Central lists "pages on your website where the Analytics tag is missing" as a reason GA4 and Search Console disagree. If Search Console clicks held steady, your tracking broke, not your rankings.

Check 2: error pages people actually reach

GA4 can't see a 404 status, but it sees the page title. The Page title dimension is your page's title tag, the name a browser tab shows (Analytics Help: Page title). Most error pages share one title, such as "Page not found".

  1. Open Reports > Engagement > Pages and screens.
  2. Switch the table to Page title and screen class, and search for "not found" (or your error page's title).
  3. Switch to Page path to see which broken addresses people asked for.
  4. To see where they came from, build a Path exploration ending at that page. Google says it lets you "choose a page or screen to start or end with" (Analytics Help: Pages and screens report).

Fix the ones with visits: redirect a moved page to its new address, fix the internal link that points at the dead one. A 404 nobody reaches can stay.

One trap GA4 can't catch: an error page that returns a 200 "success" code. Google may then report it as a soft 404, because "If the content suggests an error for Google Search, an empty page or an error message, Search Console will show a soft 404 error." (Google Search Central: How HTTP status codes affect Google's crawlers)

Check 3: pages that break on phones

Phones matter most because Google ranks the phone version:

"Google uses the mobile version of a site's content, crawled with the smartphone agent, for indexing and ranking." (Google Search Central: Mobile site and mobile-first indexing best practices)
  1. In the Landing page report (organic filter on), add the secondary dimension Device category: desktop, mobile, tablet.
  2. Add the Engagement rate metric with Customize report > Metrics > Add metric. It's hidden by default, and you need the Editor or Administrator role (Analytics Help: Engagement rate and bounce rate).
  3. Compare each page's mobile and desktop rows.

An engaged visit lasts over 10 seconds, has a key event, or views 2 or more pages (Analytics Help: Engagement rate and bounce rate). Phones often run a bit lower everywhere. A single page where mobile is far below desktop, while other pages show a small gap, points at that page.

Then open it on your own phone. Look for a pop-up covering the text, a menu or button that doesn't work, a form that won't submit, or a slow first screen. Google also asks that "your mobile site contains the same content as your desktop site": if the phone layout hides sections, Google may never see them.

Check 4: browsers or systems with oddly low engagement

Reports > Tech > Tech details breaks visits down by browser, operating system, screen resolution and device (Analytics Help: Tech details report; Tech overview report). Its Engagement rate and Key events columns are there by default; look for one browser far behind the rest. If Safari visitors engage at half the rate of Chrome visitors, test the site in Safari on an iPhone. Broken scripts, fonts and booking widgets often fail in one browser only.

Check 5: visits on the wrong address

In the Pages and screens report, add the Hostname dimension, the domain part of each visited address (Analytics Help: Pages and screens report). You should see only your real domain. Organic search visits on staging.yoursite.com, an old domain or a builder's preview address mean Google indexed a copy of your site. Block or redirect it, and check it in Search Console.

Also look for (not set) in the Landing page column. Google says it "can appear for the landing page dimension when a session doesn't have a page_view event" (Analytics Help: (not set) values in reports). A large share usually means a tag or consent-banner setup problem, which a web person fixes.

Page speed: GA4 doesn't measure it out of the box

GA4 has no built-in speed report. Google's web.dev team shows how to send Core Web Vitals into GA4: add the web-vitals JavaScript library and export to BigQuery, where you query with SQL (web.dev: Measure and debug performance with GA4 and BigQuery). The BigQuery sandbox's free tier covers the first 1 TB of queries a month. Useful for a developer; overkill for most owners. Search Console's Core Web Vitals report and PageSpeed Insights need no setup. See Core Web Vitals.

Get an alert instead of checking every week

GA4 custom insights watch a number and email you. Set the segment to organic search, the metric to sessions, and the condition to "Has anomaly", and Analytics decides when a change is unusual. You can create up to 50 per property, with the Editor role (Analytics Help: Analytics Intelligence and custom insights). A sudden drop then reaches you in days, not at your next audit.

Example

Illustrative cases. Numbers are invented.

An electrician after a website rebuild (US dollars)

The "panel upgrade" page went from 60 search visits a month to 2; other pages held. URL Inspection showed the old address now returned a 404, and Pages and screens showed 40 visits to "Page not found". One redirect fixed it. At $2,500 a panel job, that redirect was worth more than any new page.

A Toronto physiotherapy clinic (Canadian dollars)

The booking page converted 8% of desktop visits and under 1% of mobile visits; other pages showed a small gap. On a phone, the booking widget opened off-screen. The fix was a widget setting, $0.

A landscaper with two domains

Hostname showed 15% of organic visits on the old domain, which still served a full copy of the site. A sitewide redirect to the new domain merged them.

FAQ

Can Google Analytics find broken links?

Only the ones visitors click, through your error page's title. To find every broken link, use a crawler or Search Console's Page indexing report.

Does a high bounce rate hurt my rankings?

Google's Search Liaison, asked about Google Analytics data: "As a ranking signal? No." (reported by Search Engine Roundtable, January 2024). Treat it as a clue about the page.

Why does GA4 show fewer visits than Search Console clicks?

Google lists the usual reasons: visitors declining cookies, missing tags, time zones and bot filtering. Small gaps are normal; what matters is that both trends move together (Google Search Central).

How often should I run these checks?

Set custom insights to catch sudden drops, then run the five checks after any redesign, new site builder or plugin change, and otherwise every few months.

Different for you?

Keep learning

Do it yourself

Crawlability checklist: make every page reachable by GoogleA crawlability checklist for a small business site: find orphan pages, robots.txt blocks, broken links, redirect chains and server errors, with free tools.

Ask us one question

One line is enough. We reply by email.

Sources

  1. Analytics Help: Landing page report
  2. Analytics Help: Pages and screens report
  3. Analytics Help: Page title
  4. Analytics Help: Engagement rate and bounce rate
  5. Analytics Help: Tech overview report
  6. Analytics Help: Tech details report
  7. Analytics Help: (not set) values in reports
  8. Analytics Help: Known bot-traffic exclusion
  9. Analytics Help: Filter out internal traffic
  10. Analytics Help: Analytics Intelligence and custom insights
  11. Google Search Central: Using Search Console and Google Analytics data for SEO
  12. Google Search Central: Mobile site and mobile-first indexing best practices
  13. Google Search Central: How HTTP status codes affect Google's crawlers
  14. web.dev: Measure and debug performance with Google Analytics 4 and BigQuery
  15. Google Marketing Platform: Google Analytics
  16. Search Engine Roundtable: Google, GA data not used for ranking (January 2024)