Google Search Console Setup: What to Do After You Verify Your Site
Verifying your site is the easy part. Most people tick that box and then open Search Console once a month, glance at a few numbers, and close the tab. That's most of the value left on the table. The real setup happens after verification, and it takes maybe an hour done properly. Get those steps right and you'll have a far cleaner picture of how Google actually sees your site.
On this page
Submit Your Sitemap First
Verification proves you own the site. It does not tell Google what to crawl. That is what a sitemap is for.
An XML sitemap is a plain list of URLs you want Google to know about. Without one, Googlebot finds pages by following links, which sounds fine until you have product pages with no inbound links, blog posts buried three clicks deep, or new content that went live last week. The crawler may find those pages eventually, but that “eventually” can mean weeks. Submit a sitemap and you hand Google a direct inventory, cutting out the guesswork considerably. The submission itself takes thirty seconds inside Search Console under Indexing > Sitemaps.
The bit most people skip is checking whether the sitemap was actually processed. Accepted and processed are not the same thing. A sitemap can sit in Search Console with a green tick and still return zero discovered URLs if the file is malformed, points to a staging URL, or is blocked in your robots.txt. Check the “Discovered URLs” count after a day or two. If it reads zero, or far fewer URLs than you expect, fix the sitemap before you do anything else.
Most WordPress installs generate a sitemap automatically through Yoast, Rank Math, or the built-in core sitemap at /wp-sitemap.xml. The common failure is submitting the URL and never returning to it. Revisit the Sitemaps report a week after submission and confirm the numbers look right.
Set Your Preferred Domain and URL Prefix
Most sites exist under two addresses at once. Your homepage loads at both https://www.yourdomain.co.uk and https://yourdomain.co.uk, and to Search Console they are two completely separate properties. Verify only one and Google encounters the other unrecorded. Your click data, impressions, and index coverage end up split across two buckets, and you are looking at half the picture every time you open your reports.
The fix is straightforward. Verify both versions, then tell Google which one is canonical by adding both as URL-prefix properties and setting a preferred domain inside the Domain property settings if you are using that method.
Picking the right version matters less than picking consistently. Whichever address your server actually serves to visitors is the one to nominate as primary. If your DNS and server configuration already redirects the non-www version to www, make the www property your preferred domain and point your sitemap at that same address. It is a five-minute job that saves a lot of head-scratching later when your numbers do not add up.
Check the Coverage Report Before Anything Else
The Page Indexing report (Google renamed it from Coverage a while back, though you will still hear both terms) is the first place to go after verification. Pull it up and look at the Excluded tab straight away.
What the excluded tab actually tells you
A handful of excluded URLs is normal. A few hundred is a problem you need to understand. The status that trips people up most often on WordPress sites is “Crawled, currently not indexed,” which means Google visited the page, read it, and decided not to include it. That usually points to thin content. The usual suspects are tag archive pages, date archives, or author pages with a single post on them.
Noindex tags left over from a staging environment are one of the more painful causes. A site gets built on a dev server with search engines blocked, goes live, and nobody removes that setting. The entire domain can sit delisted for weeks before anyone notices.
How to work through the excluded URLs
If you have already worked through the initial verification steps in a practical setup guide, you will have a clean baseline to compare against. Cross-reference the excluded URLs with your actual site structure. Are they pages you want indexed? If not, confirm they carry a deliberate noindex and move on. If they should be indexed, dig into the page itself. A robots.txt block, a thin word count, or near-duplicate content will usually explain it faster than any tool will.
Reading the Performance Report Without Getting Lost
The Performance report is where most people either get useful information or spend twenty minutes staring at numbers that mean nothing to them. The four metrics at the top, Clicks, Impressions, CTR, and Average Position, are all connected but tell different stories.
What the four metrics mean together
Impressions count how often your pages appeared in search results. Clicks count how many people followed through. CTR is the ratio between the two, and Position tells you where you typically ranked. A page sitting at position 4 with 2,000 impressions but only 40 clicks has a CTR of 2%. That suggests the title or description is not compelling enough to earn the tap, even though the ranking itself is reasonable.
Where the filtering makes it useful
Filtering by query and page is where the report earns its keep. Switch to the Pages tab and sort by Impressions to find your highest-visibility content. Then click a specific page and toggle to Queries to see exactly which search terms are pulling people in. That combination often surfaces something surprising, a page you wrote about one topic drawing traffic for a slightly different one. That is a prompt to either adjust the content or build a new page that serves that query properly.
Do not just observe. Take the queries with solid impressions but poor CTR and test a rewritten title tag. Check whether the Coverage and Indexing reports confirm those pages are being indexed cleanly. The data only moves if you act on it.
Connect to Google Analytics and Google Ads
Most sites run Search Console, Analytics, and Ads as three separate silos. That is a waste, because the moment you link them, each one fills a gap the others leave.
Linking Search Console to Analytics
The connection between Search Console and Google Analytics is the more useful of the two. Once linked, you get organic search data sitting inside Analytics alongside your session data, conversions, and goal completions, so you can see which queries drove a user who then did something useful on the site. Without it, Analytics shows you organic traffic as a lump. With it, you can trace a specific keyword through to a specific outcome.
To link them, open Search Console, go to Settings, find the Associations panel, and add your Analytics property. You will need admin rights on both accounts. The process takes about two minutes and the data starts appearing in the Analytics Search Console reports the same day. If you are already tracking organic performance metrics inside Search Console, seeing those sit alongside your paid spend in one place makes the comparison far sharper.
Linking Google Ads
Linking Google Ads follows the same logic. You can see exactly where paid clicks begin and organic impressions leave off, which stops you bidding on terms you already rank strongly for and wasting budget in the process.
Which Alerts to Turn On
Search Console sends email notifications for several different things, and the default settings are not always what you would expect.
The alerts to keep are the ones that flag problems you cannot easily spot yourself. Manual actions are the clearest example. If Google’s review team penalises your site, you will not see it anywhere in your day-to-day traffic data until the damage is already done. Security issues, such as detected malware or hacked content, fall into the same category. Coverage drop notifications, which fire when a meaningful chunk of your indexed pages suddenly disappears from search results, belong on that list too. Those three cover the scenarios where an email at the right moment changes what you do next.
If you are also setting up your property settings and ownership verification around the same time, check the notification preferences immediately after, because they sometimes reset during that process.
Performance summary emails are a different matter. They land weekly or monthly, repeat information you can see in the dashboard whenever you choose to look, and rarely tell you anything you could not have found yourself. Most people stop reading them after the first few weeks.
Keep manual actions, security issues, and coverage alerts switched on. Turn off everything else. You get the signal when it matters, without the noise that trains you to dismiss every email Search Console sends.