# Catch accidental noindex before a website release
**Use case:**
Compare synthetic before-and-after snapshots to catch an accidental X-Robots-Tag: noindex on an expected indexable page. This ready-to-run example produces one new high-severity RS_NOINDEX finding and gate code 1. Offline snapshot comparison only, not a live crawler or indexing check. For users: $0.01 per completed report, including platform usage.
## Input
```json
{
"baseline": "{\n \"version\": 1,\n \"pages\": [\n {\n \"url\": \"https://demo.example/services\",\n \"status\": 200,\n \"headers\": [\n {\n \"name\": \"Content-Type\",\n \"value\": \"text/html; charset=utf-8\"\n }\n ],\n \"finalUrl\": \"https://demo.example/services\",\n \"html\": \"Our services
\"\n }\n ]\n}",
"expectations": "{\n \"version\": 1,\n \"pages\": [\n {\n \"url\": \"https://demo.example/services\",\n \"indexable\": true,\n \"requireTitle\": true,\n \"canonical\": {\n \"required\": true,\n \"target\": \"https://demo.example/services\"\n }\n }\n ]\n}\n"
}
```
## Output
```json
{
"adapterVersion": {
"label": "Adapter version",
"format": "string"
},
"engineVersion": {
"label": "Engine version",
"format": "string"
},
"status": {
"label": "Status",
"format": "string"
},
"gateCode": {
"label": "Gate code",
"format": "integer"
},
"pagesRequested": {
"label": "Pages requested",
"format": "integer"
},
"findingsTotal": {
"label": "Findings total",
"format": "integer"
},
"newFindings": {
"label": "New findings",
"format": "integer"
},
"resolvedFindings": {
"label": "Resolved findings",
"format": "integer"
},
"persistingFindings": {
"label": "Persisting findings",
"format": "integer"
},
"uncomparedFindings": {
"label": "Uncompared findings",
"format": "integer"
},
"indeterminateFindings": {
"label": "Indeterminate findings",
"format": "integer"
},
"currentFindings": {
"label": "Current findings",
"format": "integer"
},
"highRiskGateFailed": {
"label": "High risk gate failed",
"format": "boolean"
},
"incomplete": {
"label": "Incomplete",
"format": "boolean"
},
"coverageGaps": {
"label": "Coverage gaps",
"format": "integer"
}
}
```
## How it works
### 1. Sign up on Apify or log in
The Release Sentinel: SEO Regression Checker (Beta) Actor is ready to run with the inputs already set for "Catch accidental noindex before a website release". [Sign up or log in](https://console.apify.com/create-task-from-example/rMmDeR0xuhlDdqjTc) and you'll land in Apify Console with a copy of this exact task.
### 2. Start the "Catch accidental noindex before a website release" task
The Release Sentinel: SEO Regression Checker (Beta) Actor will start running based on the input automatically. You can also change all the input fields, like baseline snapshot json text, candidate snapshot json text, and more, to match your specific use case.
### 3. Receive the "Catch accidental noindex before a website release" 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 adapter version, engine version, status, 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 "Catch accidental noindex before a website release" task via API](https://apify.com/intuitive_crevasse/release-sentinel.md).
## FAQ
### Where is the detailed noindex evidence?
Release Sentinel saves detailed findings in the run's default key-value store under OUTPUT. The dataset used by the generated Python example contains summary counts and gateCode, not the HTML or before-and-after evidence.
### Does a successful Actor run mean the release passed?
Release Sentinel run success means processing completed. In OUTPUT, report.exitCode 1 means a new high-risk regression; 2 means incomplete coverage; 0 means no new high-risk finding in complete supported coverage. Existing problems can persist at 0.
### How do I test the corrected synthetic candidate?
For this Release Sentinel example, copy the entire baseline text into candidate and keep expectations unchanged. The corrected comparison returns report.exitCode 0. Review the active Store price before starting another run.
### What input types does the API require?
Release Sentinel requires baseline, candidate and expectations as JSON strings, not nested objects. The Code section includes complete examples. The synthetic URLs identify recorded pages; Release Sentinel does not fetch them.
## About this Actor
This example demonstrates how to use [Release Sentinel: SEO Regression Checker (Beta)](https://apify.com/intuitive_crevasse/release-sentinel.md) with a specific input configuration. Visit the [Actor detail page](https://apify.com/intuitive_crevasse/release-sentinel.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/intuitive_crevasse/release-sentinel.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`).