Google Search Console, Tag Manager, and Analytics, start to finish
Your site is live. Now you want to know whether anyone can find it, and what they do when they get there. Google's three free tools answer different parts of that. This guide explains why each one is worth the few minutes it takes, what it tells you, and, just as important, what it doesn't. It skips the click-by-click steps; Google's setup screens walk you through those.
The order
- Search Console first, because it only needs your DNS and your sitemap, and Google starts collecting search data from the day you verify.
- Tag Manager next, because it's the one script you add to your pages. Everything after it is added inside Tag Manager, without touching code.
- Analytics last, added as a tag inside Tag Manager.
1. Search Console: how Google sees your site
Google Search Console is
Google's report on your site from the search side. Add a Domain
property, publish the TXT record it gives you in your DNS, and submit your
sitemap.xml.
Why it's worth doing
It's the only place Google tells you directly whether your pages are in its index, and why not when they aren't. Submitting a sitemap gets new pages crawled sooner than waiting for Google to find them.
What it tells you
- Which pages are indexed, which aren't, and the reason, such as a 404, a redirect, or a duplicate.
- The searches your pages appeared for, how often they showed up, how often people clicked, and your average position.
- Problems Google found: broken pages, mobile layout issues, and slow pages.
- Which other sites link to yours.
What it doesn't tell you
- Anything about visitors who didn't come from Google search.
- What people did after they clicked through.
- Today's numbers: its reports run a few days behind.
What we learned
A Domain property can only be verified by a DNS record, not through Tag Manager. If your DNS is managed as code, put the record in the code too; a record added by hand gets overwritten by the next deploy.
2. Tag Manager: one script, every tool after it
Google Tag Manager is a container for other scripts. You add its snippet to every page once. After that, analytics, ad pixels, and heatmaps are added, changed, and removed in Tag Manager's web interface, and you publish them without deploying your site.
Why it's worth doing
You'll want more tools later, and each one would otherwise mean editing every page and redeploying. Tag Manager also keeps a version history of what ran on your site and when, and it applies one set of privacy rules to every tag.
What it tells you
Nothing by itself. It reports no traffic. Its Preview mode shows which tags fire on a page, which is how you check a new tag before you publish it.
What it costs you
- Page weight: our container's script is about 90 KB compressed, more than any page on this site.
- Another place where the site can break, outside your code review. Anyone with publish access to the container can change what runs on every page.
Privacy
Set Google Consent Mode defaults in your page before the Tag Manager script loads. This site denies analytics and ad cookies by default for visitors in the European Economic Area, the United Kingdom, and Switzerland, and allows them elsewhere. Then list every tag on a privacy page.
3. Analytics: what visitors do on your site
Google Analytics 4 counts visits and
what happens during them. Create a property, copy its measurement ID
(G- followed by letters and numbers), and add it in Tag Manager as a
Google tag that fires on all pages.
Why it's worth doing
It's the standard way to see which pages people read, where they came from, and whether a change you made moved anything. It's free at small-site scale.
What it tells you
- Visitors, sessions, and page views, live and over time.
- Where visitors came from: search, social sites, other sites, or direct.
- Country, device, and browser.
- Paths through the site, and events you define, such as a download or a click on an outbound link.
What it doesn't tell you
- Visitors whose browsers or ad blockers block Google's scripts. They don't appear at all.
- Visitors who denied cookies are modeled or counted roughly, not tracked one by one.
- Which searches brought people in. Google hides most search terms; Search Console has them.
- Bots, crawlers, and requests for files that aren't pages. Your host's request logs see those.
What we learned
Google offers a gtag.js snippet when you create the property. If your pages already load Tag Manager, don't paste that snippet too; add the measurement ID inside Tag Manager instead, or every visit counts twice. To check it works, open your site and watch Reports > Realtime; your own visit shows up within a minute.
How the three fit together
| Question | Where to look |
|---|---|
| Is Google indexing my pages? | Search Console |
| What searches show my site? | Search Console |
| How many people visit, and from where? | Analytics |
| What do visitors do on the site? | Analytics |
| Which scripts run on my pages? | Tag Manager |
| Every request, including bots and blocked scripts? | Your host's reports or logs |
For a site on Amazon CloudFront, the CloudFront console's reports cover that last row for free, with no setup. See the hosting guide.