Prospects (shopping)
- What is available, and when
- Layouts, square footage, what is included
- Where it is, and what is nearby
- Photos and a floor plan they can actually read
- A tour booking or an enquiry that gets answered
Property management
Property websites for two different people
A prospect wants to know what is available and what it costs. A resident wants to pay rent or report a leak. They arrive at the same homepage with nothing in common.
A property management website has two audiences with opposite intent, and most sites are built for only one of them. Prospects are shopping: they want availability, layouts, location and a way to book a tour. Residents already chose you: they want the portal, or they want a maintenance request to reach a human today.
The second failure is upkeep. Availability changes weekly, staff change yearly, and a site that was accurate at launch quietly stops being true. The most expensive fault on a property site is rarely a design flaw. It is a maintenance form emailing someone who left.
Two audiences, one homepage
Almost every avoidable problem on a property site traces back to treating these as the same visitor.
Residents (already here)
- The rent portal, in one click, not four
- A maintenance request that reaches a real person
- Who to call when it is urgent and after hours
- Office hours, parking, package and amenity rules
- No marketing copy in the way of any of it
What actually goes wrong on property websites
The pattern is consistent across portfolios of every size.
The form that emails a ghost
Maintenance and enquiry forms are configured once, at launch, pointed at whoever was doing the job that month. That person leaves. The form keeps submitting. The confirmation message keeps appearing. The resident thinks the leak is reported, and it is sitting in a disabled mailbox.
Nothing surfaces this failure on its own. Send to a role rather than a person, and test the path on a schedule. It sounds trivial until you count what a fortnight of unreported maintenance costs in goodwill and in water damage.
Availability that lies
A listed unit that went last week does not just disappoint one prospect. It burns a leasing call, and it teaches people your listings are decorative. If availability cannot realistically be kept current, it is more honest to show a contact path and answer live than to publish a list you know is behind.
Unit pages nobody needed
The instinct is to give every unit its own page. For interchangeable units this produces hundreds of near-duplicate pages that are stale by the time they are indexed, and search engines see little reason to rank any of them. Build the page when there is something true and specific to say about that unit; otherwise let the property page carry it.
Residents drowning in prospect copy
Someone paying you rent should not have to scroll past a leasing pitch to find the portal link. Resident paths get used more often than prospect paths and are almost always designed less carefully.
Wording that should have been reviewed
Fair housing language is a real legal consideration. Copy that describes the ideal resident rather than the property is a known trap, and it turns up in listings written with entirely good intentions. We are not lawyers and we do not give legal advice; we build the site to carry the language your counsel approves and flag copy that looks like it needs a professional eye. The same applies to accessibility obligations: get them right with someone qualified rather than guessing.
How we approach a property site
-
Separate the two journeys
Prospect and resident get distinct, obvious paths from the first screen. Neither one should have to read the other one's page to find what they came for.
-
Follow every form to where it lands
We submit them and watch. Who receives it, is that mailbox alive, is there a fallback if that person is out? Enquiries and maintenance requests are routed to roles, not to individuals.
-
Decide the property and unit structure honestly
Property pages carry the weight. Unit pages exist only where there is something genuinely specific to say about that unit.
-
Make availability sustainable
Whatever gets published has to be something a real person can realistically keep true. Publishing less and keeping it accurate beats publishing everything and being wrong.
-
Point residents at the systems you already run
Rent and resident accounts live in your property management software. We link to it clearly. We do not build payment systems or portals.
-
Get found for the right searches
People search by neighbourhood and by property name. See local SEO for how that visibility actually works. Portfolios across several properties should read multi-location websites first.
Who this is for
- Managers whose availability on the site is behind what leasing knows
- Anyone who cannot say with certainty where a maintenance request goes today
- Portfolios where prospect and resident content are fighting for the same page
- Owners of a site built by a company or a person who is no longer reachable
- Teams whose leasing staff waste calls on units that already went
When this is not the right fit
- Anyone needing rent collection, resident accounts or payment processing built. We do not build or sell those. We link cleanly to the software you run.
- Anyone wanting legal wording signed off. Fair housing and accessibility are real obligations and belong with a qualified professional, not with us.
- Single owners with one unit and no turnover. A page and a working phone number will do; a system is overkill.
What SolvenceHQ can help with
The test of a property site is not the launch. It is whether a maintenance request submitted eight months later reaches someone who can act on it.
- Prospect and resident paths designed as separate journeys
- Forms routed to roles, tested on a schedule, so a departure never eats requests
- Property and availability structure that a real person can keep accurate
- Clear links out to the property management software and portal you already use
- Local SEO for neighbourhood and property name searches
- Ongoing care so listings and staff changes get reflected
Common questions
Should we build a page for every unit, or just for the property?
It depends on how you actually lease. If units turn over constantly and are broadly interchangeable, unit level pages become hundreds of near-identical pages that go stale the day a lease is signed, and search engines have little reason to rank any of them. A strong property page with a live availability list usually serves prospects better.
If units genuinely differ, a corner unit with a view is not the same product as an interior one, then unit detail earns its keep. The deciding question is whether there is something true and specific to say. If there is not, the page should not exist.
Our maintenance form emails someone who left the company. How does that happen?
Because form recipients are configured once, at launch, by someone who has also moved on, and then nothing ever tells you it is wrong. The form still submits. The thank-you page still appears. The resident believes the request is filed. It is sitting in a mailbox nobody opens.
This is one of the most common silent failures on property sites. The fix is not clever: send to a role, not a person, and test the path on a schedule so a departure never becomes a maintenance backlog.
Can the website replace our resident portal?
No, and it should not try. Rent payments and resident accounts belong in the property management software you already run. We do not build payment systems. What the website should do is get residents to the right portal in one obvious click, instead of making them hunt through a page written for prospects.
How current does availability really need to be?
Current enough that a prospect who calls about a listed unit is not told it went last week. Stale availability is worse than no availability, because it converts interest into a wasted call for your leasing staff and a small resentment for the prospect. If availability cannot be kept accurate, showing a contact path instead is the more honest design.
What about fair housing language on listings?
It is a genuine legal consideration and not one to improvise. Wording that describes the ideal resident rather than the property is a well known trap, and it can appear in copy written with no bad intent at all. We build the site to carry whatever language your counsel approves, and we flag copy that looks like it should be reviewed. We are not lawyers and this is not legal advice. Get it right with a professional who does this work.
Related services and guides
Small business web design
Design and build a site that explains your business and brings in enquiries.
Website maintenance
Edits, updates, backups and monitoring so the site keeps working.
Local SEO
Get found by people searching for your service near you.
Multi-location business websites
One site, many locations, without six sites drifting out of sync.
Website redesign
Rebuild an existing site without losing the rankings you already have.
Business email going to spam
Authentication, reputation, and the fixes that actually move the needle.
Get a Quote
Not sure your forms still reach anyone?
Tell us where your enquiries and maintenance requests are supposed to land. We will find out where they are actually going.