Housebuilder websites rely on data sources from a CRM, such as COINS or Housebuilder Pro, then detailed and constantly changing marketing information, and the major property portals. A website can and should be a central source of truth for all this information.
This guide is for heads of marketing, sales directors and anyone at a regional or national housebuilder about to commission a new site.
In this article:
- Discovery
- Design
- Integrations
- Content and data migration
- The CMS and making it work for your teams
- Testing and go-live
- Launch and the first 90 days
1. Discovery
Discovery is not a kick-off chat, this is the structure that we will follow through to go live, and getting the detail right here will transform the final outcome of your website visually and functionally, it is of critical importance that integrations and workflows are correctly understood at this point of the project.
What to think about
The more of this you have ready, the faster discovery goes and the fewer assumptions end up in the design and integrations.
- Your commercial goals in numbers: enquiries, appointments, reservations, cost per lead. Say what the current site is costing you, even roughly.
- Your buyers by development type. First-time buyers and trade-up families behave differently from downsizers, and some sites will lean one way.
- The competitors you’re measured against, plus a few sites you admire and exactly why.
- “Their plot availability banners” is more useful than “it feels premium”.
- Brand guidelines, and thoughts on how strict these need to be followed or can be developed as part of your build.
- Note whether individual development brands have their own colours, and how much differentiation you allow between development branding and your master brand.
- A list of every system the website touches: sales system or ERP, Rightmove and Zoopla, your applicant tracking system, CRM, land portal, customer portal. For each one, a named technical contact at the vendor and a named owner on your side.
- A count of what you’ve got: live and forthcoming developments, phases, house types, plots and open roles. Content volume drives cost.
- Access to GA4, Google Tag Manager and Search Console, and a snapshot of current portal lead figures. You’ll need this baseline after launch.
- Summary of your current assets: photography, CGIs, video, floorplans, brochures, director headshots.
- Your IT team’s notice period to join calls or assist with the build, and the tools you can use.
- Any annual leave for key people booked during the design and build process.
Map how you release plots today
Before design starts, sit with whoever releases plots and follow one plot from the sales system to the website to Rightmove.
- Do reserved plots stay on Rightmove?
- Do some legacy listings cover several plots?
- Are forthcoming sites kept off the portals?
- How are phased or strategic sites handled?
Every one of these changes how the CMS and integrations are built.
What discovery needs to settle
- The data model: development, phase, house type, plot.
- Sign it off before design starts, because plot-level pages are easy to miss and expensive to add later.
- What “premium” means to you. Put reference sites side by side and score them.
- You can’t hack a premium site with font and colour pallets, it needs to feel premium through subtle animations, correct spacing and modern feeling blocks that have sitewide consistency.
- How much to sell the lifestyle versus the homes. A London apartment scheme leans on the neighbourhood; a village development in Sussex usually shouldn’t.
- Your accessibility target (WCAG A, AA or AAA), and whether your brand palette passes contrast checks.
- Which features are in phase 1 or a go live spec, checked against what your sales system’s API can actually do. Booking, callbacks and “coming soon” plots all depend on it.
- Who owns each part of the site (sales, marketing, careers, land), with deputies.
- Who signs off designs day to day, when the MD needs to see it, and how many feedback rounds there are.
- How change requests work once wireframes are approved. New ideas go into a priced phase 2, not the current build.
- A launch date range, not a best-case date, and the dependencies behind it.
2. Design
Your website is designed to communicate the feel of your brand, and drive customers to enquire and book a viewing at their desired location.
Search comes first
Generally our advice is to build the homepage around search, and keep motion subtle so it doesn’t pull attention away from it. A video header can work well, as long as it doesn’t slow the page or push search below the fold on mobile.
Find-your-home needs a map view as well as a list, and filters that match how people actually search: town, county, radius, bedrooms, price. Default to live developments. If search opens on forthcoming sites, you’re hiding the homes you can sell today.
Templates for every level of the hierarchy
You’ll need a template for each level of your data model. Live development pages carry video, a site plan, the local area and available homes, while forthcoming developments get a stripped-back page built around register-interest.
House types ideally need their own pages, plus landing pages by bedroom count. Plot pages show price, status, specification, floorplans and a gallery.
Breadcrumbs should mirror that structure, so a buyer always knows where they are.
Features that drive enquiries
- A sticky enquiry bar that follows the buyer down the page.
- Brochures behind a register-interest form rather than a straight download.
- Availability messaging the sales team can change in minutes: “Final two homes”, “65% sold”, “Show home now open”.
- A clear label for every plot status. If reserved plots aren’t marked, they look available.
- A way to promote specific plots and incentives when sales need to shift them.
- Buyer tools such as a stamp duty calculator and part exchange information.
- A non essential that should be considered is a mortgage calculator. A simple one takes half a day; a sophisticated one with live rate feeds can take multiple days, and rates that change between visits cause errors.
Trust signals up front
HBF star ratings, Trustpilot scores, awards and family ownership are reasons to choose your site. We advise having them visible early on and repeated on multiple pages of the site, we want to build trust through your website.
Brand, accessibility and mobile
Many housebuilder brand guides weren’t written with screens in mind. Light accent colours on dark backgrounds often fail contrast checks, and poor contrast affects far more people than those with a visual impairment. Think of using a phone with the sun behind you, reading on a phone in one hand.
Use colour consistently to show what’s clickable. Build in skip links, alt text, captions and transcripts from the start. And design for mobile first, because that’s where most of your traffic will be.
The rest of the site
Corporate pages (who we are, sustainability, community work, awards, directors, investor information) tend to be text-heavy. Break the content up with stats, image blocks and features that link to full news articles.
Careers deserves its own feel within the same design system, especially if being a great employer is a board priority. Name the customer portal and land pages in the language buyers use, not your internal product names.
3. Integrations
Integrations are where housebuilder launches can be a great success, or an operational headache. A period of transition can be normal, but the better the planning on both agency and client side of a site build smooths the process.
The goal is simple: your team enters plot information once, and it appears everywhere it needs to. A typical flow looks like this.
- Your sales system (COINS or similar) creates the plot with basic data: plot number, house type, price, status.
- The plot arrives in the CMS as a draft.
- Your team adds marketing information that is not in your sales system and publishes the plot.
- This live plot updates as pricing or incentives are updated in the sales system.
- The CMS pushes the listing to Rightmove and Zoopla on a schedule.
- Enquiries from the website are routed to the right sales team and written back into the sales system.
Write a spec for every integration
Each system needs a short written spec, signed by your IT team and the developers, before design is approved. It should cover:
- Which fields move, and in which direction.
- What triggers a sync, how often it runs, and how long a full import takes.
- Whether new records arrive as drafts or go live.
- How each plot status (available, reserved, sold, off-market) is handled on the site and on each portal.
- Who owns the data on your side, with a deputy.
- Keep the timings separate. “The sales system syncs every 30 minutes” and “Rightmove updates every X hours” are different numbers, and your sales team will ask about both.
Draft first, always
New plots from your sales system should arrive as drafts, never live. Otherwise a half-empty listing can go public over a weekend with nobody there to finish it. Test this behaviour before anyone tells your team it works.
Rightmove and Zoopla
Get feed credentials requested at kick-off, and build and validate the feed early with dummy plots. Late feeds get rejected for things as small as a file naming convention.
Agree a field map from every portal field to a CMS field. List the fields that will stay manual in Rightmove Plus, such as development descriptions or spotlight features. Build the portal limits into the CMS: the summary is around 300 characters and key features are capped, so the CMS should stop editors going over rather than just warn them.
Images need a plan too. Portal images are often resized to tiny dimensions and are useless as website hero images. Keep high-resolution masters, and let the system resize them for each feed.
Lead routing
Build a routing matrix: development, sales team email, sales system phase. Get it signed off, then test it by submitting one enquiry per development before launch, with each sales team confirming it arrived. An enquiry for one region landing in another region’s inbox is an easy mistake to make and a costly one.
Careers feeds
Your applicant tracking system is an integration too. Look at the raw feed with your HR admin during discovery. Map every filter on the careers page to a real field in the feed, and agree the HR rules: internal roles hidden, closed roles removed, early careers roles shown in the right place. If the website and the ATS categorise jobs differently, roles will show in the wrong place or not at all.
Agree on ownership for the below dependancies
Launches get held up by small things. Agree at kick-off who provides each of these, and keep them in one credentials register:
- Hosting, DNS access and SSL, including every domain the old site used.
- Email records (MX, DKIM, SPF) so switching nameservers doesn’t break your email.
- Google Maps API key.
- GA4 and GTM IDs.
- Feed and API credentials for every environment.
- Contacts at your media agency, so paid campaigns and tracking don’t break.
Test on the live site before you announce it
Staging isn’t production. Integrations that pass on staging can still fail live, because of different keys, different data or different permissions.
Test on production with live credentials before the DNS switch, and check submissions in the sales system itself.
4. Content and data migration
Plot data causes more visible errors at launch than anything else. Wrong starting prices, sold homes still showing as available, the wrong plot number on the wrong page. Our experience shows us there is always a significant amount of human checking and admin needed client side during the launch week.
Migrate plots once the integration works
It’s tempting to upload plots by hand early so the site looks finished. Don’t, unless you’ve agreed how they’ll be kept up to date. Plots uploaded manually before the sales system link exists aren’t connected to it, so every price change and reservation has to be re-keyed.
The safer route is to connect the integration first and import from it. If you can’t, set a content freeze date, log every change made after it, and apply those changes on launch day. Pick one source of truth for the import (your sales system or Rightmove Plus etc) and stick to it.
Count the content before you price it
A housebuilder site can easily run to tens of thousands of words, plus hundreds of plot and house type pages. Count developments, house types, plots and roles at the scoping stage, and agree who uploads what. Corporate pages can be populated by the build team; your sales and marketing team will usually need to own plot content.
Run a content matrix
List every page with its owner, due date and status, and set the deadline two to three weeks before handover. Give each piece one approver and a turnaround time. Agree the angle of each article before anyone writes it, so drafts aren’t rejected for the wrong message.
Content upload happens at the end of the build, after QA. If your team is small, book the time now or have your agency price and deliver the content element.
Sometimes content upload can be a quicker process if delivered by the agency, they will be more familiar with your new CMS than your team pre-launch and in the first couple of weeks.
Offline QR codes and links
QR codes in marketing suites, printed brochures, email signatures and paid ad URLs all point at your old site. Inventory them before launch and pass to your agency for redirects.
Check compliance content as a set
Privacy notices, complaints policies, energy ratings, warranty links and cookie policies should be reviewed together and signed off by you before launch. They’re easy to carry over from the old site unchanged and out of date.
5. The CMS: making it work for your teams
Build the CMS around how your team actually releases plots. If fields are designed without the people who’ll use them, you get duplicated fields.
Design fields around the real workflow
Walk through the plot release workflow with your editors before the CMS fields are built. Every piece of information should be entered once, in one place. If the same figure appears on the homepage and the About page, it should update in both from a single field. If that’s not possible, choose figures that rarely change, or set a calendar reminder.
Give every team its own space
Most housebuilders have several teams editing the site. Sales and marketing own developments, house types and plots. Corporate or communications teams look after About Us, sustainability, community work and news.
HR usually owns careers alongside the applicant tracking system, and land teams often run a separate portal embedded in the site.
Give every editor their own login, never a shared one. It’s safer and you can see who changed what.
Build a website that isn’t developer dependant for minor changes
- A block-based page builder with pre-designed modules, so pages look right whatever goes in them.
- Templated content types for developments, plots, team members, timelines, testimonials and FAQs.
- The option to duplicate an existing page, so new developments match the old ones.
- SEO fields (title, meta description, URL slug) on every page. Watch for duplicated slugs when pages are cloned.
- A published image spec for every slot, and automatic compression so editors don’t have to resize files themselves.
- Revision history, so nobody’s afraid of breaking something.
- A limited set of news categories. Too many tags make filtering useless.
6. Testing and go-live
A go-live date means nothing until the site has passed a signed checklist.
Test what buyers will actually do
A full QA script should be run before UAT starts. For a housebuilder, it should cover:
- Search by town, county and radius, including the edge cases, with live developments as the default.
- Every plot status on every page type and in the portal feed.
- Every form, submitted once per development.
- Navigation, footer links and legal pages.
- Headings, schema, metadata and page speed on mobile.
Keep UAT to the agreed spec
User acceptance testing is where your team checks the site against what was agreed. Ask each development’s sales team to sign off its own plots against a checklist: price, status, plot number, house type. Only the sales team will know that plot 35 should be plot 8.
Use one snag template: page URL, what it says now, what it should say, and who owns it. “Wrong phone number” without the right one just adds a round trip. Collect snags into one consolidated round per stage, and send anything that’s a new idea to the phase 2 list.
Plan the switchover
- Audit every DNS record, including email, before changing nameservers, and lower the TTL in advance.
- Brief your IT team and agree on a rollback plan.
- Allowlist your office IP addresses so security settings don’t lock staff out.
- Load and test redirects on staging, then crawl the old URLs within an hour of launch.
- Take a baseline of Rightmove and website lead figures.
- Tell your media agency the launch time and any URL or form changes.
- Launch Monday to Wednesday. Never on a Friday or before a bank holiday.
7. Launch and the first 90 days
Launch day is when the whole company sees the site for the first time, and they’ll find things. Plan for a busy first fortnight rather than hoping for a quiet one.
The first 48 hours
- Check prices, statuses and plot numbers against the sales system for every development.
- Crawl old URLs and every old domain to check the redirects.
- Check GA4 in real time, and make sure conversions are firing.
- Triage snags daily in one tracker, and sends the developers a written priority list each day.
Watch the numbers
Don’t panic if portal leads dip after launch, compare against the baseline you took before switchover.
Check that listings are still flowing to Rightmove with the right fields, that tracking survived the move, and that paid campaigns point at live URLs. Agree in advance who investigates and how quickly.
Watch the sales system sync closely for the first few weeks too. Form issues, missing developments, duplicate drafts and wrong house type names are all easier to fix in week one than in week six.
Ensure support is set up pre-launch
Agree one support channel, published hours, response times and a simple red, amber, green triage before sign-off. Your team shouldn’t have to work out whether to email, raise a ticket or phone.
Put a launch-week rota in place across your team, the build team and any development partner, with an escalation path if something breaks. Expect heavier support for the first two to three weeks. We call this ‘super support’
Keep a phase 2 list
Every launch generates new ideas. Keep them in a prioritised backlog you can both see, with prices and dates, rather than letting them drift into the support contract.
Appendix: checklists and key questions
Before design starts
- Plot release workflow mapped with sales, marketing and IT
- Data model signed off: development, phase, house type, plot
- Written spec for every integration, signed by your IT team
- Sales system API checked against the wireframes
- Named vendor contacts for every third-party system
- Owners and deputies named for every section of the site
- Content volume counted and priced
Before build is signed off
- Functional spec and page list signed; change log open
- Lead routing matrix signed
- Rightmove field map signed, including limits and manual fields
- Asset spec and content matrix issued with deadlines
At least two weeks before launch
- Every integration tested end to end, with a test log
- Full sales system export reconciled against the site’s development list
- Every plot status tested on every page and in the portal feed
- Rightmove test feed accepted
- Careers feed tested with open, closed and internal roles
- One test enquiry per development received by the right sales team
Before a launch date is set
- Plot content migrated from a single source after integrations passed
- Internal QA passed: search, filters, forms, navigation, legal pages
- SEO checks passed and redirects loaded
- UAT closed against the spec; new ideas in the phase 2 list
- DNS audit done, IT briefed, rollback agreed
- Training done on the finished site, guide and FAQ issued
- Support model agreed; media agency briefed; lead baseline taken
- Launch day is Monday to Wednesday
Questions to answer before launch
- How often does the sales system sync, and how long does a full import take?
- How long from releasing a plot to it appearing on Rightmove?
- What comes from the sales system, and what’s added by hand?
- Do new plots go live automatically, and how will we know one has arrived?
- What happens to existing Rightmove listings at switchover?
- Which fields still need updating in Rightmove Plus?
- How do reserved and sold plots appear on the site and on each portal?
- What image sizes should we upload?
- How will you prove every enquiry reaches the right sales team?
- Will QR codes, printed materials and ad links still work?
- Will switching nameservers affect email, and what’s the rollback?
- What support is in place after launch, and how are issues raised?
- What’s in phase 2, and when?

