Unable to insert site verification

  • Resolved l575

    (@l575)


    4 months, 1 week ago

    Hello, I can’t connect Google WooCommerce to the existing Google Merchant Center.

    There is an error: Unable to insert site verification. The necessary verification token could not be found on your site.

    Google Merchant Account is completely verified and claimed.

    The page I need help with: [log in to see the link]

Viewing 15 replies - 16 through 30 (of 33 total)
1 2 3
  • Plugin Support LovingBro (woo-hc)

    (@lovingbro)

    4 months, 1 week ago

    Hi @l575,

    Thanks for clarifying that the Google Merchant Center is already working correctly for https://steampunkbdsm.com and that the goal here is specifically to sync products through Google for WooCommerce. That context really helps, and I can see how this has been frustrating given everything you have already tested.

    The next step I would like you to try is using the built in connection test page that the plugin provides. Please go directly to this URL while logged into your WordPress admin area: /wp-admin/admin.php?page=connection-test-admin-page

    On that page, disconnect Google and Google Merchant Center completely, then reconnect them again and make sure all requested permissions are accepted during the flow. Once the connection is re established, please also click the Sync All Products button on that same page to force a fresh product sync.

    This path bypasses some of the standard UI and helps reset the Google for WooCommerce connection state more cleanly, especially in cases like this where verification already exists outside the plugin.

    Let us know what you see after reconnecting and running the full sync, and we can take it from there.

    Thread Starter l575

    (@l575)

    4 months, 1 week ago

    Hello,

    Thanks for the help.

    I did these steps before, and I did them once again. Nothing changed, I’ve got same error.

    Error submitting products to Google: Google Merchant Center has not been set up correctly. Please review your configuration.

    • This reply was modified 4 months, 1 week ago by l575.
    Plugin Support LovingBro (woo-hc)

    (@lovingbro)

    4 months, 1 week ago

    Hi @l575,

    I appreciate you coming back with an update, and I can see how discouraging it is to still hit the same error after retrying the steps. I want to make sure we are fully aligned and looking at the exact same flow on your end so we can move this forward effectively.

    Can you please confirm if you were able to visit this page directly while logged into your WordPress admin and try the steps I shared earlier: https://steampunkbdsm.com/wp-admin/admin.php?page=connection-test-admin-page

    If you have already done this and the error persists, it would really help to get a clearer picture of what you are seeing. Please share a screenshot or a short Loom screen recording showing the exact error message and where it appears in the flow. You can use https://snipboard.io for screenshots or Loom for a quick recording.

    Once I can see the behavior from your side, I will be able to guide you more precisely on the next steps.

    Thread Starter l575

    (@l575)

    4 months, 1 week ago

    I confirm I was able to visit this page directly while logged into your WordPress admin and try the steps you shared earlier: https://steampunkbdsm.com/wp-admin/admin.php?page=connection-test-admin-page

    I’ve attached screenshots, I’m not sure why they are not visible. The site you gave me works better, now I see them, thanks.

    Please find attached screenshots:

    2026-01-04T16:09:32+00:00 Error Automattic\WooCommerce\GoogleListingsAndAds\Internal\DependencyManagement\GoogleServiceProvider::handle_unauthorized_error Client error: POST https://api.woocommerce.com/google/google-ads/v20/customers/6213209427/googleAds:search resulted in a 401 Unauthorized response: {“statusCode”:401,”error”:{“message”:”Site is not connected to Google account for google-ads”},”message”:”Site is not co (truncated…) 2026-01-04T16:09:32+00:00 Error Automattic\WooCommerce\GoogleListingsAndAds\Internal\DependencyManagement\GoogleServiceProvider::handle_unauthorized_error Client error: POST https://api.woocommerce.com/google/google-ads/v20/customers/6213209427/googleAds:search resulted in a 401 Unauthorized response: {“statusCode”:401,”error”:{“message”:”Site is not connected to Google account for google-ads”},”message”:”Site is not co (truncated…) 2026-01-04T16:09:33+00:00 Debug Automattic\WooCommerce\GoogleListingsAndAds\Ads\AdsRecommendationsService::get_recommendations Please reconnect your Google account. 2026-01-04T16:09:43+00:00 Error Automattic\WooCommerce\GoogleListingsAndAds\Internal\DependencyManagement\GoogleServiceProvider::handle_unauthorized_error Client error: POST https://api.woocommerce.com/google/google-ads/v20/customers/6213209427/googleAds:search resulted in a 401 Unauthorized response: {“statusCode”:401,”error”:{“message”:”Site is not connected to Google account for google-ads”},”message”:”Site is not co (truncated…) 2026-01-04T16:09:43+00:00 Error Automattic\WooCommerce\GoogleListingsAndAds\Internal\DependencyManagement\GoogleServiceProvider::handle_unauthorized_error Client error: POST https://api.woocommerce.com/google/google-ads/v20/customers/6213209427/googleAds:search resulted in a 401 Unauthorized response: {“statusCode”:401,”error”:{“message”:”Site is not connected to Google account for google-ads”},”message”:”Site is not co (truncated…) 2026-01-04T16:09:43+00:00 Debug Automattic\WooCommerce\GoogleListingsAndAds\Ads\AdsRecommendationsService::get_recommendations Please reconnect your Google account. 2026-01-04T16:09:52+00:00 Error Automattic\WooCommerce\GoogleListingsAndAds\Internal\DependencyManagement\GoogleServiceProvider::handle_unauthorized_error Client error: POST https://api.woocommerce.com/google/google-ads/v20/customers/6213209427/googleAds:search resulted in a 401 Unauthorized response: {“statusCode”:401,”error”:{“message”:”Site is not connected to Google account for google-ads”},”message”:”Site is not co (truncated…) 2026-01-04T16:09:52+00:00 Error Automattic\WooCommerce\GoogleListingsAndAds\Internal\DependencyManagement\GoogleServiceProvider::handle_unauthorized_error Client error: POST https://api.woocommerce.com/google/google-ads/v20/customers/6213209427/googleAds:search resulted in a 401 Unauthorized response: {“statusCode”:401,”error”:{“message”:”Site is not connected to Google account for google-ads”},”message”:”Site is not co (truncated…) 2026-01-04T16:09:52+00:00 Debug Automattic\WooCommerce\GoogleListingsAndAds\Ads\AdsRecommendationsService::get_recommendations Please reconnect your Google account. 2026-01-04T16:10:07+00:00 Error Automattic\WooCommerce\GoogleListingsAndAds\Internal\DependencyManagement\GoogleServiceProvider::handle_unauthorized_error Client error: POST https://api.woocommerce.com/google/google-ads/v20/customers/6213209427/googleAds:search resulted in a 401 Unauthorized response: {“statusCode”:401,”error”:{“message”:”Site is not connected to Google account for google-ads”},”message”:”Site is not co (truncated…) 2026-01-04T16:10:07+00:00 Error Automattic\WooCommerce\GoogleListingsAndAds\Internal\DependencyManagement\GoogleServiceProvider::handle_unauthorized_error Client error: POST https://api.woocommerce.com/google/google-ads/v20/customers/6213209427/googleAds:search resulted in a 401 Unauthorized response: {“statusCode”:401,”error”:{“message”:”Site is not connected to Google account for google-ads”},”message”:”Site is not co (truncated…) 2026-01-04T16:10:07+00:00 Debug Automattic\WooCommerce\GoogleListingsAndAds\Ads\AdsRecommendationsService::get_recommendations Please reconnect your Google account. 2026-01-04T16:12:12+00:00 Error Automattic\WooCommerce\GoogleListingsAndAds\API\Google\SiteVerification::insert { “error”: { “code”: 400, “message”: “The necessary verification token could not be found on your site.”, “errors”: [ { “message”: “The necessary verification token could not be found on your site.”, “domain”: “global”, “reason”: “badRequest” } ] } } 2026-01-04T16:13:28+00:00 Error Automattic\WooCommerce\GoogleListingsAndAds\Product\ProductSyncer::validate_merchant_center_setup Cannot sync any products before setting up Google Merchant Center.

    • This reply was modified 4 months, 1 week ago by l575.
    • This reply was modified 4 months, 1 week ago by l575.
    Sai (woo-hc)

    (@saivutukuru)

    4 months, 1 week ago

    Hi @l575,

    Thank you for confirming and for retrying the connection steps. I understand how frustrating this is, especially since your Merchant Center account itself is already verified and claimed.

    Since the connection-test flow completes but product sync still fails with the message:

    “Google Merchant Center has not been set up correctly. Please review your configuration.”

    this usually indicates the issue is not with site verification, but with how the Google for WooCommerce plugin is linked to the Merchant Center account.

    To help narrow this down, could you please check and confirm the following:

    1. Merchant Center account selection
      Go to WooCommerce → Marketing → Google → Settings and confirm:
    • The correct Merchant Center ID is selected
    • There are no additional or duplicate Merchant Center accounts listed
    1. Website URL match
      In Google Merchant Center → Business information → Website, please confirm:
    1. Product destination settings
      In Google for WooCommerce → Product feed settings, please check:
    • Product destination is set to Free listings and/or Shopping ads
    • The target country and currency match what is configured in Merchant Center
    1. Enable plugin logging
      Please enable logging so we can see the exact response coming back from Google:
    • Go to WooCommerce → Status → Logs
    • Enable logs for Google for WooCommerce
    • Try syncing products again
    • Share the latest Google-related log via Pastebin

    At this stage, site verification has already been confirmed and reconnection did not resolve the issue, so this points more toward a Merchant Center configuration or API permission issue. The logs should help us pinpoint this precisely.

    Once you share the above details, especially the logs, we’ll be able to advise on the next steps.

    Thank you for your patience.

    Thread Starter l575

    (@l575)

    4 months, 1 week ago

    Hello,

    The Google WooCommerce plagin is not connected. I can’t connect it, that is why I opened this thread.

    My Merchant account existed before I downloaded the plugin.

    The products there, in Merchant account, Google find automatically.

    The url of the site is correct there, in Merchant account.

    Also I see Google Cloud at the Merchant Account: partnerupload.google.com

    In information about feeds, I can see main feed, and extra feed.

    Main feed requires to connect Google Woocommerce plugin, and extra feed I see a feed downloaded by me in 2023. It was a main feed then.

    • This reply was modified 4 months, 1 week ago by l575.
    • This reply was modified 4 months, 1 week ago by l575.
    Plugin Support shahzeen(woo-hc)

    (@shahzeenfarooq)

    4 months ago

    Hi there!

    Thank you for sharing more details about the issue. I have internally escalated your case and am discussing it with our team. Once I receive a response from them, I will update you on the issue.

    Thank you for your understanding and cooperation.

    Plugin Support shahzeen(woo-hc)

    (@shahzeenfarooq)

    4 months ago

    Hi there!

    Thank you for your patience. To assist you further, could you please confirm whether you have contacted your hosting provider and asked them about the following?

    • Server-level caching (such as Varnish, NGINX cache, or host-specific caching)
    • CDN caching (for example, Cloudflare)
    • Also if you are using any cache plugin please deactivate that plugins and try again

    The issue you’re experiencing most commonly appears due to caching. If you haven’t contacted your hosting provider yet, please reach out to them and ask if they can clear the hosting-side cache or temporarily disable it for testing.

    You can also share the following troubleshooting guide with your hosting provider, as it will help them understand how Google attempts to verify the meta tag:
    https://woocommerce.com/document/google-for-woocommerce/faq/#troubleshooting-and-error-handling

    Let us know what they said.

    Thread Starter l575

    (@l575)

    4 months ago

    Hello,

    The provider temporarily disconnected Nginx-cache for my site.

    I’ve tried to connect Google Merchant Center, but there is the same error.

    Hosting said there are some problems with Cloudfront, in particular, they can’t reach cloudfront.net.

    Internet provider wrote that Cloudfront and Cloudflare are limited for everybody due to the Law.

    Also, I have The WooCommerce Legacy REST API has been removed from WooCommerce. I see the notice, that this will cause webhooks on this site that are configured to use the Legacy REST API to stop working. A separate WooCommerce extension is available to allow these webhooks to keep using the Legacy REST API without interruption. You can also edit these webhooks to use the current REST API version to generate the payload instead.

    Nginx-cache is inactive now. Any other tests I should do?

    • This reply was modified 4 months ago by l575.
    Sai (woo-hc)

    (@saivutukuru)

    4 months ago

    Hi @l575,

    Thank you for checking with your hosting provider and for confirming that NGINX cache has been disabled.

    The Legacy REST API notice is not related to this issue. Google for WooCommerce does not use the legacy REST API for site verification or Merchant Center setup, so that warning can be safely ignored in this context.

    Based on your latest update, the key detail is this:

    CloudFront and Cloudflare traffic is limited due to local regulations.

    Google’s site verification process requires Google’s servers to directly access your site and read the google-site-verification meta tag. This verification is performed from Google infrastructure, which relies on Google- and CloudFront-backed services.

    If traffic to or from CloudFront / Google infrastructure is restricted at the ISP or regional level, verification can fail even if:

    • The meta tag is correctly generated
    • You can see it in your browser
    • Caching and plugins are disabled

    This would explain why:

    • Verification works manually in Merchant Center
    • The plugin consistently fails with “The necessary verification token could not be found on your site”
    • Disabling caching and testing with minimal plugins/themes did not change the result

    At this point, there are no additional WordPress-level tests we can run. The remaining options are:

    • Ask your hosting provider if outbound/inbound access to Google and CloudFront verification endpoints can be temporarily allowed
    • Test the connection from a network or hosting environment where CloudFront is not restricted
    • Use a feed-based setup in Merchant Center (manual or scheduled fetch) instead of the plugin, if regional restrictions cannot be lifted

    Please let us know how you’d like to proceed, or if your host is able to allow Google/CloudFront verification traffic for testing.

    Thread Starter l575

    (@l575)

    4 months ago

    Hello,

    I can open https://aws.amazon.com/ru/cloudfront/ with no problems.

    What exactly hosting should do?

    • This reply was modified 4 months ago by l575.
    Sai (woo-hc)

    (@saivutukuru)

    4 months ago

    Hi @l575,

    Thank you for checking.

    Being able to open https://aws.amazon.com/ru/cloudfront/ in your browser only confirms general access from your local network. The verification used by Google for WooCommerce is performed by Google’s servers, not from your browser.

    What your hosting provider should specifically check is:

    1. Inbound access: Requests from Google/AWS IP ranges are not blocked, rate-limited, or challenged by firewall/WAF rules
    2. Outbound access: The server can make outbound HTTPS requests to Google APIs and Automattic/Woo endpoints
    3. Security layers: Any WAF, bot protection, or geo-blocking rules are temporarily disabled for testing
    4. Response consistency: Google’s automated request receives the normal page HTML (no alternate response, redirect, or blocked headers)

    If your host confirms that traffic from Google or AWS infrastructure cannot be allowed due to regional or legal restrictions, then the plugin will not be able to complete site verification, and a feed-based setup in Merchant Center would be the viable alternative.

    Please let us know what your hosting provider reports after checking the above.

    Thread Starter l575

    (@l575)

    4 months ago

    Hello,

    I have a question. If there would be a CloudFront / Google infrastructure issue, then why products go directly to Google from my Merchant account with no problems?

    I see SFTP info with a server partnerupload.google.com, login and password, port number and notification that info about products goes directly to Google.

    • This reply was modified 4 months ago by l575.
    Sai (woo-hc)

    (@saivutukuru)

    4 months ago

    Hi @l575,

    That’s a good question, and the key point here is that these are two completely different data flows.

    When products appear in Merchant Center via SFTP (partnerupload.google.com), your server is pushing a file directly to Google using credentials. That process does not require Google to visit your website, read page HTML, or verify ownership via a meta tag. As long as outbound SFTP/HTTPS from your server is allowed, that flow will work normally, which is why your existing products continue to sync without issues.

    The Google for WooCommerce plugin works differently. During setup, Google must actively request your website URL and read the google-site-verification meta tag from the HTML response. This request comes from Google’s infrastructure, not from your browser and not from the SFTP endpoint. If inbound requests from Google/AWS IP ranges are blocked, filtered, geo-restricted, or altered by the hosting firewall, WAF, ISP rules, or regional regulations, Google cannot see the verification token even if it exists in the page source.

    That’s why you can have:
    – A fully verified and working Merchant Center
    – Products syncing via SFTP or website crawl
    – But repeated failures when the plugin tries to complete site verification

    In short, SFTP uploads prove that outbound connections from your server work. The verification error proves that Google’s servers cannot reliably access your site in the way required by the plugin.

    What your hosting provider needs to specifically confirm is not general CloudFront access in a browser, but whether inbound requests from Google/AWS infrastructure to your site are blocked, challenged, or modified in any way, and whether any WAF, bot protection, or geo rules affect those requests.

    If your host confirms they cannot allow or test unrestricted access for Google verification requests due to legal or regional restrictions, then the Google for WooCommerce plugin will not be able to complete setup on this server. In that case, continuing with a feed-based setup in Merchant Center (SFTP or scheduled fetch) is the correct and supported alternative.

    Let us know what your hosting provider reports after checking this, and we can advise on the best path forward.

    Thread Starter l575

    (@l575)

    3 months, 4 weeks ago

    Hello,

    Hosting ask particular IP-addresses of Google/AWS, Google APIs and Automattic/Woo they should check.

Viewing 15 replies - 16 through 30 (of 33 total)
1 2 3

You must be logged in to reply to this topic.