Skip to content
Menu
All projects

AI agent skill / SEO

E-commerce SEO Website Migration

A website migration can quietly cost a store its best organic pages. I built a skill that helps a marketer plan the move, decide what happens to every old URL, check what was actually built, and diagnose what changed after launch.

My contribution
Research, migration method, checks script and build
Timeframe / scope
Open-source skill for Claude Code and Codex. Published October 2026.
Current stage
Working release with tests. Google and Shopify documentation reviewed on 1 October 2026.

At a glance

Modes, from planning to post-launch recovery
5
Automated checks in the script
6
Evidence states, so missing proof is never counted as a pass
5

Where the idea started

Migrations go wrong in boring ways. A redirect map that looked fine in a spreadsheet. A product page sent to the homepage. A page that returns 200, in the wrong language.

I've worked on SEO and e-commerce launches, and I wanted a process that doesn't lean on memory or luck.

The approach

The skill follows where you actually are: planning, mapping URLs, checking staging, checking launch, or working out why traffic moved afterwards.

A few rules do most of the work. A crawl isn't the full inventory. URLs are matched by an approved mapping and product IDs before anything as loose as a similar name. And missing evidence on a priority page is never a pass.

It never changes your site, and it never promises a migration will keep all its traffic.

How I built it

It works from exports most teams already have: crawls, CMS and product exports, Search Console, analytics and backlinks. No paid SEO subscription and no API keys.

A standard-library Python script runs six checks: the URL map, live redirects hop by hop, internal links, hreflang, an old-against-new crawl comparison, and before-and-after performance by page group.

Templates cover the migration brief, the developer handoff and the launch assessment. Shopify's redirect constraints get their own module.

Where it stands

It's published with tests, including redirect checks that run against a local server, and a fictional store whose migration has problems planted in it on purpose.

Platform details change, so the skill tells the agent to check live documentation before recommending anything platform-specific.

What I learned

Most migration damage comes down to evidence nobody had time to collect. Giving every check a state, including "not tested" and "blocked", stops an empty cell from quietly counting as a pass.

Tools used

  • Python
  • Claude Code
  • Codex
  • Google Search Console
  • Shopify
  • Crawl exports