Your Google Merchant Center Won't Verify and the Error Message Is Useless. Here's the Real Fix.

By Steve Merrill | May 27, 2026

You've been staring at the same GMC error for three days. "Server error" or "Couldn't verify site", no explanation, no path forward. You've re-added the verification tag. You've cleared cache. You've tried different browsers. Nothing works.

I've seen this exact situation a dozen times in client onboarding calls. The error message is legitimately useless. But the root cause is almost always the same thing.

Orphaned verification tags.

What Are Orphaned Verification Tags and Why Do They Block You?

Orphaned verification tags are Google site verification meta tags on your store that belong to a different GMC account, not the one you're trying to verify with now.

When Google attempts to verify your site, it checks the page for a tag matching your current account's token. If it finds multiple competing tags, one from your account, others from previous accounts, it throws a server error instead of a clean failure. The system can't resolve which account should own the verification.

It's one of those situations where having more data causes more problems than having none. One tag from an old platform, a previous agency, or a past business partner is enough to block the whole process.

Where Do These Tags Come From?

Four main sources, in rough order of how often I see them:

Platform migrations. The most common scenario. A store migrated from Wix or WooCommerce to Shopify. During the migration, theme code was copied or a developer rebuilt the store and pulled tags from the old platform. The old verification tag came along for the ride.

Previous consultants or agencies. A marketing consultant set up GMC access using their own Google account or a test account. When they left, they didn't clean up. The tag they added is still in the theme.

Apps that inject verification tags. Some SEO apps, Google Shopping apps, and marketing platforms add GMC verification tags independently of Shopify's native settings. When these apps are uninstalled, they sometimes leave their tags behind in the theme or via script injection.

Previous store owners. If you bought a Shopify store, you may have inherited the previous owner's GMC setup, including their verification tag. This one trips up a surprising number of store buyers who assumed a clean handoff.

According to Google Merchant Center's verification documentation, your site should have exactly one verification tag matching your current account. Any additional tags are noise, and apparently, conflicting noise causes a server error rather than a simple failure.

How Do You Find the Orphaned Tags?

Start with the simplest method: view source.

Open your homepage in a browser. Press Ctrl+U (Windows) or Cmd+Option+U (Mac). When the source code loads, use Ctrl+F or Cmd+F to search for "google-site-verification."

Every instance you find should be your current GMC account's verification token. If you see multiple results, compare each token to the one in your current GMC account under Business info > Website. Any token that doesn't match is orphaned.

Note the token values, you'll need them to track down where they're being injected.

Next, check three places where these tags commonly hide on Shopify:

theme.liquid. In Shopify Admin, go to Online Store > Themes > Edit code. Open theme.liquid and search for "google-site-verification." Any hardcoded meta tags there that don't match your current account need to go.

Installed apps. Some apps add script tags or meta tags through Shopify's ScriptTag API, which means they inject code that doesn't show up in theme.liquid. Go through your active apps, especially any SEO, Google Shopping, or ads management tools, and check if any of them manage GMC verification independently.

Google Tag Manager. If you have GTM installed, someone may have added the verification tag as a custom HTML tag in GTM. Log into GTM, check the container, and look for any tags containing "google-site-verification."

What Does the Fix Actually Look Like?

Once you've found the orphaned tags, the fix is straightforward.

For hardcoded tags in theme.liquid: delete the meta tag line. Save the file. If you're on a published theme, the change takes effect immediately. If you're on a theme that needs to be republished, do that.

For app-injected tags: uninstall the app properly through Shopify's app management (not just deleting the app from your store, use the uninstall flow so Shopify can remove associated script tags). If the app is already uninstalled and still leaving residue, you may need to contact Shopify support to clean up orphaned script tags manually.

For GTM-injected tags: delete the relevant custom HTML tag from your GTM container and publish the container update.

After cleanup, wait 15-30 minutes, then return to Google Merchant Center and retry verification. In most cases, the server error disappears and verification completes in under a minute.

Why Does This Matter for AI Shopping Specifically?

GMC verification isn't just a Google Shopping requirement anymore. It's the gateway to Google AI Mode product discovery.

When a buyer asks Google AI Mode "find me a lightweight trail running shoe under $120," the products that surface are coming from verified, active Merchant Center accounts. If your GMC account isn't verified and your feed isn't active, you're not in the pool. It doesn't matter how good your product data is.

Google AI Mode and Google's Universal Commerce Protocol both require a verified GMC account as the foundation. The orphaned tag problem is fixable in an afternoon, and leaving it unfixed means you're locked out of AI-powered Google discovery entirely.

I've seen clients who had everything else right, clean product feed, solid structured data, good titles, but couldn't get into AI Mode results because their GMC verification was failing. One afternoon of tag cleanup changed that. Worth the effort.

Frequently Asked Questions

Why does Google Merchant Center say "server error" during site verification?

The most common cause is orphaned verification tags, meta tags on your site from old GMC accounts, old platforms (Wix, WooCommerce), or previous consultants. When Google finds multiple conflicting verification tags, it returns a server error instead of a clear failure message.

Where do orphaned GMC verification tags come from on Shopify?

Four main sources: (1) Previous platform migrations where old verification tags were copied over, (2) Former marketing consultants who set up their own GMC test accounts, (3) Apps that inject verification tags and weren't properly uninstalled, (4) Hardcoded tags in theme.liquid that were never cleaned up.

Does GMC verification failure affect AI Shopping eligibility?

Yes. Google Merchant Center verification is required for your products to appear in Google AI Mode shopping results and Google Shopping. Without a verified and claimed website, your product feed won't be trusted and your products won't show in AI-powered Google discovery.

How do I check if apps are injecting orphaned verification tags?

View your homepage source code and search for "google-site-verification." Any tag you find that doesn't match your current GMC account is suspect. Cross-reference with your installed apps list, some SEO and ads apps inject these tags without obvious disclosure.

Can orphaned GMC tags cause other verification problems beyond site verification?

Sometimes. Old verification tags from previous platform owners can also interfere with Google Search Console verification and, in rare cases, create crawl confusion. Worth doing a full cleanup any time you migrate platforms or change agencies.

Not sure if your GMC setup is blocking your AI Shopping visibility?
Check Your Store's AI Readiness →