Google Search Console Tutorial: The Complete Setup + Four Reports That Matter

If you do nothing else with SEO, set up Google Search Console. It’s free, it’s the most accurate data source about your search performance (because it comes directly from Google), and it’s the foundation every paid SEO tool builds on top of.

We’ve onboarded over a hundred small businesses to Search Console in client work. The same things consistently surprise people: the setup is faster than expected, the data is more useful than expected, and most teams only ever use four reports out of the dozen available. This tutorial walks through the setup, the four reports that matter, and the common gotchas that cost real ranking opportunities.

Quick verdict. Spend 15 minutes setting up GSC properly. Bookmark four reports — Performance, Indexing, Sitemaps, Core Web Vitals — and check them weekly. That’s 80% of the value most small businesses will ever get from SEO tools combined. Add paid tools when you’ve genuinely outgrown what GSC alone can tell you.

What you’ll need

• Your website live and crawlable by Google (no noindex on the homepage, no robots.txt blocking everything)
• Access to your domain DNS (or alternative verification method)
• A Google account
• About 15 minutes for setup, then 10 minutes per week ongoing

Step 1 — Verify your domain (the right way)

Open Google Search Console. Click “Add property.”

Two options appear: Domain and URL prefix. Pick Domain unless you have a specific reason not to. Domain verification covers all subdomains and both http/https in one verified property; URL prefix only covers exactly the URL you specify.

Frame from “Complete Google Search Console Tutorial.” The Domain option (left) is the right pick for almost every small business; URL prefix is for narrow cases like a single subdomain.

After picking Domain (or URL prefix), GSC opens the verification modal listing the methods it supports — DNS TXT record, HTML file upload, HTML tag, Google Analytics, Google Tag Manager.

Source: GSC tutorial. The verification modal — DNS is the recommended path because it survives site migrations and CMS swaps.

Verify via DNS TXT record (recommended).

1. Search Console gives you a TXT record value like google-site-verification=abcdef123456....
2. Log into your DNS host (Cloudflare, Namecheap, Vercel, GoDaddy, etc.).
3. Create a new TXT record:
   • Type: TXT
   • Name: @ (or blank/empty for “root domain”)
   • Value: the full google-site-verification=... string
   • TTL: default
4. Save. DNS propagation takes 1-60 minutes typically.
5. Back in Search Console, click “Verify.”

If verification fails, the most common cause is the TXT record not having propagated yet. Wait 30 minutes and try again. If it still fails, use DNS Checker to confirm the TXT record is visible from multiple regions.

Step 2 — Submit your sitemap

Once verified, GSC’s left nav shows multiple reports. First task: submit your sitemap.

1. Find your sitemap URL. Typical paths: yourdomain.com/sitemap.xml, /sitemap_index.xml, or /sitemap-index.xml. Most CMSs (WordPress, Webflow, Shopify, Astro) generate this automatically.
2. In Search Console: Sitemaps in the left nav.
3. Enter the path (not full URL) — typically sitemap.xml or sitemap-index.xml.
4. Submit.

Within a few hours, the Sitemaps page will show how many URLs Google discovered from your sitemap and how many it indexed.

Common gotchas:

• Sitemap returns 404 → your CMS might use a different URL. Try /sitemap_index.xml or check your robots.txt for a sitemap directive.
• Sitemap returns the homepage HTML instead of XML → your CMS isn’t generating a sitemap. Install a plugin (WordPress: Yoast or Rank Math; Astro: built-in via @astrojs/sitemap).
• Sitemap parses but shows 0 URLs → check the XML manually; some sitemap generators produce empty files when the site is brand-new.

Step 3 — Wait 2-3 days for first data

Search Console doesn’t show real-time data. After verification, expect:

• Indexing data: within 24-72 hours
• Performance data (queries, clicks, impressions): 2-3 days for first appearance, longer for new sites with low traffic
• Full historical data: none — GSC starts collecting from your verification date forward

If you’re a brand-new site with no traffic yet, you’ll see mostly empty reports for the first few weeks. That’s normal.

Step 4 — The four reports you should actually use weekly

GSC has dozens of reports. Most people only need four.

Report 1 — Performance (the most important one)

Where: Performance → Search results

What it shows: Every query that triggered an impression for your site. Clicks, impressions, CTR, average position. Plus pages, countries, devices, and search appearance breakdowns.

Source: GSC tutorial. The Devices view of the Performance report — splits the same query data by mobile/desktop/tablet, which usually surfaces a meaningful CTR difference between mobile and desktop SERPs.

Why it matters: This is your real keyword performance data straight from Google. Every paid SEO tool estimates query volumes; GSC shows actual impressions you received. For most bloggers GSC plus one paid tool is the entire keyword research stack — see our keyword research for blogs comparison for the eight tools we tested against this exact workflow.

How to use it weekly:

1. Sort by Impressions descending. Top 50 queries = your actual SEO real estate.
2. Look for queries where you rank position 5-15. These are “near-miss” opportunities. Small content tweaks can push them to top 3.
3. Look for queries with high impressions but low CTR. Usually a title tag or meta description issue. Fix the SERP snippet to capture more clicks.
4. Toggle “Compare” → “Last 28 days vs previous 28 days.” Spot trending queries (rising = new opportunity, falling = potential issue).

This single report drives 80% of the actionable SEO insight most small businesses need.

Report 2 — Indexing → Pages

Where: Indexing → Pages

What it shows: Every URL on your site, broken into “Indexed” and “Not indexed” with reasons.

Why it matters: If a page isn’t indexed, it cannot rank. Period. Indexing issues are the silent SEO killer that paid tools rarely catch.

Common reasons for “Not indexed”:

• “Crawled - currently not indexed” — Google saw the page but chose not to index it. Usually a content quality signal. Often happens to thin or duplicate pages. Fix: improve the content or merge with a stronger page.
• “Discovered - currently not indexed” — Google knows the page exists but hasn’t crawled it. Often a crawl budget issue on big sites. Fix: improve internal linking to the page, submit sitemap update.
• “Page with redirect” — page redirects elsewhere. Usually fine, but verify the redirect destination is correct.
• “Duplicate without user-selected canonical” — Google found the same content at multiple URLs. Fix: set canonical tags or merge URLs.
• “Blocked by robots.txt” — your robots.txt is blocking Google from crawling. Fix: review and update robots.txt.
• “Noindex tag” — your page has a noindex meta tag. Fix: remove the tag if you want the page indexed.

Check this report monthly. Each “Not indexed” page that should be indexed is a ranking opportunity you’re not capturing.

Report 3 — Sitemaps

Where: Sitemaps in left nav

What it shows: Sitemap submission status, how many URLs Google discovered from each sitemap, and last fetch date.

Why it matters: Sitemap discovery rate is the simplest health check for your site’s crawlability.

How to use it:

• Status: Success — your sitemap is being read. Expected.
• Status: Couldn’t fetch — your sitemap is broken. Fix immediately.
• Discovered URLs vs Indexed URLs comparison — if Google discovered 1,000 URLs but indexed only 200, you have an indexing problem (cross-reference with the Pages report).

Report 4 — Core Web Vitals

Where: Experience → Core Web Vitals

What it shows: Real-user performance metrics for your site (LCP, FID, CLS) on both mobile and desktop.

Source: GSC tutorial. The Core Web Vitals report bucketing URLs into Good / Needs improvement / Poor — the page templates flagged Poor are usually one shared issue, so a single fix often resolves dozens of URLs at once.

Why it matters: Google uses Core Web Vitals as a ranking signal. Slow sites rank worse, all else equal. GSC shows the symptom; for diagnosing the cause, pair it with one of the dedicated technical SEO audit tools — Screaming Frog, Sitebulb, or Sitechecker all surface the page templates and assets responsible for slow LCP and INP scores.

The thresholds you want:

• LCP (Largest Contentful Paint): under 2.5 seconds = “Good”
• INP (Interaction to Next Paint): under 200ms = “Good” (replaced FID in March 2024)
• CLS (Cumulative Layout Shift): under 0.1 = “Good”

If your Core Web Vitals page shows mostly “Good” or “Needs improvement” URLs, you’re in fine shape. If it shows large numbers of “Poor” URLs, prioritize the page templates affected — usually a hero image, layout shift, or render-blocking JavaScript issue.

For most small business sites on modern stacks (Astro, Next.js static, Webflow, Shopify), Core Web Vitals are passing by default. WordPress sites are the most common to need attention.

Step 5 — The reports most people don’t need (yet)

A few GSC reports that exist but are usually overkill for small businesses:

Links report — shows internal and external linking. Useful for agency work; rarely actionable for solo small businesses.

Manual actions / Security issues — only relevant if Google has flagged your site. Hopefully empty. Check monthly to make sure.

Mobile Usability — mostly absorbed into Core Web Vitals. Ignore unless you have a custom mobile site.

International Targeting — only relevant if you serve multiple countries with different language versions.

Common gotchas

A few specific issues we see consistently in small business GSC accounts:

Gotcha 1: Verifying URL prefix instead of Domain. If you verified https://yourdomain.com/, GSC won’t show data for http://yourdomain.com/ or https://www.yourdomain.com/. Verify Domain (DNS-based) instead — covers all variants.

Gotcha 2: Not noticing “(other)” anonymized queries. GSC anonymizes queries with very low impressions. Don’t panic when you see “(other)” with a chunk of clicks — that’s normal.

Gotcha 3: Comparing dates incorrectly. Default Performance comparison is “last 28 days vs previous 28 days” — but the previous 28 days might be a different seaso