Redesigning a real estate site without losing Google: the sold-listing redirect problem

Search “redesign my site without losing my SEO” and you'll get about fifteen pages saying the same six things: inventory your URLs, map one-to-one 301 redirects, rebuild your sitemap, check robots.txt, watch Search Console, keep your internal links. It's correct advice. Innotia's migration checklist, to pick the most thorough one I actually read, lays it out in three clean phases with tables and diagrams, and I have nothing to add to it.

Except that it — like every other page on that first results screen — is written for a site whose pages stay. A corporate site with twelve pages, a manufacturer with a product catalogue that changes twice a year. Read the fine print on that Innotia checklist and it says so plainly: it's aimed at industrial SMEs, at stable institutional content.

A real estate agency site is the opposite kind of animal. Most of its indexed URLs are listings, and a listing has a lifespan. Six months, eighteen months, and then the property sells and the URL has no equivalent on the new site. Not a moved equivalent — no equivalent at all. The canonical rule that every one of those fifteen pages is built on simply doesn't apply to the majority of your URLs.

Nobody in that results page addresses it. The only two pages specifically about real estate redesign that showed up are sales pages, not methods. So here's the method.

The generic part: already covered, not rewriting it

URL inventory, one-to-one 301s for pages that still exist, sitemap regeneration, robots.txt sanity check, Search Console property set up before launch rather than after, internal links pointing at final URLs instead of chains of redirects.

Do all of it. Fifteen agencies explain it well and for free, and re-explaining it here would just make this article the sixteenth. That part of your migration is a solved problem, and if your provider doesn't do it you have a provider problem, not a method problem.

The rest of this article is about the part none of them solve.

Why “redirect to the equivalent page” breaks on an agency site

Here's the shape of the problem. Your old site has, roughly:

• A dozen structural pages — home, buy, sell, rent, valuation, about, contact, maybe a blog.
• Some city or neighbourhood pages, if you were well advised.
• And then hundreds, sometimes thousands, of listing URLs. Some pointing at properties still on the market. Most pointing at properties you sold years ago and that have been quietly 404-ing ever since, or worse, still sitting there online.
• Plus a long tail of search-result URLs with parameters — ?type=house&city=…&page=3 — that got indexed because nobody told them not to.

The one-to-one rule handles the first two buckets and nothing else. For the third, “redirect to the equivalent page” is a question with no answer, because the answer is the property doesn't exist anymore.

This exact problem has been solved on the e-commerce side. Deleted products, discontinued references, out-of-stock forever — the standard playbook is a 410 for a permanent removal, a 301 to the closest live category when the URL has earned something worth keeping, and a properly designed 404 for the rest. WebRankInfo has a whole dossier on it. It's mature, it's well argued, and nobody has transposed it to real estate, where the granularity is different: not “category,” but city, property type, price band, sold-but-still-a-reference.

That transposition is the whole job. Here it is.

One test, then the tree

The test that decides every branch:

Would the person whose search landed on that old URL be served by the page you're sending them to?

A visitor who searched something like 3-bedroom house with garden, Montigny-le-Tilleuland landed on a property you've since sold is served by your Montigny house listings page. Same intent, live inventory, they can keep going. That's a legitimate 301.

That same visitor is notserved by a shared “this property has been sold” page, and is served even less by your home page. Sending hundreds of dead listing URLs to one generic destination is the pattern Search Console has an entire report for — soft 404. You get the maintenance cost of a redirect table with none of the benefit.

So: redirect to a page that answers the same question, or don't redirect at all.A 410 is not a failure. It's you telling the index, honestly, that this thing is gone — which is true.

The decision tree for listing URLs

Four rules make that table usable on a real catalogue.

1. The reference number is your join key.Your old listing URLs almost certainly contain the property's reference or ID — /bien/12345-maison-charleroi, or in the ugly cases ?id=48213. So will the new ones, because both are generated from the same CRM feed. Extract that reference on both sides and you can generate most of the map automatically instead of writing hundreds of lines by hand. If your provider tells you the mapping has to be manual, they haven't looked at the feed. This is also the first thing to check when you pick a provider at all — the short version is that the feed decides how much of your migration is a script and how much is data entry.
2. Set the threshold for individual treatment, and measure it — don't guess. My cutoff: a listing URL gets its own line in the map if it has at least one referring domain, or at least one organic entry logged in the last 16 months(Search Console's full window). Everything below that threshold gets a bulk rule by folder pattern. On most agency catalogues the individually-treated URLs are a small minority — but you have to export the data and count, because “small minority” of three thousand URLs is still a real list, and the one listing a local newspaper linked to five years ago is in it.
3. Handle the boomerang before it happens, not after.A property comes back on the market. You already 301'd its old URL to a city page — now you have a redirect pointing away from a live listing. The fix is architectural: keep the redirect table as data in the CMS, keyed on the property reference, not as lines in an .htaccess or an nginx config that nobody wants to touch. Then republishing reference 12345 automatically drops its redirect and restores a 200. If your provider hard-codes the redirects into server config, ask them out loud what happens in six months when a sale falls through. The answer tells you a lot.
4. Your sitemap is a live catalogue, not an archive. Generate it from live listings plus structural pages only, and make sure lastmod actually changes when a listing changes — a lastmod that updates on every regeneration is noise. If you want to speed up discovery of the redirects, a separate, temporarysitemap of the old URLs for the migration window is legitimate. Put a removal date on it — thirty days — and actually remove it. Otherwise you've built a permanent monument to pages that don't exist.

The part where you touch SEO thinking you're only touching design

A migration plan that only covers URLs misses the other half of what a redesign does.

The single detailed audit I have of a Belgian agency site is Etimo, in Charleroi — sixty-plus years in business, certified reviews, a wide catalogue. Its home page H1 is the word “Accueil.”“Home.”

Fixing that is obviously right. It's also not a design change. The home page is the page with more internal links pointing at it than any other page on the site — every logo in every header links there. Rewriting its H1 from a navigation label to an actual positioning line changes the most-referenced page on the whole site, on the same day you change the URL structure, the templates, the internal linking, and the page speed profile.

That's not an argument for leaving “Accueil” alone. It's an argument for writing it down. Before/after H1s, titles, and meta descriptions for your top twenty pages belong in the same document as the redirect map, for one boring reason: if something moves after launch, you need to know which change moved it. Otherwise you spend a month arguing about a redirect that was fine while the real culprit sits in a template.

Honest note on evidence:this is a practitioner's method, not the report of a migration I measured. I have no before/after Search Console data to show you — no real estate site I've rebuilt has been through a documented migration with published traffic curves, and I'm not going to pretend otherwise. What's first-hand here is the structure of the problem, from audits of real agency sites and their listing catalogues, and the reasoning behind each branch of the tree, which you can evaluate on its own merits. You'll also see numbers circulating on this topic — a percentage of traffic you'll supposedly lose, a number of days to recover. I ran into several while researching this, on agency pages selling migration services. I'm not repeating any of them, because I can't verify a single one.

The document to ask for before you sign

You don't need to build this yourself. You need to make sure it exists, in writing, before the project starts — because after launch it's forensics.

1. Ask for the URL inventory as a deliverable, not as a promise.An actual export of every indexed URL, before any code is written. If a provider can't produce it in week one, they won't produce it in week six.
2. Ask what happens to sold listings, specifically.Use the words. If the answer is “we'll redirect everything,” or “we'll set up 301s,” ask which target, for which property status. A provider who has done this on a real estate site will have an opinion about city pages versus 410s. One who hasn't will say “we'll redirect everything to the home page.”
3. Ask where the redirect table lives. CMS data keyed on the property reference, or server config? See rule 3 above — this is the question that decides whether your site survives a property coming back on the market.
4. Ask for the before/after table of H1s, titles and meta descriptions for your twenty most-visited pages. It costs an afternoon and it's the only thing that lets you diagnose a post-launch drop.
5. Ask who is watching, and for how long.D-1 (crawl the old site, freeze the inventory), D+1 (crawl the new one, check every redirect resolves in one hop and returns the status you decided), D+30 (Search Console coverage report, redirect chains, 404s that shouldn't be there). Put the three dates in the contract.
6. Get it before you compare prices.Two quotes for the same redesign aren't comparable if one includes a migration plan and the other includes the sentence “SEO-friendly.” I wrote about how quotes diverge by budget in an earlier piece on real estate website pricing — this line item is one of the biggest silent differences between them.

That's the whole argument for doing the redesign instead of postponing it again. Yes, a badly executed migration can cost you traffic you spent years earning. The answer isn't to keep a site with an H1that says “Accueil” and no visible CTA — a problem I took apart in detail in an earlier teardown of a 40-year-old Belgian agency's site. The answer is to make the plan a contractual deliverable before anyone opens a design tool.

Hamza Benjaaba

Web designer and no-code developer, specialized in websites for real estate agencies and local service businesses. What's first-hand in this article: the audits of real agency sites behind the Etimo example and the structure of the listing-catalogue problem. What isn't: measured before/after migration data, which I don't have and don't claim. The decision tree is my working method, published so you can argue with it — or hand it to whoever is quoting you.