
If your realtor site is simply changing hosts with no URL changes, you can skip most of the heavy redirect work: just test the new setup, switch DNS, and monitor both hosts. If your URLs are changing (new domain, new platform, new folder structure), treat this as a full migration: inventory everything, confirm you control your domain registrar and Search Console, then build a redirect map before you touch anything else.
TL;DR:
- For a hosting only move, keep every public URL unchanged, test the new host, switch DNS, monitor both hosts, and skip Change of Address.
- For URL changes, map indexed pages and pages that earn clicks or leads to specific new equivalents, using direct 301 or 308 redirects.
- Coordinate IDX redirect patterns with your provider, preserve listing IDs, and test saved searches, alerts, and CRM lead capture on desktop and mobile.
- Compare organic landing page traffic week over week, and investigate dips that persist beyond four to six weeks or rising crawl errors.
- Keep permanent redirects live for at least six to twelve months; Google recommends a year or longer to cover search engines, bookmarks, and backlinks.
Table of Contents
- Your step-by-step migration plan from prep to launch
- Redirects explained: which codes to use and how to implement them without losing SEO
- Hosting-only moves vs URL changes: picking the right workflow
- Domain transfers and registrar rules: AuthInfo, FOA, and the 60-day lock
- IDX and MLS listing URLs need their own migration policy
- Testing, launch, and what to check in the first weeks after
- Monitoring and verifying signal transfer after launch
- Communicating migration plans and updates to clients and stakeholders
- Handling SEO for multilingual or multi-regional realtor sites
- How migration affects your local search rankings, and how to protect them
- Overview: what a messy migration taught us about moving fast without breaking leads
- How we help with realtor website migrations
- FAQ
- Sources
Your step-by-step migration plan from prep to launch
A realtor website migration rewards agents who move in order, not in a hurry. Skipping steps is how a brokerage loses three years of ranked listing pages overnight.
Start with a full inventory. Before anyone touches code or DNS, confirm you control, or know who controls, every account tied to your site:
- Domain registrar login and the account email tied to it
- DNS management (sometimes separate from the registrar)
- Google Search Console and Google Analytics
- Tag manager and any pixel or tracking scripts
- CRM forms and their webhook or API connections
- Ad accounts (Google Ads, Meta) linked to the site
- Call tracking numbers and their routing rules
Losing access to even one of these during a vendor switch is the single most common cause of a migration turning into a multi-week outage, according to Google’s hosting move guidance, which calls out account access as the main risk factor in site moves.
Next, decide what kind of move you are actually making, and write the decision down. A hosting-only move keeps every public URL identical. A URL or domain change means your pages will live at new addresses, which triggers a very different set of steps. Confusing the two is where most agents and even some web vendors go wrong.
Once you know your migration type, crawl the current site with a tool like Screaming Frog or Sitebulb, then pull your last 12 months of landing-page data from Google Analytics and Search Console. Cross-reference the two lists. You want every indexed page, every page earning organic clicks, and every page a lead has ever come through, not just your main navigation.
From that combined list, build a redirect spreadsheet mapping every old URL to its new equivalent, one row per URL, no guessing. Then:
- Stand up a staging environment and block it from search engines with a robots directive or password wall.
- Test every form, every CRM webhook, every IDX search widget, and your phone tracking on staging.
- Verify HTTPS and canonical tags are correct on the new build.
- Push your redirects or flip DNS during a low-traffic window, typically late evening or a weekend.
- Verify the new property in Search Console and submit your updated sitemap.
- Monitor crawl stats, 404 reports, and lead form submissions daily for the first two weeks.
Keep your redirects live for a substantial period, and watch your organic traffic and Search Console data closely during that window for anything that looks like a missed mapping.
Redirects explained: which codes to use and how to implement them without losing SEO
Use a 301 or 308 redirect for anything permanent, and reserve 302 or 307 for anything genuinely temporary, like a short maintenance window. Google’s guidance on moving a site with URL changes confirms permanent redirects don’t cause a loss in ranking signal, but the mapping has to be precise and direct.
That precision matters more than most agents expect. A redirect from an old listing page straight to your new homepage technically “works,” in that visitors land somewhere, but it tells search engines the old page’s relevance doesn’t map to anything specific, and you lose the accumulated signal that page had built. Google’s own documentation is explicit that direct, one-to-one mapping between old and new URLs preserves more value than funneling everything to a generic landing page.
Redirect chains cause a similar problem. If Page A redirects to Page B, which redirects to Page C, each hop adds latency and risk, and some of the signal gets lost along the way. The fix is simple: always redirect straight from the original URL to its final destination, never through an intermediate stop.
- 301 or 308: permanent moves, the default choice for any real estate URL that’s changing for good
- 302 or 307: temporary situations only, such as a short A/B test or scheduled maintenance page
- Avoid chains: redirect A directly to C, never A to B to C
- Test every redirect with a tool like Screaming Frog or a browser’s network panel before calling the migration done
Implementation depends on your hosting setup. On Apache, redirects typically live in an .htaccess file. On Nginx, you’ll write rules into the server block. Many realtor website platforms and CDNs, including Cloudflare, offer a redirect rules panel that avoids touching server config directly, which is often the safer path for agents without a developer on call.
Pro Tip: Export your final redirect map as a spreadsheet and keep it permanently. You’ll need it again the next time you migrate, and it’s the fastest way to explain to a new web vendor exactly what moved where.
Hosting-only moves vs URL changes: picking the right workflow
These two scenarios get mixed up constantly, and picking the wrong workflow wastes time or breaks things that didn’t need to break.
A hosting-only move means your URLs stay exactly the same. You’re switching servers, maybe switching your web host or platform backend, but yoursite.com/listings/123-main-st still resolves to the same address. Google’s documentation for moves with no URL changes treats this as primarily an infrastructure task: test the new host thoroughly, change your DNS, then monitor both the old and new hosting environments until you’re confident both users and Googlebot are reliably hitting the new site. You don’t need the Change of Address tool here, because nothing about the URL structure changed.
A URL or domain change is a different animal entirely. Your addresses are shifting, whether that’s a brand-new domain, a platform switch that restructures your slugs, or folding a second site into your main one. Here you need the full redirect map built from your crawl and analytics data, server-side permanent redirects implemented and verified, and once those redirects are live and confirmed working, the Change of Address tool in Search Console set up to tell Google the domain itself has moved.
- Hosting-only: test infrastructure, flip DNS, monitor both hosts, skip Change of Address
- URL change: build redirect map, implement 301/308s, verify, then run Change of Address
- Either path: never shut down the old environment until the new one is confirmed stable for at least a couple of weeks
Mixing these up, running Change of Address when nothing actually moved, or skipping redirects because “it’s just a hosting switch” when your URLs did change, is where otherwise careful migrations go sideways.
Domain transfers and registrar rules: AuthInfo, FOA, and the 60-day lock
Moving your domain to a new registrar, separate from moving your website’s hosting, runs on rules set by ICANN’s transfer policy, and skipping a step here can lock you out of changes for weeks.
You’ll need an AuthInfo code from your current registrar, essentially a password that proves you own the domain and authorizes the transfer. Your new registrar will also require a Form of Authorization, a standardized confirmation step ICANN mandates before any transfer can complete.
- Request your AuthInfo code directly from your current registrar’s account panel or support team
- Unlock the domain and disable privacy protection temporarily if either is blocking the transfer
- Complete the Form of Authorization promptly; delays here are the most common reason transfers stall
One detail trips up a lot of agents: ICANN’s policy imposes a typical 60-day inter-registrar transfer lock after a Change of Registrant, meaning if you update the ownership contact on a domain, you generally can’t transfer it to a new registrar for 60 days afterward. Plan your ownership updates and registrar moves in the right order, or you’ll be stuck waiting it out.
IDX and MLS listing URLs need their own migration policy
Listing-detail pages aren’t like your other content, and treating them the same way during a migration is a fast way to break lead flow.
Most IDX and MLS listing pages are feed-generated, meaning they’re created dynamically from a data feed rather than hand-built, and they can number in the thousands even for a single agent site. A blanket redirect from every old listing URL to your new homepage isn’t just lazy, it actively damages the signal those pages built. Instead, you need a pattern-based mapping policy, coordinated with your IDX provider, that preserves the URL structure or redirects by listing ID rather than guessing page by page.
- Map listing URL patterns with your IDX provider rather than redirecting each page individually
- Never mass-redirect listing detail pages to your homepage or a generic search page
- Confirm saved searches and alert emails still point to working URLs after launch
- Test lead capture from an IDX listing page through to your CRM on both desktop and mobile before going live
Pro Tip: Run a test inquiry through an actual IDX listing page the day before launch and confirm it lands in your CRM within minutes. This single check catches more migration failures than any redirect audit.
Testing, launch, and what to check in the first weeks after
A realtor site migration isn’t done at launch. It’s done when you’ve confirmed, with data, that leads are still arriving the way they used to.
Before launch, crawl your staging site and compare it against your pre-migration crawl. Test every form, confirm CRM routing fires correctly, verify your HTTPS certificate is valid, and double-check that staging’s noindex tags or robots blocks are documented so you remember to remove them.
- Push your redirects or switch DNS during a low-traffic window
- Submit your updated sitemap in Search Console immediately after launch
- Verify the new site is being crawled by checking Search Console’s crawl stats report
- Monitor your 404 report daily for the first two weeks and patch any missed redirects
- Keep redirects live for at least six to twelve months. Google recommends maintaining them for a year or longer to give users and search engines time to fully transition.
For a longer-term maintenance rhythm once the dust settles, a weekly maintenance routine catches small issues before they become ranking problems.
Monitoring and verifying signal transfer after launch
Watch four things closely: organic traffic to your key landing pages, impressions and clicks in Search Console, redirect hit counts in your server logs, and crawl error reports.
A short-term dip in the first one to two weeks is normal and expected as search engines recrawl and reprocess your new URLs. What’s not normal is a dip that persists past four to six weeks with no recovery trend, or a crawl error report that keeps growing instead of shrinking.
- Organic landing-page traffic: compare week over week, not day over day, for a clearer trend
- Search Console impressions and clicks: watch your top 20 pre-migration pages specifically
- Redirect hit counts: a page getting zero hits that used to get traffic signals a broken or missing redirect
- Crawl errors: a spike that doesn’t shrink within two weeks usually means a mapping gap, not a temporary blip
Most persistent problems trace back to one of two causes: a missed redirect in the original map, or a canonical tag pointing to the wrong URL. Both are fixable within a day once you spot them, which is exactly why daily checks in week one matter more than any other step in this plan.
Communicating migration plans and updates to clients and stakeholders
A website migration isn’t just a technical project, it’s a trust project, especially if you’re part of a team or brokerage where other agents and staff rely on the same site for leads.
Tell your team and any active clients what’s changing before it changes, not after something breaks. A short heads-up, even one paragraph, that explains the site will be briefly updated and that saved searches or bookmarks might need refreshing, prevents a flood of confused calls during launch week.
If you run paid ad campaigns pointing to specific landing pages, loop in whoever manages those campaigns early. A landing page URL that changes without updating the ad destination burns ad spend on broken links, which is a far more expensive mistake than the migration itself.
For brokerages with multiple agents on a shared platform, a brief written timeline, even three bullet points with dates, keeps everyone aligned and reduces the chance that someone makes an unrelated change to the site mid-migration. Keep stakeholders updated again right after launch, confirming the site is live and working, and once more after the first couple of weeks once you’ve confirmed traffic and leads are stable. That second confirmation matters: it’s the moment everyone can stop watching nervously and get back to selling.
Handling SEO for multilingual or multi-regional realtor sites
If your site serves buyers in more than one language or targets multiple metro areas with dedicated pages, your migration needs an extra layer of care around hreflang tags and regional URL structure.
Multilingual and multi-region realtor sites typically use either separate subdirectories (/es/, /fr/) or regional subdomains to serve different audiences. During migration, every language or region variant needs its own entry in your redirect map, mapped to its corresponding new URL, not just the default English version. Dropping a language variant’s redirect and letting it fall back to the primary language page is a common and avoidable mistake.
Double-check your hreflang tags are carried over and correctly reference the new URLs after launch, since a broken hreflang reference can cause the wrong regional page to show up in search results for a given market. If your platform switch changes how regional pages are structured, rebuild the hreflang map from scratch rather than assuming the old relationships still hold.
Test search results manually for each language or region variant within the first week, searching from a VPN or location-spoofing tool if needed, to confirm the correct version is surfacing for each audience.
How migration affects your local search rankings, and how to protect them
Local search visibility, the map pack and local organic results that bring in the buyers actually searching in your market, is often the first thing agents worry about losing, and for good reason.
Your Google Business Profile links to your website, and if that URL changes without an update, you risk a mismatch that can quietly erode local ranking signals over the following weeks. Update your Business Profile URL the same day you launch, not days later.
Local landing pages, neighborhood guides, city-specific listing pages, and any “best neighborhoods in [market]” content tend to carry disproportionate local ranking weight relative to their traffic. Make sure every one of these pages is in your redirect map with a precise one-to-one mapping, since a generic redirect to a city hub page instead of the specific neighborhood page can quietly cost you local rankings over several weeks even while your overall traffic looks fine.
Citations and directory listings (Zillow, Realtor.com, Yelp, local chamber directories) that link to your old URLs won’t update automatically. Prioritize updating the handful that send the most referral traffic first, then work through the rest over the following month, since stale backlinks pointing to redirected pages still pass value, just slightly less efficiently than a direct link to the new URL.
Overview: what a messy migration taught us about moving fast without breaking leads
We once watched a brokerage flip DNS on a Friday afternoon, the worst possible timing, and spend a weekend fielding “the site is down” calls instead of showings. The fix was never complicated: inventory first, map every URL, launch during a quiet window. What you handle in-house versus hand to a migration-ready landing page partner usually comes down to how much time you actually have this month.
— Jason
How we help with realtor website migrations
Moving your site shouldn’t cost you a single lead, and that’s exactly the standard we hold a migration to. We handle critical parts: domain and DNS coordination, complete redirect mapping, IDX and CRM routing verification, and several weeks of close monitoring after launch to help ensure a smooth transition.
- Domain and registrar coordination, including AuthInfo and Change of Address steps
- Complete redirect mapping from a crawl and your analytics history
- IDX feed and CRM webhook testing before and after launch
- Post-launch monitoring of traffic, crawl errors, and redirect performance
If your calendar has room this month and you’re comfortable with Search Console, a DIY hosting-only move is entirely doable with the checklist above. If your URLs are changing, your listings run through IDX, or you simply can’t afford a bad week of missed leads, that’s exactly where our team steps in. Check our pricing and service packages to see which option fits your timeline and get your migration scheduled.
FAQ
Has Realtor.com changed their website?
Large real estate portals update their platforms regularly, and specific redesign details are best confirmed directly on the portal itself rather than through secondhand reports. For your own site, the migration principles in this guide (redirect mapping, Search Console verification) apply regardless of what any individual portal has changed.
How much would a real estate agent make on a $300,000 house?
Commission structures vary by brokerage, market, and the specific agreement with a client, so there’s no single figure that applies everywhere. An agent’s actual take-home also depends on their split with their brokerage, which is a conversation best had directly with your broker.
Which real estate website gets the most traffic?
Traffic rankings among major real estate portals shift and are best checked through a current, published traffic-analytics source rather than stated as a fixed fact here. For your own site’s migration, what matters more than any portal’s traffic is protecting your own site’s existing organic rankings through careful redirects.
What is the best website platform for real estate lead generation?
The strongest results typically come from pairing a well-structured website with dedicated lead-generation tools and CRM automation, rather than relying on a platform choice alone. Our lead generation services for agents and brokers are built around that pairing, combining site infrastructure with active prospecting support.
How long should I keep my old redirects active after a migration?
Keep permanent redirects live for at least six to twelve months, and Google recommends a year or longer to fully preserve search signals and catch any bookmarked or backlinked old URLs. Removing them too early is one of the most common causes of a lingering traffic drop.
Sources
- Move a site with no URL changes – Google Search Central
- Change of address – Search Console Help
- Transfer policy – ICANN







