Replatforming a site without throwing away search equity

Replatforming protects search equity when the new urls answer the same questions as the old ones, the titles still describe those pages, and every moved address redirects. Careful website migration seo is that body of work. It is not a promise that rankings will hold, and nobody honest can make that promise.

Search systems reassess pages. A move changes what they fetch. Your job is to make the new site a clear, continuous version of the useful site you already had. Do the unglamorous map. Leave the victory lap until the pages have been recrawled and the queries you care about still show the right urls.

Start from the urls that already earn a visit

Export the addresses that matter before you choose a new url pattern. The homepage, the pages that rank or that you hope will, the products or essays people link to, and the paths printed in emails and on invoices. A complete crawl of the current site is the raw material. The priority list is shorter: pages with impressions, pages with links from other sites, and pages a customer would notice if they broke.

Give each of those a fate. Keep the path. Move it, with a redirect. Or retire it, because the offer is gone, and redirect to the closest page that tells the truth. "We will figure the urls out in the theme" is how equity gets misplaced. The map is a spreadsheet with three columns: old address, new address, and the reason.

Match the pattern of the old paths when you can. A product that lived at a stable, readable url should not move to a hash of a database id because the new platform defaults to one. Readable paths are easier for people and easier to redirect. Change a path when the old one is misleading, not when it is merely unfashionable.

If a page will be merged into another, say so in the reason column. Two old essays that become one guide need both old addresses to land on that guide. One of them landing on the homepage is how a specific query starts to feel abandoned.

The new page has to answer the same thing

A redirect preserves the chance to arrive. The page at the end has to deserve the arrival. If the old url explained your pricing and the new url is a brand film, you have kept the address and thrown away the answer. People bounce. Search systems have less reason to treat the new page as a substitute.

Put the same facts on the new page, rewritten as clearly as you can. The offer, the proof, the way to talk to you, the product details that made the old page useful. Google's helpful-content guidance is the standard for this rewrite. It asks you to create people-first content, the kind an existing audience would find useful if they came to you directly. It also warns against removing a lot of older content mainly because you hope a site will seem fresh. Freshness theater is a bad migration plan. Keep what is still true. Improve what is clumsy. Retire what is false.

SEO, in Google's own words on that page, is a set of things you do so search engines can discover and understand content. It helps when it is applied to people-first pages. A migration that exists to manipulate rankings, stuffed with repeated queries, is the approach that guidance tells you to walk away from. Write the page for the person who had the old one bookmarked.

Read the old page and the new page side by side for the top twenty urls. Highlight any fact that disappeared. If the fact still matters, put it back before you launch. If it is obsolete, make sure the redirect target says what replaced it.

Titles that still describe the page

Google's documentation on title links explains that the title is often the main clue a person uses to choose a result. Every page needs a title element. The text should be descriptive and concise. Vague titles, keyword stuffing, and boilerplate that makes every page sound identical are named problems. During a replatform, those problems show up because a template stamps "Home" or the brand slogan onto every url.

Write titles in the same pass as the redirect map. The homepage can carry the brand and a plain description of what you do. An inner page should say which page it is. Product pages should say the product. If Google has to invent a title because yours is empty, repeated, or unrelated to the visible heading, you have made the result harder to trust.

Keep the visible heading and the title in agreement. A page whose large heading says one thing and whose title says another gives search systems a reason to pick for you. Pick first. Use the language of the page, not a translation invented for a keyword list.

Avoid stuffing the primary query into every title on the site. One clear description per page is stronger than a chorus. The person scanning results needs to tell your pages apart. So do you, six months later, when you read the report.

Redirects, then a watch

Implement redirects on the host that will serve the domain, and test them before DNS moves. An old product url should return a single hop to the new product url. Chains, loops, and redirects to the homepage are defects. Soft 404s, where a missing page smiles and returns a 200, are defects too. The server should say the page moved, and the browser should land on the thing.

Open the priority list by hand. Then sample the long tail. Check the links in the last few newsletters and the urls on your Google Search Console export if you have one. Internal links in the new templates should point at the new addresses, not at redirects. Redirects are for the outside world and for old habits. The new site should be internally direct.

After launch, watch the queries you already had. Look for a rise in 404s, a drop in impressions on a specific url, and any title Google rewrote. Fix the map when you see a miss. Give the process weeks, not an afternoon, before you judge it. Recrawling takes time, which Google notes when it describes how title and page changes get picked up.

Do not announce that rankings were preserved. Announce that the old addresses resolve, the titles describe the pages, and the answers people came for are still there. That is the work. The rankings are an outcome you measure later.

A store move adds checkout to this list. The sequence for keeping payments intact while the domain changes is in migrating a store without a week of broken checkout.

If the replatform is really a new site that has to stay findable, the design and the build belong in one scope. See Hanabi's services for how the studio takes on marketing sites and storefronts, including the mapping work that keeps the useful pages in reach.