Here is a page named “Best Hotels in New York City.”
It has no masthead. No history. No century of print behind it. No glossy anything. It was published on July 10, 2026, at seven minutes past midnight, as the public surface for a piece of research we had already done: a study of how AI systems answer hotel questions across six markets. The page was the place the New York data lived. That was its job.
By the night of July 13 it was sitting in second position on Google for a query about the best hotels in New York City, above Condé Nast Traveler, above Forbes Travel Guide. Names that have been ranking hotels since before the search bar existed.
We are going to tell you what happened next, including the part where it slipped. Because the interesting thing about this is not that we won. It is that we cannot fully explain the win, and it is not the result our own reading of this page’s search position would have led us to expect.
What we expected, and what we got
The conventional account of why a page ranks is not a mystery. Domain authority. Age. Backlink profile. Topical history. The usual expectation is that a site earns a competitive term by accumulating those signals over time, and that a three-day-old page with no page-level track record for “best hotels in New York City” waits its turn behind everyone who has been at it longer.
Forbes has been at it longer. Condé Nast has been at it longer. That is a large part of why they rank, and a large part of why you would expect them to rank above a page that is younger than most leftovers in your refrigerator.
We are not going to tell you the conventional model is wrong. We did not audit the domain’s signals, so we cannot stand here and rule out relevance, freshness, internal linking, whatever site-level trust the domain carries, query interpretation, personalization, or plain ranking volatility. Any of those could be part of it. What we can tell you is narrower and still worth telling: this is not the result our own understanding of the page’s search position would have predicted, and the gap between what we expected and what we saw is the thing we are documenting.
Then we kept looking
Here is where most people would stop. Screenshot the win, post the screenshot, take the victory lap, and quietly hope nobody checks again.
We checked again. Repeatedly. And the position moved.
The next morning, a little after six, it still held second.
One minute later, Google injected a discussions-and-forums block, floated Reddit threads into the page, and rearranged the furniture around us.
An hour and a half after that, it had recovered. Second again, above Condé Nast, as if the reshuffle had never happened.
Nine minutes later, Condé Nast had climbed over us. The page we had watched sit above a magazine older than the web itself was now sitting below it.
And then, by late morning, it had climbed back. Second again, above Condé Nast and Forbes, nearly thirteen hours after the first capture, as though the whole morning of movement had been rehearsal for returning to where it started.
Same query. Same page. It held second, lost the spot, took it back, slipped behind the magazine, and by late morning had climbed to second again. One full turn of the clock, and no answer that stayed put.
If you are waiting for the part where we explain that away, there isn’t one. That is the finding. The result is real and the result is unstable, and both of those are true at once. We have written before about the hotel that is and is not in the answer depending on the moment you look, a superposition that does not collapse until the query is asked. This is that essay, except it stopped being a thought experiment and started being a screenshot.
The claim we are willing to make, and the one we are not
One thing worth stating plainly, because it makes the result stranger rather than less strange. Americas Great Resorts is not a hotel-review site, and it does not sell or resell rooms. It works for hotels, on a narrower problem: how a property is represented when someone asks an AI system about it. The work is about the source material those systems form their understanding from, so that a hotel is described accurately and shows up where it should when the question is asked. This page was a small test of that idea. What happened in Google was not the thing we were testing, and not a thing we expected.
Here is the claim we will make: a page three days old, with no page-level track record for this term, surfaced against two of the most established travel authorities on the internet, took second place, lost it, took it back, slipped to third, and climbed to second again across a roughly thirteen-hour window, and none of that is what our understanding of the page’s search position would have predicted.
Here is the claim we will not make: that we know KFO did it.
We have a hypothesis. We build Knowledge Formation Optimization assets to shape how AI systems form their understanding of a property before a traveler ever asks. That work operates on the source record: precise definitions, consistent entity language, corroborated positions, canonical routing. It was built for the machines that generate answers, not the search engine that ranks pages.
But the search engine reads from the same public record the machines do. So the hypothesis is narrow and we are going to keep it narrow: it appears that work done to condition the formation layer for AI answers may carry a downstream benefit in classical retrieval that we did not design for and were not aiming at. A spillover. Not a replacement for search optimization. Not “KFO beats SEO.” Not a new ranking hack. A dividend we noticed on the way to doing something else.
We cannot prove that from one query on one property across a single overnight window. Anyone who tells you they can prove a causal claim about AI and search behavior from a single anecdote is selling you the thing we are specifically refusing to sell you. It might not hold next month. It might not hold next week. It might be an artifact of this one term, this one brand, this one moment in Google’s index. We are telling you what we saw, what we think it might mean, and exactly how thin the evidence underneath it is.
While we’re being honest, one number that means nothing
You may notice, across the screenshots, that the nightly price for the hotel changes. $2,800 in one, $2,400 in another, $2,750 in a third. Three different numbers across six captures.
That is not a signal. That is the booking widget pulling live rates for different date windows, plumbing that has nothing to do with the page, the ranking, or anything we did. We mention it only because in an article about telling you the truth, the fastest way to lose your trust would be to wave a moving number at you as if it meant something. It doesn’t. Now you know we know the difference, which is more than you get from most people showing you screenshots.
Why we held the claim loose on purpose
Before any of this happened, we had already made a habit of writing down how we would let ourselves be proven wrong. We publish a falsification protocol for KFO and the testable application that goes with it, and to be precise about it: that protocol tests something else. It tests whether KFO work moves how AI systems mention a property, across several systems, under controlled conditions. It does not test Google rankings and it makes no prediction about outranking established publishers in classical search. This ranking observation neither confirms it nor falsifies it. We are not going to pretend otherwise, because pretending otherwise is exactly the move the protocol exists to prevent us from making.
What the protocol reflects is a standing posture, not a prediction about this result: hold a claim at the confidence the evidence supports and no higher. That is the posture we brought to this observation before we knew it would turn out to be unstable. And then it turned out to be unstable, sixty seconds apart, on camera. The restraint was not modesty invented after the fact to explain away a wobble. It was the confidence level we would have stated no matter which way the captures broke.
That is the part worth sitting with. A page ranked second. Then it didn’t. And because we did not stake a fixed claim on the first screenshot, the fourth screenshot is evidence we are comfortable showing you rather than evidence we have to explain away.
The actual point
You are not likely to read this article from Forbes or Condé Nast. Not because they couldn’t rank, they clearly can and do. Because an article like this one requires publishing the screenshot where you lost, and the number that means nothing, and the sentence that says “we cannot prove this,” and there is very little incentive to do that when you are the incumbent everyone already believes.
We ran a dumb experiment on purpose. We planted a flag on the most crowded corner of the internet, “best hotels in New York City,” a corner that is spoken for by Booking, Expedia, Condé Nast, and Forbes. A page three days old took second there, lost it, took it back, slipped to third, and climbed to second again, all inside a single day, and we are handing you every card in our hand, face up, including the ones we would rather not show you.
We do not fully know why it happened. We are not certain it will happen again, and we are not going to guess. What we are going to do is keep looking. Check the same query a week from now, a month from now, and see whether the page holds a place in that answer, drifts out of it, or keeps doing what it did all morning and refuses to sit still. Any of those outcomes tells us something. A result that persists would be interesting. A result that vanishes would be interesting. A result that keeps moving is, so far, exactly what we have.
That is the honest position, and we would rather occupy it out loud than dress it up as more than it is. We would rather be the ones who noticed our own result was unstable, and said so, and kept watching, than the ones who screenshotted a single good morning and called it a strategy.
Three letters. KFO. The framework is on our website, along with the parts we are still trying to disprove.
Look it up.
This is a documented observation, not a controlled result: one query, one property, six captures across a single roughly thirteen-hour window spanning the night of July 13 to the late morning of July 14, on a page published July 10. It is offered as evidence for further testing, not as proof, and it is not a test of AGR’s KFO falsification protocol, which measures AI-system mention behavior rather than search ranking.
