Structured Data for a Listing Page: What an Agent Reads First

When a machine summarises your listing it reads a narrower set of facts than a guest does. Make those facts unambiguous.

Last updated: October 8, 2026

When a machine summarises your listing, it reads a narrower set of facts than a guest does. It doesn't browse the way a person does. It extracts. If the facts it needs are tangled in adjectives or split across three paragraphs, the summary comes back vague, and vague is what the next guest ends up reading.

Key Takeaways

• An assistant extracts, it doesn't browse. It lifts facts, not atmosphere.
• Three facts lead. Price and unit, policy in a line, and what guests repeatedly said.
• Ambiguity gets dropped. If a fact needs interpreting, it may simply fall out.
• Placement matters. Put the key facts where they're easy to lift, not buried mid-paragraph.
• Check the summary. Read what comes back and repair whatever got lost.

What an assistant reads and what it skips

An assistant working from your page is doing a different job from a guest. A guest reads for feeling — does this look like a nice week? An assistant reads for facts it can state without hedging. Those two readings overlap, but they aren't the same, and the gap is where listings lose information.

What gets read cleanly is anything that can be lifted whole. A nightly rate, a currency, the unit it applies to. A cancellation window. The number of bedrooms. A minimum stay. These are facts, and a summarising assistant can carry them from your page to a guest's question without losing much.

What gets skipped is anything that needs interpretation to become a fact. "Steps from the beach" isn't a distance. "A short walk to everything" isn't a location. "Charming and full of character" isn't a feature. None of these are bad writing; they're just hard to extract, so a careful summary leaves them out rather than guess.

That's the trade you're managing. Atmosphere sells the listing to a person, and facts survive being summarised. You don't have to choose, but you do have to keep the facts separate enough that a machine can find them.

Think of it as two audiences reading the same page one after the other. A guest reads it first and decides whether to look closer. An assistant reads it later, answering a narrower question — is this place available, at what price, and on what terms? Write for both and the page gets sharper, not blander.

There's a way to see this from the other side. On LOCALSBNB, an AI layer connects Claude, ChatGPT or Cursor to your store data, so you can ask a question about a listing in one sentence and get an answer back — one install, no new app. Put a question to your own page and you'll quickly see which facts it can state and which it has to dance around.

Facts that have to be unambiguous

Three groups of facts do most of the work, and each one has a way of going wrong.

Price and unit. The nightly rate, the currency, and what the rate applies to. State it once, plainly. A rate without a currency, or a price that turns out to be per person, is a fact that changes shape in a summary. Say the unit out loud: per night, per room, per stay.

Policy in one line. Cancellation, deposit and minimum stay, each as a single plain sentence rather than a paragraph of qualifications. A policy buried in caveats gets summarised as "restrictions apply," which tells a guest nothing. One line each, no stacking.

What guests said. The recurring phrases in your reviews are the facts a summary quotes back, because they're the ones that repeat. If three guests mention the quiet street, that's a fact about the property, not a coincidence. Keep those phrases in mind when you write, because they're what a summarising assistant reaches for.

Notice what the three have in common. Each is a fact a stranger could verify from the page alone, without asking you a follow-up. That's the test: if a fact needs you to explain it, it isn't ready to be summarised.

One habit keeps all three in shape: rewrite each fact as though you were answering a stranger who can't ask you anything. That forces the number, the unit and the condition into the sentence, where a summary can lift them.

You can check all three through a read-only question. On LOCALSBNB, a read-only question covers booking details, the unit-type calendar, channel rates and operating data, so you can confirm the facts a summary would lean on before you rewrite anything.

Where to write them on the page

Placement decides whether a fact gets lifted or lost. The same sentence survives or disappears depending on where it sits.

Lead with the facts. Put price, unit and policy near the top of the description, in their own short lines, rather than spreading them through the prose. A machine reads order too, and the first clear facts are the ones most likely to make it into a summary.

Keep one fact per line. A sentence that carries a rate, a deposit and a check-in time is three facts competing for the same slot, and a summary may keep only one of them. Split it. Short lines are easier to lift and easier for a guest to scan.

Spell out anything a summary could misread. Write the currency, name the unit, give the minimum stay as a number. "Reasonable deposit" and "flexible check-in" are the kind of phrases that vanish, because there's no fact underneath them to carry.

Keep the atmosphere, just don't hide facts inside it. The paragraph that makes the place feel appealing can stay exactly where it sits. What changes is that the facts no longer depend on it, so a summary can take them without taking the mood.

If you write in a second language, have the facts checked by someone fluent before you publish. A number is language-neutral, but the sentence around it isn't, and a mistranslated unit is a fact that reaches guests wrong.

Checking the summary it produces

The last step is the one most hosts skip, and it's the only one that proves the work. Ask for the summary, read it, and fix what fell out.

Put the question plainly. Ask an assistant to describe your listing in a few sentences, as it would to a guest. What comes back is your listing as a machine sees it, and it will look different from how you wrote it.

Read the summary against the page. Three things show up. Facts that survived, facts that drifted, and facts that vanished. A drifted fact is the dangerous one — a deposit that became "a fee," a minimum stay that lost its number — because it reads as correct while being wrong.

Fix the page, not the summary. When a fact drops out, the cause is almost always in the writing, not in the assistant. Rewrite the sentence so the fact can't be missed, then ask again. You can run this loop on LOCALSBNB at localsbnb.com, where a one-sentence question about a listing is the same shape as the question a guest's assistant would ask.

Repeat until the summary is dull. When what comes back is plain and accurate — price, unit, policy, the recurring guest phrases — you've made the listing readable to a machine without making it worse for a person. Dull and correct is the goal here, because the atmosphere is doing its work elsewhere on the page.

Keep the before-and-after in a note. When you change a rate next season, you'll want the phrasing that survived the last round, rather than rediscovering it.

FAQ

Do I need special markup on my page?

This is about how you write, not about adding anything technical. Plain facts, stated once and placed clearly, are what a summary can lift. The writing is the work.

Will this make my listing sound boring?

No. It moves the facts out of the atmosphere rather than removing the atmosphere. The evocative line stays; it just stops being the only place a guest can find the price.

How often should I re-check the summary?

Whenever you change a fact — a rate, a policy, a minimum stay. Each change is a chance for the summary to drift, and one question afterwards is enough to catch it.

Write the facts plainly, put them where they're easy to lift, and read the summary that comes back. Do that and your listing survives the trip from your page to a guest's question without changing shape. Put the question to your own listing at localsbnb.com and you'll see exactly what a machine keeps and what it drops.

---

This is general guidance for hosts, not legal, tax or insurance advice. Platform features, assistant behaviour and local rules change over time; check the current terms of each platform you use and the current guidance of your local authority.