Google Search Console for Beginners: Setup and Key Reports

Google Search Console for beginners means learning one free tool that shows exactly how Google sees your website: which pages it has indexed, which searches bring clicks, and what is technically broken. This guide covers verifying your property, submitting a sitemap, reading the reports that actually matter, and a 15-minute routine to check every week.

I check Search Console on every client site I run, and on this one. It is where I found that "domain trust score" was pulling 351 impressions in three months with no page built for it, and where I watched thin posts sit as "Crawled, currently not indexed" until I rewrote them. This guide covers the setup, the reports worth your time, and the weekly check that takes fifteen minutes.

What Google Search Console shows you that GA4 cannot

Google Search Console shows the half of the story that happens before a visitor ever reaches your site: what Google crawled, what it kept in its index, and the exact words someone typed before your page appeared. Google Analytics 4 picks up from the click onward. Confuse the two and you end up debugging the wrong tool, checking GA4 for a page that never got indexed, or checking Search Console for a WhatsApp click it was never built to track.

I use both on every client site and on this one. When "domain trust score" started showing up in my own Performance report with 351 impressions across three months and an average position of 7.8, GA4 had nothing useful to say about it, because nobody was clicking through yet. Search Console was the only place that query existed at all. That single row in the Queries table is why I eventually built a dedicated page explaining domain trust scores, instead of leaving that traffic with nowhere to land.

The reverse happens just as often. A site owner opens GA4, sees a page with real sessions but zero enquiries, and assumes the page is failing, when Search Console would show the page barely gets impressions for anything except its own brand name. That is not a conversion problem, it is a visibility problem, and no amount of editing the call to action fixes it. If your GA4 numbers already look thin, my Google Analytics for beginners guide is the place to start on that side. This guide covers the half Analytics cannot see.

Setting up Search Console: property type, verification and your sitemap

Setting up Search Console properly takes about fifteen to twenty minutes, and the six steps below cover it end to end: creating the right property type, verifying it, submitting your sitemap, confirming your homepage is actually indexed, adding anyone else who needs access, and building the habit of checking it. Do them in order. Verification has to happen before anything else works.

Step 1: Create your property and choose Domain or URL-prefix

Go to search.google.com/search-console and sign in with the Google account that should own this property for years, not a personal address you might lose access to. Click Add property. You get two options, Domain or URL-prefix, and the choice matters more than it looks.

A Domain property tracks your entire domain at once: www and non-www, http and https, and any subdomain, all in one set of reports. A URL-prefix property tracks only the exact address you enter, so https://yoursite.in and https://www.yoursite.in need two separate properties. For a typical small business site, Domain is the tidier choice because everything shows up in one place. Google's own guidance lays out exactly what each property type covers if you want the full technical detail.

The pitfall: people default to URL-prefix because the first screen looks simpler, then end up with three fragmented properties, www, non-www and a subdomain, and cannot see the full picture in one report months later. Verify the choice worked by checking that your property selector in the top left shows your domain name without one specific protocol pinned in front of it.

Step 2: Verify ownership with the method that matches your property type

If you chose Domain, Search Console gives you one DNS TXT record to add at your domain registrar, GoDaddy, Namecheap, BigRock or whoever manages your domain. Log in there, find the DNS or Advanced DNS section, add a new TXT record with the exact value Search Console shows, save, and return to click Verify.

If you chose URL-prefix, you get more options: an HTML file you upload to your site's root folder, a meta tag pasted into your homepage's head section, or verification through an existing Google Analytics or Google Tag Manager account already installed on the site. See my Google Tag Manager for beginners guide if that container is not set up yet. The meta tag option looks like this:

<meta name="google-site-verification" content="your-unique-verification-string" />

Paste it inside the head section before the closing head tag, then click Verify. The common pitfall with DNS verification is propagation delay: some registrars take a while to apply a new TXT record, so if verification fails immediately, wait thirty minutes and try again before assuming you did something wrong. Confirm it worked by checking for the green confirmation screen and the property appearing in your list on the left.

Step 3: Submit your XML sitemap

A sitemap is a file listing every URL you want Google to know about. Most platforms generate one automatically. WordPress with Yoast or Rank Math creates one at sitemap_index.xml, Shopify and Wix build one on their own domain path, and a hand-coded site usually keeps it at sitemap.xml in the root folder.

In Search Console, open Sitemaps under the Indexing section in the left sidebar, type just the path, sitemap.xml, not the full URL, into the box, and click Submit. Give it a few hours, then refresh the page to see the discovered and indexed counts.

The pitfall here is submitting a sitemap full of pages that carry a noindex tag or point somewhere else with a canonical tag: Google reads the conflict and trusts the noindex or canonical over the sitemap, so the page stays out no matter how many times you resubmit. My guide to XML sitemaps covers building one correctly if your platform does not generate it for you. Verify success by checking the sitemap's status reads Success rather than Couldn't fetch.

Step 4: Run URL Inspection on your homepage to confirm indexing

Paste your homepage's full address into the inspection bar at the very top of Search Console and press enter. Within a few seconds you get a verdict, URL is on Google or URL is not on Google, along with the exact date it was last crawled.

If it says not on Google, and you are confident there is no noindex tag or robots.txt block, click Request indexing. This adds the page to a priority crawl queue, though Google does not publish exactly how many requests you get in a day. In my experience it sits somewhere around ten a day per property, and pages I have requested this way have generally shown up faster than pages left to the normal crawl schedule.

The pitfall is treating Request indexing as a fix for a page that is genuinely thin or broken: the button gets Google to look again, it does not make Google store a page it has already judged and rejected. Verify it worked by re-running the inspection later and checking the verdict changed to URL is on Google. My guide on getting a new page indexed covers what to do next if it still refuses.

Step 5: Add your teammate or freelancer as a user

If a freelancer, a developer or a teammate needs to see this data, do not hand over your Google password. Open Settings from the left sidebar, then Users and permissions, then Add user, and enter their email address with either Full or Restricted access.

Restricted lets someone view reports without touching sitemap submissions or verified owners. Full lets them do everything you can, including removing your own access, so reserve it for people you genuinely trust with the property. The pitfall is granting Full access to a short-term freelancer and forgetting to remove it once the project ends. Verify the invite worked by asking the person to confirm the property now appears in their own Search Console account.

Step 6: Bookmark Performance and set a weekly reminder

Open the Performance report, set the date range to the last 28 days, and tick Compare to the previous period so every number shows a trend, not just a total. Bookmark that exact view.

Put a recurring fifteen-minute reminder in your calendar, the same day every week, to open that bookmark and glance at what changed. The pitfall is setting this up once during a burst of enthusiasm and never opening it again after the new-website excitement fades. Verify the habit is sticking by checking, a month from now, whether you can say what changed in your last two weekly checks without reopening the report.

The Performance report: reading clicks, impressions, CTR and position correctly

The Performance report answers one question: which searches are showing your site, and what happens when they do. Four numbers drive it: impressions, how often a page appeared; clicks, how often someone followed through; click-through rate or CTR, clicks divided by impressions; and average position, roughly where you sat in the results.

Set the date range to the last 28 days and switch on Compare to the previous period before reading anything, because a single day's numbers swing too much to mean anything and Search Console itself lags by two to three days. Then split the report three ways: by query to see which searches you rank for, by page to see which URLs earn the traffic, and by both together using the filter to check one page against one query at a time.

A site-wide CTR of 2 to 5 percent is normal for a small business site, because most impressions come from long, specific searches sitting on page two or three, not the searches you would guess. For your own brand name, CTR should sit well above 50 percent; if it does not, something is actively wrong, a competitor's ad or a wrong result outranking you. For a non-brand query in positions 1 to 3, expect somewhere from 15 to 30 percent. My keyword research guide covers finding the searches worth building a page around in the first place, before you get to reading this report at all.

The single most useful filter on a small site is Position greater than 7. That list shows every query where Google already considers your page relevant enough to sit on page one or the edge of it, and a modest improvement, a better title, one more paragraph answering the question directly, two internal links from related pages, is often enough to push it into the top 5. Treat that filtered list as your content to-do list, not the ideas a keyword tool hands you.

The Page indexing report: what "Crawled, currently not indexed" and the other statuses mean

The Page indexing report, under Indexing in the left sidebar, splits every URL Google knows about into indexed and not indexed, and for every URL in the second group it gives a specific, named reason. Reading that reason correctly saves weeks of guessing.

I learned this the direct way on my own site. A batch of early blog posts, each a little thin and fairly generic, sat under "Crawled, currently not indexed" for a stretch. Google had visited every one of them and chosen not to store them, which is a quality judgment, not a technical block. The fix was not resubmitting the sitemap or clicking Request indexing again. It was rewriting each post to be genuinely more useful than what already ranked, after which Search Console started moving them into the indexed column as Google recrawled the new versions.

The table below covers the statuses you will actually run into, roughly in the order I see them on small business sites.

For anything beyond a handful of affected URLs, or if the pages involved genuinely matter to your business, my guide to why a website is not showing on Google walks through the full diagnosis in order, including how crawling and indexing are two separate steps people conflate. If the underlying cause turns out to be two pages competing for the same query, that is keyword cannibalization, and this report is the easiest free way to spot it.

URL Inspection: checking exactly what Google sees on one page

URL Inspection answers a narrower question than the Page indexing report: not your whole site, just this one address, right now. Paste any URL from your property into the bar at the top of Search Console and you get the last crawled version, the indexed version if it differs, any structured data Google found, and mobile usability, as Google's own documentation for the tool explains in full.

The tool has two views worth knowing. The default view shows what Search Console has on file from the last crawl, which can be days old. Click Test live URL and Search Console fetches the page fresh, right now, which is the one to trust when you just fixed something and want to confirm it worked rather than wait for the next scheduled crawl.

I use this constantly for small checks: confirming a new page's canonical tag points at itself and not somewhere else, checking structured data validates after adding schema markup, or verifying a noindex tag was actually removed after asking a client's developer to take it off. It is faster than waiting for the Page indexing report to refresh on its own schedule.

Run your important pages through my free website SEO checker alongside URL Inspection. The checker flags on-page issues like missing meta tags and heading problems in one pass, Search Console confirms how Google itself is actually reading the page, and the two together catch almost everything worth catching before you touch a ranking factor.

Core Web Vitals and Links: the two reports most beginners skip

Core Web Vitals and Links sit lower in the left sidebar than Performance and Page indexing, and most beginners never open either, which is a mistake because both explain problems the other reports cannot.

Core Web Vitals, under Experience, grades your site on three numbers measured from real visitors: Largest Contentful Paint under 2.5 seconds, Interaction to Next Paint under 200 milliseconds, and Cumulative Layout Shift under 0.1. A URL group only earns a Good rating when at least 75 percent of visits meet all three, measured over a rolling 28-day window. Small sites often see "not enough data" here simply because too few visits qualify for the sample; when that happens, my Core Web Vitals guide covers running the same three numbers through PageSpeed Insights instead.

Links, under the same sidebar, shows the external sites linking to you and the internal links connecting your own pages together. It updates slowly and never shows every single link the way a paid backlink tool does, but it is a free, direct-from-Google signal of which pages other sites consider worth linking to, and a quick way to spot a page on your own site that nothing else links to internally, often the same page stuck at Discovered, currently not indexed.

Neither report changes daily, so quarterly is often enough unless you have just redesigned the site, changed hosting, or started actively building links, in which case check monthly until the numbers settle.

A 15-minute weekly Search Console routine

A fifteen-minute weekly routine catches almost everything that needs catching, and fifteen minutes is short enough that it actually happens every week instead of becoming the check you mean to run and never do.

Open Performance first, with the last 28 days compared to the period before, and note which query or page moved the most in either direction. Open Page indexing next and confirm the indexed count has not dropped since last week; a sudden drop is the one thing on this list worth acting on immediately rather than waiting for next week's check to come around. Glance at Core Web Vitals and Links only if you changed something on the site recently.

Close by writing one line, not a screenshot, not a spreadsheet, just a sentence: what changed, and what you will do about it next. "Impressions for the Kothrud service page dropped, check the title still matches what people search" is a more useful note than a week of numbers nobody rereads. If you also track the wider picture, this routine slots directly into the ten-row sheet in my SEO KPIs guide, where Search Console supplies most of the rows.

Common Search Console mistakes that waste the data you are already collecting

Almost every small business Search Console account I open has at least one of these problems, and each one is quick to fix once you know to look for it.

• Never opening it after setup. Verifying the property and then not returning is the most common mistake by far. The data is free, but only useful if someone actually reads it.
• Reading daily numbers. A one or two day swing means nothing, because Search Console's own data lags by two to three days. Use the 28-day comparison view instead.
• Fragmenting into multiple properties by accident. One for www, one for non-www, without realising a single Domain property would show everything together.
• Treating site-wide average position as a health score. It naturally drops as you rank for more long-tail queries, which looks like decline and is often growth. Track specific money keywords instead.
• Ignoring Manual Actions and Security Issues. Both sit under that heading in the sidebar. They are rare but serious, and the only place Google will directly tell you about a penalty.

The habit worth building is small and boring: fifteen minutes, every week, on the same day. It will not feel like it is doing anything for the first month. By the third, the weekly note becomes the clearest record you have of what is actually working, more honest than any tool's opinion of your site because it comes straight from Google. If the technical basics still need a check first, run a free website SEO audit before reading too much into the reports above, since one blocked page will make every other number in this guide look worse than the content actually is.

Frequently asked questions

Is Google Search Console really free for a small business website?

Yes, completely free, with no paid tier and no meaningful limit for a single business website. Search Console covers indexing reports, performance data, URL inspection, sitemap submission and Core Web Vitals at no cost, however many pages your site has. The tool that costs money in this workflow, if any, is a rank tracker or an all-in-one SEO platform layered on top. For a site with under a few hundred pages, Search Console alone answers almost every question you actually have.

Do I need both Google Search Console and Google Analytics?

Yes, because they answer different questions and neither substitutes for the other. Search Console shows what happens before a click: which searches surfaced your pages, how often, and at what position. Google Analytics 4 shows what happens after the click: which pages a visitor read, and whether they messaged you on WhatsApp, called, or filled a form. Link the two together from inside GA4 and you get one report that shows a search query next to the enquiry it produced, which is the number that actually matters.

How long before Google Search Console shows data after I verify my site?

Verification itself is instant, but the reports take longer to fill in. The Page indexing report updates within a day or two of a crawl. The Performance report showing clicks and impressions usually has a first day of data within 24 to 48 hours, then needs a few more days before the numbers are reliable enough to read, since Search Console reports on a rolling delay. Give a brand new property two full weeks before judging whether anything is working.

What is the difference between a Domain property and a URL-prefix property?

A Domain property covers your entire domain at once: www and non-www, http and https, and every subdomain, but it only verifies through a DNS TXT record at your domain registrar. A URL-prefix property covers just the exact address you type in, such as one protocol and one subdomain, but it accepts easier verification methods like an HTML tag or an existing Google Analytics or Tag Manager connection. Choose Domain if you can reach your DNS settings, URL-prefix if you cannot.

Why does Search Console show impressions but my pages get no clicks?

It usually means the page ranks for the query but the title or description does not earn the click, or the position is low enough that few searchers scroll to it. Open the Performance report, filter to that query, and check the average position alongside the click-through rate. A position past 10 explains low clicks on its own. A position in the top 5 with a click-through rate under 2 percent points at the title and meta description instead, which is worth rewriting before anything else on the page.

Related guides

• Google Tag Manager for beginners
• Google Analytics 4 for beginners
• Why your website is not showing on Google
• SEO KPIs to track
• How to run a free website SEO audit
• Keyword research for beginners
• XML sitemap: what it is and how to submit one
• Free website SEO checker

Your next step

Verify your property, submit your sitemap, and give it two weeks before you judge the data. If you already have Search Console running and want the tag setup to go with it, my Google Tag Manager guide covers installing GA4 and the Meta Pixel without touching your site's code. If you want a second pair of eyes on what the reports are telling you, get in touch and tell me what you are seeing.