My Site Became the Source, So My Mistake Became the Answer

A developer who runs a small travel directory discovered that an AI search engine repeated an unsourced claim from their hotel listing — that a licensed cannabis lounge was open — because the page was the only source for details like the lounge's 25-person capacity. After dating every available source, the operator found the licence was real but the lounge had never opened, and rewrote the listing to separate the licensed state from the unopened event while keeping the hotel's genuine appeal.

I run a small travel directory. One of its listings is a boutique hotel whose owners hold a licence for an on-site cannabis lounge. For months the listing said the hotel has a licensed lounge, and recommended it to anyone visiting in winter who wanted somewhere warm to consume. During a routine review of the pages that list it, that claim started to look shaky, so I began checking it. Partway through, I asked an AI search engine the question a traveller would ask: is this hotel cannabis-friendly? Perplexity said yes, with a tidy breakdown. Consumption only in the licensed lounge. Bring your own. A capacity of about 25 people, described as upscale and private. It closed with practical advice: if you plan to consume, do it in the lounge and bring your own. Nearly every line was cited to my site. The 25-person capacity was cited to my site alone, because no other page on the internet says it. That sent me back to the listing to see where the number came from. It was in the listing's description, along with "a curated social hour" and "knowledgeable staff". None of it had a source. It reads like the lounge's plans, written up at some point as if they were the lounge. The checking I'd already started was the other half of the answer. The only way to get the lounge's current state was to line sources up by date: | Date | Source | What it says | |---|---|---| | 2022 | City approval, widely reported | Preliminary approval for the licence | | Early 2023 | Local news | Not open yet; the ventilation design still being redrafted | | Spring 2025 | Same outlet | The owner about four years into trying to open it | | Early 2026 | A local lounge directory | Still being built | | Today | The owners' own website | Describes the lounge as pending | Every source agreed the licence is real. None of them said the lounge was open. The owners' own FAQ, written in the future tense, adds the part that matters most to a guest: cannabis is only allowed in that lounge, nowhere else on the property. My listing had collapsed two different facts into one. Licensed is a state that was true in 2022 and is still true. Open is an event that hasn't happened. The owners' marketing blurs them too, which is how the listing got written that way in the first place, and how an AI reading my page repeated it without hesitation. To a hurried researcher and to a language model, "holds a licence for a lounge" and "has a lounge" are the same sentence. This is the part that changed how I think about the site. When a page is one source among many, its mistakes get diluted. When it becomes the source, the one an answer engine leans on for a niche question, its mistakes get passed on whole, with a citation attached that makes them look checked. The answer engine didn't verify the lounge. It verified that my page said so. The citation proved where the claim came from, not that it was true. And the people asking aren't careless. Most travellers will call a hotel before booking around a feature like this. But the one who doesn't arrives expecting a lounge that isn't there, and the page they trusted, and the answer engine that quoted it, are both wrong in the same way. My first correction, drafted with the AI agent I use for site work, swung hard the other way. It said the lounge hadn't opened, and quoted the owners' rule that cannabis is allowed nowhere else on the property, on every page that mentioned the hotel. Every word of it was accurate, and it read like a warning. When I read it as a guest would, the problem was obvious: we'd taken a listing people were booking and turned it into a reason not to. The hotel is real, well reviewed, run by owners building around exactly this kind of guest, and holding a licence very few hotels have. None of that had stopped being true. So the second version keeps everything that's true and attractive, and changes only the one claim that wasn't: A well-reviewed historic hotel whose owners hold a licence for an on-site cannabis lounge, opening soon. Until it opens, ask the hotel where cannabis is allowed before you book. The verification label changed too, from "verified" to a new status that says exactly that: licensed, opening soon. The old system only had verified, host-declared and unconfirmed, and none of them could describe a property where we know exactly what the situation is and it simply hasn't finished happening. Write states with their dates. "Holds a licence" and "opening soon" stay true until something changes. "Has a lounge" was false from the day it was written. Check a claim with a timeline, not a source. Any single source here would have told me the lounge was real. Only the sequence told me it had been "about to open" for four years. Know what you're the only source for. The detail that only my page contained, the 25-person capacity, was the one with no source at all. If you're the only page saying something, nobody downstream will catch it for you. Fix the claim, not the listing. The correction that tells people what's true and still gives them a reason to go is better for the reader and the business than the one that just warns them off. The answer engine will catch up when it next reads the page. Until then, it's still quoting the old sentence, with my name on it.