Retail operations · Technical SEO · Data QA

Six checks to run before and after an ecommerce storefront migration.

A new storefront can look identical while its machine-readable product details change. Use this workflow to separate catalog metadata quality, price extraction, international SEO, accessibility and competitor price monitoring rather than trying to use one tool for all six jobs.

Start with free, browser-only checks where possible. The optional Apify Actors linked below handle specific public-data tasks and may charge when you run them. There is no customer account access, actual stock verification, automated SEO ranking improvement, or guaranteed sales uplift.

Choose the check you need

01 · PRODUCT STRUCTURE

Check Product and Offer JSON-LD before launch

Review representative product templates for declared Product identity, name, SKU, price, currency, published availability and image references. Check the same URLs after theme or platform migration; flag changed or missing fields for investigation.

A declared Offer is not proof that the price matches checkout or stock exists in a warehouse.

Try the free browser-only Product JSON-LD checker

Open batch Product Schema Checker ↗
02 · DATA EXPORT

Export published product prices, currency and SKU

Use the price extractor when the actual job is to capture a structured CSV or JSON snapshot. Reconcile missing identifiers and blank offers in a spreadsheet rather than treating an empty value as an out-of-stock signal.

This is a point-in-time data extraction, not recurring historical price monitoring.

Compare price extraction with a tracking workflow

Open Product Price & Stock Extractor ↗
03 · INTERNATIONAL SEO

Review hreflang alternate URLs

Inspect each language or regional URL's static HTML alternates, checking for duplicate language labels, malformed locale formats, missing URLs and unintentional differences between pre- and postlaunch templates.

A local markup check does not validate reciprocal hreflang across the entire site or confirm search indexing.

Try the free browser-only hreflang checker

Open Hreflang Tag Checker ↗
04 · CONTENT STRUCTURE

Check the H1 heading on changed page templates

Review product, collection, landing and editorial templates for missing or repeated main headings. Export findings, then validate the most consequential templates manually before sign-off.

One H1 does not by itself make a page rank higher; the tool does not inspect rendered client-side frameworks.

Open H1 Heading Checker ↗
05 · ACCESSIBILITY REVIEW

Find product images with missing alt attributes

Inspect static HTML for images without alt attributes or images with intentionally or unintentionally empty descriptions. Prioritize critical product images for human review rather than replacing every empty alt automatically.

Decorative images may appropriately have an empty alt attribute. A field check is not a complete WCAG audit.

Open Image Alt Text Checker ↗
06 · PRICING OPERATIONS

Start a repeatable competitor-price monitor after migration

Once the new catalog is stable, compare your reference price with a competitor's declared public price on the first run. Reuse the same monitor ID for later checks and review price or availability-label differences.

Requires supported static product markup. No checkout confirmation, hidden stock validation or automatic email alerts.

Test page compatibility locally before paying

Open Competitor Price Tracker ↗

Start small: a two-page smoke test

Start with the same fixed set of public product pages before and after migration. You can copy a simple input shape for an Actor that supports a urls array:

{
  "urls": [
    "https://your-public-store.example/products/product-a",
    "https://your-public-store.example/products/product-b"
  ]
}

The URLs above are placeholders, not real endpoints. Replace them with actual public HTTPS product pages you are authorized to inspect. The exact Actor input schema may support additional controls; use the Actor's current Input tab as the source of truth. To avoid a paid run while learning the workflow, try ten verified synthetic website QA samples.

Cost control: Reading this guide and using its browser-only checkers does not run an Actor. An Apify execution may incur run-start, successful-event and/or platform usage fees. Read each live Pricing tab, then start with one or two pages only if you accept the charges.

Prelaunch and postlaunch sign-off

CheckpointMinimum evidenceWhen to recheck
Product structured dataBefore/after sampled Product and Offer field snapshotsTemplate or feed changes
Price and SKU dataCSV/JSON export with noted omissions or currency mismatchesCatalog import, SKU changes
HreflangPublic HTML alternate mappings reviewed against actual localesInternational redirects or URL migration
H1 and image altRepresentative template findings signed off by content and accessibility ownersTheme, design, content changes
Competitor pricesBaseline monitor ID and consistent reference currencyRepeated supported public-price checks

For more specialized tasks, see the eight-job tool selector, published Apify input examples or all publicly listed PAL Actors. Avoid running tools on sites or data you are not authorized to inspect.