<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Edvinas Ivanauskas</title>
    <description>The latest articles on DEV Community by Edvinas Ivanauskas (@storeverifier).</description>
    <link>https://dev.to/storeverifier</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4151469%2Fd3d5cd94-828c-4702-b1b4-7f2012b838d5.png</url>
      <title>DEV Community: Edvinas Ivanauskas</title>
      <link>https://dev.to/storeverifier</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/storeverifier"/>
    <language>en</language>
    <item>
      <title>How to fix a Google Merchant Center misrepresentation suspension, step by step</title>
      <dc:creator>Edvinas Ivanauskas</dc:creator>
      <pubDate>Wed, 30 Sep 2026 05:58:14 +0000</pubDate>
      <link>https://dev.to/storeverifier/how-to-fix-a-google-merchant-center-misrepresentation-suspension-step-by-step-2j2j</link>
      <guid>https://dev.to/storeverifier/how-to-fix-a-google-merchant-center-misrepresentation-suspension-step-by-step-2j2j</guid>
      <description>&lt;p&gt;A misrepresentation suspension usually arrives with a vague notice and no list of pages to change. The good news: most of the causes are on your own site, and you can find and fix them yourself. This is the order I would work in, based on the patterns that show up across more than 900 store scans.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 1: Read what Merchant Center actually says
&lt;/h2&gt;

&lt;p&gt;Open the issue details in Merchant Center first. Note the policy named and any example given. Everything below is a check on your store, but this tells you where to look hardest.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 2: Make your policy pages agree with each other
&lt;/h2&gt;

&lt;p&gt;This is the most common fix. Compare the returns window, refund timing, shipping times and shipping cost across the product page, cart, checkout, footer and policy pages. A product page saying "free returns within 30 days" while the returns page says 14 reads as a promise the store will not keep. Pick the true answer and put it everywhere, and say when the return window starts.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 3: Make prices match from product page to checkout
&lt;/h2&gt;

&lt;p&gt;Add the same item to the cart and follow it to the last step. The price, tax and shipping should not move without explanation. If you show a compare-at price, there must be a real previous price behind it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 4: Remove urgency that is not real
&lt;/h2&gt;

&lt;p&gt;A countdown timer that restarts on every reload, or "only 3 left" on an item that is always in stock, is exactly what a reviewer notices. Tie any timer to a real end date or remove it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 5: Show who is behind the store
&lt;/h2&gt;

&lt;p&gt;The legal or trading name, a real contact route and a phone number people can find should be on the site, and they should match the details in your Merchant Center account. A mismatch between the two is a frequent cause of a suspension that seems to make no sense.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 6: Make sure a reviewer can actually load everything
&lt;/h2&gt;

&lt;p&gt;Check that a bot challenge is not blocking Googlebot, that robots.txt is not hiding your policy pages, and that no coming-soon or password page is still up. If a reviewer cannot open a page, they cannot verify it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 7: Keep a dated record, then request the review once
&lt;/h2&gt;

&lt;p&gt;Write down every change with the date. Google's review page recommends a comprehensive audit before requesting a review and warns that if issues are not resolved by the second attempt, a one-week cool-down may begin. So do the audit first and request the review only after the work is done.&lt;/p&gt;

&lt;h2&gt;
  
  
  Do it faster with a scan
&lt;/h2&gt;

&lt;p&gt;If you want a quick read of your own store, I built a free checker that reads the public pages the way a shopper's browser does and shows what it found: &lt;a href="https://storeverifier.com/" rel="noopener noreferrer"&gt;StoreVerifier&lt;/a&gt;. The free scan needs no account and no Merchant Center access, and it cannot tell you what Google will decide, only what it found on your store.&lt;/p&gt;

&lt;p&gt;Prefer to do it by hand? The rules are written down for free in the &lt;a href="https://storeverifier.com/library" rel="noopener noreferrer"&gt;Compliance Library&lt;/a&gt;, one rule per guide.&lt;/p&gt;

</description>
      <category>ecommerce</category>
      <category>seo</category>
      <category>shopify</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
