Google Search Console verification

Overview

Google Search Console reports how Google crawls and indexes your store, which searches bring you traffic, and what is broken. Before it shows you any of that, Google asks you to prove you control the site. Without that check, anyone who typed in your domain could read your traffic figures.

The proof works the same way every time. Google gives you a token that is unique to you and to your site, you put that token somewhere only an operator of the site could put it, and Google goes and looks for it.

Verifying does not change how your store is crawled, indexed, or ranked. It opens the reporting, nothing more.

Two routes work on a StoreFront:

Route	Where the token goes	Best for
DNS TXT record	Wherever your DNS is managed	Any property, and the only route for a Domain property
Verification file	StoreFront File Manager, root folder	Merchants without access to DNS

Both survive a theme upgrade. You only need one.

Choose your property type

Search Console asks you to add a property before it asks you to verify, and the type you pick decides which routes are open to you.

A Domain property covers every subdomain and both http and https at once, so yourstore.com, www.yourstore.com, and shop.yourstore.com all report together. It can only be verified with a DNS record.

A URL prefix property covers one exact address. That makes https://yourstore.com/ and https://www.yourstore.com/ two separate properties, each needing its own verification. It accepts either route on this page.

tip

Choose Domain if you can edit DNS. A single property then covers the whole store, including any subdomain you add later, so you do not repeat this work each time the store grows.

Verify with a DNS TXT record

This route proves control of the domain itself rather than of any one page, so it keeps working no matter what you change about your theme or your pages.

1. Sign in to Google Search Console and select Add property.
2. Choose Domain, enter your domain with no https:// and no www, then select Continue.
3. Google shows a TXT record whose value begins with google-site-verification=. Copy the whole value.
4. Sign in wherever your DNS is managed and add a TXT record on the root of the domain, shown as @ or as the bare domain, with that value. Leave the other fields at their defaults.
5. Save the record, then return to Search Console and select Verify.

UltraCart does not host your DNS. Add this record in the same place you added the A record and www CNAME that point the domain at your StoreFront. If you are not sure where that is, DNS at your registrar explains how to find out and walks through several registrars.

DNS changes take time to spread, so Google may not see a record you just saved. If the first attempt fails, wait and select Verify again rather than editing the record.

Verify with an HTML file

Use this route when someone else controls your DNS, or when you would rather not wait on DNS propagation. It puts a single file at the root of your storefront for Google to fetch.

1. In Search Console, select Add property, choose URL prefix, and enter your storefront address exactly as it appears in a browser, including https:// and including www if your store uses it.
2. Choose the HTML file verification method. Google names a file google followed by a long token and ending in .html, and shows you the single line of text it contains.
3. Go to Main Menu → StoreFronts → (select your StoreFront host) → File Manager.
4. Confirm you are in the root folder rather than a subfolder. Google only looks at the root.
5. Select the New File icon, type the file name exactly as Google gave it including the .html extension, then select OK.
6. Paste Google's line of text into the editor and select Save.
7. Open https://yourstore.com/ followed by the file name in a browser. You should see that one line of text.
8. Return to Search Console and select Verify.

The file name is the token, so renaming the file or moving it into a subfolder breaks the verification. StoreFronts serves a file that exists at the requested path before it tries to match the path to a page or an item, which is why a file at the root resolves. See How URLs resolve.

Routes that do not work on a StoreFront

Search Console offers three other methods, and none of them is a good fit here.

Google Analytics and Google Tag Manager verification both require their script to sit inside the page's <head>. UltraCart renders those scripts lower in the page so they do not hold up the first paint, so neither method verifies against a StoreFront. This is the same reason Google Merchant Center rejects a StoreFront when you try to verify it that way. See Google Integration.

The HTML tag method needs a <meta> tag hand-added to your theme's top.vm template between the head tags, and the tag has to be put back after every theme upgrade. Use DNS or a verification file instead.

Keep the verification in place

Google re-checks your verification periodically rather than only once. Delete the TXT record or the verification file later, perhaps while tidying up during a redesign, and Google revokes your access to the property and stops giving you the reports. Leave the token where it is for as long as you want the data.

Tokens belong to a person, not to a site. When an agency or a colleague verifies the same store, they receive their own token and you both hold ownership, so removing yours leaves theirs working. To give someone access without a second token, add them under Settings → Users and permissions in Search Console.

Google shares one verification service across its products, so the token you add here also satisfies other Google services that ask you to prove control of the same site, Google Merchant Center among them.

If verification fails

• The DNS record is not visible yet. Propagation can take anywhere from minutes to a day. Wait, then select Verify again.
• The file returns a 404. Check that it sits in the root folder and that the name matches Google's exactly, including the .html extension and the full token.
• The address does not match. A URL prefix property is exact. Verifying https://yourstore.com/ does nothing for https://www.yourstore.com/. Add the address your visitors actually reach, or switch to a Domain property.
• The domain does not resolve yet. A store that has just moved to a new address cannot be verified until its DNS points at UltraCart. See Domains and hosting.

Next steps

• Sitemaps and crawling: submit your sitemap now that you have access, and control crawlers with robots.txt.
• SEO on StoreFronts: the settings that shape your titles, descriptions, and canonical URLs.