Catch accidental noindex before a website release

Created by

Kestrelspan Tools

Actor

Release Sentinel: SEO Regression Checker (Beta)

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.

Try for free

Release Sentinel: SEO Regression Checker (Beta)intuitive_crevasse/release-sentinel

Adapter version

Engine version

Status

Gate code

+11 fields

Input

Baseline snapshot JSON text(required):{ "version": 1, "pages": [ { "url": "https://demo.example/services", "status": 200, "headers": [ { "name": "Content-Type", "value": "text/html; charset=utf-8" } ], "finalUrl": "https://demo.example/services", "html": "<!doctype html><html><head><title>Our services</title><link rel=\"canonical\" href=\"https://demo.example/services\"></head><body><h1>Our services</h1></body></html>" } ] }

Candidate snapshot JSON text(required):{ "version": 1, "pages": [ { "url": "https://demo.example/services", "status": 200, "headers": [ { "name": "Content-Type", "value": "text/html; charset=utf-8" }, { "name": "X-Robots-Tag", "value": "noindex" } ], "finalUrl": "https://demo.example/services", "html": "<!doctype html><html><head><title>Our services</title><link rel=\"canonical\" href=\"https://demo.example/services\"></head><body><h1>Our services</h1></body></html>" } ] }

Expectations JSON text(required):{ "version": 1, "pages": [ { "url": "https://demo.example/services", "indexable": true, "requireTitle": true, "canonical": { "required": true, "target": "https://demo.example/services" } } ] }

Output fields

Adapter version

Engine version

Status

Gate code

Pages requested

Findings total

New findings

Resolved findings

Persisting findings

Uncompared findings

Indeterminate findings

Current findings

High risk gate failed

Incomplete

Coverage gaps

How it works

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 and you'll land in Apify Console with a copy of this exact task.

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.

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.

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.

Integrate "Catch accidental noindex before a website release" into your workflow

Connect "Catch accidental noindex before a website release" with 100+ integrations, or run it via API or MCP.

Webhook

n8n

Make

Zapier

Airbyte

Keboola

IFTTT

Hubspot

GDrive

Gmail

Apify MCP

GitHub

Slack

LangChain

LlamaIndex

Flowise

Pinecone

OpenAI

Mastra

Clay

Frequently asked questions

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.