# Sitemap Migration Parity Auditor (`riparazionecomputerecellulari/my-actor-1`) Actor

Compare old and new pages from a sitemap: redirects, status codes, canonical and noindex directives, titles, descriptions, H1s and content fingerprints. Built for migration QA with up to 200 public URL pairs per run.

- **URL**: https://apify.com/riparazionecomputerecellulari/my-actor-1.md
- **Developed by:** [Riparazione Computer\&Cellulari](https://apify.com/riparazionecomputerecellulari) (community)
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.50 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

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 examples already wired to this Actor's own input schema, see the [API](#api) section below.

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`).

# README

## SEO Migration Auditor — Redirect, Canonical & Noindex Checks

Validate a website migration before organic traffic is put at risk. The Actor reads an existing public sitemap, maps every path to a new domain, and checks both versions side by side. You can also provide explicit source/target URL pairs.

### What it checks

- Final HTTP status and complete redirect chain
- Accidental `noindex` directives in HTML or `X-Robots-Tag` headers
- Missing or mismatched canonical URLs
- Missing title and meta description
- H1 count
- Title and normalized-content changes
- Long redirect chains
- A transparent 0–100 diagnostic score with issue codes

### Typical uses

- Domain or CMS migrations
- HTTP-to-HTTPS and subdomain moves
- Staging-to-production launch checks
- Redirect-map quality assurance
- Scheduled post-launch monitoring

### Input

Use either:

1. `sourceSitemapUrl` plus `targetBaseUrl`, or
2. `urlPairs` containing exact `sourceUrl` and `targetUrl` values.

Runs are capped at 200 pairs. Only public HTTP(S) URLs are accepted. Static HTML and response headers are inspected; client-rendered metadata is outside scope.

### Output

Each dataset row contains the source URL, intended target, final target URL, status, redirect chain, source and target metadata, issue list, verdict, and score. A run-level summary is stored as `SUMMARY` in the default key-value store.

### Important

The results are diagnostic signals. They do not guarantee indexing, rankings, traffic, or revenue. Always review critical findings before changing production redirects.

### Pricing

$1.50 per 1,000 dataset results ($0.0015 each), plus $0.0001 per Actor start. Platform usage is included. Diagnostic error rows also count as results. A 10-pair run costs $0.0151.

### Limits and interpretation

Up to 200 pairs, 20 sitemap documents, index depth 2, 8 redirect responses and 2 MB per HTTP response. Plain XML sitemaps only; gzip archives and JavaScript rendering are not supported. The normalized content fingerprint covers the first 100,000 characters. Target base must be a domain origin; path mapping preserves source paths and query strings. The source must remain accessible for content comparison. This is a page parity check: it does not certify that old URLs redirect to the expected new URL. Canonical differences are review signals and can be intentional. The score is a heuristic, not a Google metric.

# Actor input Schema

## `sourceSitemapUrl` (type: `string`):

Public sitemap.xml from the old/current site. Used with Target base URL.

## `targetBaseUrl` (type: `string`):

New site origin. Each sitemap path is mapped to this base URL.

## `urlPairs` (type: `array`):

Optional. When provided, these pairs replace sitemap mapping.

## `maxUrls` (type: `integer`):

Safety limit. Maximum 200 pairs per run.

## `timeoutSecs` (type: `integer`):

Maximum time allowed for each public HTTP request.

## Actor input object example

```json
{
  "targetBaseUrl": "https://example.com",
  "urlPairs": [
    {
      "sourceUrl": "https://example.com/",
      "targetUrl": "https://example.com/"
    }
  ],
  "maxUrls": 50,
  "timeoutSecs": 20
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "urlPairs": [
        {
            "sourceUrl": "https://example.com/",
            "targetUrl": "https://example.com/"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("riparazionecomputerecellulari/my-actor-1").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "urlPairs": [{
            "sourceUrl": "https://example.com/",
            "targetUrl": "https://example.com/",
        }] }

# Run the Actor and wait for it to finish
run = client.actor("riparazionecomputerecellulari/my-actor-1").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "urlPairs": [
    {
      "sourceUrl": "https://example.com/",
      "targetUrl": "https://example.com/"
    }
  ]
}' |
apify call riparazionecomputerecellulari/my-actor-1 --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,riparazionecomputerecellulari/my-actor-1"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/dFQ285av6dN8lG7qG/builds/ryOilg2NzBBlPS7u7/openapi.json