"Online store URL not verified" or "could not verify your website" blocks every Shopping ad, free listing and Performance Max feed. This guide covers all five verification methods, the six reasons they fail, and the exact fix for each.
Website verification is the single check that proves you control the domain you submitted to Merchant Center. Without it, no product reaches Google Shopping, no free listing appears in the SERP, and Performance Max campaigns lose their entire feed input. The verification error often shows up before a full suspension does, so fixing it fast prevents the issue from escalating into a misrepresentation review.
Google supports five verification methods, each with a different failure mode. This guide explains how each method works, why each one fails most often, and the fastest path to a green check for Shopify, WooCommerce, Magento, Wix, Squarespace and custom builds.
Verification proves you control the domain. Claiming associates that verified domain with your Merchant Center account, exclusively. Many merchants verify successfully, see a green check, and then wonder why Shopping ads still do not serve. The reason is that the URL is verified but not claimed. Both must be green in Merchant Center -> Business Information -> Website.
A URL can be verified by multiple Google users at the same time (an SEO agency, the developer, the owner). It can be claimed by only one Merchant Center account. If your "Claim" button is greyed out, another Merchant Center account already claims it. We cover the claim conflict fix in a dedicated section below.
Google gives you a small <meta name="google-site-verification" content="..."> tag that must go in the <head> section of your homepage, before <body>. Once placed, you click Verify in Merchant Center, Google fetches the homepage, finds the tag, and marks the URL verified.
Google gives you a uniquely named HTML file (something like googleXXXXXXXX.html) to upload to your domain's root directory. The file must return HTTP 200 at https://yourdomain.com/googleXXXXXXXX.html with no redirect.
Google gives you a long TXT record string to add to your DNS zone. After propagation (up to 24 hours), Merchant Center checks the DNS, confirms the record, and verifies the domain. DNS verification verifies the entire domain including all subdomains.
If you have Google Analytics 4 or Tag Manager installed with the same Google account that owns the Merchant Center, Google detects ownership automatically. No code change required.
If your domain is already verified in Google Search Console under the same Google account, Merchant Center inherits the verification automatically. Single click in Merchant Center, no theme changes.
Fastest path by platform: Shopify: Search Console (one click via Shopify Admin). WooCommerce: Yoast SEO inserts the HTML meta tag. Magento: HTML file upload to /pub/. Wix and Squarespace: DNS TXT record. Custom builds: DNS TXT or HTML file upload to root.
You enter https://yourdomain.com in Merchant Center but verification was set up for https://www.yourdomain.com (or vice versa). Google treats these as different URLs. Fix: in Merchant Center, edit the website URL to match the verified variant exactly, including www and the protocol. Use the same variant Search Console uses.
HTML meta verification fails if the tag lands after the opening <body> tag. Some theme editors auto-insert tags at the bottom of the template, which puts them outside <head>. Fix: open the theme's head template file (theme.liquid in Shopify, header.php in WordPress, header.phtml in Magento) and paste the <meta> tag directly inside <head>, before the closing </head> tag. Re-verify in Merchant Center.
The verification file must be reachable at the domain root (https://yourdomain.com/googleXXX.html), with HTTP 200, no redirect, and no authentication. Common failures: WordPress redirects all non-page URLs to the homepage, Cloudflare cache returns stale 404, Shopify does not allow root files at all. Fix: in WordPress, add a pass-through rule to .htaccess. With Cloudflare, purge cache for the verification file URL. For Shopify, switch to Search Console verification instead.
DNS propagation can take up to 24 hours. If your nameservers point to Cloudflare but you added the TXT record at GoDaddy (where the domain was registered), Google never sees it. Fix: check which nameservers your domain uses with a WHOIS lookup. Add the TXT record at the provider those nameservers point to. Use a DNS checker like whatsmydns.net to confirm propagation before clicking Verify in Merchant Center.
Analytics-based verification needs the GA4 tag to be present in the HTML at the time Google fetches the page, and the GA4 account must be the same Google account that owns Merchant Center. Fix: confirm GA4 is installed via direct gtag.js (not via GTM, which delays firing). Confirm the GA4 property is owned by the Merchant Center Google account, not by an agency or a former employee. If the agency owns the property, transfer ownership before retrying.
Verification succeeds but Claim fails with "Another account has already claimed this URL". This happens when an agency, a former employee, or a stale Merchant Center account from a previous tenant of the domain holds the claim. Fix: file a "Claim conflict" request in Merchant Center -> Business Information -> Website -> Claim conflict. Google requires proof of ownership (an HTML file at the root) plus a description of the relationship. Resolution typically takes 5-10 business days.
Run the free GMCSuspension audit. The Googlebot simulator renders your homepage exactly as Google does and confirms that the verification meta tag is present in the <head> before any <body> content, plus surfaces 42 other policy checks that often cause downstream suspensions.
Run free audit| Platform | Fastest verification method | Why it works best |
|---|---|---|
| Shopify | Search Console (via Shopify integration) | One-click setup in Shopify Admin, no theme changes; works for verified.myshopify.com or custom domains |
| WooCommerce / WordPress | HTML meta tag via Yoast or Rank Math | Direct field in plugin settings, persists across theme switches |
| Magento / Adobe Commerce | HTML file uploaded to /pub/ | Magento's /pub/ folder serves static files at domain root |
| Wix | DNS TXT record via Wix domain settings | Wix does not allow root-level static files; DNS is reliable |
| Squarespace | DNS TXT record via Squarespace DNS | Same constraint as Wix, DNS works cleanly |
| BigCommerce | Google Tag Manager (already integrated) | BigCommerce ships with GTM integration; reuse it for verification |
| PrestaShop | HTML meta tag via header.tpl | Direct template control; persists across module updates |
| Custom build | DNS TXT record | No dependency on template, framework or deploy pipeline |
Before April 2026, a verified URL was the end of the identity story. Now, the April 2026 AI verification layer takes the verified URL as a starting point and runs a deeper check: it compares the domain WHOIS record against the business name shown in the footer, against the address on the policy pages, and against public business registries (Companies House, Handelsregister, INSEE, Registro Mercantil, Camera di Commercio). A merchant whose URL is verified but whose footer business name does not match the WHOIS registrant now fails the AI step even though the verification step passes.
This is why merchants who got reinstated easily in 2025 are now finding the same fix does not work in 2026. The mechanic of the new AI layer is covered in our AI verification 2026 guide. Before submitting an appeal, run through the Pre-Appeal Suspension Checklist to catch any identity-layer mismatch the verification step alone will not flag.
A green verification check is necessary but not sufficient. Once the URL is verified and claimed, walk through the rest of the policy stack to avoid a suspension hitting a freshly-verified account:
It means Google cannot confirm that the Merchant Center account holder controls the domain. Verification is the step that proves ownership of the URL; claiming is the separate step that associates the verified URL with the Merchant Center account. The error shows up in the Diagnostics tab and blocks all Shopping ads, free listings and Performance Max product feeds until resolved.
Verification proves you own the domain (you place a code on the site, or DNS, or have Search Console access). Claiming is what associates that verified domain with your Merchant Center account exclusively. Only one Merchant Center account can claim a given URL at a time. A URL can be verified by multiple Google users but claimed by only one Merchant Center account.
On Shopify, the fastest path is Search Console verification. Go to Search Console, add your store URL as a property, verify it via the Shopify integration (a single click in Shopify Admin -> Online Store -> Preferences -> Google Search Console), then in Merchant Center -> Business Information -> Website, click "Verify and claim". Google picks up the Search Console ownership and verifies in seconds without touching theme files.
Verification and claiming are separate. A verified URL that is not also claimed by your account does not enable Shopping. Open Merchant Center -> Business Information -> Website and look for the "Claim" button next to a green Verification check. Click it; the account state will switch to both verified and claimed. If the Claim button is greyed out, another Merchant Center account already claims the URL.
Yes, both Wix and Squarespace allow custom TXT records at the DNS level. In Wix, go to Domains -> Manage DNS Records -> Add Record -> TXT and paste the verification string Google provides. In Squarespace, go to Settings -> Domains -> Advanced DNS -> Custom Records -> Add TXT. After saving, allow up to 24 hours for propagation, then click Verify in Merchant Center. DNS verification is the most reliable method because it does not depend on theme rendering or JavaScript.
The free GMCSuspension audit confirms your verification tag is in the right place, then checks 42 other policy requirements (price, availability, policies, GTIN, structured data, April 2026 identity signals). One report, 60 seconds, no signup.
Run free audit