Most founders either skip analytics setup entirely in the early rush to launch, or install it in a way that looks done but silently isn’t tracking anything correctly for weeks. This is the setup sequence that actually works, including the specific verification steps almost every guide skips.
Why setup order matters
Set up Google Search Console before GA4, not after โ Search Console tells you whether Google can even find and index your site at all, which is a precondition for any traffic GA4 would measure. Founders who set up GA4 first often spend weeks confused about “zero traffic” when the real problem is indexing, not analytics.
Step 1: Google Search Console setup (do this first)
Verify your property using the domain property method (via DNS TXT record), not the URL-prefix method, if your hosting allows it โ domain property verification covers all subdomains and protocols (http/https/www/non-www) in one verification, which URL-prefix verification doesn’t. This single choice prevents a surprisingly common problem: traffic split across multiple unverified URL variants that never gets consolidated in reporting.
Immediately after verification: submit your sitemap (`yoursite.com/sitemap_index.xml` for most WordPress SEO plugins), and use the URL Inspection tool to request indexing on your 5โ10 most important pages rather than waiting for organic discovery.
Step 2: GA4 setup โ the verification most people skip
Installing the GA4 tracking code isn’t the same as confirming it’s actually firing correctly. After installation, use GA4’s Realtime report and visit your own site from a different device or incognito window โ if you don’t see yourself appear within 30 seconds, something is broken (usually a caching plugin serving a cached page without the tracking script, or the code placed in the wrong location).
This step alone catches the most common silent failure: WordPress caching plugins (common on most hosting) serving old cached versions of pages to new visitors, meaning the GA4 code technically exists in the site’s code but isn’t reaching real visitors’ browsers because they’re being served a cache from before the code was added.
Step 3: Connect GA4 and Search Console together
In GA4, under Admin โ Product Links โ Search Console Links, connect the two properties. This unlocks organic search query data directly inside GA4 reports rather than needing to check both tools separately โ a small setup step that meaningfully improves how usable your combined data is for actual decision-making.
Step 4: Set up the 3 conversion events that actually matter early
Most GA4 setup guides push founders toward tracking dozens of events immediately. For a brand-new site, three matter: contact form submission, outbound click to booking/call link (if you use an external scheduler), and scroll depth on key pages (a rough proxy for content engagement before you have enough conversions to measure directly). Configure these as GA4 conversion events specifically โ not just “events,” which don’t get the same reporting treatment.
Step 5: Exclude your own traffic
An easily-skipped step that quietly inflates every metric: use GA4’s internal traffic filter (Admin โ Data Streams โ Configure Tag Settings โ Define Internal Traffic) to exclude your own IP and your team’s. Without this, your own repeated visits during development and testing artificially inflate early traffic numbers, making it harder to see genuine visitor behavior.
The mistake that wastes the first month
Setting up analytics correctly but never looking at it. GA4’s interface has a real learning curve, and many founders install it once and don’t return until they have a specific question weeks later โ by which point weeks of baseline data that would have been useful context are gone unreviewed. A 10-minute weekly check-in habit from week one is worth more than a perfect setup nobody looks at โ once this data is flowing, building a dashboard that actually drives decisions is the natural next step.
Want help setting this up instead of building it yourself? Send me a few lines about your business and I will tell you what to automate first and what to skip. Free 30-minute call, no pitch, no obligation. Available for founders in India and Australia. Book a Free Call →
Frequently asked questions
Should I set up Google Search Console or GA4 first?
Search Console first โ it tells you whether Google can find and index your site at all, which is a precondition for any GA4 traffic data to reflect reality.
How do I know if my GA4 tracking code is actually working?
Check the Realtime report and visit your own site from another device or incognito window. If you don’t appear within 30 seconds, the tracking code isn’t firing correctly, often due to a caching plugin serving old pages.
What’s the best Search Console verification method for a new site?
Domain property verification via DNS TXT record, if your hosting supports it โ it covers all URL variants (http/https/www/non-www) in one verification, avoiding split, inconsistent traffic reporting.
Which GA4 conversion events matter most for a new founder site?
Contact form submissions, outbound clicks to booking/call links, and scroll depth on key pages โ these three give meaningful signal before you have enough traffic for more granular event tracking to matter.