✧ Key takeaways
Google Search Console is free, and setup takes about 15 minutes. Add your property, verify ownership, submit your sitemap — here is each step, done right.
Google Search Console is the one tool Google gives you for free that actually tells you what is happening with your site in search. Not guesses, not third-party estimates — the real numbers: which queries bring clicks, which of your pages are indexed, and what Google tripped over while crawling. If you run a website and do not have it set up, you are flying blind. The good news: setup takes about 15 minutes, and this guide covers every step.
What Search Console actually shows you
Before the steps, it helps to know why you are doing this. Search Console has four reports you will use constantly:
- Performance — which search queries show your site, how many clicks and impressions each gets, your average position, and click-through rate. This is where you find out what is actually working.
- Indexing > Pages — which pages Google indexed, which it skipped, and why. The first place to look when a page does not show up in search.
- Experience — Core Web Vitals and mobile usability problems.
- URL Inspection — the status of one specific page, including a Request Indexing button.
It also sends you email alerts when something breaks: a sudden drop in indexed pages, a server error spike, a manual action. That alone is worth the setup.
Before you start
You need two things: a Google account, and a live website you control. Search Console only shows data from the day you add the property — it cannot show you history from before setup, so there is no reason to wait. Add it the day your site goes live, even if the site is tiny. Future you will be glad the data exists.
Step 1: Add your site as a property
Go to search.google.com/search-console and sign in. Click "Add property" and you will see two options:
- URL prefix — you enter the exact URL, like
https://yoursite.com. This covers only that exact protocol and subdomain. Simple, and the right choice for most beginners. - Domain — you enter just
yoursite.comand it covers every subdomain and both http and https. More complete, but verification requires editing DNS records, which is a bigger step if you have never touched DNS.
Pick URL prefix unless you have a specific reason to need the Domain option. You can add both later — they do not conflict, and many site owners run both.
Step 2: Verify that you own the site
Google needs proof you own the site before showing you its data. It offers several methods; you only need one:
The HTML-file method (recommended for beginners)
Google gives you a small HTML file with a strange name, something like google123abc.html. Download it, upload it to the root folder of your website — the same folder your homepage lives in — and click Verify. Google fetches the file, sees it is there, and you are done.
On WordPress, upload it through your hosting file manager or an FTP client into the public_html folder. On static hosting such as Cloudflare Pages or Netlify, add the file to your project and deploy. Do not delete the file afterwards — Google re-checks it occasionally, and removing it can break verification.
This is the method we used for SaaSNivo itself, and it worked on the first try.
The HTML-tag method
Google gives you a meta tag to paste into the <head> of your homepage. On WordPress, that usually means your theme settings or an SEO plugin such as Rank Math or Yoast, both of which have a verification-code field. It works fine, but a theme change can wipe the tag out, so the file method is more durable.
The DNS method
Google gives you a TXT record to add at your DNS provider. This is the only method for Domain properties. It works, but DNS changes can take minutes to hours to propagate, so verification sometimes fails the first time and succeeds an hour later. If it fails, wait before assuming you did something wrong.
Google Analytics or Tag Manager
If you already run Google Analytics or Google Tag Manager with the same Google account, verification can happen automatically. Convenient, but it ties your Search Console access to those tools staying in place.
Step 3: Submit your sitemap
Once verified, go to Indexing > Sitemaps in the left menu and paste your sitemap URL — usually yoursite.com/sitemap.xml. WordPress SEO plugins generate one automatically; static sites often need one generated at build time. Click Submit.
A sitemap is a list of your pages handed directly to Google. It helps Google discover pages, especially new ones with few links pointing at them. It does not force Google to index anything — Google still decides — but it removes the "we never found it" excuse. Check back in a day or two: the Sitemaps report should say Success, with a count of discovered pages.
Step 4: Request indexing for your key pages
For your most important pages — homepage, main guides, money pages — use the URL Inspection tool: paste the URL, wait for the check, and click Request Indexing if it is not indexed yet. This puts the page in Google's crawl queue. It is a request, not a guarantee, and there is a daily limit, so use it on pages that matter rather than every URL on the site.
For a fuller picture of what happens next — crawling, indexing, ranking, and how long each takes — read our beginner's guide to Google indexing.
What to check in your first week
Do not expect data on day one. Search Console starts collecting from setup, and the first numbers usually appear within a few days. Check these three things in your first week:
- Indexing > Pages: are your main pages indexed? Any errors? Fix anything marked as an error before worrying about anything else.
- Performance: even a handful of impressions tells you Google is serving your pages. Zero impressions after two weeks usually means an indexing problem, not a ranking problem.
- Experience: any mobile usability or Core Web Vitals failures? Fix the worst ones first — they affect real visitors, not just rankings.
Common problems and fixes
Verification keeps failing. The HTML file is in the wrong folder, the meta tag was pasted into the body instead of the head, or DNS has not propagated yet. Check the exact placement, wait a few hours for DNS, and try again. Switching methods is fine — you only need one to work.
"Sitemap couldn't be fetched." Open the sitemap URL in your browser. If it loads, the problem is usually temporary — wait a day and resubmit. If it 404s, your sitemap is not where you think it is; check your SEO plugin settings or your build output.
Pages show "Discovered — currently not crawled." Google knows the URL exists but has not visited yet. New sites wait longer. Add internal links to the page from related content and be patient — this usually resolves itself within a couple of weeks.
No data at all after a week. Double-check you added the right property — https://yoursite.com and https://www.yoursite.com are different properties. If Google serves the www version and you verified the non-www one, you will see nothing.
Make it a habit
Search Console is not a set-and-forget tool. A five-minute weekly check catches problems while they are small: a page that dropped out of the index, a query that suddenly brings traffic (write more on that topic), a mobile error on a page you just redesigned. The sites that rank well are rarely the ones with the cleverest tricks — they are the ones whose owners actually read what Google tells them. Now that Search Console is running, the next useful skill is knowing what people actually search for — our free keyword research guide covers that without any paid tools.