Sample report
What a useful finding looks like.
This example uses synthetic store data to demonstrate the investigation and correction process. It is not a client case study or a reinstatement result.
Illustrative example · synthetic store data
Example finding: conflicting dispatch information
- Evidence
- The product page promises dispatch within two business days. The shipping policy states dispatch within five business days.
- Why it needs review
- The storefront gives customers two different expectations for the same process.
- Confirmed fact
- For this example, the merchant confirms dispatch within five business days.
- Proposed correction
- Update the product-page dispatch statement to match the confirmed process. Leave the product's other content and design unchanged.
- Approval
- Publication waits for the authorized merchant representative to approve the proposed version.
- Verification
- Check both live sources after publication and record whether the inconsistency has been resolved.
- Review boundary
- This correction addresses the demonstrated inconsistency. It does not establish the reason for a Google restriction or predict the review outcome.
Preliminary check output for the same synthetic store
https://aster-shop.example
5 of 6 requested pages read; 1 not checked.
- Medium
A potential inconsistency was found in sampled delivery information.
- Low
One sampled product page is missing an observed offer currency.
- Public sample only; Merchant Center account issues and review history were not available.
- The scan does not determine the reason for a suspension or guarantee recovery.
- No full page text, exact sensitive findings, account details, or reusable access tokens are disclosed in this preview.