Google Search Console for Beginners: A 2026 Setup Guide

Google Search Console for beginners comes down to four jobs: verify that you own your site, submit your sitemap, read the Performance report, and fix the pages Google won't index. The tool is free, setup takes about 15 minutes, and your first data usually appears within a few days.

Search Console is Google's own view of your website. Unlike third-party SEO tools, it shows your real clicks, the actual searches people typed, and the exact reason a page is missing from Google. If you are new to SEO, our guide to getting found on Google gives you the big picture. This search console tutorial covers the tool that measures all of it, step by step.

What do you need before you start?

You need three things, and you probably have two of them already.

• A Google account. Pick one you will keep for years, ideally a work account rather than an old personal one.
• A live website. Any platform works: WordPress, Shopify, Wix, Squarespace or a hand-coded site. If you are still choosing, our guide on starting a blog that makes money covers that first.
• Access to your settings. That means a login for your domain registrar (the company you bought the domain from, such as Namecheap, GoDaddy or Cloudflare) or admin access to your site.

Expected result: by the end of this guide you will have a verified property, a submitted sitemap, a clear read of your traffic and a short list of pages to fix.

Step 1: How do you set up Google Search Console?

Here is how to set up Google Search Console. Go to the Search Console homepage, sign in, and click Add property. Google asks you to choose between two property types. Here is how they compare.

Choose a Domain property if you can. Adding boredlisted.com this way, for example, covers the https, www and subdomain versions in one place.

How to verify a Domain property with DNS

1. Choose Domain, type your domain without https or www (for example, example.com), and click Continue.
2. Copy the TXT record Google shows you. It starts with google-site-verification=.
3. Log in to your registrar or DNS host and open the DNS settings. Add a new TXT record, set the host or name field to @ (which means your root domain), and paste the value.
4. Save the record, return to Search Console and click Verify.

DNS changes can take anywhere from a few minutes to a day or two to spread. If verification fails right away, wait an hour and try again before changing anything. Never delete the TXT record afterward, because Google rechecks it and removing it can cost you access.

How to verify a URL-prefix property with an HTML tag

Choose URL prefix, enter your full address including https (for example, https://www.example.com/), and pick the HTML tag method. Copy the meta tag and paste it into the <head> section of your homepage. On WordPress, most SEO plugins have a field for this, so you only paste the code inside the content attribute. Then click Verify. Google's site verification guide lists every other method if neither of these fits.

Step 2: How do you submit a sitemap to Google?

A sitemap is a file that lists the pages you want Google to find. Submitting it doesn't guarantee those pages get indexed, but it helps Google discover new posts faster and gives you a simple way to see how many of them made it in.

Find your sitemap URL

Most platforms create a sitemap automatically. Add one of these common paths to your domain and open it in your browser:

If the page loads a list of links or XML code, you found it. If you get a 404 error, check your platform settings or SEO plugin to make sure sitemaps are turned on.

Submit it

1. In the left menu, open Indexing, then Sitemaps.
2. In the Add a new sitemap box, type the path (for example, sitemap_index.xml) and click Submit.
3. Refresh after a few minutes. The status should read Success, with a count of discovered pages.

You only submit a sitemap once. Your platform updates it as you publish, and Google keeps rereading it. If the status says Couldn't fetch, wait a day, because it often clears on its own. If it doesn't, open the sitemap yourself to confirm it loads. The official Sitemaps report documentation explains each error message.

Step 3: How do you read the Search Console performance report?

Open Performance, then Search results. Four metrics sit at the top, and you can click each box to add it to the chart.

Below the chart, tabs let you slice the data by Queries, Pages, Countries, Devices, Search appearance and Dates. If your readers are in both the US and the UK, compare the two under Countries. The same page can rank differently in each market, and the wording people use often differs too (Americans search for a "resume," while Brits usually say "CV").

The report keeps 16 months of data, so export anything you want to keep longer. Google counts clicks and impressions from AI Overviews and AI Mode inside these totals, and it has been adding separate views for visibility in its generative AI features. If your property shows one, read it alongside our guide on getting cited by AI search.

Four quick wins to look for

• High impressions, low CTR. Open the Pages tab, sort by impressions and check CTR. Rewrite the title and meta description so they match what the top queries show people want.
• Striking-distance queries. Sort queries by position and find the ones ranking 8 to 20. A content refresh, clearer headings or a few internal links can push them onto page one.
• Queries you never targeted. These are free topic ideas. Pair them with our list of free tools to find search topics to decide whether a new post makes sense.
• Sudden drops. Under Date, click Compare and set the last 28 days against the previous 28. If many pages fell at once, check whether a Google update rolled out, as many sites saw during the December 2025 core update.

Step 4: How do you find and fix indexing errors?

Go to Indexing, then Pages. The Page indexing report splits your URLs into indexed and not indexed, with a reason for each group. Not every unindexed URL is a problem. Redirects, tag archives and duplicate versions are often excluded on purpose, so focus on pages you actually want people to find.

How to fix an error and tell Google

1. Click a status row to see example URLs.
2. Paste one URL into the inspection bar at the top of Search Console. URL Inspection shows whether the page is indexed, which canonical Google chose and when it last crawled the page.
3. Fix the cause on your site, then click Test live URL to confirm Google can see the change.
4. Click Request indexing for important pages. There is a daily limit, so save it for pages that matter.
5. Back in the report, click Validate fix. Google rechecks every affected URL, which often takes a few days to a couple of weeks.

Google's Page indexing report help page lists every status in detail. To catch on-page problems before Google does, run new posts through our free SEO page audit tool, which flags issues like missing titles and stray noindex tags.

What mistakes should beginners avoid?

• Verifying the wrong version. A URL-prefix property for http://example.com shows almost nothing if your site actually runs on https://www.example.com. Use a Domain property, or match the exact live address.
• Panicking over excluded pages. A large "not indexed" number is normal on WordPress, where tags, categories and media attachment pages create extra URLs.
• Requesting indexing again and again. Repeat requests for the same URL don't speed anything up. Improve the page instead.
• Judging by one day of data. Daily numbers swing, and the most recent day or two is often incomplete. Read trends over 28 days or longer.
• Using the Removals tool to delete pages. It only hides a URL from results temporarily. To remove a page for good, delete it or add a noindex tag.
• Sharing your Google login. Under Settings, then Users and permissions, give a freelancer or agency their own Full or Restricted access instead.

How often should you check Search Console?

Once setup is done, a 15-minute weekly check covers most small sites. Copy this routine:

1. Open the Overview page and look for new alerts or messages.
2. In Performance, compare the last 28 days with the previous 28 days for clicks and impressions.
3. In the Pages report, look for any new spike in errors.
4. Inspect each post you published that week to confirm it is indexed or queued.
5. Write down one page to improve, based on low CTR or a near page-one position.

Once a month, also glance at Core Web Vitals (Google's page speed and stability scores) and the Manual actions report. A manual action is a penalty from a human reviewer, and that report should say no issues detected.

The bottom line

Set up Search Console today, even if your site is brand new. Verify a Domain property, submit your sitemap and give it a few days to collect data. Then make the weekly check a habit: find one page with high impressions and low CTR, improve it, and watch what happens over the next month. The data is free, it comes straight from Google, and it beats guessing every time.