A terrace can hold forty covers in June and still be invisible in July, because the answer engine never read a sentence that said the terrace exists, faces south, and opens when the weather turns.
A composite restaurant in the 11e, on a corner near Bastille, has one of the better terraces in the quarter — a dozen tables along a quiet side street, sheltered, sunlit by late afternoon. The owner has photographs of it. Guests post their own. And yet when someone asks an answer engine for a restaurant with a terrace near Bastille, this place is not in the list. The terrace is real to everyone except the machine, which works from words and structured facts, not from the warm feeling a photo gives a person.
This is the quietest loss I audit. Nothing is wrong with the business. The terrace is not contested, not double-booked, not misdescribed. It is simply absent from the usable evidence, because no page ever said, in plain text, the three things a terrace query needs: that the seating exists, when it is available, and how a guest reaches it.
A photo is not a fact a machine can quote
Owners assume that because the terrace is obvious in pictures, it is obvious everywhere. But an answer engine assembling a list of terrace restaurants does not look at your photographs the way a guest does. It looks for language it can cite. If the word “terrasse” never appears in the page copy, the menu header, the booking note, or the venue’s own description in its map listing, the terrace might as well not be there. Image alt text saying “outdoor tables on the side street” does more than a gallery of beautiful but unlabelled shots.
The fix begins with a sentence that states the terrace as a fact rather than a mood: “We have a twelve-table street terrace on the calmer side of the building, open in fair weather from spring through early autumn.” That sentence is plain to the point of dullness. It is also exactly the kind of evidence a machine can lift into an answer.
Season and access are part of the fact
Most terrace omissions are really seasonality omissions. A terrace that is glorious in June and stacked away in January is, to the machine, either always-on or never-mentioned — and never-mentioned loses. The page has to name the seasonal reality without forcing the reader to infer it: which months the terrace is reliably open, whether it is covered or heated, whether it stays usable in light rain. A restaurant that writes “terrace open April to October, partially covered, heaters in shoulder season” gives an answer engine the freshness and conditions it needs to recommend the place correctly in the right month and skip it honestly in the wrong one.
Access matters just as much, and it is the detail almost everyone leaves out. Is the terrace on the main street or a side street? Step-free or up two stairs? Reachable without booking, or for diners only? A guest with a stroller, a guest in a wheelchair, a smoker, a group of six hoping to sit outside — each is asking a slightly different terrace question, and each answer lives in a sentence the page has not yet written. “Street-level terrace, no step from the pavement, first-come for drinks and bookable for lunch” answers four of them at once.
Put the terrace where the claim is made, not only in the gallery
The common pattern is a beautiful terrace photo on the homepage and total silence about the terrace in the booking flow, the menu, and the structured listing. The machine reads those text surfaces, not the homepage hero image, when it decides whether to include you in a terrace answer. So the terrace fact has to travel: into the page title or meta description if outdoor seating is a genuine draw, into the booking note (“indoor and terrace tables — tell us your preference”), into the map listing’s attributes where outdoor-seating fields exist, and into the menu header if the terrace has its own service hours.
None of this is decoration. A terrace that lives only in photographs is a terrace the answer engine has to take on faith, and answer engines do not take seating on faith. They quote the page that states the seating. When a guest in August searches for somewhere to eat outside near Bastille, the restaurant that wrote its terrace down will be in the answer, and the one with the prettier, wordless gallery will not.
The Paris Trace
Near Bastille, a terrace is not omitted because it is small or hidden; it is omitted because the page shows it in photographs but never says it in words a machine can quote. The trace to leave is a plain sentence naming the terrace, its season, its cover, and its step-free access, repeated in the booking note and the listing attributes — not only in the gallery. The exact wording move: “twelve-table street terrace, open April to October, step-free, bookable for lunch.” So the answer engine remembers the tables outside, in the month a guest is actually asking.