Set Up GA4 and Search Console for Clean Data and Actionable Lead Insights
Practical GA4 & Search Console checklist for small businesses: tidy account setup, GTM and consent, track conversions, fix common reporting and SEO issues.
Account structure & GA4 setup
If your GA4 setup is a spaghetti bowl, every report becomes “maybe?” and your decisions become “vibes?”. Set it up properly once, keep it tidy, and the numbers stay trustworthy.
Here’s a quick GA4 checklist you can smash out in one sitting (with a coffee strong enough to see through time):
- Create your GA4 property, then add a Web data stream (Admin → Property → Data Streams). Your Measurement ID (G-XXXX) lives in the stream details — you’ll need it for your tag or Google Tag Manager (GTM). [Source: Create a property] [Source: Data streams & Measurement ID]
- Turn on Enhanced Measurement so you automatically track things like pageviews, scrolls, outbound clicks and file downloads — then turn off what you don’t need. Less noise = less “why is this spiking?” panic. [Source: Enhanced measurement]
- Set data retention to the longest sensible option for your business (often 14 months for SMEs so you can do year-on-year comparisons). Decide whether it should “reset on new activity”. Long retention is useful — not mandatory — but future-you will usually thank you. [Source: Data retention]
- Sort permissions early (Admin → Account/Property Access). Use least privilege: give Analyst/Editor only where needed, and use individual Google accounts (not “marketing@gmail.com” shared by 9 people and a ghost). [Source: Manage user permissions]
- Plan cross-domain tracking if users move between domains (e.g. shop.example.co.uk → pay.example.co.uk). Otherwise sessions get split and your funnel looks like it’s been hit by a bus. Add linked domains in your tagging (or use the linker plugin) and test in DebugView. [Source: Cross-domain measurement]
If you’re implementing GA4 on WordPress or a bespoke site, keep it practical: tracking only becomes useful when your site is fast, mobile-friendly, and built around a clear customer journey. Otherwise you’re just measuring people leaving.
Step-by-step web design process · Business website: fast & mobile friendly
Safe, low-maintenance tracking: GTM, gtag & consent
For most small business sites, Google Tag Manager (GTM) is the sensible choice. It keeps tags organised, lets you add/disable tracking without wrecking your templates, and behaves nicely with consent tools.
Direct gtag (or a decent CMS plugin) is fine if you only need basic GA4 + one conversion tag. It’s simpler, and for some sites it’s genuinely lower maintenance.
If you’re doing heavy ad tracking, ecommerce, or you’re in a privacy-sensitive sector, server-side tagging and first-party cookie approaches can help — just don’t pretend it’s “a quick tweak”. It usually means extra cost and developer time. [Source: GTM docs] [Source: gtag docs]
- UK/GDPR basics: don’t set non-essential cookies before consent, give clear choices, and keep a record of consent. Follow ICO guidance. [Source: ICO]
- Use Consent Mode v2 so you can still get some modelling when users decline ad cookies (better conversion signals without storing identifiers). [Source: Consent Mode v2]
- Enable IP anonymisation in Analytics where needed. [Source: IP anonymisation]
Quick GTM checklist (aka the “don’t make this future-you’s problem” version): install the container, migrate any existing gtag tags, connect your CMP, set blocking triggers until consent, test everything in Preview, then publish.
If you’re on WordPress and want the simplest reliable route, our guide will help you avoid the classic plugin/theme tracking chaos. [Source: Server-side tagging] [Internal: WordPress for small businesses] [Internal: step-by-step web design]
Turn actions into leads: events, conversions & phone/form tracking
GA4 only becomes business useful when you track what matters. Decide what counts as a lead on your site — form submits, CTA clicks, phone taps, brochure downloads — then track those actions as events and mark the important ones as conversions.
GA4 is event-based. Universal Analytics Goals are gone. You send/capture an event, then mark it as a conversion in GA4. [Source: Mark events as conversions]
- Forms: fire an event on successful submit (GTM form submit trigger or a
dataLayerpush), then mark it as a conversion. [Source: GTM trigger types] - Phone taps: track
tel:link clicks with a click trigger in GTM (mobile leads love a phone tap). - CTA clicks & downloads: capture click events, then treat the valuable ones as conversions.
Before you build dashboards or make decisions, verify tracking. Use GA4 DebugView and Realtime to confirm events are arriving properly (and only once). [Source: DebugView] [Source: Realtime]
If your site isn’t generating enough enquiries, mapping and tracking these actions is one of the fastest ways to find where the journey breaks. Same approach as our guide on why most business websites don’t generate leads. And because a scary number of leads happen on mobile, pair it with the basics: fast, mobile-friendly sites.
Make Google index the right pages: Search Console & sitemaps
Search visibility isn’t “do we have a website?”. It’s “is Google indexing the right pages, and are they healthy?”. Google Search Console is where you stop guessing and start knowing.
Start with verification:
- Domain property: best when you want example.com, www, http/https treated as one site — requires DNS (TXT) verification.
- URL-prefix: fine if you only control one version and want HTML file or meta-tag verification (but it won’t cover other subdomains).
Next, submit your sitemap (usually /sitemap.xml) in Search Console → Sitemaps. It helps Google find what you actually want crawled — and flags issues early.
[Source: Submit a sitemap]
Then keep an eye on the reports that actually affect leads and rankings:
- Coverage: what’s indexed, excluded, or blocked. [Coverage]
- Mobile Usability: issues that quietly murder conversions on phones. [Mobile Usability]
- Core Web Vitals: real-world performance signals (and a solid early warning system). [Core Web Vitals]
- URL Inspection: test a page live, then Request Indexing after a fix. [URL Inspection]
Finally, link Search Console to GA4 (Admin → Property links) so you can see search data alongside on-site behaviour. [Source: Link Search Console to GA4]
If these reports show performance problems or thin visibility, don’t immediately jump to “we need more blogs”. Start with foundations: speed, mobile UX, and pages that match what people actually search for. Next steps: Improve search rankings · Fast & mobile-friendly sites
Reports that help growth + quick troubleshooting
You don’t need 40 dashboards. You need a handful of reports that tell you:
(1) where visitors come from, (2) what they do, and (3) what turns into enquiries.
In GA4, focus on Acquisition, Pages, Events, and Conversions. Then use Search Console’s Performance report to connect queries to pages that are winning (or nearly winning). That’s where your next improvements usually live. (Source: GA4 reports overview, Source: Search Console Performance)
- Monthly review (30 minutes): top 5 acquisition sources, top 5 pages by conversions, 3 key events to monitor, and Search Console queries with rising impressions.
- Simple alerts: set GA4 custom insights for sudden drops/spikes and enable email notifications, so you spot problems before a bad month becomes a bad quarter. (Source: GA4 custom insights)
- Quick troubleshooting:
- No data at all: check tag + property IDs and use Tag Assistant.
- Duplicate events: remove extra GTM/
gtagsnippets. - Consent blocking everything: confirm Consent Mode is implemented properly.
Next step: run the checklists above, set one conversion alert, and prioritise fixes that restore clean data first. Once tracking is trustworthy, improving the site gets a lot easier (and a lot less guessy). If you want to zoom in on conversion issues and SEO basics: why sites don’t generate leads · improve search rankings.
Sources
- Google Developers – Consent Mode v2
- Google Developers – Google Tag Manager docs
- Google Developers – gtag docs
- Google Developers – Server-side tagging overview
- Google Analytics Help – Create a property
- Google Analytics Help – Consent Mode
- Google Analytics Help – Data retention
- Google Analytics Help – Data streams & Measurement ID
- Google Analytics Help – DebugView
- Google Analytics Help – Enhanced measurement
- Google Analytics Help – Mark events as conversions
- Google Analytics Help – Realtime report
- Google Analytics Help – IP anonymisation
- Google Analytics Help – Cross-domain measurement
- Google Analytics Help – Link Search Console to Google Analytics
- Google Analytics Help – Reports overview
- Google Analytics Help – Manage user permissions
- Google Analytics Help – Custom insights
- Information Commissioner’s Office – Cookies and similar technologies
- Google Search Central – Search Console Help
- Google Search Console Help – Submit a sitemap
- Google Search Console Help – Coverage report
- Google Search Console Help – Mobile Usability report
- Google Search Console Help – Core Web Vitals report
- Google Search Console Help – URL Inspection tool
- Google Tag Assistant Help – Tag Assistant
- Google Tag Manager Help – Trigger types (including form submission)
- Google Search Console Help – Performance report

