PW FeedSmarter Feed Management for Google Merchant Plugins
BUY

How to verify and claim your WooCommerce store URL in Google Merchant Center

How to verify and claim your WooCommerce store URL in Google Merchant Center

Before Google Merchant Center can reliably associate submitted WooCommerce products with an online store, the merchant must establish control over the store’s website and connect that website to the correct Merchant Center account.

Google describes this as two related but different operations:

Product error details and recommended fixes in the PW Merchant interface
  • Website verification proves that an authorised person controls the website.
  • Website claiming reserves the verified website address for use by a specific Merchant Center account.

A WooCommerce store can be publicly accessible, use HTTPS and contain valid products while still showing an “Online store URL not verified” or domain-related issue in Merchant Center.

The problem may occur because the website has not been verified, the person completing the process does not have the required permissions, the verification tag is missing, the domain is already claimed by an older Merchant Center account or the submitted product URLs use a different domain.

The correction must therefore cover the website, Google account permissions, Search Console ownership, Merchant Center account structure and submitted WooCommerce product links.

The short answer

To verify and claim a WooCommerce store URL in Google Merchant Center:

  • Decide which domain is the store’s permanent public address.
  • Confirm whether the store uses the root domain or a subdomain.
  • Confirm whether www redirects to the non-www version or the reverse.
  • Confirm that HTTPS works correctly.
  • Open the homepage while logged out.
  • Confirm that customers can reach products and checkout.
  • Sign in to the intended Merchant Center account.
  • Check that the correct online store URL is entered.
  • Confirm that the Google account has the required Merchant Center access.
  • Check whether the same Google account is a verified owner in Search Console.
  • If necessary, verify ownership through the ecommerce platform, email, an HTML tag or file, Google Tag Manager or Google Analytics.
  • For durable domain-level ownership, consider creating a Search Console Domain property and verifying it through DNS.
  • Do not delete the verification tag, file or DNS record after verification succeeds.
  • Return to Merchant Center.
  • Complete the claim step for the verified website.
  • Check whether the domain is already claimed by another Merchant Center account.
  • Resolve any old, duplicate, agency or automatically created account claim.
  • Confirm that WooCommerce product links use the registered domain.
  • Confirm that variation URLs also use the registered domain.
  • Update products through the authoritative data source.
  • Allow Merchant Center to process the corrected account and product information.
  • Monitor the online store and product status.

Verification and claiming do not guarantee product approval.

They establish the relationship between the merchant, the website and the Merchant Center account. Google still evaluates product data, website quality, policies, checkout functionality and other applicable requirements independently.

What website verification means

Verification proves to Google that an authorised person can control or modify the website.

This control may be demonstrated through:

  • Access to the ecommerce platform
  • Access to an email address associated with the website
  • Permission to add an HTML verification tag
  • Permission to upload an HTML verification file
  • Control over the domain’s DNS records
  • Administrative access to an applicable Google Analytics property
  • Administrative or publishing access to an applicable Google Tag Manager container
  • Existing verified ownership in Google Search Console

Google explains that website verification establishes that the user is the website owner or is working with the person responsible for the website. Verification does not by itself reserve the domain for one Merchant Center account.

Google Merchant Center account connection screen in PW Merchant

Google’s current verification methods are described in About online store URL verification.

What website claiming means

Claiming connects the verified website address to a particular Merchant Center account.

Google describes the claim as the step that reserves the website address for that account’s exclusive use.

This distinction is important.

A person may already be a verified Search Console owner but still need to claim the website in Merchant Center. Conversely, attempting to claim a website before ownership has been verified will not complete the process.

The normal sequence is:

  1. Enter or update the online store URL.
  2. Verify control over the website.
  3. Claim the verified website for the intended Merchant Center account.
  4. Submit products whose landing pages use the claimed domain.

Why Merchant Center requires both steps

Merchant Center receives product links that direct customers away from Google and into the merchant’s store.

Google must be able to associate those product links with a business that controls the destination website.

The process helps prevent an unrelated Merchant Center account from using another company’s domain for product submissions.

PW Merchant settings for scheduling automatic product synchronization

Verification and claiming also support a consistent relationship between:

  • Merchant Center business information
  • Submitted product links
  • WooCommerce product pages
  • Shopping-cart and checkout pages
  • Customer policies
  • The business operating the store

The claimed website should represent the store where customers can understand the offer and complete the purchase.

Website claiming is not website approval

A verified and claimed domain is not automatically compliant with every Merchant Center requirement.

Google’s current online store requirements include providing eligible products at displayed prices, supporting a conventional payment method during secure checkout, allowing customers to purchase directly from the website and disclosing applicable purchase conditions such as return and refund policies.

These requirements are summarised in Google’s Online store URL domain requirements.

A website can therefore be:

  • Verified but not claimed
  • Verified and claimed but still under review
  • Verified and claimed while individual products remain disapproved
  • Verified and claimed while the account has another website or policy issue
  • Verified in Search Console but connected to the wrong Merchant Center account

Treat verification and claiming as essential account-identity steps, not as guarantees of approval, visibility, ranking, clicks or sales.

Choose the correct WooCommerce store URL first

Before selecting a verification method, determine which public address represents the store.

Possible formats include:

WooCommerce products prepared for submission through the Google Merchant API
  • https://example.com
  • https://www.example.com
  • https://shop.example.com
  • https://example.com/store/

The selected URL should lead customers to the real online store and remain consistent with the domain used in submitted product landing pages.

Check:

  • The preferred protocol
  • The preferred hostname
  • Whether www is used
  • Whether a subdomain hosts the store
  • Whether the store is located in a subdirectory
  • Whether redirects preserve the intended destination
  • Whether a language or country path is required
  • Whether the domain is permanent
  • Whether the same domain appears during checkout

Do not select an address merely because it is easier to verify.

Select the website that genuinely represents the WooCommerce store.

Root domain, subdomain and path differences

Domain structure affects claims.

Examples:

  • example.com is a root domain.
  • shop.example.com is a subdomain.
  • example.com/shop/ is a path beneath the root domain.
  • www.example.com is another hostname under the same root domain.

Google explains that a claim at a higher level in the domain path can take precedence over a lower-level address.

For example, a Merchant Center account that has claimed example.com can prevent another account from independently claiming shop.example.com.

This commonly occurs when:

  • A previous agency claimed the root domain.
  • An old Merchant Center account is still active.
  • A test account claimed a broader domain.
  • A parent advanced account holds the claim.
  • A platform created another Merchant Center account automatically.
  • Different departments created accounts for the same business.

Do not create additional Merchant Center accounts until the existing claim structure has been identified.

PW Merchant product review screen highlighting missing WooCommerce data

The difference between Search Console property types

Google Search Console supports two relevant website property structures.

Domain property

A Domain property normally uses a form such as:

example.com

It covers the root domain, subdomains and supported protocols.

Google requires DNS verification for a Domain property. The property definition does not include http, https, a path or the www prefix.

For example, a verified Domain property for example.com can cover:

  • http://example.com
  • https://example.com
  • https://www.example.com
  • https://shop.example.com
  • Paths under those hosts

Google documents this coverage in Add a website or platform property to Search Console.

URL-prefix property

A URL-prefix property represents one specific protocol and prefix, such as:

Product diagnostics summary showing approved and problematic catalogue items

https://www.example.com/

It may be verified through methods including an HTML file, HTML tag, Google Analytics or Google Tag Manager, subject to the requirements of the selected method.

A URL-prefix property does not automatically have the same breadth as a Domain property.

For a stable WooCommerce store, a DNS-verified Domain property can reduce future confusion because it is not dependent on a WordPress theme, SEO plugin or page template continuing to output a verification tag.

However, the appropriate method depends on who controls the domain and which account structure is required.

Before starting verification

Complete the following checks.

Confirm the intended Merchant Center account

Record:

  • Merchant Center account name
  • Merchant Center account ID
  • Business name
  • Primary administrator
  • Online store URL currently entered
  • Whether the account is standalone or part of an advanced account
  • Whether an agency manages the account
  • Whether another account exists for the same store

Do not claim the production website from an experimental or temporary account.

Confirm Google account permissions

The person completing the process should have the necessary access to Merchant Center and the selected verification service.

Depending on the method, this may include:

PW Merchant reporting screen for monitoring catalogue quality and synchronization results
  • Merchant Center user or administrator access
  • Verified owner status in Search Console
  • Edit or administrator access in Google Analytics
  • Publish or administrator permission in Google Tag Manager
  • WordPress administrator access
  • Hosting-file access
  • DNS-provider access
  • Access to the website-associated email address

If different people control Merchant Center, WordPress, DNS and Search Console, coordinate the process before changing verification records.

Inspect the public homepage

Open the selected store URL while logged out.

Confirm that:

  • The homepage loads without authentication.
  • HTTPS is valid.
  • The domain does not redirect to an unrelated website.
  • The store is not in maintenance mode.
  • A security system does not block Google.
  • The page source is accessible.
  • The store name is visible.
  • Products can be reached.
  • Prices are displayed.
  • Customers can add products to the cart.
  • Checkout is accessible.
  • Business and policy information is available.

Verification proves control, but an inaccessible or incomplete store may still fail other reviews.

Method 1: Verify through the ecommerce platform

Google may offer platform-assisted verification when a store uses a supported ecommerce platform or integration.

WooCommerce is self-hosted, so the available workflow can depend on:

  • Hosting provider
  • WordPress configuration
  • Installed Google integration
  • Merchant Center onboarding method
  • Existing Search Console ownership
  • Existing Google Analytics connection

Follow only the verification option shown for the actual store and account.

Before authorising a plugin or service to change Merchant Center settings, confirm:

  • Which Google account will be connected
  • Which Merchant Center account will be selected
  • Whether the service creates a new account
  • Whether an existing website claim will be replaced
  • Whether another product source will also be activated
  • Whether disconnecting the service removes verification data

Do not allow a setup assistant to create an unnecessary duplicate Merchant Center account.

Method 2: Verify through email

Merchant Center may allow verification through an email address associated with the website.

Google indicates that the email address can qualify when it uses the website domain or is listed on the website.

Examples may include:

  • admin@example.com
  • info@example.com
  • support@example.com

During email verification:

  1. Select the email verification option.
  2. Confirm the address displayed by Merchant Center.
  3. Request the verification code.
  4. Check the inbox and spam-related folders.
  5. Copy the code from the email.
  6. Paste the code into the code field in Merchant Center.
  7. Complete the verification.
  8. Continue to the claim step.

Google notes that following a link in the email does not necessarily fill the Merchant Center code field automatically. The code may need to be copied and pasted.

If the message does not arrive:

  • Confirm that the mailbox exists.
  • Confirm that it can receive external messages.
  • Check spam, promotions and quarantine folders.
  • Confirm that the email address is connected to the website.
  • Request another code after the interval shown by Google.
  • Use another verification method when necessary.

Email verification may be convenient, but the store should also maintain durable ownership records and controlled Google account access.

Method 3: Verify with an HTML tag

The HTML tag method provides a unique verification meta tag.

It normally resembles:

<meta name="google-site-verification" content="verification-value">

The exact tag must come from Google. Do not invent, shorten or modify it.

For a WooCommerce store:

  1. Copy the verification tag shown by Google.
  2. Add it to the <head> section of the public homepage.
  3. Clear WordPress, server and CDN caches.
  4. Open the homepage while logged out.
  5. View the page source.
  6. Search for google-site-verification.
  7. Confirm that the complete tag appears inside <head>.
  8. Return to the verification screen.
  9. Select Verify.
  10. Continue to the Merchant Center claim step.

Google’s Search Console ownership guidance states that the tag must appear in the <head> section of the non-logged-in homepage and must remain valid.

In WordPress, the tag may be added through:

  • A suitable site-verification field
  • A child theme
  • A controlled custom plugin
  • A verified header-management feature
  • An SEO plugin that supports Search Console verification

Avoid editing the parent theme directly because a theme update may remove the change.

Do not install several plugins merely to output the same verification tag.

After adding it, inspect the final live source rather than relying only on the WordPress settings screen.

Why Google cannot find an HTML tag

Common causes include:

  • The tag was added to <body> instead of <head>.
  • The tag appears only for logged-in administrators.
  • The tag was added to a staging website.
  • A cache still serves the old homepage.
  • A security or consent tool removes the tag.
  • The selected property uses another hostname.
  • The site redirects before Google can inspect the intended page.
  • The tag belongs to another Google account.
  • The content value was edited.
  • The theme update removed the tag.
  • A performance plugin delayed or relocated the tag.
  • The homepage is generated differently for crawlers.
  • The page is protected by maintenance mode or authentication.

Correct the live implementation, clear applicable caches and test again in a private browser window.

Method 4: Verify with an HTML file

The HTML-file method requires uploading Google’s verification file to the location specified by the verification interface.

The file must normally remain accessible at a public address similar to:

https://example.com/google-verification-file.html

To use this method:

  1. Download the exact file supplied by Google.
  2. Do not rename it.
  3. Do not change its contents.
  4. Upload it to the required website root.
  5. Open the exact file URL in a private browser.
  6. Confirm that it returns the file directly.
  7. Confirm that no login is required.
  8. Complete verification.
  9. Leave the file in place.

Google explains that HTML-file verification is available for URL-prefix properties, not Domain properties. Search Console periodically checks verification tokens, so removing the file later may cause ownership to be lost.

This method usually requires hosting-panel, SFTP or server-file access. Uploading the file to the WordPress Media Library is generally not equivalent to placing it at the required root URL.

Method 5: Verify with Google Analytics

Google Analytics verification depends on both technical placement and account permissions.

The relevant Google account should have the required access to the Google Analytics property already used by the website.

The public homepage must contain the applicable Analytics code in the required location.

Check:

  • The correct Google Analytics property is used.
  • The correct web data stream is connected to the WooCommerce domain.
  • The Merchant Center user has the necessary Analytics access.
  • The same Google account is used where Google requires account matching.
  • The tag appears on the public homepage.
  • The tag is not injected only after an action that Google cannot perform.
  • Cookie-consent behaviour does not prevent verification.
  • The Analytics code has not been modified incorrectly.

If Analytics verification fails, do not repeatedly reinstall Analytics.

Inspect the live page source, account permissions and property-domain relationship. Use an HTML tag, HTML file or Search Console DNS method if those options provide clearer ownership control.

Method 6: Verify with Google Tag Manager

Google Tag Manager verification requires the correct container to be installed on the public homepage and the user to have the required container permissions.

Google’s Search Console documentation states that the user needs Publish or Admin permission and must use the Google account associated with the Tag Manager container.

Also check:

  • The container belongs to the intended business.
  • The container is published.
  • The correct container ID appears on the homepage.
  • The code is in the required positions.
  • The <noscript> portion follows the opening <body> tag as required.
  • No security or optimisation plugin removes part of the code.
  • The homepage does not require authentication.
  • The Merchant Center and Tag Manager account access is properly aligned.

Do not use Tag Manager verification merely because a container ID appears in the source. The Google account completing verification must also have the required rights.

Verify through Search Console DNS ownership

For merchants who control the domain’s DNS, a Search Console Domain property is often a strong long-term method.

The general process is:

  1. Open Google Search Console.
  2. Add a Domain property.
  3. Enter the root domain without https, a path or www.
  4. Copy the TXT or CNAME record provided by Google.
  5. Open the DNS provider’s control panel.
  6. Add the record exactly as provided.
  7. Preserve existing unrelated DNS records.
  8. Save the DNS configuration.
  9. Wait for the record to become publicly available.
  10. Return to Search Console.
  11. Select Verify.
  12. Keep the verification record after verification succeeds.
  13. Confirm that the verified owner is also a user in the intended Merchant Center account.
  14. Return to Merchant Center and complete the claim.

DNS propagation is not always immediate. Google advises that manually installed records can take time to become visible.

Do not delete the TXT or CNAME verification record after success. Search Console periodically checks whether ownership can still be verified.

How Search Console ownership connects to Merchant Center

If a user in the Merchant Center account is already a verified owner of the website in Search Console, Google may recognise the website as verified.

The accounts must be aligned correctly.

For example:

  • Search Console verified owner: owner@example.com
  • Merchant Center administrator: merchant@example.com

If these are different accounts and the first account is not a Merchant Center user, automatic recognition may fail.

Possible corrections include:

  • Add the verified Search Console owner to Merchant Center with the necessary access.
  • Verify the website in Search Console using the Merchant Center administrator’s Google account.
  • Coordinate ownership with the actual business owner.
  • Remove obsolete users and verification tokens only after access continuity has been secured.

Do not transfer website control to an unknown agency account simply to complete onboarding.

How to claim the verified website

After verification:

  1. Sign in to the intended Merchant Center account.
  2. Open Settings.
  3. Open Business info.
  4. Find Your online store.
  5. Review or edit the store URL.
  6. Confirm that the displayed address is correct.
  7. Complete the confirmation or claim action shown.
  8. Check that the website is reported as verified and claimed.
  9. Record the account ID and claim status.
  10. Inspect submitted product links.

Merchant Center menu wording can change. Follow the current online store confirmation section shown in the account.

Do not assume that successful Search Console verification automatically proves that the claim belongs to the correct Merchant Center account.

How to fix “Online store URL not verified”

First determine whether the failure is related to the website, user permissions or account claim.

Check:

  • Is the exact website entered in Merchant Center?
  • Is the website publicly accessible?
  • Is HTTPS working?
  • Is the Google account a Merchant Center user?
  • Is the same account a verified Search Console owner?
  • Is the verification tag or file still present?
  • Is the DNS record visible?
  • Does the Analytics user have sufficient permissions?
  • Does the Tag Manager user have Publish or Admin permission?
  • Is the homepage accessible while logged out?
  • Is another Merchant Center account using the domain?
  • Is a higher-level domain already claimed?

Google’s current troubleshooting guidance is available in How to fix: Online store URL not verified.

How to fix “Website already claimed by another account”

This error often indicates that the website is connected to:

  • An older Merchant Center account
  • A duplicate account
  • An account created by a previous agency
  • An automatically generated platform account
  • A parent advanced account
  • Another division of the same company
  • A test account

Before attempting an overwrite:

  1. Record the intended Merchant Center account ID.
  2. Search business records for other account IDs.
  3. Check users who previously managed Google Shopping.
  4. Check old Google Ads and Merchant Center connections.
  5. Check Search Console owners.
  6. Check ecommerce integrations that may have created accounts.
  7. Determine whether an advanced account legitimately owns the claim.
  8. Confirm who should control the production website.
  9. Preserve product and account information needed from the old account.
  10. Reclaim the website only after authority is established.

Deleting an account or overwriting a claim can affect existing product sources and integrations.

Do not remove an account merely because its name looks unfamiliar.

Higher-level domain claims

A higher-level claim can prevent a lower-level website from being claimed separately.

For example:

  • Account A claims example.com.
  • Account B attempts to claim shop.example.com.

The broader root-domain claim can take precedence.

Google’s troubleshooting guidance suggests testing the higher-level domain format and, in some cases, removing www or the protocol from the online store address shown in Merchant Center.

However, do not make random URL changes.

First determine:

  • Which URL customers use
  • Which account owns the higher-level claim
  • Whether both stores belong to the same business
  • Whether an advanced account structure is appropriate
  • Whether products from both stores are intentionally managed together

Multiple accounts and advanced account structures

Google states that a single URL can normally be claimed by one account.

Where several Merchant Center accounts legitimately need shared claiming rights, an advanced account structure may allow sub-accounts to inherit the parent account’s claim.

This is relevant for organisations managing:

  • Multiple clients
  • Multiple stores
  • Multiple country operations
  • Marketplace sellers
  • Agency-managed accounts
  • Separate business units

Do not use an advanced account merely to avoid resolving an accidental duplicate.

The structure should reflect genuine business and account-management needs.

WooCommerce product links must match the claimed domain

After the website is claimed, inspect the product URLs sent from WooCommerce.

Google requires the domain used by submitted landing-page links to match the domain registered at the account level.

Review:

  • Product link
  • Mobile link, if used
  • Variation-specific links
  • Canonical URLs
  • Language-specific URLs
  • Country-specific URLs
  • Redirect destinations
  • Affiliate or tracking redirects
  • Staging-domain remnants
  • Old-domain URLs
  • CDN-generated page links

Google’s Mismatched domains guidance explains that the landing-page domain must match the registered website domain.

Image URLs may be hosted elsewhere under applicable image requirements, but product landing pages must be associated with the registered store domain.

Common WooCommerce domain problems

WordPress Address and Site Address are different

WordPress includes:

  • WordPress Address
  • Site Address

If these values do not reflect the production domain correctly, plugins may generate unexpected product URLs.

Review the settings carefully. Do not change them on a live site without understanding the hosting structure because an incorrect change can make WordPress inaccessible.

Old domain remains in the database

After a website migration, old URLs may remain in:

  • Product content
  • Post metadata
  • Variation metadata
  • Cached transients
  • SEO fields
  • Structured data
  • Plugin settings
  • Scheduled tasks
  • Merchant integration tables

Use a controlled migration process that respects serialised WordPress data.

Staging URLs are submitted

A product may accidentally use:

  • staging.example.com
  • dev.example.com
  • A temporary hosting hostname
  • A local development URL
  • A preview URL

These URLs should not be submitted as production product landing pages.

Canonical URL points elsewhere

A product loads on the claimed domain but its canonical tag points to another hostname.

This can confuse website and product processing. Ensure the visible product, canonical URL, structured data URL and submitted link describe the intended production page.

Language plugins change the hostname

A multilingual store may use:

  • example.com/en/
  • example.com/de/
  • en.example.com
  • de.example.com

Confirm that the website claim and Search Console ownership cover the submitted language URLs.

Also confirm that every submitted product opens the correct language version without an unstable cookie or IP redirect.

Currency or country redirects change the domain

Some WooCommerce extensions redirect customers to another country-specific domain.

If the submitted link begins on the claimed domain but automatically redirects to a different unclaimed domain, the product can produce a mismatch.

Test product links:

  • While logged out
  • Without cookies
  • On mobile
  • From relevant countries where possible
  • With tracking parameters
  • With every submitted variation

Structured data uses another URL

WooCommerce, the theme and SEO plugins may create duplicate Product structured data.

Inspect:

  • Product URL
  • Offer URL
  • Canonical URL
  • Brand URL
  • Seller URL
  • Variation URL

Structured data does not replace Merchant Center website claiming, but it should not describe a different store domain.

Verification tokens must remain in place

Search Console states that verification lasts while Google can confirm that the verification token remains present and valid.

Do not remove:

  • DNS TXT verification records
  • DNS CNAME verification records
  • HTML verification files
  • HTML meta tags
  • Required Analytics access
  • Required Tag Manager access

A WordPress redesign, theme replacement, SEO-plugin removal, DNS cleanup or agency transition can unintentionally remove the token.

Maintain at least one controlled verification method. Search Console also supports multiple verification methods, which can provide continuity if one method is removed.

Merchant API homepage management

Merchant API provides a dedicated Homepage resource for store URL management.

The resource supports operations to:

  • Retrieve current homepage settings
  • Update the homepage URI
  • Claim the homepage
  • Unclaim the homepage
  • Recheck claim status

Google states that updating, claiming or disclaiming a homepage through Merchant API requires administrator access to the Merchant Center account.

The current technical sequence is:

  1. Set or update the homepage URI.
  2. Verify website ownership.
  3. Call the homepage claim operation.
  4. Confirm that the returned claimed value is true.

Google documents these operations in Manage your homepage settings.

Merchant API can perform the account-side homepage operation, but it does not remove the requirement to prove control over the website.

A successful API request also does not prove that the store satisfies every Merchant Center policy.

How PW Merchant API fits into website verification

PW Merchant API is designed to support controlled product communication between WooCommerce and Google Merchant Center.

Depending on the installed version and supported configuration, it can help merchants:

  • Connect an authorised Google account.
  • Identify accessible Merchant Center accounts.
  • Prepare supported WooCommerce product data.
  • Submit products through Merchant API.
  • Update existing products.
  • Process simple and variable products.
  • Review operation results.
  • Monitor supported product issues.
  • Manage controlled synchronisation workflows.

As a WooCommerce Google Merchant Center plugin, PW Merchant API can help ensure that submitted product links come from the intended WooCommerce store configuration.

However, it cannot independently prove that the user owns a domain.

PW Merchant API cannot:

  • Provide DNS access.
  • Create legitimate Search Console ownership without authorisation.
  • Resolve an unknown agency’s account ownership automatically.
  • Decide which business should control a disputed domain.
  • Restore a deleted verification token.
  • Guarantee successful website claiming.
  • Guarantee Google approval.
  • Guarantee product visibility.
  • Guarantee rankings, impressions, clicks or sales.
  • Replace Merchant Center account administration.
  • Correct an incomplete checkout automatically.
  • Override Google’s independent policy evaluation.

WooCommerce remains the source of the store’s commercial product pages, PW Merchant API supports applicable product communication and Google Merchant Center independently processes and evaluates the submitted information.

A controlled verification and claiming workflow

Step 1: document the intended production structure

Record:

  • Root domain
  • Preferred hostname
  • HTTPS address
  • Store homepage
  • Product URL pattern
  • Cart URL
  • Checkout URL
  • Language URLs
  • Country URLs
  • Canonical format
  • Merchant Center account ID
  • Search Console owner
  • DNS administrator

Step 2: remove accidental ambiguity

Identify:

  • Old domains
  • Staging domains
  • Duplicate Merchant accounts
  • Former agency accounts
  • Unused product sources
  • Old Analytics properties
  • Old Tag Manager containers
  • Previous Search Console owners

Do not delete anything until its purpose and ownership have been confirmed.

Step 3: choose the verification method

Select the method that the authorised team can maintain.

For long-term control, consider a method independent of the active WordPress theme. If DNS access is centrally managed, a Search Console Domain property can provide broad ownership coverage.

Step 4: complete verification

Implement the exact token or account connection provided by Google.

Test it publicly and complete the verification action.

Step 5: preserve the token

Document:

  • Verification method
  • Responsible account
  • Token location
  • Date completed
  • Backup owner
  • Merchant Center account connected

Do not publish secret account credentials in this record.

Step 6: claim the website

Return to the intended Merchant Center account and complete the online store claim.

Confirm that the domain is attached to the correct account.

Step 7: inspect every submitted product domain

Check simple products and every submitted variation.

Correct links through the authoritative WooCommerce or integration source.

Step 8: process updates

Submit corrected products and allow Merchant Center to process the changes.

A technically successful update does not immediately prove that all account and product reviews are complete.

Step 9: monitor ownership continuity

After theme, hosting, domain, DNS, plugin or agency changes, recheck:

  • Search Console ownership
  • Merchant Center claim
  • Product link domains
  • Verification tokens
  • Account permissions

Common mistakes

Confusing verification with claiming

Search Console verification proves ownership, but the site may still need to be claimed in Merchant Center.

Claiming from the wrong account

A test, agency or duplicate account may reserve the domain and block the intended production account.

Removing the verification token

Deleting the DNS record, HTML file or meta tag can cause ownership to be lost later.

Changing the WordPress theme

A verification tag placed directly in the parent theme may disappear after an update or theme replacement.

Using the wrong Google account

The Merchant Center user may not match the Search Console verified owner, Analytics administrator or Tag Manager administrator.

Submitting staging URLs

WooCommerce products may still contain temporary or development-domain links after migration.

Ignoring redirects

The submitted URL may begin on the claimed domain but redirect customers to a different hostname.

Assuming www and non-www are always interchangeable

They may redirect correctly for customers while the account, verification method or product links use an inconsistent configuration.

Creating another Merchant Center account

A new account can create more ownership and product-source conflicts without resolving the original problem.

Correcting products manually

Manual edits may be overwritten by the next Merchant API, XML, scheduled file or WooCommerce update.

Assuming a successful claim guarantees approval

Google still reviews the website, product data, policies and customer purchasing experience.

Frequently asked questions

What is the difference between verifying and claiming a website?

Verification proves that an authorised person controls the website. Claiming connects that verified website to a specific Merchant Center account.

Do I need Search Console to verify my WooCommerce store?

Not in every case. Merchant Center supports several verification methods. However, existing verified ownership in Search Console can allow Merchant Center to recognise the website as verified.

Which verification method is best for WooCommerce?

The best method is one the authorised business can maintain reliably. DNS verification through a Search Console Domain property is often durable, while an HTML tag or file may be easier when DNS access is unavailable.

Can I use an SEO plugin to add the verification tag?

Yes, if the plugin outputs the exact tag in the public homepage’s <head> section. Confirm its presence in the live page source and avoid duplicate verification implementations.

Can I remove the verification tag after success?

No. Google periodically checks verification tokens. Removing the only valid token can cause ownership to be lost.

Should I remove the DNS TXT record after verification?

No. Google specifically advises keeping the verification record in place.

Why is Merchant Center not recognising my Search Console ownership?

The verified Search Console owner may not be a user in the Merchant Center account, the wrong property may have been verified or the website entered in Merchant Center may not match the verified property.

Can two Merchant Center accounts claim the same website?

A single URL is normally claimed by one account. An applicable advanced account structure can allow sub-accounts to inherit a parent claim.

What if an old agency claimed my domain?

Identify the account, establish the business’s authority, review existing product sources and arrange an orderly ownership transition. Do not create repeated duplicate accounts.

What does “claimed at a higher level” mean?

A broader claim, such as example.com, can take precedence over a lower-level address such as shop.example.com.

Can I claim only a subdirectory?

Account and domain-path behaviour depends on the broader existing claim. Review the actual store structure and any higher-level claim before attempting a path-specific setup.

Should I enter www in Merchant Center?

Enter the address that represents the real store and matches the submitted landing-page structure. If verification fails, Google’s troubleshooting guidance may recommend testing a higher-level format without www or the protocol.

Can HTTP and HTTPS differences cause a problem?

They can contribute to an inconsistent configuration. Use a valid HTTPS production store and confirm that all redirects and submitted links resolve to the intended domain.

Can product images use another domain?

Google permits image links hosted outside the registered product landing-page domain when they meet the applicable image requirements. The product landing-page domain must still match the registered store.

Does claiming the homepage verify every product page?

The claim establishes control over the website. Individual product pages must still be accessible, accurate and compliant with applicable requirements.

Can Merchant API claim the website?

Merchant API provides a homepage claim method, but ownership verification must be completed first and the caller requires Merchant Center administrator access.

Can PW Merchant API verify my DNS automatically?

No. Domain ownership requires legitimate access to the website, DNS or an authorised Google service.

Does a successful Merchant API claim mean products are approved?

No. It confirms the homepage claim operation. Google evaluates submitted products and the website separately.

Why do products show a mismatched-domain issue after claiming?

The submitted product links may use another hostname, old domain, staging address, country domain, language subdomain or unexpected redirect.

Should I request a review after verification?

First confirm that the website is verified and claimed, product links use the correct domain and other website requirements are satisfied. Follow the issue-specific option shown in Merchant Center.

How long does verification take?

HTML and account-based methods may complete quickly when correctly configured. DNS records can require additional propagation time. Merchant Center processing after correction may also take time.

Can a domain migration remove the claim?

A migration can affect the claim or product eligibility if the Merchant Center homepage, Search Console ownership and product links are not updated for the new domain.

What happens when I change my WooCommerce domain?

The new website must be verified and claimed as required, and all product links, redirects, canonical URLs, structured data and Merchant sources must be updated in a controlled sequence.

Final checklist

Before considering the store URL verification and claim complete, confirm that:

  • The production domain was identified.
  • The preferred hostname was identified.
  • HTTPS works correctly.
  • www and non-www behaviour was tested.
  • Root-domain and subdomain relationships were documented.
  • Country and language URLs were reviewed.
  • The homepage works while logged out.
  • Product pages are publicly accessible.
  • Cart and checkout are accessible.
  • Customers can purchase directly from the store.
  • Prices are visible.
  • Payment methods are available.
  • Return and refund information is accessible.
  • The intended Merchant Center account ID was recorded.
  • Duplicate Merchant Center accounts were investigated.
  • Former agency accounts were investigated.
  • Advanced-account relationships were reviewed.
  • The intended Google account has Merchant Center access.
  • The Search Console property was identified.
  • The Search Console property type was recorded.
  • The verified Search Console owner was identified.
  • The Search Console owner is connected to Merchant Center where required.
  • The selected verification method is maintainable.
  • The exact Google verification token was used.
  • The HTML tag appears inside <head> where applicable.
  • The HTML file is accessible at the required URL where applicable.
  • The DNS record is publicly visible where applicable.
  • The Analytics property belongs to the intended store.
  • The Analytics user has the required permissions.
  • The Tag Manager container belongs to the intended store.
  • The Tag Manager user has the required permissions.
  • WordPress caches were cleared.
  • Server caches were cleared.
  • CDN caches were cleared.
  • The homepage source was tested while logged out.
  • Security tools do not block verification.
  • Maintenance mode is disabled.
  • Verification completed successfully.
  • The verification token remains in place.
  • A backup ownership method was considered.
  • The website was claimed in the intended Merchant Center account.
  • The claim status was recorded.
  • Higher-level domain claims were investigated.
  • Old or duplicate claims were resolved safely.
  • Simple-product links use the registered domain.
  • Variable-product links use the registered domain.
  • Variation-specific URLs were tested.
  • Mobile links were reviewed where used.
  • Language links were reviewed.
  • Country links were reviewed.
  • Redirect destinations were inspected.
  • Old-domain links were removed.
  • Staging links were removed.
  • Canonical URLs use the intended domain.
  • Structured-data URLs use the intended domain.
  • WordPress Address and Site Address were reviewed.
  • Product sources were inventoried.
  • The authoritative WooCommerce source was identified.
  • Obsolete sources were removed only when safe.
  • Corrected products were submitted through the authoritative source.
  • Merchant Center was allowed to process the updates.
  • Mismatched-domain issues were monitored.
  • The claim will be rechecked after future theme, hosting, DNS or domain changes.

Verifying a WooCommerce website and claiming it in Google Merchant Center are separate but connected operations.

Verification proves that an authorised person controls the store. Claiming reserves that verified store URL for the correct Merchant Center account. Product landing pages must then use a domain that matches the registered website.

A reliable implementation begins by identifying the permanent production domain, the intended Merchant Center account and the authorised Search Console owner. It continues by preserving verification tokens, resolving older account claims and inspecting every product link submitted from WooCommerce.

Merchant API provides dedicated homepage operations, but it does not replace legitimate website ownership verification. Similarly, a WooCommerce Google Merchant Center plugin can support product communication but cannot decide who legally or operationally controls a disputed domain.

WooCommerce remains the customer-facing commercial source, PW Merchant API supports the applicable product communication process and Google Merchant Center independently verifies, processes and evaluates the submitted information.

When the domain, account ownership, website claim and submitted product URLs all describe the same store, Google can associate the Merchant Center account with the WooCommerce website more reliably.