Google Search Console setup: a step-by-step guide for business owners

What does Google Search Console do for a small business?

Google Search Console is a free tool from Google that shows how Google sees your website. It tells you which searches show your pages, how many people click, which pages are indexed (stored by Google and eligible to appear in results) and what is stopping the rest.

It does not change your rankings on its own. What it gives you is evidence: real search queries, real indexing errors and a direct way to tell Google about new pages. Every other SEO task is easier once it is in place, which is why it sits near the top of any SEO audit checklist.

You need a Google Account and access to either your domain settings (at your registrar or DNS host) or your website's code or CMS.

Domain property or URL-prefix property: which should you pick?

When you choose Add property, Search Console asks for one of two property types. The choice decides how much of your site the property covers and which verification methods you can use.

• What you enter

  Domain property

  example.com (no https://, no www)

  URL-prefix property

  https://www.example.com/ (exact address)

• What it covers

  Domain property

  All subdomains (www, shop, blog) and both http and https

  URL-prefix property

  Only URLs that start with that exact prefix

• Verification

  Domain property

  DNS record only

  URL-prefix property

  HTML file, HTML tag, Google Analytics, Google Tag Manager, or DNS

• Best for

  Domain property

  Most businesses that control their domain

  URL-prefix property

  When you cannot edit DNS, or want a separate view of one section

For most business owners the Domain property is the better default. It catches traffic to http, https, www and non-www versions in one place, so you do not miss data because your site redirects between them.

Pick a URL-prefix property when you cannot reach your DNS settings (for example, an agency or IT team controls them) or when you want a focused report for one folder such as https://www.example.com/blog/. You can have both types for the same site.

How do you verify ownership of your site?

Verification proves to Google that you control the site. Search Console checks the proof regularly, so leave it in place after you verify. If the token disappears, you lose access after a grace period.

For a Domain property, Search Console shows a TXT record to add at your domain provider. With some providers it can add the record for you after you sign in. Otherwise, copy the value and create the record yourself:

Type:  TXT
Host:  @   (some providers want the bare domain or leave the field blank)
Value: google-site-verification=AbCdEf123ExampleTokenOnly
TTL:   default (often 3600)

Your real value comes from Search Console, so never copy the example above. Google's help notes that a new DNS record can take up to two or three days before your provider serves it, so if Verify fails, wait a day and try again rather than adding duplicate records.

For a URL-prefix property you can choose from several methods:

• HTML file upload: download a small file and upload it to the root of your site without renaming or editing it.
• HTML tag: paste a meta tag into the head section of your homepage. Many CMS platforms and SEO plugins have a field for this.
• Google Analytics tracking code: works if your homepage already has the gtag.js or analytics.js snippet in the head and your Google Account has edit rights on that Analytics property.
• Google Tag Manager container snippet: works if you have Publish or Admin permission on the container and the snippet is installed as Google instructs.

The full list and requirements are in Google's verification help page. If you build on Blogger or Google Sites with the same Google Account, verification can be automatic.

How do you submit your sitemap?

A sitemap is an XML file that lists the pages you want Google to find. Most CMS platforms create one automatically, often at /sitemap.xml or /sitemap_index.xml. Open it in your browser first to confirm it loads and lists your real pages.

1. In Search Console, open the Sitemaps report (under Indexing in the left menu).
2. Under Add a new sitemap, enter the sitemap address and select Submit.
3. Wait for the status. Success means Google read it. Has errors means some entries had problems. Couldn't fetch means Google could not get the file at all.

One sitemap file can hold up to 50,000 URLs and 50MB uncompressed. Larger sites split it into several files listed in a sitemap index, which you can submit as a single entry.

A sitemap is a hint, not a command. Google decides which listed pages to crawl and index, so do not expect every URL to show as indexed.

How do you use URL Inspection and Request indexing?

Paste any URL from your property into the search bar at the top of Search Console. The URL Inspection result tells you whether the page is on Google, which canonical URL Google picked, and when it was last crawled.

Select Test live URL to check the current version of the page, then View tested page to see the rendered HTML and a screenshot. This is the quickest way to catch pages that look fine to visitors but come through nearly empty to Google, a common problem covered in our JavaScript SEO guide.

If the page is new or recently updated, select Request indexing. There is a daily limit on requests per property, and Google states that a request does not guarantee the page will be indexed. For many pages at once, an updated sitemap is the better route.

Which reports should you check first?

Search Console has many reports. Four of them answer most questions a business owner has in the first weeks. Menu labels change from time to time, so look for the closest match if yours differ.

• Performance (Search results): clicks, impressions, average CTR (click-through rate) and average position, broken down by query, page, country, device and date. Start with queries to see the words people actually use to find you.
• Page indexing: how many pages are indexed and the reasons others are not, such as "Crawled - currently not indexed", "Duplicate without user-selected canonical" or "Not found (404)". Some non-indexed pages are normal; focus on pages that should rank.
• Core Web Vitals: loading (LCP), responsiveness (INP) and visual stability (CLS) for real visitors on mobile and desktop, grouped as Good, Needs improvement or Poor. New or low-traffic sites often show no data here because there is not enough real-user data yet.
• Enhancements: reports for structured data Google found on your site, such as breadcrumbs or product snippets. They only appear when Google detects that markup. See our schema markup guide if this section is empty.

How do you add your team or agency as users?

Only owners can add users. Open Settings, then Users and permissions, select Add user, enter the person's Google Account email and choose a permission level.

• Owner: full control, including adding and removing users. Keep at least two owners in your own business so access does not depend on one person.
• Full user: sees all data and can take some actions, which suits most agencies and freelancers.
• Restricted user: view rights on most data, fine for colleagues who only need reports.

A property can have up to 100 non-owner users, and email groups cannot be added. Details are in Google's users and permissions help.

How do you fix verification failures and "Couldn't fetch" sitemaps?

Most verification failures come from a few causes:

• The DNS record was added to the wrong domain, or the host field doubled the domain (example.com.example.com).
• The DNS change has not spread yet. Wait up to two or three days before trying again.
• The meta tag was added to a page template that the homepage does not use, or a caching plugin is serving an old copy of the page.
• The verification file was renamed, moved or blocked behind a login, or the homepage redirects to another domain.

For a sitemap stuck on Couldn't fetch, first open the exact URL you submitted in a private browser window. A typo, a 404 or a login wall is the usual cause. Next, check that robots.txt does not block the file, and run URL Inspection with Test live URL on the sitemap address. Google's Sitemaps report help also lists unresolved manual actions and server errors as reasons.

Before you set up Search Console, run a free Growli audit. It checks your robots.txt, sitemap, canonicals and more, so the first reports you see are not full of problems you could have fixed in advance.

Growli subscribers also get an SEO setup checklist per website that walks through Search Console and Bing Webmaster Tools. If you use Bing too, our Bing Webmaster Tools guide shows how to import your verified Google sites in a few clicks.