The three tools are free and often set up together, but each does a different job. This guide says what each one is for and which to start with.
Search Console shows how your site appears in Google Search before anyone clicks. Google Analytics shows what visitors do on your site after they arrive. Google Tag Manager measures nothing itself: it is a control panel for adding and changing the tracking code that feeds Analytics and other tools. Most small businesses need Search Console and Analytics, and add Tag Manager when tracking grows.
Google Analytics vs Google Tag Manager: the short answer
Google Analytics vs Google Tag Manager is not a contest between rivals. Analytics is where measurements are stored and turned into reports. Tag Manager is how the code that takes those measurements gets onto your pages and is changed later. Search Console is the third tool, and it works from a different source altogether: Google's own search data.
| Tool | The question it answers | Where its data comes from | Needs code on your site? |
|---|---|---|---|
| Google Analytics | What do visitors do on my site, and where did they come from? | Measurement code on your pages | Yes, a Google tag, installed directly or through Tag Manager |
| Google Tag Manager | How do I add or change tracking without editing the site each time? | It collects nothing itself. It runs the tags you set up | Yes, its container code on each page, added once |
| Search Console | How does Google find my site, and which searches show it? | Google Search itself | No tracking code. Ownership is proven with a DNS record or another method |
What Google Analytics does
Google Analytics records visits and actions on your website and turns them into reports: how many visitors came, which sources sent them, which pages they viewed and which important actions they took, called key events. Its data comes from code on your pages, so it only sees visitors to pages that carry the code. Google offers it free of charge, and also sells a paid version for large organisations.
The beginners' guide to what Google Analytics tells you covers the reports and terms in detail. This page stays with how Analytics differs from the other two tools.
What Google Tag Manager does
Google Tag Manager lets you set up and manage tags on your site without changing your website's code each time, as Google's own documentation puts it. A tag is a small piece of code that sends data to a tool such as Analytics or Google Ads. A trigger decides when a tag fires, for example on every page load or when someone clicks a button. A variable holds a value that tags and triggers use. The set of tags, triggers and variables for a website is called a container.
A practical case shows the difference. You want to know how many people click the WhatsApp button. Without Tag Manager, a developer edits the site so that every click sends an event to Analytics. With Tag Manager, someone sets a trigger for clicks on that button and attaches a tag that sends the event, tests it in preview mode and publishes it. The site's own code is not touched again.
Tag Manager keeps saved versions, so a mistake can be reversed by returning to an earlier one. It also has user permissions, so you decide who may edit and who may publish. Those controls matter because a tag can include custom code, including code from outside companies, and a careless tag can slow a page, break it or collect data you never meant to collect.
What Search Console does
Search Console is a free service from Google that helps you monitor, maintain and troubleshoot your site's presence in Google Search results. Its reports show whether Google can find and crawl your site, which pages are indexed and which have problems, which searches show your site, how often it appears and how often people click. It can alert you to indexing, spam or security problems, and show which sites link to yours. You do not need it for Google to list your site, but it shows you how Google sees it.
To use it, you add your site as a property and prove that you own it. A Domain property covers every version of the address, including www and non-www, and can only be verified with a DNS record at your domain provider. A URL-prefix property covers one exact address and can be verified in several ways, including an HTML tag or file, a Google Analytics tag or a Tag Manager snippet. Leave the verification record in place afterwards. Google checks it from time to time, and ownership lapses if it disappears. The guide to running a basic SEO audit shows Search Console in use.
Google Analytics vs Search Console: before the click and after
Google Analytics vs Search Console is the comparison people ask about most, and the simplest way to hold it is time. Search Console covers what happens before someone reaches your site: your pages appearing in Google results and being clicked. Analytics covers what happens once they arrive. Search Console also covers Google Search only, while Analytics counts visits from every source, such as email, social media, other websites and direct visits.
| Question | Better tool |
|---|---|
| Which searches show my site, and how often is it clicked? | Search Console |
| Is Google indexing my important pages? | Search Console |
| How many people visited, and from which channels? | Analytics |
| Which pages do visitors enter on, and what do they do next? | Analytics |
| Did visitors send an enquiry or buy? | Analytics, with key events set up |
| Why did traffic from Google fall? | Both: Search Console for impressions and clicks, Analytics for what happened on the site |
Their numbers will not match. Search Console counts clicks from Google results, and Analytics counts sessions where its code ran. Compare the direction of each, not the exact totals.
You can also link the two, which adds search query and landing page reports inside Analytics. Linking needs Editor access to the Analytics property and verified ownership in Search Console. Google notes that anyone with access to the linked Analytics property may be able to see the site's Search Console data, so link them only when that suits you.
Do you need all three?
Usually you need two, and the third when your tracking needs it. Search Console is worth setting up for any site that should be found in Google, because it is free and reports indexing problems that nothing else does. Analytics is the second tool once you want to know what visitors do. Tag Manager earns its place when you have more tracking jobs than a developer wants to add one at a time.
| Situation | Sensible setup |
|---|---|
| A small brochure site with one contact form | Search Console and Analytics. Install the Google tag directly or through your platform's setting |
| A site that tracks several actions, such as calls, WhatsApp clicks and form submissions | Add Tag Manager, so each action can be added and tested without editing the site |
| A business running Google Ads or several marketing tools | Tag Manager, so the conversion tags and the others sit in one place with controlled access |
| An online store | Analytics, and often Tag Manager. Check what your store platform already offers before adding more |
| A site managed by an agency or several people | Tag Manager with named users, and with the business as owner of every account |
Google's own documentation says the Google tag on its own is a good option if you have no development team, and that you can move to Tag Manager later if your needs grow. Starting simple is acceptable.
Which one should you set up first?
- Search Console. Add and verify the site first. Google's help says data is collected for a property from the moment it is added, so adding it early means your history starts sooner.
- Analytics. Set it up before the site launches or before any campaign starts, so that you have a baseline from the first visit.
- Tag Manager. Add it once you know which actions you want to measure. If you already know you want it, install it first and add Analytics through it. If you add it later, remove the direct Analytics code at the same time so that visits are not counted twice.
If the order feels rigid, the principle is simple: set up the tools before you need the numbers, because you cannot count on any of them showing data from before they were installed.
Can you use Tag Manager without a developer?
Partly. Once Tag Manager is installed, everything inside it is done in a web interface without writing code: you create tags, choose triggers, test in preview mode and publish. Installing it is different. The container code has to reach every page, which means access to the site's code, a theme setting or a plugin on your platform. Some tracking, such as online-store purchases or form submissions on certain platforms, also needs the site to pass extra information to Tag Manager, and that needs a developer.
If you do the work yourself, use preview mode before every publish, name each version clearly and keep a note of what every tag is for. Give edit access to as few people as you can. If you would rather have the tracking planned, set up and checked by a team, the digital marketing service page describes the work Liftup Technologies does in this area, and the SEO service page covers search work that relies on Search Console.
Who should own the accounts
The business should own all three accounts, using a Google account that belongs to the business and is protected with 2-step verification, and should give its developer or agency access as a user. If an agency creates the accounts in its own name, the business can lose its data history when the work ends. Google's help for Search Console says that if all verified owners lose access, all users lose access to the property. Review each user list every few months and remove people who have left.
Mistakes that spoil the data
- The same tracking installed twice, for example directly in the page and again through Tag Manager, which can count visits twice.
- The Search Console verification record deleted during a DNS or hosting change, which ends verification.
- Tracking left off new pages or lost in a redesign, so a section of the site goes unmeasured.
- A Tag Manager change published without testing it in preview mode.
- Your own visits counted as customers' visits.
- Key events never marked, so Analytics shows visits but not results.
Questions and answers
What is the difference between Google Analytics and Search Console?
Search Console reports on your presence in Google Search: searches, impressions, clicks and indexing, before visitors arrive. Analytics reports on what visitors do on your site, from every source. Use Search Console to see how people find you in Google and Analytics to see what they do next.
What does Google Tag Manager do?
It lets you add and manage tracking tags on your site from a web interface instead of editing the site's code each time. It does not collect or report data itself. It sends data to tools such as Google Analytics or Google Ads.
Do I need all three?
Not always. Most sites benefit from Search Console and Analytics. Tag Manager helps when you track several actions, run ads with conversion tracking or have more than one person managing tags. A small brochure site can start without it.
Which one should I set up first?
Search Console first, because it starts collecting data once the property is added. Then Analytics, before launch or before any campaign. Add Tag Manager once you know which actions to measure, and avoid installing the same tracking twice.
Can I use Tag Manager without a developer?
Partly. Creating tags, triggers and variables needs no code, but installing the container code on your pages needs access to the site or a platform setting. Some tracking also needs the site to pass extra data, which needs a developer.
Does Tag Manager replace Google Analytics?
No. Tag Manager delivers the tracking code. Analytics stores the data and produces the reports. You need an Analytics property to receive and read the data, whichever way the tracking is installed.