What is site-migration?

A process for rebuilding or relaunching an existing website without losing its search visibility. It records current URLs and search performance, maps old URLs to new ones, and checks the live migration.

Use it before a redesign, relaunch, URL-structure change, or move from one website system to another.

Changing URLs can make search engines lose track of pages and can reduce traffic. A redirect map tells them where moved pages now live.

How textura-agency/ai-design-vault configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to textura-agency/ai-design-vault. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/textura-agency/ai-design-vault/main/.claude/skills/site-migration/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/textura-agency/ai-design-vault

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/textura-agency/ai-design-vault/site-migration/github.svg)](https://agentmods.dev/skills/textura-agency/ai-design-vault/site-migration)

Your own site

<a href="https://agentmods.dev/skills/textura-agency/ai-design-vault/site-migration"><img src="https://agentmods.dev/badge/skills/textura-agency/ai-design-vault/site-migration/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/textura-agency/ai-design-vault/site-migration"><img src="https://agentmods.dev/badge/skills/textura-agency/ai-design-vault/site-migration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 81 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,006 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 89% copy Near-identical to another mod in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00081	$0.01006
Opus 5.5	$0.00032	$0.00402
Sonnet 5.5	$0.00016	$0.00201
Haiku 4.5	$0.00008	$0.00101

Measured 23d ago against content hash 7b9f606eef16, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

site-migration scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 23d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

89% identical to site-migration — 13 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/skills/site-migration/SKILL.md · 85 lines

How it starts

The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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.

Read the full file on GitHub · 85 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

23d ago First seen · 85 lines · 81 tokens per session scan A 7b9f606eef16

Subscribe to this mod's changes

site-migration is a skill published in the GitHub repository textura-agency/ai-design-vault (25 stars, last pushed 2mo ago), licensed Unlicense. It adds 81 tokens to every session and 1,006 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to site-migration, differing in 13 lines, and is treated as a copy.

Marketing and SEO

site-migration next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
site-migrationtextura-agency/ai-design-vault	Skill	25	2mo ago	Unlicense	A	81	Claude Code
imagegenopenai/codex	Skill	133k	yesterday	Apache-2.0	A	113	Codex
playwright-climicrosoft/playwright	Skill	99k	yesterday	Apache-2.0	A	19	Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	4d ago	MIT	A	200	Claude Code, Codex
systematic-debuggingobra/superpowers	Skill	313k	3d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	today	MIT	A	95	Claude Code
next-partial-prefetching-adoptionvercel/next.js	Skill	143k	today	MIT	A	103	Claude Code

ai-design-vault: Skill for Claude Code