When Google says your website needs improvement.

“Website needs improvement” is Google’s catch-all label for technical issues that prevent their crawler (AdsBot-Google or Storebot-Google) from properly indexing your storefront. Unlike misrepresentation, which is editorial, this suspension is almost entirely technical - and that makes it the fastest to fix.

What Google actually checked

The reviewer’s automated pipeline runs against your storefront and your feed URLs. Common failures:

1. Feed landing pages return 4xx, 5xx, or redirect chains

The most frequent cause. Your feed lists https://example.com/products/widget-12 but the URL returns 404, 410, 5xx, or redirects more than once before resolving.

Fix:

• Export your feed product URLs
• Run them through curl -I -L and check final status code + redirect count
• For products that 404: re-publish them or remove from the feed
• For redirect chains >1 hop: collapse them (Shopify often inserts /products/ slug redirects after handle changes)

2. SSL handshake failure or mixed content

Storefront serves on HTTPS but loads images, scripts, or fonts from http://. Google’s crawler treats mixed-content pages as unverified.

Fix:

• Run Lighthouse mobile against your homepage + 3 sample PDPs
• Look for “mixed content” warnings in the Issues tab
• Update theme CSS / JS imports to use https:// everywhere
• Verify HSTS header is set: Strict-Transport-Security: max-age=31536000; includeSubDomains

3. Schema.org Product markup invalid or absent

Google’s crawler expects valid Product schema on every PDP - name, image, description, offers (price + currency + availability). Invalid JSON-LD fails the review.

Fix:

• Test 3 PDPs in Google’s Rich Results Test
• Resolve every “Error” (warnings are usually OK)
• If your theme’s product.liquid doesn’t emit Product schema, install a structured-data app or update the template

4. robots.txt blocks AdsBot

Some merchants accidentally Disallow: / for everything except Googlebot, forgetting that AdsBot-Google is a separate crawler.

Fix:

• Visit yourdomain.com/robots.txt
• Ensure these are explicitly allowed:
  • User-agent: AdsBot-Google → Allow: /
  • User-agent: Storebot-Google → Allow: /
• Or simply User-agent: * → Allow: / (subject to your other SEO requirements)

5. Lighthouse mobile score below 70

Some reviewers manually check Lighthouse on a sample PDP. Stores with mobile scores under 50 get flagged for poor user experience as a contributing factor.

Fix:

• LCP under 2.5s on PDPs (compress hero images, remove unused JS)
• CLS under 0.1 (set explicit width/height on product images)
• TBT under 200ms (defer or remove non-critical Shopify apps)

The reinstatement playbook

Because this suspension is technical, the cycle is faster than misrepresentation:

1. Run all 5 checks above (our Prevention scanner does this in 60 seconds across 45 rules)
2. Fix every flagged issue
3. Re-test with Google’s Rich Results Test + Lighthouse + curl on feed URLs
4. Wait 24 hours for Google’s crawler to re-evaluate
5. Confirm positive re-evaluation signal via productstatuses delta
6. Request review

Most “website needs improvement” suspensions reinstate on the first attempt when all technical issues are genuinely resolved. The 6% that don’t usually have a missed mixed-content reference or a CDN that’s returning 4xx for AdsBot’s User-Agent specifically.

---

Try the free Prevention scan - it walks the full 45-rule technical pipeline (SSL, schema, robots.txt, Lighthouse, landing page validation) and surfaces every gap in under a minute.