Migrate your product catalogue without losing your rankings
Website Migration + Technical SEOWe move products, images and specifications off your current website builder into WordPress or whichever platform actually fits the job, with URL mapping, per-URL 301 redirects, canonical tags, sitemaps and Search Console checks both before and after launch.
Migrating a site means migrating its rankings, not just its looks
What this service isA catalogue site with a few thousand products usually has several thousand URLs once you count categories, filters and paginated listings. Every one of those paths that people have found through search is an asset built up over years, which is why an unplanned migration can cost a business a decade of traffic in a single week.
This work starts with a plan, not a design. The first step is crawling every URL on the existing site, establishing which pages hold traffic and rankings, and mapping each old path to its new destination. Only then do we migrate the product data and images, set canonical tags and sitemaps against the new structure, and verify everything before go-live.
The job does not end at launch. We keep reviewing Search Console weekly to see how many new pages Google has indexed, whether any 404s slipped through, and where redirects are stacking up — fixing each one as it appears and comparing against the baseline recorded beforehand, so it is clear exactly when rankings have come back.
What the engagement covers
ScopeAll of this sits in one engagement — you do not need to hire a migration team and an SEO team separately.
Which systems can we migrate from
Supported sources- Closed website builders you cannot export your own data from
- Storefronts on hosted marketplace platforms, when you want a site of your own
- Existing WordPress sites whose product data structure has become unworkable
- Hand-written PHP or HTML sites left without anyone to maintain them
- ERP systems or Excel files that are the real source of product data
- Sites already migrated once that lost rankings because redirects were incomplete
If your current platform has no export function, we collect the data from the live pages systematically and convert it into a structured table before import, reconciling the counts against the real totals.
Why it should be a technical SEO team
What sets this service apartA technical SEO team first, a web team second
Audits and technical fixes are our day job, so a migration starts from an SEO plan rather than from a design that has to be retrofitted for rankings later.
Comfortable with thousands of URLs
A catalogue with over a thousand products usually has several thousand URLs once categories and filters are counted. We handle that with mapping tables and scripts, not by clicking through pages one at a time.
Everything is tested before go-live
Before the switchover we request every old URL to confirm it lands on the right destination, with no redirect chains and nothing left unmapped.
The destination platform fits the job
A catalogue that does not sell online is usually well served by WordPress with custom post types. WooCommerce comes in only when you genuinely transact. We do not push an oversized system you then have to pay to maintain.
Product data you can actually reuse
Data is structured into real fields — codes, specifications, categories, document files — instead of one blob of text, so filtering, search and exports remain possible later.
Delivered with evidence
You receive the URL mapping table, the results of the redirect test run, and Search Console figures from before and after, so you can verify what moved and what was intentionally retired.
How the migration runs
ProcessEvery stage produces something you can inspect, not just a description of what happened.
Survey and baseline
We crawl every URL on the current site, count products and categories, identify which pages hold traffic and rankings, and record Search Console figures as the baseline.
Migration and URL plan
We choose the destination platform, design the new URL structure, build the mapping table line by line, and agree which pages get merged and which get retired.
Data migration and build
Products, images and descriptions are imported on a staging environment, with titles, descriptions, canonical tags and product structured data all in place.
Pre-launch verification
We request every old URL to verify its destination, reconcile product counts, look for missing images, check speed, and rehearse the switchover.
Go-live and sitemap submission
We switch over in the agreed window, enable the redirects, submit the new sitemaps, and ask Google to crawl the priority pages first.
Monitor and fix after launch
We review Search Console weekly, fix 404s that slip through, clear redirect chains, and report progress against the baseline.
What you receive
Deliverables- A new site with the full product count agreed during reconciliation, images and descriptions all carried over
- The complete old-to-new URL mapping table, in a file format you can open and check yourself
- Per-URL 301 redirects actually in place, with the test-run results for every path
- Titles, meta descriptions, canonical tags and product structured data on every page
- Sitemaps split by page type and submitted to Search Console
- A pre-migration baseline report plus follow-up reports on the agreed schedule
- A guide to adding and editing products in the new system, plus one live training session
Risks you should know about first
Written honestlyA migration always carries risk. Our job is to make that risk as small and as predictable as possible.
1. Ranking fluctuation early on is normal
After a migration Google has to recrawl every new URL, so rankings and traffic typically move around for the first two to eight weeks. What actually matters is whether they return to the previous level or better after that.
2. Messy legacy data adds work
If the existing product data has duplicate codes, inconsistent naming or missing images, it has to be cleaned before import. That effort is quoted against what we actually find during the survey.
3. Some closed platforms are hard to export from
Several closed website builders have no complete export. In those cases we collect the data from the live pages directly, which works but takes noticeably longer.
4. Filter and pagination URLs need a plan
Catalogue sites generate large numbers of filter URLs. Moving them all across without thinking produces heavy duplication, so we decide together which pages to keep, which to canonicalise and which to keep out of the index.
5. The switchover window has to be agreed
The cutover should happen during a low-traffic period, with immediate access to whoever controls the domain and hosting in case something needs reversing.
Suitable for
- Product catalogue sites from a few hundred up to tens of thousands of SKUs
- Businesses that already rank well and cannot afford to lose that in the move
- Companies locked into a closed website builder who want to own their site
- Sites that already migrated once, lost rankings, and need it done properly
- Marketing teams who want product data they can build new pages from
Not suitable for
- Projects that only want a redesign and are not concerned with URLs or existing rankings
- Migrations that have to happen within a few days with no time for verification
- Highly complex commerce logic such as per-customer contract pricing, which belongs in a software project scope
Services that often run alongside
Work we handle in-houseHand-coded site to WordPress 100%
When the destination is a WordPress site your team can edit on every page. From 2,500 THB.
Custom WordPress plugin development
Product import routines, catalogue filters or an ERP connection, written as your own plugin. From 999 THB.
WordPress development
When the destination is a WordPress site your own team can edit on every page, without touching code.
Custom development
Product import routines, catalogue filtering or an ERP connection can be built as purpose-made software for your setup.
Technical SEO audit
Not migrating yet, but want to know where the current site is losing opportunities? Start with an audit.
Frequently Asked Questions
FAQWe have over 1,000 products. Can you migrate that, and how long does it take?
Will our rankings drop after the migration?
Why per-URL 301 redirects? Can't everything just point at the homepage?
Does it have to be WordPress?
Can you extract data from a system with no export button?
We have a huge number of filter and pagination URLs. What should we do with them?
How long do you monitor the site after launch?
How much does it cost?
Send us the current site and we will survey it first
Tell us the URL, the approximate number of products and the platform you are on now. We will work through the URL structure and come back with what the migration plan should look like, how long it takes, and where the risks sit.