Agency self-serve kit · Current Store release

Standardize a client-safe product-page preflight.

Give operators one bounded workflow for checking a selected Shopify or WooCommerce variant, documenting supported differences, and verifying a repair—without sending client product or feed data to MMP.

Free to install. No bespoke pilot, account integration, or cloud workspace is required.

Reusable operating workflow

One sequence for each store or client.

This is a preflight and evidence workflow. It does not replace Merchant Center diagnostics or guarantee approval.

01

Verify once

Install the current Store release and reproduce R02 and R09 on the fictional fixture before opening a client page.

02

Select one variant

Keep the visible page, structured Offer, and optional feed row tied to the same SKU, GTIN, ID, or selected variant.

03

Scan locally

Run the comparison in the active tab. No Merchant Center authentication, catalog crawl, or remote product upload is used.

04

Export the report

Copy or export only the local report you choose to use. Review it before placing it in a client record.

05

Correct the source

Change the authoritative page, structured-data, or feed value outside MMP using the client's normal workflow.

06

Rescan and retain

Run a repair scan on the same variant and retain only the evidence your client authorizes.

Kit resources

Everything needed for a clean first operator handoff.

Start with fictional evidence. Move to a live product page only when the operator is authorized to inspect and retain it.

Optional agency attribution

Use one coarse cohort profile across the agency kit.

Operators who voluntarily enable measurement can use the values below. This groups pseudonymous activity without transmitting an agency name, client name, domain, page, product, or feed value.

Role
Agency or Consultant
Business context
Ecommerce agency
Operating scope
Multiple clients or stores
Acquisition source
Agency
Partner cohort code
MMP-AGENCY-KIT

Self-reported telemetry is not named agency proof. Any attributable case note or agency record requires separate authorization and must exclude confidential client material.

Client-data boundary

Keep the workflow useful without widening data exposure.

Product and feed contents remain local. The operator controls every report copy, export, retention, and deletion action.

Use

Authorized current product pages, redacted one-row feed inputs, and reviewed local reports.

Do not send

Credentials, Merchant Center exports, customer personal data, private catalog files, or unrelated feed rows.

Delete locally

History is capped and time-bounded; operators can export first, then clear all local data.

Authorized evidence return

Completed a real-store fix and clean rescan?

Return a redacted repair note only when the operator or client has authorized the information being shared.

Send a redacted repair record.

Include the date, MMP version, authorized page or platform, selected-variant context, mismatch before correction, correction made, and the clean same-variant rescan result. Redact a domain or identifier when authorization does not cover it.

Email the redacted evidence note

Keep proof and activity separate.

The fictional fixture, anonymous telemetry, Store impressions, page views, installs, clicks, and unverified claims are not repair evidence. Naming an agency or quoting its result requires separate explicit authorization.

Do not include credentials, complete feeds, Merchant Center exports, customer personal data, or confidential client material.