How to Set Up Google Search Console: Step by Step
Search Console shows you how Google sees your website and which search terms bring visitors. Here is how to set it up cleanly, step by step.

Setting up Google Search Console: what it shows
Google Search Console is the free tool in which Google shows you how your website appears in search: which search terms bring visitors, which pages are in the index, where errors occur and how well the pages load. To set up Google Search Console, you create a property, verify that you own the website, submit your sitemap and link Search Console to Google Analytics 4 (GA4). Not counting any wait for the DNS record, this usually takes less than half an hour.
The difference from GA4 matters: GA4 measures what visitors do on your website, and that needs consent. Search Console shows what happens before the click, in Google Search itself. It needs no code for visitors and no cookie banner, because the data comes straight from Google. For small websites where many visitors decline in the banner, that makes it a reliable second source.
Domain property or URL prefix: which is better?
When you create a property, Search Console asks which property type you want. A domain property covers the whole domain with all subdomains and both protocols. If you enter example.co.uk, for instance, www.example.co.uk, shop.example.co.uk, http and https are all included. For most businesses this is the best choice, because nothing slips through.
A URL prefix property only covers addresses that begin exactly with the prefix you enter, for example only https://www.example.co.uk. This makes sense if you want to analyse a specific section separately, such as a blog in a subfolder, or if you have no access to the DNS settings. You can create both types side by side without any harm.
| Feature | Domain property | URL prefix property |
|---|---|---|
| Scope | All subdomains, http and https | Only addresses with exactly this prefix |
| Verification | DNS record only | HTML file, HTML tag, Google Analytics, Google Tag Manager or DNS |
| Best for | The whole picture of the business | Individual sections, or no DNS access |
→ Cookie banner with Consent Mode v2: compliant, with no monthly licence
How do I verify my website in Search Console?
Before Search Console shows any data, you have to verify that you own the website. For a domain property, this works only through a DNS record. Search Console gives you a TXT record, which you add in the DNS settings at your domain provider. Depending on the provider, it takes a few minutes to a few hours for the record to become visible. After that, you click Verify.
For a URL prefix property there are more options. The routes through existing Google tools are especially convenient: if Google Analytics is installed on the page and you have edit permissions in GA4, one click is enough. The same applies to Google Tag Manager, if the Google Tag Manager container is installed on the page and you have publish or administrator permissions there. In both cases you sign in to Search Console with the same Google account.
- DNS record: the only way for a domain property, and it always works.
- HTML file: upload a file from Google to the root directory of the website.
- HTML tag: add a meta tag to the head section of the homepage.
- Google Analytics or Google Tag Manager: verification through the existing code.
A common mistake: verification runs through an HTML tag or a file, and after a relaunch or a theme change both have disappeared. Search Console checks the verification regularly. If it no longer finds the proof, you get a notification, and after a grace period your permissions lapse. The DNS record is more robust here, because it stays in place independently of the website. So do not delete it, even if it seems no longer needed after verification.
Submitting a sitemap in Search Console
The sitemap is a list of all the pages you want Google to know about. Most systems create it automatically: with WordPress, for example, at /wp-sitemap.xml or through an SEO plugin, and with Shopify at /sitemap.xml. Open the address in your browser once to make sure it exists. In Search Console, you then go to the Sitemaps report and enter the full address of the sitemap.
After a while, Search Console shows whether the sitemap could be read and how many addresses it contains. If it shows an error, check that the sitemap is publicly reachable and not blocked by password protection or robots.txt. A submitted sitemap does not guarantee inclusion in the index, but it helps Google find new and changed pages faster.
→ Setting up Google Consent Mode v2 correctly: no warning in Tag Assistant
The most important reports at a glance
The Performance report is the core of Search Console. It shows clicks, impressions, click-through rate and average position, broken down by queries, pages, countries and devices. The data goes back up to 16 months. Here you can see which terms your pages are found for, and where many impressions but few clicks point to a weak title.
The filters and the comparison of date ranges are useful. For example, filter out all queries that contain your company name. Then you can see how many visitors find you through general terms and not just because they already know you. If you compare the last three months with the same period last year, you can spot seasonal swings and real losses. Search Console also sends emails to the owners when it finds new problems, for example with indexing or security. Make sure these emails go to an address that someone actually reads.
The Page indexing report shows which pages are in the index and why others are missing, for example because they are set to noindex, redirect or were recognised as a duplicate. With URL inspection in the search field at the top, you can check a single address and request reindexing after a change. The Core Web Vitals report shows how fast and stable the pages are from the point of view of real Chrome users.
An example from practice: a trades business with a contact form finds that its new bathroom renovation page has had no impressions after several weeks. URL inspection shows that the page is set to noindex, because it was copied from a draft template. After removing the tag and requesting indexing, the page appears in search a few days later.
Linking to GA4 and adding users
You set up the link to GA4 in GA4 itself, in Admin under Product links. For this you need owner permissions in Search Console and the Editor role in the GA4 property. You choose the Search Console property and the matching web data stream. A web data stream can be linked to exactly one Search Console property. After that, you will find a report collection for Search Console in the GA4 library, which you first have to publish. Then you see queries and landing pages from organic Google Search alongside behaviour on the website.
You add other people, such as your agency or a colleague, in Search Console under Settings, in Users and permissions. There are owners, full users and restricted users. Give only as many permissions as necessary. For an agency that reads reports and submits sitemaps, a full user is usually enough. Owner permissions should stay within the company.
Thinking about Search Console and tracking together
Search Console shows you the path up to the click, while GA4 and Google Tag Manager show what happens afterwards. Only together do you see which search terms lead to enquiries or sales. If you want to set up measurement on your website properly: Trackum sets up Google Tag Manager, GA4 and Consent Mode v2 for €150 excl. VAT, tested and live within one working day. You give access through the user management of Google Tag Manager, without a password. Get in touch through the enquiry form.
Frequently asked questions
Is Google Search Console free?
Yes, Search Console is a free service from Google. All you need is a Google account and access to your domain or website to verify ownership.
Domain property or URL prefix: which is better?
A domain property covers all subdomains and both protocols, so http and https, with and without www. It is usually the better choice, but it needs a DNS record. A URL prefix is often verified faster, but it only covers exactly that address.
Can I verify Search Console with Google Tag Manager?
Yes, for a URL prefix property. The Google Tag Manager container must be installed on the page, and your Google account needs publish or administrator permissions in the container.
How do I link Search Console to GA4?
In GA4, go to Admin, then Product links, then Search Console links. You need owner permissions in Search Console and the Editor role in GA4. After that, you publish the Search Console reports in the GA4 library.
Sources
- Search Console Help: Verify your site ownership support.google.com
- Google Analytics Help: Link Search Console to Google Analytics support.google.com
- Search Console Help: Performance report support.google.com
- Search Console Help: Sitemaps report support.google.com
- Search Console Help: Manage owners, users and permissions support.google.com
Read more
FeaturesCookie banner with Consent Mode v2: compliant, with no monthly licence
Reject on the first layer, settings per purpose, Consent Mode v2 with every consent type and a record of each choice. No monthly licence.
FeaturesSetting up Google Consent Mode v2 correctly: no warning in Tag Assistant
The most common warning in Tag Assistant says a tag read consent before a default was set. How to avoid it, and what else matters.
FeaturesMarketing dashboard with GA4 and Google Ads: every number on one page
Visitors, leads, orders, ad spend and ROAS per campaign on one page, compared with the previous period. One link, nothing to set up.
FeaturesRevenue from your CRM, shop and ERP in one dashboard: HubSpot, Shopify, Odoo and more
Google Analytics only sees what happens on the website. Orders by phone or email are missing. With a data connection, the real revenue from your system appears in the dashboard.
FeaturesWebsite leads with their source in your CRM: HubSpot, Pipedrive, Brevo, Salesforce or webhook
Where did the lead come from? The CRM handover writes source, campaign and click ID into the CRM with every enquiry, without a form plugin.
FeaturesOffline conversions: report sales from your CRM to Google Ads and Meta
Google Ads and Meta learn from what you report to them. If they only get form fills, they optimise for form fills. With offline conversions, they optimise for sales.