1. Home
  2. Work
  3. E-commerce

Case study 01 · E-commerce · Technosport

A platform can change without losing its search foundation.

As SEO Specialist at Technosport — an Indian activewear brand with an online store and a retail network — I handled SEO for its move from Shopify to a custom-built platform, on the same domain.

My role
SEO strategy, migration planning & QA
Brand
Technosport · activewear e-commerce
The move
Shopify → custom platform, same domain
Development
Product / development team
01ContextWhy this mattered

The situation

I look after SEO for Technosport’s online store: category and page optimisation, keyword research, content planning, metadata and headings, internal structure, schema, sitemap, image SEO and store-location pages.

Then the store moved off Shopify onto a platform built by Technosport’s own product and development team. The domain stayed the same — but almost everything underneath it changed: URL structures, how pages are generated, how products are discovered.

Why it was risky

Search engines carry years of history attached to the old pages. If old URLs simply disappear, the links and rankings attached to them go too — and shoppers who land on a dead page leave.

Missing redirects, a stale sitemap, lost structured data or new search-parameter URLs can quietly erase visibility that took years to build, often before anyone notices.

02The workBefore → launch day → after

What the work covered

The goal: everything search engines already knew about the store should carry over to the new platform. That meant planning before launch, checking everything on launch day, and tracking issues after it — working with the developers throughout.

  1. URL map
  2. Redirects
  3. Sitemap
  4. Schema
  5. Launch QA
  6. Monitoring
Illustrative URL patterns — not the store’s actual URLs
  1. 01 · Before

    Pre-launch SEO plan

    Mapping old URLs to new ones and setting requirements for redirects, sitemap, schema, headings and content on the new platform.

  2. 02 · Before

    Redirects

    Old → new 301 redirects so existing links and rankings point to the right new page.

  3. 03 · Before

    Developer coordination

    Crawlability, indexation, URL structures, search parameters and how products get discovered on the new site.

  4. 04 · Launch day

    Launch QA

    Checking redirects, status codes, indexability, sitemap, schema and page metadata as the new site went live.

  5. 05 · After

    Monitoring

    Watching crawling, indexing and search performance after launch to catch problems early.

  6. 06 · After

    Issue tracking

    Logging technical SEO issues and following them through with the developers until resolved.

03RolesWho did what

Who did what

My part

  • SEO strategy for the migration
  • Pre-launch planning: URL mapping, redirects, sitemap, schema, headings, content
  • Launch-day QA and post-launch monitoring
  • Technical issue tracking with developers

Product / development team

  • Designing and building the new platform
  • Implementing the changes in code
04TakeawayWhat this shows

Migrations are where search visibility is most fragile — and where planning matters more than tactics.

Next case study · 02 Local searchWhen a business has many locations, discovery becomes a systems problem.
05ContactSay hello

Planning a migration?

If your site is about to change platforms, the time to plan for search is before launch. Happy to talk it through.