The Search Console (short: GSC) is the only free tool that tells you exactly how Google sees your website: which pages made it into the index, which searches brought people to you, what worked, what didn't. This guide walks you through the setup in about 15 minutes — in plain language, without jargon. Every technical term gets a short explanation right where you meet it.
Search Console is Google's own reporting tool for website owners — free, made by Google itself, and connected directly to the search index. Once your site is set up, you see how Google views your pages: which ones are indexed, which searches bring visitors, where technical errors get in the way.
Every other SEO tool works with its own database and estimates what your visibility might be. Search Console does not estimate. It tells you what actually happened. That is the difference — and the reason no serious SEO tooling stack works without it.
One thing here is really unique: manual actions from Google. If Google's review team issues a penalty against your site (for example because harmful backlinks or spammy content were flagged), you only find out here. Security notifications and page-speed data from real Chrome users are available in other Google tools as well (PageSpeed Insights, CrUX) — but in Search Console they land bundled for your property.
Search Console has many reports, but in daily work you keep coming back to the same handful:
Three things — nothing more:
[email protected] that stays with the company.
Go to search.google.com/search-console and sign in with your Google account. Click „Add property" — Google now asks whether you want to add your site as a Domain property or a URL prefix property. This choice matters, so let's take a moment.
Domain property is the recommended default. One entry, and Search Console automatically collects everything belonging to your domain: HTTP, HTTPS, with and without www, plus every subdomain like shop.example.com or blog.example.com. Catch: you need access to your domain settings — where you bought the domain.
URL prefix only ever covers exactly the URL you enter. So https://www.example.com and https://example.com are two separate properties. Upside: you can verify without domain access, using a small snippet or an existing Analytics installation.
Recommendation: take the Domain property if you can get to your domain settings. Otherwise URL prefix — you can always add a Domain property later.
| What it covers | Domain property | URL prefix |
|---|---|---|
| HTTP and HTTPS | both, automatic | one property each |
| www and non-www | both, automatic | one property each |
| Subdomains | all included | one property each |
| What you need | domain access | website OR Analytics |
| When it fits | standard case (recommended) | if you cannot touch the domain |
Google wants to double-check that the property really belongs to you — otherwise anyone could add any random site. To do that, Google offers five ways. You only need one of them to work. Which one is easiest depends entirely on where you have access.
Google gives you a text string that starts with google-site-verification=. You store this string as a small note in your domain settings — a so-called TXT record. Google then reads the note automatically and knows: yes, you have access to the domain.
So this is what you do:
@ or leave it empty (that stands for the main domain).At modern providers (Cloudflare, IONOS, Netcup, Hetzner) verification usually works within a few minutes. Older systems can take a few hours. If nothing happens after 30 minutes, jump to problem number 5 in the troubleshoot table further down.
Google gives you a small code snippet that looks like this: <meta name="google-site-verification" content="XYZ..." />. This snippet goes into the head area of your homepage — the invisible section at the top of your HTML.
Depending on your CMS:
theme.liquid → paste the code just before </head>, save.Important: paste Google's code exactly as delivered. Do not reformat it, do not break lines, do not add quote marks. This sounds trivial, but it is the number-one reason verifications fail.
Google gives you a small file with a name like google1234abcd.html. Download it, then upload it to the root of your website — the top-level folder, where index.html also lives. Test it briefly in the browser: example.com/google1234abcd.html must open without an error.
Nice side effect: the file stays on the server. Even if you switch themes at some point and lose the meta tag, the file still validates. Zero maintenance.
If Google Analytics is already installed on your site (the small tracking snippet in the head), verification is really one click. Precondition: you are signed in with the same Google account that has edit rights on Analytics.
Same principle as Analytics: if Google Tag Manager is installed and you have manage rights on the container, verification is done with a single click. No code changes.
A sitemap is a list of all URLs on your site that Google should know about. Think of it as a table of contents. Every serious CMS creates one for you — you rarely have to build it yourself.
/sitemap.xml) that lists all your pages so search engines can find them faster.
Where the sitemap sits, depending on your CMS:
/sitemap.xml or /sitemap_index.xml/sitemap.xml (created automatically)/sitemap.xml
In Search Console, click „Sitemaps" in the left menu, enter sitemap.xml (without domain, just the file name), click „Submit". Within minutes the status flips to „Success". Google then works through the URLs — this can take days to weeks. Patience.
Common trap: your sitemap contains pages you have marked as „do not index". Google flags this as contradictory (you send them, then tell them to ignore them). Best to clean out those URLs before submitting the sitemap.
After the setup, wait 2 to 3 days. Google needs that time to link data to your fresh property. Then open the „Performance" report — this is the report you will visit most often.
You will see four numbers, always for the last 16 months:
Three quick wins hide in every report:
Two things to know when reading the numbers: the data has a 2 to 3 day delay (yesterday is never fully in yet), and searches with very few impressions are hidden by Google for privacy reasons — you see only totals, not individual queries, for a big chunk of long-tail terms.
Search Console keeps your data for 16 months, then it drops out. Every day a small chunk falls off the tail end. Fine for the short term — but if you want to compare year over year across two or three years, you need a tool that stores the data on its own.
Rankmio does exactly that. Connect once — from that point on, Rankmio pulls in your GSC data every day and keeps it. Bonus: the connection unlocks five modules inside Rankmio (visibility index, GEO audit, quick-win engine, cannibalization detector, chat agent). Read-only — Rankmio cannot change anything in your Google account.
Setup: project settings → „Connect Google Search Console" → sign in with Google → choose the property. That's it.
Project settings → „Connect Google Search Console" → sign in with Google. Free, read-only, disconnect anytime.
Open project settings →These five problems account for the majority of failed first-time setups. Below each: the symptom you actually see, the cause behind it, and the fastest fix in plain language.
| # | Symptom | Cause | Fix |
|---|---|---|---|
| 1 | „Verification failed" although the meta tag is embedded in the head. | A caching layer (Cloudflare, WP Rocket, Varnish) is still serving the old version of the site — Google is checking against the stale copy. | Purge the cache in your CMS or hosting panel, wait 1 minute, click „Verify" again. Then check view-source:yourdomain.com in the browser — the tag must be visible in the HTML source there. |
| 2 | After 3 days, no impressions in the Performance report. | The property was created as URL prefix (e.g. https://), but the site redirects to a different version (e.g. https://www.). Search Console only counts data for the exact prefix. |
Additionally create a Domain property (via DNS record). Domain property covers all variants at once and fixes the problem permanently. |
| 3 | Sitemap status shows „Could not fetch". | Either your robots.txt is blocking Google's crawler, or the sitemap redirects — Google does not follow sitemap redirects. |
Test the sitemap URL directly in the browser (yourdomain.com/sitemap.xml). Must open without error and without redirects. If it redirects, submit the final URL instead. |
| 4 | „0 valid URLs" in the sitemap although 200+ URLs are in there. | The URLs in the sitemap end with a slash (example.com/page/), the canonical tag on the page does not (example.com/page) — or the other way round. Google sees a mismatch. |
Pick one variant (with or without trailing slash) and use it consistently in sitemap, canonical tags, and internal links. Regenerate the sitemap. |
| 5 | „This property needs your attention" warning stays for weeks. | The verification record has a very long refresh interval set in the DNS. Google re-checks every 30 days; if the check hits a stale moment, the property is temporarily deactivated. | In your domain settings, look for a value called „TTL" on the TXT record. Set it to 300 (5 minutes) during setup. Once verification runs stable, you can raise it to 3600 (1 hour). |
About 15 minutes of active work. Adding the property takes 3 minutes, verification 5 minutes, submitting the sitemap 2 minutes. Then you wait 2 to 3 days until the first Performance data shows up — Google needs that long to link data to a fresh property.
In almost every case: Domain property. One entry, and Google collects data for your entire website automatically — HTTP, HTTPS, with and without www, all subdomains. URL prefix only makes sense if you cannot touch your domain settings, or you really want a separate report for your blog and your shop.
A small text note that you store at your domain provider — the company where you bought the domain. Google gives you a text string, you paste it into your domain settings under the label „TXT record", and save. Google then reads this note automatically and knows: yes, the person who set this up really has access to the domain.
Google needs 2 to 3 days after verification before the first data appears. That is normal, not a mistake. In addition, queries with very few impressions are hidden for privacy reasons — that is why long-tail searches often show only totals, not the individual queries.
16 months, then it drops out. Every day a small chunk falls off the tail end. If you want to compare year over year across two or three years, you need an external tool that saves the data on its own — Rankmio does exactly that when you connect the two.
Yes. Sistrix and Ahrefs work with their own databases and estimate what your visibility might look like. Search Console tells you what really happened — real impressions, real clicks, straight from Google. Both together give the fullest picture.
Via one-click login with Google, from your project settings. Rankmio then pulls in the data every day and feeds the visibility index, the GEO audit, the opportunity engine, the cannibalization detector, and the chat agent. Read-only — Rankmio cannot change anything in your account.
Editing the verification code. The tag Google gives you must be pasted exactly as delivered — no line breaks, no changed quote marks, no additional attributes. Small thing, big impact: this alone causes roughly one out of three failed first-time verifications.
Search Console is not glamorous, but it is the foundation. Fifteen minutes of setup, plus a two-day wait, and from then on you have real numbers to work with instead of estimates. Every SEO decision you make afterwards rests on solid ground.
The three highest-leverage moves after setup: rewrite titles on queries with high impressions and low click rate, refresh content on URLs sitting at positions 8 to 15, and connect a tool that stores your data past the 16-month window if you need long-term trends.
Rule of thumb: if verification takes longer than 30 minutes, the problem is almost never the code — it's the refresh time of your DNS. Lower TTL to 300 seconds, delete the record, re-add, retry. This fixes the majority of stuck verifications.
Free SEO & GEO Check
SEO score, AI visibility and citability of your website in 30 seconds — no registration required.
Register for free, get 10 credits and start right away.
Register now