Skip to main content
24/7 Available
SEO

How to Set Up Google Search Console for Your Website (Step by Step)

2026-11-03•8 min read•By Apex Web Expert Team
Photo for article: How to Set Up Google Search Console for Your Website (Step by Step)

You can have a good-looking website and still be flying blind. If someone asked you what people typed into Google right before they found you, or whether your most important page is even in Google's index, you'd probably be guessing. Google Search Console is the tool that ends that guessing. It's free, the data comes from Google itself, and the basic setup takes about 20 minutes. Here's how to do it properly.

In This Guide

What Search Console Shows You — and What It Doesn't

Search Console, once called Google Webmaster Tools (Google renamed it on May 20, 2015), is a free tool that reports how your site performs in Google Search: the searches you appear for, how often you appear, how often people click, and your average position. It also tells you which pages Google has indexed and why others aren't indexed.

The distinction worth getting straight: Google Analytics tells you what visitors do after they arrive. Search Console tells you what happened before the click — how they found you, and whether Google could find you at all. You want both, and we've covered the Analytics side in our guide to setting up Google Analytics (GA4).

Two honest limits first. Adding your site doesn't put it on Google by itself — it gives you the tools to help Google find your pages and see what's wrong; indexing is still Google's decision. And data only starts from the day you set the property up: no backfill, so a property created today can't tell you what happened last month. That alone is a reason not to put it off.

Step 1: Sign In With an Account the Business Controls

Go to search.google.com/search-console and click Start now, then sign in. The account you choose here matters more than most people realise: use a Google account the business owns and controls — not a contractor's personal Gmail, and not a personal account you might lose access to.

This is the lockout story we hear most often: an agency or freelancer sets everything up under their own account, the relationship ends, and the business discovers it can't see its own search data. You can add other people later under Settings, so there's no reason to let someone else own it.

Step 2: Pick Domain or URL-Prefix — and Get It Right

Google asks you to add your website as a "property". You get two choices, and they report on different things. A Domain property covers everything on your domain — http and https, www and non-www, every subdomain — in one place. You enter just example.com, no www, no protocol. The catch: it can only be verified with a DNS record.

A URL-prefix property covers only the exact address you type, protocol and all, such as https://www.example.com. It offers more ways to verify, so it's the right choice when you can't get into DNS settings, or when you want a separate view of one section, like /blog/.

The classic mistake is a URL-prefix property for the wrong variant: you add https://example.com while your site actually lives at https://www.example.com, and half your data quietly lives somewhere else. If you can edit DNS, choose Domain — Google has recommended Domain properties where possible since 2019 — and add URL-prefix properties only for sections you want separate.

Step 3: Prove You Own the Site

Verification is Google's way of checking you control the site before it hands over private search data. Google's own verification help lists the methods. For a Domain property, DNS is the only option. For URL-prefix, you can also use an HTML file, an HTML tag, Google Analytics, or Google Tag Manager.

DNS record (for Domain properties — and the most durable option overall)

Google gives you a TXT record. Add it in your domain's DNS settings — at your registrar, your host, or Cloudflare — usually with the host field left blank or set to @, paste the value exactly, then click Verify. It often works within minutes, but DNS changes can take up to two or three days to spread, so if the first attempt fails, wait a day and try again. Leave the record in place afterwards: Google re-checks it, and removing it can cost you access.

HTML file or HTML tag

For the file method, upload the file Google gives you unmodified to your site's root folder — usually public_html — and open it logged out first: if you can see it without logging in, Google can too. A redirect to a different domain fails verification; a same-domain or http-to-https redirect is fine. For the tag method, paste the meta tag into the head section of your live homepage, not a staging copy. On WordPress, Yoast or Rank Math have a field for it, and Google's own Site Kit plugin handles it too; builders like Wix, Squarespace, and Shopify usually have a built-in field in their SEO or domain settings.

Google Analytics or Tag Manager

If Analytics or Tag Manager is already installed and you're signed in with the same Google account, with edit rights on the Analytics property, verification is one click. It's the fastest route — and the most fragile. If someone removes the tag during a redesign, your verification goes with it.

That's the real question behind this step, and most guides skip it: which token will still be there after your next redesign? Theme changes eat meta tags, migrations lose files, tag cleanups remove Analytics — but a DNS record lives outside the website entirely, so redesigns and platform moves never touch it. Whatever method you start with, add a second one under Settings, then Ownership verification, as backup. And if verification keeps failing even though the file or tag loads for you, check whether a firewall or login wall is blocking Google's Site Verifier, which checks with its own user agent.

If DNS records and meta tags aren't your thing, this setup is part of the ongoing care included in our web design services,

Hands on a laptop keyboard with a website analytics dashboard on screen

Step 4: Submit Your Sitemap

With the property verified, go to Indexing, then Sitemaps, paste in your sitemap address — usually yourdomain.com/sitemap.xml — and click Submit. Then check the status: Success means Google queued every URL for crawling, Has errors means it was read with problems, and Couldn't fetch usually means a wrong address or a blocked file. Check that the number of discovered URLs looks sensible for your site.

One permission quirk: restricted users can't submit sitemaps, so if the button simply isn't there, that's why — you need owner or full-user access, A sitemap helps Google discover your pages faster; it doesn't guarantee indexing. New sites typically take a few days to a few weeks to start appearing.

Step 5: Give Your Team Access the Right Way

Under Settings, then Users and permissions, you can add the people who work on your site without ever sharing a password. A verified owner placed their own token on the site and can do everything; a full user can view all data and use most tools but can't add users or link Analytics; a restricted user can mostly just view reports.

Two rules keep this clean. First, have at least two verified owners, one of them inside the business — if every verified owner loses access, everyone loses access, . Second, when someone leaves, remove them as a delegated owner first and then delete their verification tokens, or they can simply re-verify. You can't downgrade a verified owner; you can only remove them.

While you're here, link Search Console to Analytics: in GA4, go to Admin, Product links, Search Console links, and pick the property covering the same pages as your data stream. One catch: the Search Console reports inside Analytics are unpublished by default, so publish the collection from GA4's Library after linking.

What to Check First, Once the Data Arrives

Give it a few days — empty reports at first are normal. When data starts arriving, start with Performance: clicks, impressions, click-through rate, and average position, . The quick win hiding in there is searches with lots of impressions but very few clicks. That usually means you're showing up but your page title and description aren't convincing anyone to pick you — a copy problem you can often fix in an afternoon.

Next, Page indexing under Indexing. It splits your pages into indexed and not indexed, . Don't panic at a long not-indexed list — redirects, duplicates, and pages you've deliberately hidden belong there. What deserves attention is an important service page marked "Crawled, currently not indexed" or "Discovered, currently not indexed": Google found it but doesn't think it's worth including yet, often a sign the page is thin or too similar to another one. If your pages aren't showing up at all, our guide to why a website doesn't show on Google walks through the fixes in order.

URL Inspection is the third tool worth learning: paste any page address into the bar at the top to see whether it's on Google, when it was last crawled, and any problems. After you publish or significantly update an important page, Request indexing nudges Google to look at it sooner — a nudge, not a guarantee. Finally, Manual actions and Security issues should both say no issues detected; if either ever flags a problem, deal with it before anything else. After that, fifteen minutes once a month is plenty for most small businesses — and make sure Search Console's alert emails go to an inbox someone actually reads.

The Mistakes That Quietly Cost Months

Most Search Console problems were decided on setup day: a URL-prefix property for the wrong variant, splitting your data in two; a contractor's personal account owning the property; a verification token removed during a redesign and only noticed months later; expecting data on day one, or expecting a sitemap submission to force indexing. And remember: the tool reports; the improvements still have to come from the site.

Set it up this week, submit your sitemap, then come back in a fortnight and check two things: are your key pages indexed, and what are people actually searching to find you? Those two answers will tell you more about your website than most monthly reports. And if the reports raise questions you'd rather hand to someone, talk to us — we'll read the data with you and tell you honestly what needs fixing.

Frequently Asked Questions

Is Google Search Console free?

Yes, completely free. You only need a Google account and a website you can verify. One account can hold up to 1,000 properties, so there is no cost reason to put it off.

Should I choose a Domain or a URL-prefix property?

Choose a Domain property if you can edit your domain's DNS settings: it covers www and non-www, http and https, and all subdomains in one property, and Google has recommended it where possible since 2019. Choose URL-prefix if you can't touch DNS, or if you want a separate view of one section of a site.

How long does setup take, and when will I see data?

Tag, file, Analytics, and Tag Manager verification work as soon as the token is live and you click Verify. A manually added DNS record can take up to two or three days to be served. Reports then take a few days to fill in, and new pages can take days to weeks to appear in search.

Will Search Console get my website on Google?

Not by itself. Submitting a sitemap and requesting indexing help Google discover your pages, but Google decides whether to index them. If pages aren't appearing, the Page indexing report's reasons are the first place to look.

Muhammad Usman, Founder of Apex Web Expert
Muhammad Usman
Founder, Apex Web Expert

Muhammad Usman designs and builds high-converting websites for small businesses — and writes practical guides like this one from real project experience.

Share this guide:

Keep Reading

Need a Website That Actually Performs?

Fixed pricing, professional build, live in weeks. Tell us about your project — free strategy call, no pressure.