Your website can be live, fast, and secure, yet still be hard for customers to find in Google. Google Search Console gives you a direct view of how Google sees your site. This guide explains how to set up Google Search Console for your website, verify that you own it, and start using the reports that matter most.

For a small business site, blog, or new online project, this is one of the first free tools worth configuring after your domain, SSL certificate, and website are in place. It will not instantly improve rankings, but it can show you indexing problems, search queries, mobile issues, and page errors before they become bigger traffic problems.

What Google Search Console Does

Google Search Console is a free service from Google for website owners. It helps you monitor your website’s presence in Google Search and gives you practical information that regular website analytics may not show.

For example, analytics can tell you that a visitor arrived on a page. Search Console can tell you which Google search terms helped that person find it, how often the page appeared in search results, and whether people clicked it.

It also alerts you to issues that can prevent pages from appearing in Google, including crawl errors, pages blocked from indexing, broken redirects, and security concerns. Think of it as a health check for your site’s connection with Google.

Before You Start

You need a Google account and access to your domain or hosting account. If your website is hosted with Visiba, you can usually complete verification through your cPanel account, where domain DNS records and website files are managed.

You should also know whether your site uses one version of the domain or several. For example, these can be treated differently:

  • https://example.com
  • https://www.example.com
  • http://example.com
  • http://www.example.com

A working SSL certificate should redirect visitors from HTTP to HTTPS. Even so, Google Search Console has two property types, and choosing the right one at the beginning saves time.

Choose a Domain Property or URL Prefix Property

When you add a site, Google Search Console will ask you to choose between a Domain property and a URL prefix property.

A Domain property is usually the better choice for most website owners. It covers every subdomain and protocol connected to the domain, including www and non-www versions. If you own example.com, the Domain property includes https://example.com, https://www.example.com, and any subdomains such as shop.example.com.

The trade-off is that a Domain property can only be verified by adding a DNS record. You need access to your domain’s DNS settings to do this.

A URL prefix property tracks only the exact address you enter. It can be verified using a DNS record, an HTML file, an HTML tag, Google Analytics, or Google Tag Manager. This option can help when you do not control domain DNS, or when you only need data for one specific section of a website.

For most small business sites and blogs, select Domain and enter your domain without https:// or www, such as example.com.

Verify Website Ownership With DNS

After entering your domain, Google will display a TXT record. A TXT record is a short piece of information added to your domain’s DNS zone. It proves to Google that you control the domain.

Keep the Google Search Console window open and copy the full TXT value provided. Then sign in to the account where your domain’s DNS is managed. This may be your hosting cPanel account or the domain registrar where you purchased the domain.

Add the TXT Record in cPanel

In cPanel, look for Zone Editor, DNS Zone Editor, or a similar DNS management option. Choose the domain you want to verify and add a new TXT record.

Paste the value supplied by Google into the record field. The host or name field may be left blank, set to @, or filled with your domain, depending on the DNS interface. Use the default TTL unless you have a reason to change it, then save the record.

Return to Google Search Console and select Verify. DNS updates can be recognized quickly, but they may take several hours in some cases. If verification fails right away, wait a little and try again rather than adding duplicate records.

Do not remove the verification TXT record after the site is verified. Google may check it again later. Keeping it in place avoids losing verified access.

Alternative Verification Methods

If you chose a URL prefix property, Google may offer other verification methods. The HTML file method asks you to upload a specific file to your website’s main public folder. On many cPanel accounts, that folder is called public_html.

The HTML tag method provides a meta tag to place in the <head> section of your homepage. This can be convenient for WordPress users who have an SEO plugin or a theme setting for header code.

Google Analytics and Google Tag Manager can also verify a property when the same Google account already has the right level of access. These methods are useful, but DNS verification remains the most complete option because it supports a Domain property.

Submit Your XML Sitemap

Verification gives Google access to your site information. Your next step is to submit an XML sitemap.

A sitemap is a file that lists the important pages on your website. It helps Google discover new pages and understand your site structure. It does not guarantee that every page will be indexed, but it makes discovery more reliable, especially for a new website with few external links.

Many WordPress SEO plugins automatically generate a sitemap. Common sitemap addresses include sitemap.xml and sitemap_index.xml. You can visit the address in a browser to confirm that it loads before submitting it.

In Google Search Console, open Sitemaps from the left menu. Enter the sitemap file name after your domain and select Submit. Check back later to see whether Google processed it successfully and how many URLs were discovered.

Only include pages you want people to find in search. Login pages, duplicate tag pages, internal search results, and thin confirmation pages generally do not belong in a sitemap.

Check That Your Important Pages Are Indexed

A submitted sitemap is helpful, but you should still check your most valuable pages individually. Use the URL Inspection tool at the top of Google Search Console and enter the full address of a page, such as your homepage, service page, contact page, or a key blog post.

The report will tell you whether the page is on Google. If it is not, read the reason before requesting indexing. A page may be excluded because it redirects, has a noindex setting, is blocked by robots rules, or is considered a duplicate of another page.

Request indexing when you have published a genuinely new or substantially updated page. It is not necessary to request indexing repeatedly for every small edit. Google still decides when and whether to crawl the page.

Use the Reports That Help You Make Decisions

New accounts may not show much data for a few days. That is normal. Once data begins to arrive, start with the Performance report.

This report shows clicks, impressions, average position, and search queries. Look for pages that receive many impressions but few clicks. Often, improving the page title or search description can make the result more useful and specific to searchers.

Review the Pages report regularly as well. It separates indexed pages from pages that are not indexed and explains common exclusions. Not every excluded URL is a problem. For instance, redirected URLs and intentionally blocked admin pages are often expected. Focus on errors affecting pages that should be visible to potential customers.

The Core Web Vitals and mobile usability reports can also point to experience issues. A slow or difficult-to-use mobile page can hurt visitors even when it ranks. Still, avoid changing your entire site based on one warning. Check affected URLs, test the page on a phone, and prioritize fixes that improve real visitor experience.

Give Access Without Sharing Your Google Login

If a web designer, SEO provider, or team member needs access, add them through Search Console instead of sharing your personal Google account. In Settings, open Users and permissions and assign the level of access they need.

Use full access for trusted people who need to manage settings and submit sitemaps. Restricted access is better for someone who only needs to view reports. Remove access when a project ends or a contractor no longer works on your site.

Keep Search Console Part of Routine Website Care

Google Search Console works best as an early-warning tool, not a report you check once and forget. Review it after launching a new website, redesigning pages, changing domain settings, moving hosts, or publishing important content.

A quick monthly check is enough for many smaller sites. Look for indexing errors, unexpected traffic drops, security messages, and pages that are gaining impressions. If something looks wrong, act on the specific report instead of guessing.

Your hosting keeps your website available. Search Console helps you confirm that Google can find the pages you built for customers. Set it up early, keep the verification record in place, and give new pages enough time to be crawled before making rushed changes.