HTTPS Requirement for Google Shopping: Full Guide
Google requires HTTPS on every page of your site, not just checkout. Here's how to verify and fix SSL issues.
One missing policy page can suspend your account.
FeedShield catches issues like this automatically. Run a free audit before it costs you.
Google's HTTPS Requirement
Google Merchant Center requires that your entire website is served over HTTPS — not just the checkout page. This includes product pages, category pages, blog posts, and every other page on your domain.
An active SSL certificate is a baseline requirement. Without it, products will be disapproved and the account may be suspended.
Checking Your SSL Status
Open your website in a browser. Look for the padlock icon in the address bar. If you see a warning ("Not Secure") on any page — including pages you wouldn't think are sensitive — your HTTPS setup has issues.
Common HTTPS problems:
- •Mixed content: Page loads over HTTPS but references some resources (images, scripts, CSS) via HTTP. The page shows as "Not Secure" even though the main document is HTTPS.
- •SSL expired: Certificate is installed but expired. Browser shows a full warning screen.
- •Partial HTTPS: Some pages redirect to HTTPS but others still load on HTTP.
- •Checkout bypasses HTTPS: Checkout was set up on a subdomain or third-party platform without SSL.
Fixing Mixed Content
Mixed content is the most common HTTPS issue on established sites. Resources loaded over HTTP break the secure connection.
Find mixed content: Open Chrome DevTools (F12) > Console tab. Look for warnings that say "Mixed Content."
Fix: Update all hardcoded HTTP URLs in your theme, page builder, and database to HTTPS. For WordPress: use a plugin like Better Search Replace to update all HTTP references in the database.
After Fixing
- •Test every page type (home, category, product, cart, checkout, confirmation)
- •Verify padlock shows on all pages
- •In GMC, request a re-crawl of your website URL under Settings > Business Information