Search Console setup guide

Search Console is the free Google tool that tells you whether Google can find, read and show your website in search results. It does not improve rankings by itself. It gives you the evidence you need to fix problems.

Before you start

Use a Google account that belongs to the organisation, not only one person's personal account.
Find your exact website address. Check whether it uses https://, www, or no www.
Find out who controls the domain name. This might be your web developer, Squarespace, Wix, GoDaddy, 123 Reg, Cloudflare, IONOS, or another domain host.
Find out who can edit the website settings or add custom code.

Choose the right property type

Domain property: Best if you can edit DNS. It covers the whole domain, including https, http, www and non-www.

URL-prefix property: Easier if you only have website-builder access. It covers the exact version you enter, so use the real live homepage URL.

If you have no idea what DNS is, choose URL prefix first. You can always ask someone to add domain verification later.

Step-by-step

Go to search.google.com/search-console.
Click to add a property.
Choose Domain if you can edit DNS. Choose URL prefix if you cannot.
Follow the verification method you can complete.
After verification, open Sitemaps and submit your sitemap if you know it. Many sites use https://yourdomain.com/sitemap.xml.
Open Pages or Indexing after a day or two to see what Google can and cannot index.
Open Performance after a few days to see queries, clicks and impressions.

Verification methods explained

DNS TXT record

Best long-term option. You copy a code from Google into your domain host's DNS settings. Use this if you or your developer controls the domain.

HTML meta tag

Good for website builders. Google gives you a line of code. You paste it into the site's head/custom-code/SEO verification area.

HTML file upload

Useful for developer-managed websites. Google gives you a file. Your developer uploads it to the website root.

Google Analytics

Can work if GA4 is already installed and you have the right permissions. If not, use DNS or HTML tag instead.

Platform notes

Squarespace

Use URL-prefix verification if DNS is managed elsewhere. Add Google's HTML tag in the SEO or code-injection/verification area. If Squarespace controls your domain, DNS verification may also be possible through domain settings.

WordPress

Use Site Kit by Google or an SEO plugin if you do not edit code. If a developer manages the site, ask them to add the HTML tag or DNS TXT record. Clear cache after adding the tag.

Wix

Use Wix's SEO or marketing integrations flow. Wix often gives a guided connection to Search Console. Confirm the property appears inside Search Console afterwards.

Webflow

Add the HTML meta tag in Site settings, Custom code, Head code, then publish the site. For domain verification, update DNS where the domain is managed.

Cargo

If Cargo lets you add custom head code, use the HTML meta tag. If not, use DNS verification through your domain host or ask the person who manages the site.

What to ask a helper

"Please verify our website in Google Search Console. Use domain verification if you can access DNS. If not, use URL-prefix verification with the HTML meta tag. Submit the sitemap, confirm the site is verified, and add [email address] as an owner."

What to check after it is live

Performance: the searches people used before seeing your site.
Pages/Indexing: pages Google can or cannot include.
Sitemaps: whether Google has received your sitemap.
Links: which websites Google sees linking to you.

Common problems

Verification failed: the tag/record is in the wrong place, the site was not published, or cache needs clearing.
No data yet: wait 24 to 48 hours. New sites can take longer.
Wrong version added: add the live https:// version, not an old http:// or staging URL.
No sitemap: your platform may generate one automatically, or an SEO plugin may be needed.