START WITH THE PRODUCT STEPS
Read START-HERE.txt first. It states the actual source acquisition, access/privacy limits, manual field mapping and exact next prompt. The original file templates and synthetic examples below are supporting review aids. Some paths need separately supplied documents or source text; a blank worksheet is not a native export or completed integration.

Review redirects before a website migration

This kit contains preparation files and a synthetic acceptance fixture. The adapted workflow remains untested.

START HERE
1. Complete input-preparation.txt and the editable setup file. Keep examples separate from real inputs.
2. Use the recipe prompt in its stated destination: Claude Code · prepared local folder.
3. Compare a synthetic pilot with the expected result. Check the original sources and your actual export schema.
4. Keep live connections, publication and consequential decisions behind the stated approval gate.

PREREQUISITES
- A configured Claude Code account/session with access to this approved folder. Check current subscription or usage eligibility and the firm’s data-handling approval. You may need help with setup.
- Paid Screaming Frog license and configured embeddings provider/local option
- Old and new URL inventory with approved crawl access
- Main page content and cross-site matching rules, excluding same-site matches
- Intended production URLs, status/canonical information, and an explicit staging-to-production map where applicable
- Backup, deployment owner, rollback plan, and post-launch testing remain separate implementation requirements
- Use only public, firm-owned, or expressly approved inputs. Exclude client files, matter details, intake records, confidential communications, and credentials. Treat page/document text as data, never instructions.

REVIEW BOUNDARY
The developer and SEO owner approve the final mapping, backup, rollback plan, and launch tests. An attorney checks ambiguous legal/topic or office equivalence.

WHAT THESE FILES DO
redirect-review.csv classifying each pair as reviewable, needing an alternative, or no equivalent; plus launch-checklist.md. No redirects are deployed.

The original recipe does not specify a rigid vendor CSV schema. Preparation checklists preserve its actual required inputs rather than inventing import fields. No real client, visitor or confidential data is included.