Introduction
Before even discussing product feed, compliance, or suspension, there's a prerequisite technical step that blocks everything if it fails: site verification and claiming. Without it, no product can be served, regardless of catalog quality.
Table of Contents
- Verification vs Claiming: the Difference
- The 3 Available Verification Methods
- The Most Common Failure Causes
- Special Case: Site Already Claimed by Another Account
- How to Verify a Subdomain or a Marketplace
- Step-by-Step Resolution Process
- FAQ
Verification vs Claiming: the Difference
Verification proves you're the legitimate owner/admin of the site via technical proof (HTML tag, file, or linked Analytics/Search Console account). Claiming is officially associating that verified site with your specific Merchant Center account to use it in product feeds. Both steps must be completed within Merchant Center itself to unblock distribution.
The 3 Available Verification Methods
- HTML tag — a unique meta tag added to your homepage's
<head>. - HTML file — a file uploaded to your domain's root, requiring FTP/hosting access.
- Google Analytics or Tag Manager — reuses an existing account/container as proof of ownership.
- Google Search Console (recommended) — if already verified with the same Google account, Merchant Center can reuse it directly — the most durable method over time.
The Most Common Failure Causes
The tag or file was removed during a site update (theme change, migration, redesign); the Google account used lacks sufficient admin rights; a cache or CDN serves an outdated page version to Google; the site blocks Googlebot at verification time (restrictive robots.txt, anti-bot protection, WAF); the verified domain doesn't exactly match the feed's domain.
Special Case: Site Already Claimed by Another Account
A domain can only be claimed by one Merchant Center account at a time — common when a former agency/provider claimed the site from an account you no longer access, or a forgotten previous account still claims the domain. Merchant Center offers a "force claim" (overwrite) procedure that transfers the claim to your account provided technical verification is demonstrated with your current account.
How to Verify a Subdomain or a Marketplace
Each subdomain generally needs its own separate verification, unless the Search Console domain-property method is used to cover all subdomains automatically. For marketplace/multi-brand structures, verification happens at the main domain level, but feed structure must clearly reflect which URL maps to which product.
Step-by-Step Resolution Process
- Identify the verification method currently used in Merchant Center.
- Manually confirm the proof is still present (in a private browsing window to avoid cache false positives).
- Clear any cache or CDN serving an outdated page to Googlebot.
- Verify the Google account used has admin rights on the site/Search Console/Analytics.
- Test page accessibility for Googlebot via Search Console's URL Inspection tool.
- If the domain is already claimed elsewhere, start the force-claim procedure.
- Prefer the Search Console method going forward — more resilient to theme/code changes than an HTML tag alone.
FAQ
Do I need to re-verify after a theme change or migration? Yes — systematically check that the verification tag or file is still present after any migration or theme change, since these operations frequently remove it without warning.
Does verification expire over time? No, a successful verification doesn't automatically expire, but it can become invalid if the underlying technical proof is removed from the site.
Can I use multiple verification methods at once? Yes, and it's recommended for redundancy — if one method is accidentally invalidated, a second active method prevents total loss of verification.
Check Nothing Else Is Blocking Your Account
Once your site is properly verified and claimed, feed and product page compliance still need checking. MyGoogle scans your pages in 30 seconds and identifies active violations before they block your distribution.
Launch the free audit — no installation required, immediate results.