Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

SEO › Advanced

Building a Redirect Map for a Bathroom Retailer Migration

A replatforming exercise for an invented bathroom fittings retailer whose URL patterns change and whose new front end renders listings with JavaScript. You write the redirect rules and their exceptions, decide the fate of discontinued ranges, list the rendering checks for staging, and set the benchmarks and launch-day checks that decide whether the move worked.
ExerciseAdvanced levelModule 1: Migrations and rendering risk5 minUpdated

Why this matters

A replatforming changes URLs, templates and often rendering in one release. Pattern rules cover most of a catalogue in a few lines; the damage hides in the exceptions: the redirect left over from the last move, the rewritten slug, the download that plumbers link to. The site migrations guide sets out the method; this exercise makes you apply it to an inventory where the expensive URLs are the awkward ones.

The retailer and its URL inventory

Tarnwick Bathroom Supplies is an invented bathroom fittings retailer moving to a new e-commerce platform with a JavaScript front end. Category and product URL patterns change, two ranges are discontinued, and the new category templates load the product grid from an API on a separate subdomain.

Illustrative example — not a real result

Tarnwick Bathroom Supplies: URL inventory by group

GroupOld pattern or URLURLsOrganic clicks a monthReferring domainsNew pattern
Categories/c/112/basins.html8521,000140/bathrooms/basins/
Products/p/AL-2201-aldwick-mixer.html6,40038,000210/products/aldwick-mixer/
Advice guides/advice/how-to-measure-for-a-bath.html1209,50095/advice/measure-for-a-bath/ (slugs rewritten)
Installation PDFs/downloads/AL-2201-install.pdf9001,20060/files/install/al-2201.pdf
Aldwick showers (discontinued)40 product URLs401,80012Successor range Aldwick Pro exists
Penrose baths (discontinued)range page plus 25 products2670014, all to the range pageNo successor; other freestanding baths exist
Legacy redirects/shop/basins and http:// versions300n/a30Currently redirect to the old /c/ URLs
Sale category/c/115/basins-sale.html14003No sale category on the new site
Internal search/search?q=...thousands00/search?q=...

Staging notes: category grids load from api.tarnwick-shop.example after page load; product cards use click handlers; titles and canonical tags are set by script; staging carries a site-wide noindex.

Redirect rules and their exceptions

Write the rules first: one per pattern, permanent, single hop, to the true equivalent. Then hunt the exceptions. Three classes always need a look: URLs that already redirect, which must resolve to the new final destination; URLs whose slug changed, where the rule cannot guess; and URLs with no equivalent, where someone decides on purpose between a close redirect and a gone status. Watch the Canonical Tag on every new template too: if it is set by script, or still names old URLs, it contradicts the redirect.

Task

  1. Write the redirect rule for each group that follows a pattern, and say how you would test it on staging.
  2. List the exceptions the rules miss and write the explicit mapping each needs.
  3. Decide, with a reason, what happens to each discontinued range and the sale category.
  4. Flag the rendering checks the new front end needs before launch.
  5. List the benchmarks to capture before launch and why each is needed.
  6. Write the launch-day sequence and the first weeks of monitoring.

Worked answer

Rules. Categories map by a lookup table from category ID to new path, not by slug, because some slugs changed. Products map by SKU to the new slug from the platform export. Installation PDFs map by SKU to the new file path. Every rule is permanent and resolves in one hop; test with a script that requests every old URL and checks status and destination.

Exceptions. The advice guides need a hand-built mapping, because the slugs were rewritten. The legacy shop and HTTP URLs currently point at old category URLs, so map them straight to the new final destinations to avoid chains. Internal search URLs are left alone, with a noindex on the new search template.

Discontinued ranges. Aldwick showers redirect product by product to the matching Aldwick Pro models, since a direct successor exists. The Penrose range page keeps its links if it becomes a useful freestanding baths page explaining the range has ended; redirect it there, and send the Penrose product URLs, which have no links and little traffic, to that page or let them return a gone status. The sale category redirects to the basins category, the closest real equivalent.

Rendering. Product cards must be anchors with real addresses, not click handlers, or the crawler cannot reach products. The API subdomain must not be blocked in its robots rules. Titles and canonicals must be in the initial HTML, as the JavaScript SEO guide recommends. Check rendered HTML with the live test in GSC on staging-equivalent pages, crawl staging with and without rendering and compare link counts, and ask whether category content can be server-rendered so indexing does not wait on the render queue.

Benchmarks. Before launch, export clicks and impressions by page and section, rankings for priority terms, indexed counts, the linked-URL list, a full crawl with canonicals and titles, and conversion event counts. Without them the outcome is argued, not measured.

Illustrative example — not a real result

Tarnwick: priority order for testing the map

Test order by value at risk: categories (85 URLs, 21,000 clicks, 140 referring domains), products (6,400 URLs, 38,000 clicks), advice guides (120 URLs, 9,500 clicks, hand-mapped), legacy redirects (300 URLs, 30 referring domains), PDFs (900 URLs, 60 referring domains), then the discontinued ranges. A failed test on any of the first three groups delays launch; a failed test on the last two goes on the first post-launch ticket list.

Launch day and after. Work through the launch-day group of the website migration checklist in order: remove the staging noindex, deploy the full map, test the top URLs from every group at once, submit the new sitemap, and confirm analytics and conversion events fire. Keep the old sitemap available so old URLs are recrawled. Then watch daily: not-found responses in server logs, the indexing report, and clicks by section against the benchmark. On a catalogue this size, recrawling draws on Crawl Budget, so recovery takes weeks. If losses persist, diagnose by elimination with the guide to traffic drops after a migration.

Common mistakes

  • Mapping by pattern alone. Rewritten slugs, legacy redirects and downloads fall through the rule.
  • Sending discontinued pages to the home page. Treated as soft not-found; the links are wasted.
  • Leaving old redirects in place. They chain through the old URLs instead of reaching the new ones.
  • No benchmark. A loss cannot be located, let alone fixed.

Check your judgement in the migrations and rendering checkpoint, or revisit the intermediate SEO level for crawling and indexing basics.

Pages this lesson applies

Terms used on this page

Also related

Related