Browse Guides
Move to another guide without going back to the documentation hub.
Use the Right Merchant Setting for the Right Task
Use this page when you know the outcome you want but need to confirm which setting controls it. It saves time before you change automation, moderation, SEO, notifications, or billing.
How to Use This Reference
Open the Exact Section First
Each card points to a specific settings area so users can stop guessing where a feature lives.
Verify the Right Save Point
The notes below focus on what to check before and after saving, which is usually where merchants get stuck when something looks unchanged.
Review Requests
Use this section to manage how review request automation runs after a purchase.
- Adjust request timing, reminders, and follow-up behavior.
- Check automation status when request delivery does not behave as expected.
Review Controls
Use this section to manage review moderation and submission defaults.
- Set approval and moderation behavior for incoming reviews.
- Review submission requirements such as verification and media uploads.
Q&A Controls
Use this section to manage how customer questions are collected and published.
- Control question form availability and response visibility.
- Review collection and publishing settings for Q&A activity.
SEO Rich Snippets
Use this section when you want search engines to read structured product data from the storefront HTML rather than a visible review widget. The SEO path is JSON-LD only, while the widget path is the visible review block.
- What it is: a direct HTML-rendered JSON-LD script tag (<script type="application/ld+json">) that provides structured product and review data to search engines.
- Google Crawlability: while visual widgets use JavaScript and iframes for UI styling, the SEO JSON-LD snippet is rendered in page HTML, allowing Googlebot to crawl and index reviews directly without relying on iframe execution.
- Google Schema Compliance: 100% compliant with Google Search Central guidelines. AggregateRating and Review schemas are wrapped in a top-level @type: 'Product', with Person author attributes, ISO 8601 dates, SKU, Brand, and Offer metadata.
- Minimum Review Rule: AggregateRating is generated only when at least 1 approved review exists, preventing Google Search Console schema warnings.
- Where to paste it: place the JSON-LD in the server-rendered product template or theme head/body file that owns the live product URL.
- How to verify: test your live product URL in Google Rich Results Test (https://search.google.com/test/rich-results) to validate green checkmarks.
- Common mistake: do not expect JSON-LD to render a visible box on the storefront; if you want customer-facing review widgets, use the widget embed path instead.
<!-- Paste this in the server-rendered page head or body -->
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Product",
"name": "{{PRODUCT_NAME}}",
"sku": "{{SKU}}",
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": "{{AVERAGE_RATING}}",
"reviewCount": "{{REVIEW_COUNT}}"
}
}
</script>Notifications
Use this section to manage who gets notified about review and Q&A activity.
- Choose the channels your team should use for alerts.
- Keep notifications aligned with your moderation and response workflow.
Billing and Plan
Use Billing and Plan to review subscription access, usage, and commercial details.
- Check available features and current usage limits.
- Review subscription status, invoices, and payment details.
Need the next practical step?
Open the section that matches the behavior you want to change, confirm the save action, then re-check the related preview, queue, or report before moving on.
Was this helpful?