A redesign is the one website project that can make everything look better and still cost you money. The new site launches, the team is pleased with it, and six weeks later the owner inquiries have thinned out and nobody can say exactly when it started. The design was never the problem. What broke was the quiet infrastructure underneath it: the URLs, the redirects, and the accumulated credit your old pages had earned with Google.

Most migrations take far longer to recover than anyone budgets for
SALT.agency published a study in June 2026 covering 1,052 domain migrations, drawn from its own client work plus crowdsourced data from the wider SEO community. Recovery was defined strictly: the point at which the new domain's monthly organic traffic matched or beat the old domain's pre-migration baseline, measured against a six-month rolling average taken just before the drop.
The results are sobering. Only 22.8 percent of migrations had recovered by day 90. By six months the figure was 35.4 percent, and it took a full year to reach 59.5 percent. The median recovery took 304 days and the mean was 489. A footnote to the dataset records that 13.9 percent of the migrations studied still showed no full recovery signal after three years.
Read that against how these projects are usually sold internally. The redesign is scheduled around a rebrand or a busy leasing season, the launch date is the milestone everybody tracks, and the implicit assumption is that traffic returns within a few weeks. For roughly two thirds of migrations, it does not. Planning for a one-month dip when the median is ten months is how a redesign turns into a year of quietly reduced lead flow.
What migration recovery actually looks like
22.8%
Of domain migrations had recovered pre-migration organic traffic by day 90
304 days
Median time to recovery across the dataset, with a mean of 489 days
54.1%
Of converted owner leads come from Google Search and the Map Pack, the channel a migration puts at risk
Sources: SALT.agency domain migration study, 1,052 migrations, published June 2026; Goodjuju 2026 property management lead source report, 31 companies and 1,975 converted owner leads tracked from February to May 2026.
Property managers are betting a bigger share of the business
For most industries a migration dip is a marketing problem. For property management it lands directly on owner acquisition, which is the revenue that compounds. Goodjuju tracked 1,975 converted owner leads across 31 property management companies over a 90 day window in 2026 and found that 54.1 percent came from Google Search and the Map Pack, with the wider Google ecosystem including direct and Maps traffic accounting for 88.4 percent.
That concentration cuts both ways. It is why local search is worth investing in, and it is also why a botched migration is not a partial loss. If nearly nine in ten of your owner leads arrive through one company's index, disrupting how that index understands your site is close to an all-eggs event. A renter lead lost today is one unit. An owner lead lost today is a management contract you do not sign, and the fees you would have collected on it for years.
There is a second complication specific to this industry. A property management website is rarely one site. It is usually a marketing site on your domain, a listings section generated by your software, an application flow that may live somewhere else again, and a resident portal on a vendor subdomain. A redesign that only considers the pages your designer touched will leave three quarters of your actual URL footprint unmapped.
Where property management redesigns break
The failures are consistent and none of them are subtle once you know to check. They are missed because the person testing the new site is looking at the homepage, not at the long tail of URLs that were quietly earning rankings for four years.
| What breaks | Why it happens | The fix |
|---|---|---|
| City and neighborhood pages dropped | The new design has no obvious slot for them, so they are cut rather than rebuilt | Rank pages by entrances before deciding what to remove |
| Listing URLs change wholesale | A new software integration generates a different URL pattern for every unit | Map the pattern, not each unit, and redirect at the rule level |
| Blog archive left behind | Content is treated as disposable because it does not generate leads directly | Migrate posts with their URLs intact, or redirect one to one |
| Redirect chains three and four deep | This is the third redesign, and each one layered rules on the last | Collapse every chain so old URLs point straight at the final target |
| Portal and application links break | Those URLs live on a vendor subdomain nobody included in the audit | Inventory every subdomain and vendor destination before launch |
| Staging site left indexable | The build blocked crawlers and the block shipped to production with it | Check robots rules and noindex tags on the live site day one |

What Google actually asks for, including a change made in June 2026
Google publishes specific instructions for site moves, and they are short enough that there is no excuse for guessing. Use server-side permanent redirects, meaning a 301 or 308 status code, and keep them in place for as long as possible, generally at least a year. Keep redirect chains short, ideally no more than three hops and fewer than five. For small and medium sites, move every URL at once rather than section by section. Update your internal links to point at the new URLs directly instead of relying on the redirects to do it. Submit the new sitemap in Search Console once you have launched.
The Change of Address tool is narrower than most people assume. It applies when you move from one domain or subdomain to another. You do not need it for an HTTP to HTTPS move, for switching between www and non-www on the same domain, or for changing paths within a domain you already own.
Google updated this documentation on 17 June 2026 with a clarification that matters a great deal in this industry. Operators are now told to submit Change of Address requests for all subdomains and both the www and non-www variants of the old domain, even if those variants are not actively in use, and to verify every variant of both the old and new sites in Search Console before starting. The reason is that without it, Google may keep indexing old variant URLs alongside the new destinations, splitting the migration signal and slowing the transfer. Property management companies, who tend to run listings, portals and applications across several subdomains, are exactly the operators this gap was catching.
On timing, Google is honest that disruption is normal. Any significant change produces ranking fluctuations while the site is recrawled and reindexed, and for a medium-sized site it can take a few weeks or more before the new URLs consistently replace the old ones in results. Larger sites take longer. That is the floor, not the expectation.
The part nobody remembers: your local footprint
If the Map Pack is carrying half your owner leads, the redesign is not finished when the site is live. Your Google Business Profile carries a website field pointing at a URL that may no longer exist. So do your listing portal profiles, your directory entries, your social profiles, and any local citation built over the years. Every one of those is an external link into a page you just changed.
Redirects will keep those links working, which is why this rarely shows up as a broken page and instead shows up as a slow, unexplained decline. The goal is consistency: your Business Profile, your website, your structured data and your major citations should all describe the same business at the same addresses. Update them deliberately rather than waiting to see whether anything breaks, because the failure mode here is silent.
Seven steps for a redesign that keeps its rankings
Export every URL before you touch anything
Crawl the current site, then pull Search Console and analytics data for the last twelve months. You need the full inventory including listings, portal links, PDFs and old campaign landing pages, not just the pages in the navigation.
Rank those URLs by what they earn
Sort by organic entrances, conversions and referring domains. This is the list that decides what gets rebuilt, what gets merged and what can genuinely go. Deleting a page nobody visits is housekeeping. Deleting a city page ranking third is a self-inflicted wound.
Write the redirect map before the design is signed off
Every old URL gets a destination, and the destination should be the closest equivalent page rather than the homepage. Mass redirects to the homepage are treated as soft 404s and transfer nothing.
Verify every domain variant in Search Console first
Old and new, www and non-www, and each subdomain your listings, portal or application flow uses. Do this before launch so the Change of Address submissions can go in for all of them.
Test the redirects on staging, then again on launch day
Confirm each rule returns a 301 or 308 and lands in one hop. Collapse any chain left over from previous redesigns. A redirect that works but takes four hops is a redirect that is losing you something.
Update your local footprint the same week
Google Business Profile website field, listing portal profiles, directories, social links and structured data. These are the external references pointing into your site, and leaving them stale undercuts the channel that produces most of your owner leads.
Monitor for a year, not a fortnight
Watch indexed pages, crawl errors, organic entrances by page and owner lead volume weekly at first, then monthly. Given a median recovery of 304 days, the useful comparison is against last year rather than last week, and the redirects stay in place throughout.
The bottom line
A redesign is not a design project with some technical work attached. It is a migration with a new look on top, and the migration is the part that decides whether the investment pays back. Fewer than a quarter of domain migrations recover within 90 days, the median takes about ten months, and a meaningful share never fully recover at all. Property managers carry more exposure than most because Google search and maps deliver the overwhelming majority of owner leads, and because a typical property management site is spread across subdomains that redesign projects routinely forget. None of this is an argument against rebuilding a site that deserves it. It is an argument for treating the URL inventory, the redirect map and the Search Console setup as launch requirements rather than cleanup tasks. Do that work first and the new site keeps everything the old one earned.


