# Post-release technical SEO & Core Web Vitals check

**Use case:** 

Verify that key pages pass Core Web Vitals, Lighthouse SEO and Accessibility checks after a release, with redirect and HTTP status verification.

## Input

```json
{
  "urls": [
    "https://www.wikipedia.org/",
    "https://example.com/"
  ],
  "fromSitemap": false,
  "maxPagesPerDomain": 50,
  "mode": "audit",
  "devices": [
    "phone",
    "desktop"
  ],
  "includeHistory": false,
  "historyWeeks": 25,
  "onlyChanges": false,
  "syncReset": false,
  "minChangePercent": 10,
  "lcpGoodMs": 2500,
  "lcpPoorMs": 4000,
  "inpGoodMs": 200,
  "inpPoorMs": 500,
  "clsGood": "0.1",
  "clsPoor": "0.25",
  "maxPages": 10,
  "maxRunSecs": 0
}
```

## Output

```json
{
  "finalUrl": {
    "label": "URL",
    "format": "string"
  },
  "device": {
    "label": "Device",
    "format": "string"
  },
  "cwvAssessment": {
    "label": "CWV Assessment",
    "format": "string"
  },
  "fieldSource": {
    "label": "Field Source",
    "format": "string"
  },
  "lcpP75Ms": {
    "label": "LCP p75 (ms)",
    "format": "number"
  },
  "inpP75Ms": {
    "label": "INP p75 (ms)",
    "format": "number"
  },
  "clsP75": {
    "label": "CLS p75",
    "format": "number"
  },
  "labPerformanceScore": {
    "label": "Lab Perf (0-100)",
    "format": "number"
  },
  "changeType": {
    "label": "Change",
    "format": "string"
  },
  "status": {
    "label": "Status",
    "format": "string"
  },
  "statusReason": {
    "label": "Reason",
    "format": "string"
  }
}
```

## How it works

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

The Core Web Vitals & PageSpeed Monitor – CrUX & Lighthouse Actor is ready to run with the inputs already set for "Post-release technical SEO & Core Web Vitals check". [Sign up or log in](https://console.apify.com/create-task-from-example/iOspFH0ewFeIcryQG) and you'll land in Apify Console with a copy of this exact task.

### 2. Start the "Post-release technical SEO & Core Web Vitals check" task

The Core Web Vitals & PageSpeed Monitor – CrUX & Lighthouse Actor will start running based on the input automatically. You can also change all the input fields, like page urls, discover pages from sitemap, and more, to match your specific use case.

### 3. Receive the "Post-release technical SEO & Core Web Vitals check" 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 URL, device, CWV Assessment, 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 "Post-release technical SEO & Core Web Vitals check" task via API](https://apify.com/datarelay/core-web-vitals-monitor.md).

## About this Actor

This example demonstrates how to use [Core Web Vitals & PageSpeed Monitor – CrUX & Lighthouse](https://apify.com/datarelay/core-web-vitals-monitor.md) with a specific input configuration. Visit the [Actor detail page](https://apify.com/datarelay/core-web-vitals-monitor.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/datarelay/core-web-vitals-monitor.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`).