Check a redirect plan
Prepare old-to-new path mappings before a migration. This tool examines your table; HTTP responses and suitable destination content still need testing on the website.
Analysis and file reading stay in this tab. No paths are sent to the website and no persistent storage is used. Download the report to keep it.
Two columns with no header: old path, then target. Choose the delimiter. Use paths on the same site starting with /, without a domain, raw spaces or a # fragment. Query parameters are retained. Limits: 500 rows and 100,000 UTF-8 bytes. Fields may use double quotes.
Structure report
Even with no structural issue, test the server and content equivalence. This report creates no rules and chooses no HTTP status.
| Row | Old path | Entered target | Observation | Inferred chain endpoint | Proposed steps |
|---|
The export includes every row regardless of the filter. It is a six-column review report, not a server configuration or a table to import back here.
Prepare the next migration steps
Paths are compared after ordinary browser URL encoding. Letter case, trailing slashes and query parameter order remain distinct. Your server may handle these variants differently; check them separately.
A chain points to another old path in the table. A conflict gives one source several targets; a loop returns to a previously visited path. No endpoint is inferred through ambiguous or invalid mappings. Targets outside the table still need checking.
For each moved page, compare the target’s purpose and content. Prepare affected internal links and annotations, then apply rules through your server’s release procedure. Test old URLs and final pages afterwards. The example describes no real migration.
- Prepare a migration
- Fix broken links
- Google Search Central — Site moves
- Google Search Central — Redirects
Documentation consulted on October 10, 2026.