site-migration
Skill141 starsChanged 34 days agoUnlicenseView on GitHub
Protect search rankings when rebuilding or relaunching an existing site — pre-migration crawl and inventory, rankings snapshot, redirect map, and post-launch verification. Use when the user is rebuilding a live site, replacing an existing site, changing URL structure, or says "we're relaunching", "migrating from WordPress/Webflow", or "will this hurt our rankings".
2 other projects use a version of this.
Adopted by
Most recently taken up by
- jbobbink/seo-gsc-wizardtheir own version, first seen Nov 1, 2026
- afeezadebayo/technical-seo-skillstheir own version, first seen Oct 20, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- afeezadebayo/technical-seo-skills★ 2same name
- jbobbink/seo-gsc-wizard★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- aeo-visibilitySkill
- figma-to-sectionSkill
- i18n-seoSkill
- local-seoSkill
- mobile-device-qaSkill
- optimize-3d-sceneSkill
- optimize-loadSkill
- optimize-performanceSkill
- payload-adminSkill
- payload-analyticsSkill
- payload-cmsSkill
- qa-verifySkill
- schema-markupSkill
- seo-auditSkill
- seo-growSkill
- ship-checkSkill
- supabase-authSkill
- supabase-dbSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
If the user is rebuilding a live site, raise this at the start of the project, not at the end.
- Distinctive: line 28
Ask the user for a Google Search Console performance export (last 3–6 months: Performance → Export).
- Distinctive: line 61
Keep URL structure identical wherever there is no strong reason to change it.
- Very specific: line 65
Keep the same canonical/lang conventions.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Site migration without losing rankings
Traffic collapse after a relaunch is almost always the same cause: URLs changed and nothing told search engines where they went. The work below happens before the new site goes live. After launch it is damage control.
If the user is rebuilding a live site, raise this at the start of the project, not at the end. It is the cheapest insurance in the whole engagement.
1. Inventory the live site — before anything changes
Crawl or list every indexed URL. Record: URL, page title, H1, content type,
whether it currently ranks. Save to MIGRATION-URL-INVENTORY.md.
Sources, in order of reliability: the existing sitemap.xml, Search Console's Pages report, an actual crawl, the CMS's own page list. Use several — each misses different things, and the ones they miss (old landing pages, PDFs, paginated archives) are exactly the ones that quietly carry links.
2. Snapshot what you are protecting
Ask the user for a Google Search Console performance export (last 3–6 months: Performance → Export). From it record:
- top 20 pages by clicks
- top 30 queries by clicks and impressions
- everything ranking in positions 1–10
Save to MIGRATION-RANKINGS-SNAPSHOT.md. This is the baseline you will be judged
against, so capture it before the rebuild touches anything.
Also capture the most-linked pages (Ahrefs/Semrush export if they have one). A page with backlinks must keep its equity — losing it is far more expensive than losing an unlinked page.
3. Build the redirect map
MIGRATION-REDIRECT-MAP.md, two columns: old URL → new URL. Rules:
- Every old URL gets a destination. Mark unknowns
[TBD]and resolve them all before launch — a[TBD]at launch is a 404. - Map to the closest equivalent page, never blanket-redirect everything to the homepage. Google treats mass homepage redirects as soft 404s and the equity is lost.
- 301 (permanent), not 302, unless the change genuinely is temporary.
- One hop. Chained redirects leak and slow crawling — if the old site already redirects, map to the final destination.
- Preserve query-parameter and trailing-slash behaviour, or normalise it deliberately and consistently.
In this starter, redirects live in next.config.ts (redirects()), or at the
platform edge if the volume is large. Keep them in code so they are reviewable.
4. Carry over what search engines already trust
- Keep URL structure identical wherever there is no strong reason to change it. "The new IA is nicer" is rarely worth the risk on a ranking page.
- Preserve page titles and H1s on pages that rank, unless improving them is the point.
- Carry over the content — a rebuilt page with a third of the copy usually drops.
- Keep the same canonical/
langconventions; re-add structured data.
5. Launch checklist
- Every old URL redirects, one hop, 301, to a real page
robots.tsallows crawling (staging blocks removed — check this twice)sitemap.tslists every new public route, and is submitted in Search ConsoleNEXT_PUBLIC_SITE_URLpoints at the production domain- No
noindexleft over from staging - Analytics and Search Console verified on the new site
- Core Web Vitals measured on the new site (
seo-auditskill)
6. After launch
Watch weekly for the first month: Search Console coverage errors, 404s in logs, and the ranking snapshot from step 2. Some fluctuation for 2–4 weeks is normal; a sustained drop on a specific page means its redirect or its content is wrong.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

