Meet Lissa V2: Pulserig's Google Merchant Center Compliance Scanner Built From Real Suspension Audits

Most Shopify and ecommerce store owners find out about Google Merchant Center problems the same way: their ads stop running, their products disappear from Google Shopping, or they receive a suspension notice with little explanation of what triggered it.

By that point, the damage is already done. Revenue stops. Appeals take days or weeks. And the specific issue that caused the suspension is rarely spelled out in plain language.

Pulserig built Lissa V2 to change that. Lissa is Pulserig's GMC compliance scanner — a real browser-based tool that scans live ecommerce storefronts for the policy, technical, product data, trust, feed and Shopify-specific risk signals that are often missed until it is too late.

This guide explains what Lissa V2 checks, why those checks matter for Merchant Center, and how store owners — whether already suspended or actively advertising — can use it to identify risk signals before they escalate.

Why do Google Merchant Center accounts get suspended?

Google Merchant Center suspensions are more common than many store owners realise — and the misrepresentation category alone accounts for a large proportion of account-level suspensions across Shopify stores.

The misrepresentation policy is a broad one. It covers situations where Google's systems detect signals that the business, its products, or its website may not represent what they claim to be. That can include:

• Missing or inconsistent business identity information (trading name, address, registration number)
• Product prices that differ between the website and the product feed
• Policy pages that are absent, inaccessible or contain contradictory wording
• Trust signals that do not hold up under automated scrutiny
• Structured data that does not match visible page content
• Shopify theme rendering issues that affect what Google's crawlers actually see

The difficulty is that Google rarely tells you which specific signal triggered the suspension. You receive a policy category — misrepresentation, policy violation, item disapproval — but not a precise list of what to fix. That gap is what Lissa is designed to help close.

"Lissa uses real browser-based crawling and crawler-style tests to inspect live storefront output, rendered content, raw HTML, product data, policy pages and structured data. This helps Pulserig identify risk signals that may not be visible from a normal homepage review."

What is the Pulserig GMC Compliance Scanner (Lissa V2)?

Lissa is Pulserig's evolving AI-assisted GMC compliance scanner. It was built from the ground up using real Pulserig Merchant Center audit and suspension-repair case experience — not from a generic list of SEO rules.

The V2 update expands Lissa's scanning to 14 specialist modules covering more than 60 compliance check rules, with the system continuing to evolve as new suspension patterns emerge.

Unlike basic website checkers or plugin-based tools, Lissa launches a real browser, visits your live storefront, and inspects what is actually rendered — including JavaScript-rendered content, product page output, policy page availability, structured data, schema markup, feed signals and Shopify-specific template behaviour.

After a scan, merchants receive:

• A compliance score out of 100
• A categorised report of risk signals identified, rated as Critical, Warning or Informational
• Plain-language explanations of what was found and why it may matter for Merchant Center
• Guidance on areas that may need manual review or repair

Every Lissa report includes a clear disclaimer: the scanner identifies potential risk signals. It does not make final determinations about whether a store will be approved, disapproved or suspended. Final Merchant Center decisions remain with Google. Serious issues may require Pulserig's manual review and repair services.

What does Lissa V2 scan? The 14-module breakdown

Lissa V2 organises its checks across 14 specialist scanning modules. Each module targets a specific area of Google Merchant Center compliance risk.

Shopify theme bugs and Google Merchant Center — a hidden risk most merchants miss

One of the most frequently overlooked sources of Merchant Center risk signals is not in your product feed or your business settings — it is in how your Shopify theme renders your storefront to a crawler that does not behave like a logged-in shopper.

Shopify themes are built for human browsers, with JavaScript loading large portions of page content dynamically. Google's crawlers — and Lissa's browser-based scanner — access your storefront differently. What they see is not always what your customer sees.

Common Shopify-specific GMC risk signals that Lissa's theme bug module looks for include:

• Broken Liquid template output — strings like {{amount}} or translation missing: en.products.product.price appearing in rendered page HTML instead of actual price values
• Price range display on product pages — themes showing "From £12.99" or a price range rather than a single specific price, which can create a price mismatch between the storefront and the feed
• Deferred purchase or backorder messaging — buttons or copy that suggest the product is not available for immediate purchase, even when the feed says "in stock"
• Local pickup or collection components — storefront UI elements designed for local retail pickup appearing on stores that are supposed to be purely online retailers
• "Add to cart" contradictions — pages where a product appears sold out in one section but shows "Add to cart" elsewhere, creating contradictory availability signals
• Review schema without visible reviews — structured data claiming review ratings with no matching customer reviews actually visible on the page
• Policy contradictions or placeholder content — policy pages that contain conflicting timeframes, template placeholder text, or copied boilerplate that contradicts the rest of the site

None of these issues are visible during a standard manual site review. They surface only when you inspect the rendered HTML and structured data in the same way a crawler would.

Why price visibility matters more than you think

Price accuracy is one of the highest-priority data points in Google Merchant Center compliance. When the price Google's systems read from your storefront does not match the price in your product feed, the result is typically item-level disapproval — and in patterns of repeated mismatch, it can contribute to account-level flags.

There are two Lissa checks that specifically target this risk area:

1. Prices May Not Be Visible Without JavaScript

Many Shopify themes load product prices via JavaScript after initial page render. If the price is not present in the initial HTML that a non-JavaScript crawler reads, Google may not be able to confirm the correct price — creating a mismatch risk between the crawled storefront price and the feed price.

2. Structured Data Price vs. Visible Product Price

If your Product schema markup declares a different price than what is visible to the user on the product page — even by a small amount due to currency formatting, rounding, or sale logic — this creates a schema-to-page contradiction. Google's structured data quality guidelines flag this type of inconsistency directly.

Both of these issues are caught by Lissa's browser-based scan. Neither would show up in a standard SEO site audit tool, because those tools typically do not simulate crawler-level price reading against visible product page content.

Klarna, BNPL and Google Shopping — what the scanner checks

Buy Now Pay Later services like Klarna have become standard on many Shopify stores. The integration is usually straightforward from a customer experience perspective — but the On-Site Messaging (OSM) widgets that Klarna provides can create a specific GMC risk signal that catches many merchants off guard.

Klarna's OSM widget is designed to appear near the product price. Its purpose is to show shoppers the instalment payment option — for example, "3 easy payments of £16.99" — to encourage conversion.

From a shopper's perspective this is helpful. From Google's crawler perspective, an instalment price displayed alongside or near a product price can be read as the actual product price — which is lower than the full price in the feed. This creates a price mismatch signal.

Lissa's Klarna / BNPL module specifically checks for:

• Klarna On-Site Messaging widget presence near product prices
• Other BNPL provider messaging widgets (Clearpay, Laybuy, Paidy and similar)
• Situations where the combination of BNPL messaging and JS-rendered prices creates compound price visibility risk

If Lissa flags a BNPL-related risk signal, it does not necessarily mean your Merchant Center will be suspended. It means this is an area worth reviewing carefully — particularly if you are also seeing price-related item disapprovals.

What should you check before appealing a Merchant Center suspension?

Submitting a Merchant Center appeal before you have identified and addressed the likely root cause risks two outcomes: the appeal is rejected, or the cooldown period resets — costing you additional days or weeks.

Before submitting any appeal, Pulserig recommends running a full Lissa scan and reviewing findings in these priority areas:

1. Misrepresentation signals — Is your business name, address, phone number, email and company registration visible and consistent across your storefront and your Merchant Center business information?
2. Policy page accessibility — Are all required policy pages (privacy, returns, terms, shipping) accessible without login, and do they contain specific and consistent information?
3. Price visibility — Are product prices visible in plain HTML — not just rendered via JavaScript? Does your structured data price match the visible page price?
4. Shopify theme output — Are there any broken Liquid strings, contradictory availability signals, or BNPL widget interference visible in your rendered product pages?
5. Feed quality signals — Do all products have product_type, brand / vendor, and GTIN fields populated where applicable?
6. Trust signals — Does your storefront have clear contact information, an About Us page, and verifiable social links?

If Lissa's report shows Critical findings in any of these areas, those should be addressed before submitting an appeal. If you are unsure how to resolve a specific finding, or if findings point to deeper technical or policy issues, Pulserig's manual audit and repair services can review your store and Merchant Center account directly.

Can active Google Ads accounts use the scanner to avoid problems?

Yes — and this is increasingly the more important use case for Lissa.

The merchants who benefit most from ongoing compliance monitoring are not the ones who are already suspended. They are the ones who are currently advertising, currently generating revenue through Google Shopping, and who want to keep it that way.

Google's systems scan live storefronts continuously. A theme update, a new Shopify app, a Klarna widget configuration change, or a product description that triggers a policy flag can all create problems that are invisible until ads stop running.

Lissa's monitoring subscription gives active advertisers a way to stay ahead of these risks:

• Daily automated scans of your store at 08:00 UK time
• Compliance score tracking so you can see if your score is trending in the wrong direction
• Scan history dashboard to review what has changed between scans
• Email alerts when new risk signals are detected
• Support guidance on how to interpret and prioritise findings

Subscribers get ongoing monitoring, dashboard reports, email alerts, risk history and support guidance. If manual repair work is identified as necessary, Pulserig can offer Essential Fix or Full Rescue support separately, with subscriber discounts available.

Monitoring does not guarantee that your account will never face a disapproval or suspension — final Merchant Center decisions remain with Google. But it gives you significantly earlier visibility into potential risk signals than discovering them after the fact.

Frequently Asked Questions