SEO-ready migration
Transfer page intent and search signals when site routes change.
Customize the recipe
0/1500 characters
Prompt preview
# SEO-ready migration Transfer page intent and search signals when site routes change. ## Deliverable A migration map, targeted changes and a repeatable staging verification report. ## Stack and visual direction - Recommended starting stack: Use the existing stack, browser tooling and the project's test commands. Capture before-and-after evidence. - Minimalism: Use deliberate spacing, a compact palette and a clear typographic hierarchy. Retain the labels, feedback and affordances people need to act. Use this direction for any new or revised UI within the agreed patch scope. ## Tools and setup · Universal Use the receiving agent’s documented skill and tool mechanisms. Match setup to the agent and workspace you actually have. Check available tools first. Propose documented project-level setup only when it materially helps and follow the host's permission prompts. If a tool or integration is unavailable, continue with the workflow below using existing tools, local fixtures or a manual check. Keep secrets in the intended configuration environment. - [OpenSEO](https://openseo.so/docs/skills) (Skill) — Run an appropriate site audit, keyword or local visibility workflow when data access is available. Live data may require OpenSEO access or a configured MCP connection. Some lookups can incur charges. [Official setup](https://openseo.so/docs/agent-setup). Fallback: Inspect local page metadata, internal links and available first-party exports. Label unavailable competitive or search-volume data as unknown. - [Next.js](https://github.com/vercel/next.js) (Repository) — Use App Router conventions, server rendering, metadata and accessible route structure. [Official setup](https://nextjs.org/docs/app/getting-started/installation). - [Lychee](https://github.com/lycheeverse/lychee) (Repository) — Check internal and external links and make transient failures distinguishable. ## Workflow 1. Inventory old and new routes, map one-to-one replacements, preserve useful metadata, and verify redirects, canonicals, sitemap entries and internal links on staging. 2. Use the simplest implementation that delivers the stated outcome. Follow the user's project constraints and treat the starting stack as a default. Reuse existing work and ask for essential input only when it would change the result. Use realistic labeled sample data when real inputs are unavailable. 3. Run the applicable checks and report what actually passed along with any checks you could not run. ## Acceptance checks - [ ] Sample old URLs reach the intended final destinations without redirect loops. - [ ] Canonical and sitemap entries use the correct live destination pattern. - [ ] Walk the primary journey with keyboard only. Check visible focus, logical order, accessible names, readable contrast, zoom and reduced motion. Use axe where available and manually check behavior that automation cannot assess. - [ ] Capture a reproducible baseline, validate the changed flow afterward, and report evidence and any findings still open.
Recipe resources
Source, setup, and compatibility details.
OpenSEO
Run an appropriate site audit, keyword or local visibility workflow when data access is available.
Live data may require OpenSEO access or a configured MCP connection. Some lookups can incur charges.
Upstream documents Codex, Claude Code.
Setup guide for OpenSEONext.js
Use App Router conventions, server rendering, metadata and accessible route structure.
License · MIT
Setup guide for Next.jsLychee
Check internal and external links and make transient failures distinguishable.
License · Apache-2.0 or MIT
Playwright CLI
Walk real browser interactions and collect screenshots or evidence for regressions.
Node.js and supported browser binaries. Use a local build or authorized test environment.
License · Apache-2.0
Setup guide for Playwright CLI