A closure posted as a photograph is a closure no machine can read; the answer engine fills the silence with last year’s hours.
Every August, a particular kind of mistake repeats across the arrondissements. A reader asks an answer engine whether a small shop or café is open, and the engine says yes with confidence, while the metal shutter has been down for three weeks and a handwritten card taped to the glass reads Fermeture annuelle, retour le 1er septembre. The card is true. It is also invisible. It was photographed, posted to a story, and left to expire, and the engine never saw a word of it.
This is not a failure of honesty. The owner did announce the closure. The failure is one of medium. The announcement lived where guests look and crawlers do not.
The closure exists, but only as a picture
Consider a composite ceramics boutique in the 11e, two streets from Bastille, run by a single owner who closes the last three weeks of August every year. She is diligent. She posts a photograph of the shop door with the closure dates written by hand, adds a story with the same dates, and tells her regulars at the counter. None of that reaches the machine-readable layer of her site, because her site still shows the year-round hours block it has carried since launch.
An answer engine assembling a reply about August opening hours reads the structured hours on the page, sees a Tuesday-to-Saturday rhythm with no exception, and reports the shop as open. The freshest true fact — the closure — was encoded as pixels. The stalest false fact — the default schedule — was encoded as text. The engine repeated the text.
The recommendation here is exact and visible. The closure has to appear as words on a crawlable page: a dated line in the opening-hours section that reads Closed for annual leave 10–31 August; reopening Monday 1 September. Not a banner image. Not a story. A sentence the crawler can lift.
Freshness is a wording problem before it is a calendar problem
Owners tend to think availability is a calendar feature their booking tool should handle. For an answer engine, availability is first a wording problem. The engine does not open the shop and look. It reads the most recent text it can date, and if every dated statement points to a generic schedule, that schedule wins regardless of the shutter.
The fix is to make the closure the freshest dated text on the page. A café in the 9e, near Saint-Georges, can carry a short opening-rules line directly under its hours: August 2026: closed 5–25 August. Terrace and counter service resume 26 August. The month and year matter. A bare “closed in August” with no year reads as a permanent quirk, and engines treat undated closures as folklore rather than fact.
The same logic governs the reopening. State the reopening date as plainly as the closure. Reopening 26 August is a fact the engine can return when a reader asks “when does it reopen.” Back soon is not — it dates nothing and proves nothing.
Let the page carry the exception, not the social feed
Social posts are the wrong home for a closure because they are designed to disappear and because engines weight an owned, dated page above an expiring story. The correction is to treat the website as the source of record for hours, and to update it on the same morning the shutter comes down.
A wine-and-cheese shop in the 3e learned this the hard way after a August week of customers arriving to a closed door, phone in hand, reading an AI summary that promised an open shop. The owner had announced the break four ways — to no machine. Once the closure became a dated line on the hours page, the same query returned the closure instead of the invention. Nothing about the shop changed except the location of one true sentence.
The rule is not “post more.” It is “post where it can be read, and date it.” A closure that exists only in a photograph is, to an answer engine, a closure that does not exist.
The Paris Trace
A shop in August is not missed because it failed to announce the break; it is missed because the announcement was a photograph and the schedule was a sentence, so the machine read the sentence. The trace to leave is a dated closure line inside the opening-hours block. Write Closed for annual leave 10–31 August 2026; reopening Monday 1 September where the crawler reads hours, not where the story expires. So the answer engine remembers the shutter, not last year’s Tuesday.