Workspace Sign in

Evidence capture guide

Qurifix Capture

Load the Chrome developer beta for product-page evidence.

Use the Chrome extension when a marketplace, DTC page, or product detail page needs richer evidence than a URL alone can provide. This page is the setup and safety guide for the plugin; it explains what Capture collects, what it blocks, and how a reviewed evidence draft can be sent into Qurifix.

Load unpacked developer beta Review safety rules
Public PDPs Marketplace and storefront pages only Evidence draft Review before sending to Qurifix No publishing Repair assets stay in your workflow
01

Install in Chrome

  1. Open chrome://extensions.
  2. Turn on Developer mode.
  3. Click Load unpacked.
  4. Select the project folder chrome-extension.
02

Capture a public product page

  1. Open a public product detail page, marketplace listing, or storefront PDP.
  2. Click the Qurifix Capture extension.
  3. Choose Capture product page.
  4. Review the draft evidence preview before sending.
03

Send evidence to Qurifix

  1. Click Send to Qurifix.
  2. The audit form opens with captured evidence prefilled.
  3. Add platform, market, competitor, and concern.
  4. Use the reviewed evidence in the Quick Audit form, Fix Packs, or retesting.

Safety boundary

Capture public product evidence only.

Do not capture admin pages, checkout flows, account pages, order pages, customer records, billing pages, private seller-center screens, or any page that shows credentials or personal data. Qurifix Capture does not directly publish to Shopify, Amazon, TikTok Shop, or seller centers; it creates a reviewed evidence draft for your normal audit and repair workflow.

Read privacy policy Developer docs

When it helps

Use Capture when the URL alone is not enough.

Marketplace pages

Use it when Amazon, TikTok Shop, Walmart, or other marketplace pages block server-side evidence fetching.

Evidence-heavy SKUs

Use it when specs, FAQ, reviews, variants, policy proof, or page copy are critical to the recommendation case.

Before retesting

Use it after publishing repairs so the retest compares current page evidence against the saved baseline.

Platform guidance

Capture evidence differently by selling surface.

Shopify

Capture the public PDP, visible product image, variant/spec modules, FAQ, reviews, structured data, shipping, and returns proof. Publish repairs through your Shopify theme, metafields, feed, or app workflow.

Amazon

Capture the public listing, bullets, A+ content, Q&A, review themes, price, availability, and screenshots. Use Qurifix output as seller-reviewed copy guidance, not as direct Seller Central automation.

TikTok Shop

Capture the public product page, creator-facing claims, offer details, visible reviews, and screenshot context. Map repairs to product attributes, listing copy, FAQ, and compliant creator briefs.

Custom storefront

Capture the public custom-domain storefront, Product schema, Offer availability, specs, FAQ, comparison language, and full-page screenshot metadata before editing the CMS or feed.

Capture quality

Review captured evidence and anything still needed before sending.

Strong capture

Core product facts, offer evidence, schema or page proof, and screenshot context were found. Review the preview before sending.

Review before send

Some useful surfaces were found, but Capture will label missing evidence so the audit can be completed with manual proof.

Needs manual evidence

Important surfaces such as FAQ, reviews, policy proof, comparison, creator proof, or schema need manual evidence before retesting.