What property management websites get wrong

The most expensive defect in this industry is also the least visible from the inside: a portfolio that exists on the website but not in the index. It happens when every property is served from one URL and the individual property is chosen by the part of the address after the hash. People see the right page. Search engines see one page, over and over — and often what they see is an error state, because the fragment that would have selected a property never reaches the server.

A portfolio in that shape has as many indexable property pages as a single-page brochure site: one. Every photograph, every tenant list, every leasing contact and every downloadable flyer is invisible to the thing the owner is about to search with. The fix is not subtle and it is not a redesign — it is one real URL per thing worth finding, each with its own title, its own description and its own structured data.

We check this first because it changes what every other recommendation is worth. There is no point tuning meta descriptions on pages a crawler cannot reach.

Across fifteen commercial real estate and multifamily websites we audited in one Texas market in September 2026, the same defects recurred with uncomfortable consistency. Twelve of fifteen had missing or thin metadata, most often on the pages that matter commercially — portfolio, about, contact, team. Eleven had broken heading structure: pages with no h1 at all, or several competing ones.

Eleven had no FAQ page and no neighborhood or area page — the two page types that answer what people actually type, and the two an assistant most readily extracts from. Eleven had no meaningful entity schema: three had no structured data of any kind in the raw HTML of any page we checked, seven had nothing but breadcrumbs, and only four declared anything that identifies them as a real business at a real address.

Thirteen of fifteen showed no price or availability on their own site. Some showed nothing at all; others said “check availability” with no number anywhere in the page. Several linked out to a third-party listing instead, which means a portal owns the page where the money decision happens. Six had the same street address written two or three different ways across the site, or address markup that matched no address a visitor could see.

That is one segment, one market, one date, and we would not stretch it into a claim about the industry as a whole. But it is the shape of what we keep finding, and none of it requires a rebuild to fix.

A property management site serves two audiences whose searches look superficially similar and are worth wildly different amounts. Tenants hunting a listing generate traffic. Owners deciding who should manage their building generate revenue. Optimize for the first and you can grow sessions for a year while adding no doors.

Owner intent has its own vocabulary — the city plus the service, “rental property management company”, and the question-shaped searches people run before they are ready to call anyone: whether to hire a manager at all, what management actually costs them in practice, what a manager does that they are currently doing badly themselves. Those questions are where the relationship starts, and most property management sites answer none of them.

The pages that serve owner intent are rarely the pages a property management company has built. They have a services page and a listings page. They do not have the page that answers the question the owner is actually asking at the moment they start looking.

Property management is inherently local, and a company operating across several cities has a structural problem before it has a content problem. One page trying to rank in four markets ranks properly in none of them, and the four end up competing with each other for the same searches.

Each market needs its own page with its own reason to exist — the neighborhoods actually covered, the property types actually managed there, the local specifics an owner in that market would recognize. Thin location pages that swap a city name into the same paragraph are worse than no location pages: they look to a search engine exactly like what they are.

The same discipline applies to how the business describes itself off-site. If the address, the phone number and the service area are written one way in the page copy, another way in the structured data and a third way in a directory listing, an assistant trying to resolve which company this is has three candidates and no tiebreak.

Most property management companies are not on their first website. Somewhere behind them is a previous build whose URLs earned rankings, and those URLs usually died silently at launch. We have found pages still sitting near the top of the first page for their search while returning a 404 — real demand arriving at nothing.

So a rebuild starts with an inventory of what already ranks and a redirect for every one of them. That is ordinary discipline. The part that is not ordinary is knowing when a redirect is the wrong tool: a legacy page whose content was selected by a hash fragment cannot be redirected per-property, because the fragment never reaches the server to be read. Redirect the base URL and you break every working legacy link at once. The correct move there is to leave the page reachable, mark it noindex while keeping its links followable, and let the new per-property pages take the rankings.

It is a small distinction that decides whether a launch keeps its search equity or quietly throws it away.

Owners increasingly open ChatGPT, Perplexity or Google's AI mode — the assistants we track — and ask who manages property in their city. Three things about this industry make that shift hit harder than most. The decision is local, so the answer set is small — a handful of names, not a page of them. It is referral-driven, so asking a machine for a recommendation substitutes naturally for asking a person. And it is high-consideration, so owners research before they call, which is exactly the behaviour these tools absorbed.

Getting named in that answer is not a different discipline from search; it is the same foundations pointed at a different reader. Structured data so a machine can tell what each page is. Entity signals stated in the same words everywhere, because inconsistent self-description makes a company harder to resolve. Content organised so a single sentence can be quoted without the paragraph around it. A machine-readable summary at llms.txt. And crawler access, which is a one-line decision most sites have never consciously made.

Worth saying plainly, because it is the opposite of what people assume: across those fifteen audited sites, not one was blocking AI crawlers. Access is almost never the problem. Having something worth citing is.

Eight of the fifteen sites we audited had no analytics of any kind, and three more were still running a measurement product that stopped collecting data in 2023. That is a business making decisions about its website from impressions and instinct.

Even where analytics exist, they usually count the wrong things. A leasing business is not paid for sessions or time on page. It is paid when someone downloads a flyer, taps the phone number, or clicks through to email a leasing contact. Those three events are the ones worth instrumenting, and once they are instrumented the argument about which pages matter stops being an argument.

Two silent failures on a site we had built — flyer buttons that had stopped working without anyone noticing — are the reason monitoring is part of the work rather than a follow-up offer.

Search is the front door. Behind it is a company whose week is largely the same messages, the same notices and the same reports as last week: tenant requests and owner questions, renewal outreach and move-in sequences, rent follow-up and delinquency chasing, notices and lease documents and compliance deadlines, data moving between systems, and the reporting that gets assembled by hand every month.

Every one of those is a workflow with a shape, and a workflow with a shape can be drafted by an agent and approved by a person. The approval step is the default, not an upgrade — nothing goes to a tenant or an owner because software decided it was time.

The usual objection is that the property management platform is closed, so nothing can be connected to it. In practice that is rarely true, because almost every one of these platforms can put a scheduled report somewhere on a timetable. A rent roll, an income statement, an aged receivables report, a work order list and a unit availability export are enough to assemble a genuine operating picture without touching the platform's API at all.

The engineering that makes this hold up is unglamorous and matters enormously. Scheduled exports arrive with a title block above the data, so a loader that assumes the headers are on row one breaks the first time somebody reconfigures the report; find the header row by reading it instead. Different configurations of the same platform label the same column four different ways — suite or unit or space or bay, monthly rent or base rent or actual rent — so map by meaning rather than by position. Do that and a differently configured export from the same system lands in the same dashboard without a code change.

Owner enquiries, doors added, ranking position for the searches that produce owners, and hours returned to the team. Those are the numbers that pay for an engagement, and they are the ones we report against.

Rank positions are hand-verified and checked logged out, because the search engines block automated rank queries often enough that a tool claiming otherwise is guessing. Visibility inside AI answers is reported as the count it actually is — how many of nine runs across three assistants named you, with the date and the domains that were cited — never as a rank, because there is no rank inside an AI answer to report.