# Check storefront price, canonical and noindex regressions

**Use case:** 

Compare one fictional product page before and after a release: USD 19.90 becomes 29.90, the canonical is wrong, and noindex is added. Expected result: complete=true, decision=FAIL, with JSON, CSV and HTML evidence. FAIL means the comparison found regressions. Saved settings: 512 MB, 120 s, $0.10 cap. $0.05 per completed report. Supplied HTML only; no crawling.

## Input

```json
{
  "baselineId": "baseline-1",
  "releaseId": "release-2",
  "observedAt": "2026-10-10T23:00:00.000Z",
  "expectedUrls": [
    "https://store.example/products/a"
  ],
  "before": [
    {
      "url": "https://store.example/products/a",
      "html": "<html><link rel=\"canonical\" href=\"https://store.example/products/a\"><meta name=\"robots\" content=\"index,follow\"><script type=\"application/ld+json\">{\"@type\": \"Product\", \"@id\": \"a\", \"sku\": \"SKU-a\", \"offers\": {\"@type\": \"Offer\", \"price\": \"19.90\", \"priceCurrency\": \"USD\", \"availability\": \"https://schema.org/InStock\"}}</script></html>",
      "status": 200
    }
  ],
  "after": [
    {
      "url": "https://store.example/products/a",
      "html": "<html><link rel=\"canonical\" href=\"https://store.example/wrong\"><meta name=\"robots\" content=\"noindex\"><script type=\"application/ld+json\">{\"@type\": \"Product\", \"@id\": \"a\", \"sku\": \"SKU-a\", \"offers\": {\"@type\": \"Offer\", \"price\": \"29.90\", \"priceCurrency\": \"USD\", \"availability\": \"https://schema.org/InStock\"}}</script></html>",
      "status": 200
    }
  ],
  "severity": {}
}
```

## Output

```json
{
  "decision": {
    "label": "Decision",
    "format": "string"
  },
  "complete": {
    "label": "Complete",
    "format": "boolean"
  },
  "baselineId": {
    "label": "Baseline",
    "format": "string"
  },
  "releaseId": {
    "label": "Release",
    "format": "string"
  },
  "coverage.expected": {
    "label": "Expected pages",
    "format": "integer"
  },
  "coverage.compared": {
    "label": "Compared pages",
    "format": "integer"
  },
  "reportLinks.html": {
    "label": "HTML evidence",
    "format": "string"
  },
  "reportLinks.json": {
    "label": "JSON evidence",
    "format": "string"
  },
  "reportLinks.csv": {
    "label": "CSV evidence",
    "format": "string"
  },
  "manifestLink": {
    "label": "Artifact manifest",
    "format": "string"
  },
  "canonicalReportSha256": {
    "label": "Report SHA-256",
    "format": "string"
  }
}
```

## How it works

### 1. Sign up on Apify or log in

The Storefront SEO Regression Checker | HTML Release Diff Actor is ready to run with the inputs already set for "Check storefront price, canonical and noindex regressions". [Sign up or log in](https://console.apify.com/create-task-from-example/H9HT17yWMLkWl8If2) and you'll land in Apify Console with a copy of this exact task.

### 2. Start the "Check storefront price, canonical and noindex regressions" task

The Storefront SEO Regression Checker | HTML Release Diff Actor will start running based on the input automatically. You can also change all the input fields, like baseline capture id, release capture id, and more, to match your specific use case.

### 3. Receive the "Check storefront price, canonical and noindex regressions" output

Monitor the progress in real time. You will be notified as soon as your dataset is complete and ready for review. Each result includes data such as decision, complete, baseline, and more.

### 4. Integrate into your workflow

The final output is delivered in JSON, CSV, or Excel format, ready to be plugged into your workflow. You can also [run the "Check storefront price, canonical and noindex regressions" task via API](https://apify.com/cygnix_labs/cygnix-storefront-release-proof.md).

## About this Actor

This example demonstrates how to use [Storefront SEO Regression Checker | HTML Release Diff](https://apify.com/cygnix_labs/cygnix-storefront-release-proof.md) with a specific input configuration. Visit the [Actor detail page](https://apify.com/cygnix_labs/cygnix-storefront-release-proof.md) to learn more, explore other use cases, and run it yourself.


## How to integrate an Actor?

This Task's input is already configured above. Use it as-is rather than inventing a new one.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For full API examples (JavaScript, Python, CLI, MCP, OpenAPI), see this Task's Actor page: https://apify.com/cygnix_labs/cygnix-storefront-release-proof.md

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).