Google Merchant Center Suspension Scanner: Meet Pulserig Lissa V2

Lissa is Pulserig’s automated ecommerce compliance scanner for Shopify and other public storefronts. It is designed to find technical, policy, product-data and trust inconsistencies that deserve investigation before a Google Merchant Center review or as part of routine store maintenance.

The important word is investigation. Lissa does not know why Google has suspended an account, it cannot predict whether Google will approve a store, and a scanner warning is not automatically a policy violation. It gives merchants and Pulserig a faster way to locate areas worth checking manually.

You can run a Lissa storefront scan here. If your Merchant Center account is already suspended, you can also request a free human + Lissa audit.

What is a Google Merchant Center compliance scanner?

A compliance scanner is not a replacement for Merchant Center Diagnostics or Google’s own review process. Its job is to inspect information that is publicly available on a store and highlight patterns that may be inaccurate, incomplete, contradictory or technically broken.

That is useful because ecommerce information is spread across many layers. A merchant may have one price in Shopify, another value in structured data, different shipping wording in a policy, and a product feed that has not refreshed yet. The storefront can still look visually polished while those inconsistencies remain underneath.

Lissa is built around that wider view. Depending on what the public storefront exposes, checks can cover areas such as:

• business and contact information;
• shipping, returns and other policy pages;
• product price and availability signals;
• product identifiers and feed-related data;
• structured Product and Offer data;
• broken or inaccessible links;
• checkout-transparency signals visible before payment;
• Shopify purchase-option wording;
• pickup, preorder or deferred-purchase indicators;
• compare-at and sale-price presentation;
• placeholder or stale theme output;
• mobile and storefront usability indicators; and
• other public trust and technical signals.

The scanner is deliberately broader than a normal SEO crawler because Merchant Center problems are not purely SEO problems. Product data, customer policies, checkout expectations and business transparency all matter to the ecommerce journey.

What Lissa can tell you — and what it cannot

Lissa can tell you that a public page contains something worth checking. For example, it may identify conflicting price-like values, missing contact information, a policy link that does not resolve, or recurring-purchase wording on a product page.

It cannot tell you, by itself, that Google used that exact signal to make an enforcement decision.

That distinction matters because automated checks can produce false positives. A Shopify theme may contain code supporting subscriptions even when no live product uses a subscription. A page may contain multiple price values because it displays several legitimate variants. A contact detail may be present in a format the scanner did not initially recognise.

For that reason, a useful workflow is:

1. run the automated scan;
2. review the highest-priority findings;
3. confirm each finding against the live customer journey;
4. check Shopify, the product feed or Merchant Center where appropriate;
5. fix genuine inconsistencies at their source; and
6. retest after the changes are live.

That is also why Pulserig describes its main audit as a human + Lissa audit. Automation speeds up discovery; human review provides context.

How Lissa fits into a Merchant Center suspension investigation

If Google Merchant Center is already suspended, the scanner should be treated as one evidence source within a wider audit.

Start with the policy issue shown in Merchant Center. If the notice is Misrepresentation, our main Google Merchant Center Misrepresentation guide explains the wider checks around business identity, shipping, returns, product data, checkout and review preparation.

For a broader account suspension, use our Google Merchant Center suspension recovery guide.

Lissa can then help surface technical and storefront inconsistencies that are easy to miss during a quick visual inspection. Examples might include a broken policy URL, an unexpected purchase option, conflicting product structured data or a product page whose availability is unclear.

The correct response is not to fix every warning blindly. Confirm whether the finding is real and whether it materially changes what a customer or machine-readable product record communicates.

Business identity and contact checks

A customer should be able to understand who they are buying from and how to get help. Lissa can inspect public pages for common business and contact signals, but it cannot verify every legal relationship or determine whether an address is appropriate for a particular business.

A manual check should compare:

• trading and legal business names where relevant;
• customer-service email;
• telephone details where offered;
• company information where applicable;
• contact and About pages;
• footer information; and
• the information configured in Merchant Center.

For UK ecommerce stores, see our Shopify Contact Page Requirements guide.

Policy-page consistency checks

Having a shipping or refund policy is only useful if it describes the real service. A scanner can identify missing pages, broken links and some conflicting phrases, but a human still needs to judge whether the policy accurately reflects fulfilment and customer support.

Compare the policy wording against:

• Shopify shipping settings;
• checkout delivery options;
• Merchant Center shipping configuration;
• product-specific delivery statements;
• returns information; and
• the customer process your business actually follows.

Useful supporting guides include Shopify Shipping Policy Requirements and Shopify Policy Pages for Google.

Price and availability checks

Price and availability are ideal examples of why automation needs context. A scanner may see several price values on one page because a product has variants, compare-at pricing or structured data. The job is to determine which value represents the offer submitted to Google.

For an affected product, compare:

1. the submitted Merchant Center item;
2. the exact landing page and variant;
3. Product/Offer structured data;
4. cart; and
5. checkout.

If those values disagree, correct the underlying Shopify, feed, market, app or theme configuration rather than trying to hide the symptom.

See How to Fix Google Price Mismatch for a deeper walkthrough.

Shopify subscriptions, preorders and deferred purchases

One area where older automated tools can easily over-report risk is subscription and deferred-purchase code.

Shopify legitimately supports subscriptions, preorders and other purchase options. Themes can also contain support code for those features even when they are not active. Finding the words “recurring” or “deferred purchase” in source code is therefore not enough to call a product non-compliant.

The proper check asks three questions:

1. Is there support code?
2. Is a selling plan or purchase option actually attached?
3. Does it change the customer’s price, payment schedule, consent or fulfilment?

Our updated Shopify recurring and deferred purchase guide explains that distinction in detail.

Theme code and structured data checks

Shopify themes and apps can output machine-readable information that is not immediately obvious from the visual page. That does not make hidden code a violation. It becomes relevant when it produces inaccurate or conflicting information about the live offer.

Examples worth investigating include:

• structured data showing the wrong variant price;
• availability not updating with inventory;
• two Product schema sources giving different values;
• old app output still changing a live page;
• pickup or purchase-option information that affects checkout unexpectedly; or
• broken placeholder values appearing in rendered content.

Our Shopify Theme Bugs and Merchant Center Mismatches article separates meaningful live-store issues from harmless theme support code.

Product-feed and identifier checks

Lissa can help identify public product-data patterns, but it cannot see every value inside a private Merchant Center account without authorised access. A proper feed review still needs the submitted data.

For representative products, check:

• title and description;
• price and sale price;
• availability;
• brand;
• GTIN and MPN where applicable;
• variant and item-group relationships;
• image URLs;
• shipping information; and
• the exact landing URL.

Use our Google Feed Audit and Product GTIN Requirements guides for the manual checks behind those signals.

Can Lissa prevent a Google Merchant Center suspension?

No scanner can promise that.

What Lissa can do is give merchants earlier visibility into public inconsistencies that might otherwise remain unnoticed until a customer, advertising platform or internal team finds them. That makes it useful after theme changes, app installations, catalogue imports, pricing changes and policy updates.

Ongoing monitoring can also make it easier to notice when a storefront changes unexpectedly. The current monitoring options and features are shown inside the Lissa app rather than hard-coded into this article, because the service continues to evolve.

Google retains final authority over product eligibility, account reviews and suspensions.

When should you use a human audit instead?

A human review is especially useful when:

• Merchant Center is already suspended;
• the policy reason is broad;
• previous reviews have failed;
• the scanner finding depends on business context;
• multiple feed apps or markets are involved;
• checkout behaves differently by product or location;
• branded or restricted products need judgement; or
• the automated result appears to be a false positive.

Pulserig’s free initial audit combines automated evidence with a human review of the store and current situation before paid compliance work is recommended.

Request a free human + Lissa audit.

Lissa FAQ

Is Lissa an official Google tool?

No. Lissa is an independent Pulserig ecommerce compliance scanner. It is not owned, endorsed or operated by Google.

Does a Lissa warning mean Google has found a violation?

No. A warning is a potential risk or inconsistency to investigate. It needs to be confirmed against the live store, underlying configuration and, where relevant, Merchant Center.

Can Lissa tell me exactly why my Merchant Center account was suspended?

No. Google controls the enforcement decision and may not provide one exact root cause. Lissa can help identify areas that deserve examination as part of a wider audit.

Does Lissa only work for suspended stores?

No. It can also be used as a routine storefront check before Merchant Center setup or after meaningful Shopify changes.

Does Lissa replace Search Console or Merchant Center Diagnostics?

No. Those Google tools remain important. Lissa adds a separate storefront-focused layer and can help connect technical, product and policy signals that sit across different parts of an ecommerce site.

Can Pulserig guarantee reinstatement after a scan or audit?

No. Pulserig can identify and repair issues it can verify and help prepare the store or account for review. Google retains the final decision.

Run a Lissa scan

If you want to inspect your public storefront for technical, policy, product-data and trust inconsistencies, run a Lissa scan.

If your Google Merchant Center is already suspended or the automated findings need interpretation, request a free Pulserig human + Lissa audit.

Pulserig is independent of Google and Microsoft. Automated findings are indicators for review, not platform decisions or guarantees of approval.