Add missing URLs
Paste individual 404 URLs or bring them in through a file or Google Drive.
Recovery engine
Turn dead-ends into recovered
traffic.
Paste or upload broken URLs, match them against a sitemap or project crawl and review the suggested live destinations.
Review queue
Targets suggested
Fallback review
No suitable target?
yoursite.com/old-product/blue-widget
404
Page not found
The page you're looking for has moved or no longer exists.
Status
404
Target
Not selected
Review
Required
The problem
A broken URL needs a relevant decision.
A broken legacy URL can send users and crawlers to a dead end.
Finding replacement pages manually becomes harder as the list grows.
A homepage redirect is not automatically a relevant replacement.
How it works
From broken to recovered in 4 steps
01
Add 404 URLs
Paste, upload CSV or import from your link report.
02
Match against live
Engine compares against your sitemap or crawl data.
03
Review suggestions
Each suggestion has a confidence score and reasons.
04
Export redirects
Download ready-to-deploy redirect rules.
Capabilities
Review replacement URLs before they become redirects
Add missing 404s, choose the live URL set and inspect each proposed destination with its reasons.
Select the live target inventory
Use an SEO Project, sitemap, upload or Google Drive file as the set of possible destinations.
Review proposed replacements
Inspect the broken URL, proposed destination, match status and reasons before accepting anything.
Replacement reviewIllustrative flow
Broken/old/blue-runnerTarget/shoes/blue-runner
ReviewTitle matchSame product type
The proposed URL remains editable before acceptance.
Parent and homepage options
Review a relevant parent, homepage or no-redirect decision when there is no direct replacement.
Manual destination optionsIllustrative flow
Direct replacementPreferred
Relevant parentReview
HomepageLast resort
No redirectValid choice
Locale and page-type review
Keep configured language paths and page types visible so questionable suggestions remain manual decisions.
Checks before acceptanceIllustrative flow
Language mapping configuredSame locale
Different page typeManual review
No relevant pageLeave unresolved
Accept and export redirects
Add accepted suggestions to the redirect plan and export the implementation file when review is complete.
Accepted redirectIllustrative flow
Source/old-pageTarget/new-pageStatus301
AcceptedRedirect planCSV
Use cases
Use one review flow for different 404 sources
01
Post-migration cleanup
Review broken legacy URLs that were not included in the original redirect plan.
Add the missing URLs manually and compare them with the current sitemap, crawl file or project crawl.
Missing legacy URLs - paste or upload
Current URL source - sitemap or crawl
Suggested targets - match reasons and score
Category fallback - review a relevant parent
02
Legacy URL cleanup
Review old URLs that still receive visits or remain in reports even though they are no longer part of the current crawl.
Keep those URLs in the same matching and review process as crawl-based 404s.
Manual URL input - include URLs outside the crawl
Relevant target review - prefer a relevant destination
Accepted suggestions - separate from review
CSV export - source and target pairs
03
Periodic site audits
Review broken URLs from a project crawl together with URLs collected outside that crawl.
Use the latest active project URLs as the target pool and keep manual additions in the same review queue.
Project crawl - use current live URLs
Sitemap input - fetch the target URL set
Manual additions - include uncrawled 404s
Fallback review - use only when appropriate
FAQ
Questions, answered.
Turn 404s back into traffic.
Add the broken URLs, choose the current URL source and review each suggested destination before export.
No credit card required