How to Set Up Google Search Console on Any Website: Shopify, Squarespace, Wix, WordPress and More

Step one: pick the right property type

Go to search.google.com/search-console, sign in with the Google account you want to own the data (use a business account you will still control in five years, not a freelancer’s or an old employee’s), and click Add property. Google offers two choices, and the one you pick decides how you verify.

Domain property. You type just the domain, like example.com. It covers everything: www and non-www, http and https, and every subdomain, in one report. The catch is that it can only be verified with a DNS record at the company that manages your domain. This is the one I recommend whenever you can get into your DNS, because it is the complete picture and it survives theme changes and platform migrations.

URL-prefix property. You type the full address, like https://www.example.com/. It only covers URLs that start with exactly that string, so a visitor landing on the non-www version is invisible to it. It is easier to verify, though: an HTML tag in your site’s header, an uploaded HTML file, or your existing Google Analytics or Tag Manager. This is the practical choice when you are on a hosted builder and do not control the domain’s DNS.

You can have both. Plenty of sites verify a URL-prefix property through their platform in two minutes today and add the domain property later when someone finds the registrar login.

Step two: verify ownership on your platform

Search Console will show you either a TXT record (for a domain property) or a meta tag that looks like <meta name="google-site-verification" content="abc123..."> (for a URL-prefix property). Leave that tab open, do the platform step below, then come back and click Verify. Builders rename their menus often, so if a label below has moved, search the platform’s settings for “Search Console” or “verification” and it will turn up.

Domain property on any platform (DNS)

Copy the TXT record Google gives you. Log in wherever your domain’s DNS lives (GoDaddy, Namecheap, Cloudflare, Squarespace Domains, Shopify, and so on), add a new record with type TXT, host or name set to @ (some providers want it left blank), and paste the value. Save it and click Verify.

Some registrars, Cloudflare among them, support a one-click flow where Search Console signs into the registrar and adds the record for you (pictured below); if you see that option, use it. DNS changes are often live in minutes but can take up to a day or two, so if verification fails right away, wait an hour and try again rather than adding a second record.

Shopify

Shopify does not let you upload files to the root of your domain, so your options are DNS or the meta tag. If you bought the domain through Shopify, go to Settings, then Domains, pick the domain, and open its DNS settings to add the TXT record for a domain property. For the meta tag route, go to Online Store, then Themes, click the three dots next to your live theme and choose Edit code. Open layout/theme.liquid, find the opening <head> tag, paste the full meta tag on the line directly below it, and save. Two warnings from experience: the tag lives in that theme only, so if you switch or reinstall themes later you have to paste it again, and verify it on the published theme, not a draft copy. Shopify generates your sitemap automatically at /sitemap.xml.

Squarespace

Squarespace connects to Search Console from inside its own dashboard, and it is the easiest route of any platform here. Open the Analytics panel, click Search keywords, then click Connect. Sign in with your Google account (pick the right one if you have several) and click Allow. Squarespace handles the verification itself, so there is no tag or DNS record to copy. It verifies your site’s primary domain, whether that is the built-in Squarespace address or your custom domain, so if you change the primary domain later you have to reconnect. Before you start, the site has to be published (trial sites are hidden from search engines), the homepage cannot be behind a password, and a newly connected custom domain needs about 48 hours to settle first. Keyword data takes around 72 hours to show up in the Search keywords panel. The sitemap is generated automatically at /sitemap.xml; submit it in Search Console in step three.

Wix

Wix’s own instructions use a URL-prefix property with the full https://www. address. In Search Console, choose URL prefix, enter the address, open the HTML tag method and copy the meta tag. Then, in a second tab, go to SEO & GEO in your Wix dashboard, scroll to Tools and settings, select Site Verification, expand Google Search Console, paste the complete meta tag (the whole thing, not just the code inside it) and click Save. Go back to Search Console and click Verify. Wix also has a guided SEO Setup Checklist that connects your Google account for you, but the manual tag is quicker when Search Console is already open. Either way the site needs a premium plan, a connected custom domain and to be published, and the Let search engines index your site toggle in SEO Settings must be on. The free wixsite.com addresses cannot be verified. Wix’s sitemap is at /sitemap.xml.

WordPress

You have three good options. Google’s own Site Kit plugin walks you through sign-in, verifies the site and shows Search Console data inside your WordPress dashboard. If you already run an SEO plugin, use it instead of adding another: Yoast has a Google verification code field under its site connections settings, and Rank Math connects to Search Console directly in its setup wizard. Paste only the value inside content="..." when a field asks for a code, not the whole tag. Your sitemap is usually /sitemap_index.xml with Yoast or Rank Math, or /wp-sitemap.xml on a site with neither.

Webflow

Open Site settings, then the SEO tab, paste the verification ID (the value inside content="...") into the Google Site Verification field, save, and publish the site. Unpublished changes do not count, which is the most common reason Webflow verification fails. In the same tab, turn on the auto-generated sitemap; it will be at /sitemap.xml.

Custom-coded or static sites

Download the HTML verification file from Search Console, upload it to the root of your site so it loads at https://yourdomain.com/google1234abcd.html, and click Verify. Or paste the meta tag into your shared header template. If your site already runs Google Analytics or Google Tag Manager with the same Google account, Search Console can verify through those without touching any code.

Whichever method you use, leave it in place. Search Console rechecks ownership periodically, and removing the tag, file or DNS record later quietly revokes your access.

Step three: submit your sitemap and inspect your homepage

Once verified, open Sitemaps in the left menu, type your sitemap path (from the platform notes above) and click Submit. Status should read Success within a day.

Then paste your homepage URL into the URL Inspection bar at the top. If it says the URL is on Google, you are done. If not, click Request Indexing. Do the same for your two or three most important pages, and stop there: requesting indexing is rate-limited, and the sitemap handles everything else.

While you are in there, add anyone who helps with your site through Settings, then Users and permissions, rather than sharing your Google password. Give a consultant Full access if they need to submit sitemaps and fix issues, Restricted if they only need to read reports. You can remove them in one click when the work ends.

What to check in the first 30 days

Do not expect much on day one. Search Console only shows data from the day you verify forward, and the Performance report runs a couple of days behind. On the three sites we tracked from launch, impressions appeared within days and the first clicks came about a month in; I wrote up the exact timelines in how long it takes to show up on Google. In the first month, look at three things:

• Pages (under Indexing). How many pages are indexed versus not, and why. “Crawled, currently not indexed” on thin pages is normal. A page you care about showing “Excluded by noindex tag” is a setting someone forgot to turn off, and it is the most common expensive mistake I find on builder sites.
• Performance. Which queries you already appear for, even at position 40. Those are the topics Google already associates you with, and the cheapest place to improve.
• Experience and Security issues. These should be empty. If they are not, fix them before anything else.

One thing Search Console will not tell you: whether ChatGPT, Perplexity or Claude mention you. Google folds clicks from its own AI Overviews and AI Mode into the regular web numbers without separating them, and the other AI engines do not report to it at all. The averages can also mislead in ways I covered in how Search Console misleads you. Search Console is the foundation, not the whole picture. Set it up today, give it a month, and then read what it says before you spend money on anything else.