What You Can and Can't Put on a Sold Listings Page in Ontario

Nearly every agent site we're handed has the same block on it, usually two scrolls down the home page. A grid of photographs, each one stamped SOLD in a corner, each one captioned with a street address and a number.

It's the best-performing content on the site. It's also the block the template vendor built without reading anything, and it's the one a competitor can report in about four minutes.

What the rule actually says

The rules for Ontario registrants sit under TRESA and its regulations, and RECO publishes a series of advertising bulletins that a compliance review will measure your marketing against. Bulletin 5.4 is the one about sold properties. Read it yourself rather than taking this article's word for any of it, and ask your brokerage what its own policy adds, because most add something.

The shape of it is this. An advertisement saying a property has sold must not contain anything that could reasonably be used to identify a party to the transaction, unless that party has consented in writing, or to identify a specific property, unless the owner of that property has consented in writing.

Then the part that catches people. Who counts as the owner depends on when you're advertising. Before the deal completes, the owner is the seller. After it completes, the owner is the buyer, which means the consent you collected from your seller at listing time does not cover the sold post you put up in March. And if the ad carries the price or any other term of the agreement, you need both of them.

That grid of addresses and sale prices is, in the language of the rule, a set of advertisements identifying specific properties along with the contents of their agreements of purchase and sale. It needs written consent per property, from both sides, and it applies whether you were the listing brokerage or the buyer's.

An expiry date is a content-model problem

Once you've read the rule, the interesting part isn't legal. It's that consent with a start and an end date can't be expressed at all by the thing most agent sites use to store sold listings, which is a grid of images someone pasted in.

What it needs is a field. Each sold entry carries the date its consent starts, the date it ends, and whether price was included in what was agreed. The site reads those fields and decides what to render: the full entry, the entry with the price suppressed, or nothing at all. When a date passes, the entry comes off the page because the data said so, not because somebody remembered.

We build these as static sites, so the build is the enforcement point. A rebuild runs, the expired entries are gone from the HTML, and there's no database call and no plugin and nobody to forget. It's the same argument as validating frontmatter at build time: the machine should refuse to publish the wrong thing, rather than trusting a person to catch it.

Why you still want the page

Because it's the only content on the site that's genuinely yours.

Everything coming down an IDX or VOW feed arrives identically on every other site in the region. Same description, same photos, same remarks. None of it can distinguish you, and asking Google to rank you on text that exists in four hundred other places is asking to lose. Your own record of what sold, on which street, at what pace, written by the person who was there, has no duplicate anywhere.

It's also the evidence behind every other claim on the site. "Specialist in the east end" is marketing. Eleven entries on six named streets is proof, and it's proof in the exact vocabulary somebody types when they're deciding whether to call you.

One thing worth checking before a redesign: your board's data agreement registers the specific URLs where listing data is allowed to appear, and moving to a new domain or a new vendor mid-project is where that quietly breaks. Handle it in the same pass as the redirect map, not after launch.

The pages that do the actual ranking

Sold data feeds them, it isn't them. The pages that rank are the neighbourhood pages, and they're the ones almost nobody writes, because writing one takes an afternoon and a genuine opinion about a place.

What the schools are like and which catchment ends where. What a semi on that street went for in the spring and what it goes for now. Which building has the maintenance fee problem everyone in the industry knows about. The parking. The train. That page can't be syndicated, can't be generated, and it's what a buyer reads at eleven at night before deciding which agent to email.

Link each neighbourhood page to the sold entries it earned. That's the internal structure doing real work: the claim and the evidence on adjacent pages, which is also how an assistant ends up with something to quote about you.

The short version

Keep the sold page. Get the consents properly, with both dates in them. Store those dates as fields, so the site can enforce what you agreed to instead of hoping. Suppress the price when you don't have consent for it, which costs you almost nothing, because the street and the pace tell the story anyway.

And write the neighbourhood pages. That's where this all points.

We build for agents and brokerages in Ontario, which means the consent fields and the expiry logic are in the spec before anything gets designed. If you'd like someone to look at what's currently on your site against Bulletin 5.4, that's a twenty-minute call and it costs nothing.