Find the URLs that need fixing after a website migration

Paste your old-to-new URL map. Get the actual destination, redirect chain and a specific next step for each pair, plus separate CSV lists for fixes, review and checks that could not be verified.

Best for: SEO teams, website owners and agencies checking a migration, domain move or URL restructuring before signing off the work.

An old URL returning HTTP 200 can still lead to the wrong page. This tool compares the observed destination with the exact new URL you intended.

Try one redirect

1. Open Input and replace the example in Redirect map with two columns: old URL and expected new URL. Copy cells from Excel/Google Sheets or paste CSV. One row checks one pair.
2. Set Maximum charge per run to $0.01 for this one-pair example, then click Start. This is a spending cap, not a fixed fee.
3. After Succeeded, read Result summary and Next step. Compare Actual destination with Expected destination, then open Readable report or download a named CSV.

old_url,new_url
https://docs.apify.com/api/v2/act-put,https://docs.apify.com/api/v2/actor-put

The sample has been tested as a permanent redirect to the expected documentation page. Live websites can change. It is an independent technical example, not a customer endorsement.

Use complete public URLs, including the intended trailing slash and query string. For a batch, paste up to 1,000 pairs. An optional header can be old_url,new_url. Each data row needs exactly two non-empty columns.

Turn the results into a fix list

Decision	Meaning	What to do next
pass	One permanent 301/308 redirect reaches the expected healthy page, with the supported canonical and indexing checks passing.	Keep the mapping and recheck after website changes.
review	The destination checks passed, but there are cautions such as extra hops, a temporary redirect or no observed canonical.	Inspect the specific warning before approving it.
fail	A problem was observed: for example, the wrong destination, no source redirect, a loop, noindex or a canonical mismatch.	Follow Next step and send the affected rows to your maintainer.
unknown	A block, rate limit, server/network error or redirect limit prevented verification.	Check manually; do not treat this as a confirmed broken redirect.

Open Fix these URLs CSV for fail rows, Review CSV for cautions, or Unverified CSV for unknown rows. Checked rows CSV includes the full checked list. Choose the file in the output selector, then use its Download action. For Excel, use Export → Excel → Download on the dataset. Readable report provides the same findings in HTML.

For example, if an old article opens the homepage instead of the mapped new article, the result shows both URLs and recommends updating that redirect. The tool reports the problem; your maintainer applies the website change.

Pricing

$3 per 1,000 checked pairs ($0.003 each), plus $0.00005 per run start at supported memory settings. Platform usage is included.

Completed checks	Total at these prices
1	$0.00305
10	$0.03005
1,000	$3.00005

Each delivered diagnostic row is charged, including failed checks, blocked pages and uncertain results. This is a price per check, not per discovered problem. Downloading the supplied reports has no separate Actor event fee.

Set the run cap above the number of pairs × $0.003, plus the start fee. Run budget too low means the Actor stopped before fetching the URLs or writing result rows; use a smaller list or raise the cap. A start fee can still apply. Interrupted runs can leave charged partial output. Treat the batch as complete only after Succeeded and OUTPUT.status: complete; success means the checks finished, not that every redirect passed.

What this check covers

The result includes the HTTP chain, final response status, destination match, static HTML canonical tags, robots/googlebot meta directives and X-Robots-Tag hints. Query strings and trailing slashes matter; fragments are ignored, hostname case is normalized and default ports are omitted.

It checks server redirects and static responses. It does not render JavaScript, follow meta-refresh redirects, inspect robots.txt, detect every soft 404, prove Google indexability or judge whether page content is equivalent. A 200 challenge page can require manual review. Pages larger than 2 MB are truncated and cannot receive a clean pass.

Limits: 1–1,000 pairs, 1 MB input, up to five redirects and 2 MB response content. Default memory is 256 MB (512 MB maximum); default run timeout is 3,600 seconds. Public HTTP/HTTPS on standard ports only. No login, proxy or automatic retry is used.

API use and support

Existing workflows can send checks: [{"url": "https://old.example/page", "expectedUrl": "https://new.example/page"}]. Clear Redirect map before using Advanced JSON checks. The original single-pair oldUrl / newUrl API format remains supported.

Input and results stay in the initiating Apify account's storage. Use the Issues tab to share a non-confidential URL pair, expected outcome and actual result. Start with a few mappings you know before checking the entire migration.