You can't fix what you can't see, and the two tools that let you see are free. Most small business sites have one of them, half configured, installed by whoever built the site and never opened since.
The two answer different questions and neither can answer the other's. Search Console tells you what happened before the click: which queries you appeared for, where you ranked, whether Google will even index the page. Analytics tells you what happened after: what people did once they arrived. Decisions made on one of them alone are usually wrong.
Every screen here's a recreation, not a screenshot. Both tools sit behind a Google login and block automated capture. Every procedural claim links Google's own documentation so you can check it against the live interface.
Create the property under the right account
Stop before you click anything and decide which Google account you're signing in with. That account will own your historical data. Not your web designer's, not the marketing coordinator who left last year. An account the business controls.
Then the structure, which is three nested things and confuses everyone the first time:
- Account is the top level, usually your company.
- Property is the thing being measured, usually one website.
- Data stream is the source feeding the property, in your case a web stream for your domain.
Create all three in that order. Set the reporting timezone and currency to yours at property creation, because getting them wrong means every daily total is shifted and historical data doesn't retroactively fix itself.
At the end you get a measurement ID that looks like G-XXXXXXXXXX. That's what you install in step 2.
How to know it worked You have a measurement ID starting with G-, and the property's timezone and currency match where you actually operate.
Common trap Creating the property while signed into a personal Gmail because it was the account already open in the browser. Everything downstream inherits that mistake, and step 7 is how you unpick it.
Install the tag and prove it works
Two reasonable routes for a small business site:
- Direct install. Paste the gtag snippet into your
<head>, or enter the measurement ID into your platform's analytics field if it has one. Simplest, and correct for most sites. - Google Tag Manager. A container you install once, then manage tags inside without touching the site again. Worth it if you expect several tracking tools. Overkill if this is the only one.
Pick one. Installing both is how sites end up double-counting every session.
Then prove it. Open your site in one tab and the Realtime report in another. Your own visit should appear within about thirty seconds. That's the only confirmation that means anything, and it takes a minute.
How to know it worked You can see yourself in the Realtime report. Not a green tick in a settings screen. Your actual visit, live.
Common trap The tag on the homepage only. If your platform requires the snippet per template, check a service page and your contact page too. Half-tagged sites produce confidently wrong reports.
The three settings nobody changes
Defaults are chosen for Google's convenience, not yours. Three are worth your attention right now.
1. Data retention. Admin, then Data settings, then Data retention. Google documents the options as 2 or 14 months for user data, and 2 or 14 months for event data on a standard property. Set it to 14. You need the Editor role, and the change takes about 24 hours.
Be clear about what this actually affects, because most advice overstates it. Google says the retention setting affects Explorations and funnel reports, and does not affect the standard aggregated reports. So a short retention doesn't wipe your traffic charts. It limits the custom analysis you can run later, which is exactly the analysis you'll want in a year.
2. Internal traffic. Your own visits inflate everything on a low-traffic site. Define an internal traffic rule for your office IP and exclude it. On a site getting forty visits a week, you and your staff can be a quarter of the data.
3. Reporting identity and timezone. Confirm the timezone matches your business, since this is the one that quietly ruins day-level comparisons later.
How to know it worked Retention reads 14 months, an internal traffic rule exists for your own IP, and the timezone is right. Note the date, since the retention change needs about a day to apply.
Common trap Believing short retention deletes your traffic history. It doesn't. It limits Explorations. Overstating it is how people end up ignoring the setting entirely when someone tells them the truth.
Verify Search Console as a domain property
Search Console offers two property types and the choice matters more than it looks.
- URL-prefix property covers one exact protocol and path.
https://example.comandhttp://example.comandhttps://www.example.comare three separate properties. - Domain property covers the root domain across every protocol and every subdomain in one go.
Take the domain property. It's the one that doesn't silently miss half your traffic because someone linked to the www version.
The catch, per Google's documentation: DNS verification through your domain name provider is the only way to verify a domain property. The other methods, HTML file, HTML tag, Analytics, Tag Manager, only work for URL-prefix properties.
So: log into your registrar, find DNS records, add the TXT record Google gives you, wait. Propagation is usually minutes but can take longer, and clicking Verify repeatedly doesn't speed it up.
If you genuinely can't reach DNS, a URL-prefix property verified through your existing Analytics tag is better than nothing, and you can add the domain property later.
How to know it worked
The property shows as verified and is the domain type, not a URL-prefix one. If you see https:// at the front of the property name, you have a URL-prefix property.
Common trap
Verifying only https://www.yourdomain.com and wondering later why the numbers look thin. The non-www version was reporting into a property nobody created.
Submit your sitemap
A sitemap lists your pages so Google doesn't have to discover them all by following links.
- Find it. Try
yourdomain.com/sitemap.xmlfirst, then/sitemap_index.xml. Most platforms generate one automatically. - Open it in a browser and confirm it lists real pages and no broken ones.
- In Search Console, go to Sitemaps and submit the path.
A brand new domain frequently shows Couldn't fetch for the first day or two. That's normal and usually resolves itself. If it's still failing after a week, then something is genuinely wrong and it's worth looking at.
How to know it worked Status reads Success and the discovered page count is roughly what you expect. A count far below your real page count is a finding, not a formality.
Common trap Submitting a sitemap full of URLs that redirect or 404, usually left over from an old site. That teaches Google to trust the file less.
Once data is flowing, the next guide turns it into a ranked list of what to fix first.
READ THAT GUIDEConnect the two, then publish the collection
Linking puts your Search Console query data inside Analytics, so you can see which queries brought people in and what they did next, in one place.
You need the Editor role on the GA4 property and to be a verified owner of the Search Console property. Then: Admin, Product links, Search Console links, choose the property, choose your web data stream, submit.
Now the part that catches almost everyone. The reports won't appear. You have linked correctly and the navigation shows nothing new, so you assume it failed.
It didn't. Google documents that the Search Console collection is unpublished by default. You have to go to the Library at the bottom of the Reports navigation, find the Search Console collection, and publish it. Nothing in the linking flow mentions this.
Once published you get two reports: Google Organic Search Queries, and Google Organic Search Traffic.
Three limits worth knowing so you don't chase them later. One data stream links to exactly one Search Console property and vice versa. Data appears in Analytics about 48 hours after collection. And Search Console metrics only combine with Search Console dimensions plus Landing Page, Device and Country, so they won't slice by anything else.
How to know it worked The two Search Console reports appear in your Reports navigation and show data after a couple of days. If the link says connected but you see no reports, you haven't published the collection.
Common trap Unlinking and relinking repeatedly because the reports never showed. The link was fine every time.
Fix who owns the accounts
This is the step people skip and the one that costs the most later.
If your agency or web developer created these properties under their own account, they own your historical data. When the relationship ends, so does your access, and sixteen months of Search Console history plus everything in Analytics goes with it. That's rarely malice. It's just what happens when nobody thinks about it at setup.
- In Analytics: Admin, then Property access management. Confirm a business-controlled account has Administrator.
- In Search Console: Settings, then Users and permissions. Confirm a business-controlled account is listed as Owner.
- Add contractors as delegated users, not owners.
- Remove anyone who has left.
Do this while the relationship is good. It takes ten minutes now and is an awkward email later. The same failure mode applies to your domain, your hosting and your Business Profile, and who actually owns your website, domain and hosting covers auditing the rest of it.
How to know it worked In both tools, an account the business controls is listed at the top permission level, and you can name every other person with access and why they have it.
Common trap Accepting Editor or Manager access to a property somebody else owns. You can read everything and lose it all at any time. Owner or Administrator, or it isn't yours.
Learn the three reports worth checking
You now have two tools capable of producing hundreds of reports, almost all of which you should ignore. Three are worth knowing by name.
- Search Console, Performance. Queries, pages, clicks, impressions, position. This is where the fix list in the next guide comes from.
- Search Console, Pages. Indexing. Which pages Google has, and which it refuses. Outranks everything else when something is wrong.
- Analytics, Traffic acquisition. Where people came from. Note that Google added an AI Assistant channel to the default channel group in May 2026, so assistant traffic is broken out separately now, with real caveats about what it misses.
That's the whole dashboard. Anything past those three is analysis rather than monitoring, and analysis is a different job on a different schedule.
How to know it worked You can find all three without help, and you have a recurring calendar entry to look at them. Setup without a habit is just configuration.
Common trap Building a custom dashboard on day one. You don't yet know which numbers matter for your business. Watch the three defaults for a quarter first.
ANALYTICS
Data retention .............. 14 months (max on a standard property)
affects Explorations and funnels, not
standard reports
Internal traffic ............ rule for your office IP, then exclude
Reporting timezone .......... your actual timezone, set at creation
Property access ............. business account = Administrator
SEARCH CONSOLE
Property type ............... Domain, not URL-prefix
Verification ................ DNS TXT record (only method for Domain)
Sitemap ..................... submitted, status Success
Users and permissions ....... business account = Owner
LINKED
Admin > Product links > Search Console links
THEN: Reports > Library > Search Console collection > Publish
(unpublished by default, this is why reports go missing)The whole setup on one page
What comes next, and where this stops
This is pure setup, and it caps out immediately. There's no expert component. If you can add a DNS record and paste a snippet, you can finish the whole thing in an hour, and you should, because every other guide on this site assumes it is done.
The one thing worth saying: data only becomes useful once there's some. Come back in three months, not next Tuesday. When you do, the Search Console guide turns it into a ranked fix list, and the DIY audit uses it as step one.
There's also a nice side effect worth knowing about. Verifying your domain in Search Console under the same Google account can make you eligible for instant verification of your Google Business Profile, which otherwise means a five day wait or filming a video walkthrough. Doing this hour first can save that entirely.
Questions people ask
Do I need both Google Analytics and Search Console?
Yes, because they answer different questions. Search Console tells you what happened before the click: which queries you appeared for, where you ranked, whether Google will even index the page. Analytics tells you what happened after: what people did once they arrived, and whether they contacted you. Neither one can answer the other's question, and a decision made on only one of them is usually the wrong decision.
Why do my Analytics sessions not match my Search Console clicks?
They're counting different things and they never reconcile. Search Console counts clicks from Google Search results only, removes duplicates and filters bot traffic, and reports in California local time. Analytics counts sessions from every source, is blocked by some ad blockers and privacy settings, and uses your own reporting timezone. Expect a gap in both directions and stop trying to close it.
How long until Search Console shows data?
A few days for the first performance data to appear, and Google says collected data should normally be available within two to three days after that. A new domain also often shows a sitemap status of Couldn't fetch for the first day or two, which usually resolves itself and isn't a sign anything is broken. If it persists past a week, then it's worth investigating.
Who should own my analytics accounts?
The business, through an account the business controls, with everyone else added as a delegated user. If your agency or your web developer created the property under their own account, they own your historical data and you lose it the day the relationship ends. That isn't usually malice, it's just how it gets set up when nobody thinks about it. Fixing it takes ten minutes while the relationship is good and is much harder afterwards.
I linked Search Console to Analytics but the reports are missing. Why?
Because linking is only half the job. Google documents that the Search Console collection is unpublished by default, so the reports exist but don't appear in your navigation until you publish that collection from the Library section. This trips up almost everyone, because nothing in the linking flow tells you there's a second step.
