SEO Release Guard — Sitemap & Indexability Regression Audit

Catch accidental noindex directives, broken sitemap URLs and changed canonical targets after a site release, migration or theme update.

Built for SEO agencies and web teams that need a repeatable release checklist with machine-readable differences between audits.

Start

{"demoMode": true}

The offline fictional demo includes a newly noindexed product page, a 404 and a robots-blocked page. Real operation accepts page URLs:

{
  "urls": ["https://your-site.example/products/backpack"],
  "maxItems": 100
}

Or sitemap URLs:

{
  "sitemapUrls": ["https://your-site.example/sitemap.xml"],
  "maxItems": 100
}

Use urls OR sitemapUrls. Replace the fictional .example URLs.

Checks and outputs

• HTTP 404/410, redirects in the URL inventory and final destination.
• noindex/none in head-level robots/googlebot meta tags and applicable X-Robots-Tag response headers.
• Missing, conflicting or elsewhere-pointing HTML canonicals.
• Missing title, and title/canonical/noindex/HTTP changes since the last audit.
• New and resolved issues with evidence and a next action.
• JSON dataset, SUMMARY, SNAPSHOT, Markdown REPORT and formula-safe CSV.

Sitemap indexes and XML urlsets are supported. Index loops and duplicates are bounded. Off-origin sitemap entries are skipped. Each run reads at most 20 unique sitemap documents. Unsupported or blocked discovery is reported in SUMMARY. Gzip served using Content-Encoding is supported by the HTTP client; raw .gz files without a Content-Encoding header are not supported in this version.

Compare releases

Run before a release and pass its SNAPSHOT as previousSnapshot in the next run. For automated monitoring, provide an existing stateStoreId that you own and a unique monitorId, grant storage access, and avoid overlapping runs. Use separate stores for separate customers.

The baseline retains previous successful observations when a check is inaccessible. Only the most recent 5,000 observations are retained. Missing URLs from truncated or changed sitemap inventories are never claimed to be deleted pages.

Pricing

Proposed launch price: $2 per 1,000 audited HTML pages or confirmed missing pages ($0.002 each), including normal runtime costs. No startup fee or rental. Event name: page-audited, activated in Apify Publication before sale.

Sitemap documents, skipped duplicates and unverified fetches are not charged. Confirmed 404/410 pages are billed because they are actionable audit findings. Unchanged checks are billed once per URL per run. 500 pages cost $1 per audit; four weekly audits cost $4. Use the platform maximum charge per run.

Boundaries

This is a focused check of HTML signals, not a full SEO crawler, Google URL Inspection replacement, indexation guarantee, uptime monitor or ranking predictor. robots-blocked URLs are marked unverified; a robots rule does not prove deindexing. Intentional canonicals and noindex pages may correctly appear as findings. Review their purpose before editing the site.

The Actor does not render JavaScript, fetch canonical targets, crawl inbound links, compare page content, inspect HTTP Link-header canonicals, handle all search bots, or determine Google's selected canonical. It does not submit changes to Google. No messages are sent; route dataset findings through your own workflow if desired.

Up to 1,000 pages/run, 2 MB per response after decompression, 10-minute crawl ceiling, bounded redirects/retries, public HTTP(S) ports 80/443 and robots.txt compliance. No proxies or paid external APIs.

Account plans, optional workflows and dataset reads after completion may incur separate charges. Demos have no Actor event fee, but platform execution can still consume usage.