Real estate website design is judged on photographs and rarely on the things that decide whether the site works: how listings are pulled in and kept current, how the search and map behave on a phone, whether the pages a rebuild replaces still resolve, and whether anything on the site can be indexed at all. A brokerage or agent site is a data-driven application wearing a brochure, and most of the money lost on a redesign is lost in that gap. This page covers what to specify, what breaks, and how to hold an agency to a standard you can check yourself.
The listing feed decides the architecture
Almost every property site is populated from a data feed, and the way that feed is rendered decides whether the site can be found at all. Google processes JavaScript in three stages: crawling, where Googlebot fetches URLs and checks robots.txt; rendering, where a headless Chromium executes the JavaScript; and indexing of the rendered result. Its documentation notes that pages are queued for both crawling and rendering, and that it is not obvious when a page is waiting for which. The failures it names are exactly what listing widgets produce: fragment-based routing whose URLs Googlebot cannot reliably resolve, soft 404s where meaningful status codes are impractical, and canonical URLs rewritten in JavaScript. Google recommends the History API for routing, real HTTP status codes, and server-side rendering or pre-rendering, noting that it makes a site faster for users and crawlers alike. Ask any agency how expired listings will return a status code and what the search results page renders in raw HTML.
A redesign is a site move, and it is where visibility disappears
If the rebuild changes URLs, Google treats it as a site move and has published guidance for it. It recommends server-side permanent redirects from the old URLs to the new ones, prefers 301 or 308 where technically possible, and asks that an updated sitemap be submitted in Search Console so the new URLs are discovered. It warns that for medium-sized sites it can take a few weeks or more before the new URLs are shown instead of the old ones, and longer for larger sites. The mistakes it names are ordinary and expensive: noindex tags or robots.txt blocks left over from development, redirects pointing at URLs that do not exist, and sitemaps never updated. Put the redirect map in the contract as a named deliverable with an owner and a post-launch check, because on a property site the pages at risk are the neighbourhood and community pages that took years to earn.
Speed and mobile behaviour are the design brief
Property browsing happens on phones, over cellular connections, on pages carrying dozens of large images. Google says its core ranking systems look to reward content that provides a good page experience, that Core Web Vitals are used by its ranking systems, and simultaneously that good results in those reports do not guarantee top rankings and that Search always seeks to show the most relevant content even where page experience is sub-par. It advises checking that pages are served securely, that content displays well on mobile devices, and that pages avoid an excessive amount of advertising that distracts from or interferes with the main content. For a design brief that means image handling, layout stability while a map or gallery loads, and restraint with pop-up capture forms. Specify measurable targets in the contract rather than an adjective like fast.
What to specify, and what to check on launch day
Specify the URL structure for listings, neighbourhood pages and agent profiles, and who owns it. Specify how a sold or withdrawn listing behaves, since a site that quietly deletes thousands of URLs teaches search engines to distrust it. Specify structured data for the brokerage itself; Google's local business documentation lists name and address as required properties with telephone, opening hours, geographic location and price range among those recommended, while stating that it does not guarantee that features consuming structured data will appear. Specify the redirect map, the sitemap submission, and a launch-day check that spot-tests old URLs, renders key templates without JavaScript, and confirms nothing is blocked. None of those checks require privileged access, which is exactly why they belong to you rather than to the agency that built the site.
Questions people ask about real estate website design
Will a redesign hurt our search traffic?
It can, if URLs change without a complete redirect map. Google recommends server-side permanent redirects, prefers 301 or 308, and asks for an updated sitemap in Search Console; it warns that a medium-sized site can take weeks or more to settle even when the move is done properly.
Can Google index listings loaded by JavaScript?
Usually, since it renders pages with a headless Chromium before indexing, but rendering is queued and several common patterns break it. Server-side rendering or pre-rendering, real HTTP status codes and History API routing are Google's own recommendations.
How fast does a property site need to be?
Fast enough that image-heavy pages stay usable on a phone. Google says Core Web Vitals are used by its ranking systems while noting that good scores do not guarantee top rankings, so treat speed as a usability requirement with measurable targets in the brief.
What should be in the contract for a rebuild?
The URL structure, the behaviour of sold listings, the redirect map with a named owner, sitemap submission, structured data for the brokerage, and a launch-day verification pass. Each of those is checkable by you without any special access.