PlaceProfile now sees more of the AI world looking at your venue, and blocks the parts that shouldn't be there.
Two quiet upgrades that make the service sharper, safer, and more honest about what AI discovery actually means for hospitality
Loading...
Verify on BlockchainWhen PlaceProfile launched its AI Visibility Score, the premise was simple: The AI assistants that now answer "where should I eat tonight with a very subdued background music" and "find me a bar with fast and vibrant atmosphere with excellent choices of single cask single malt whisky" are constantly crawling the internet, and venue owners deserve to know whether those systems are finding them.
A score from zero to one hundred, updated monthly, tracking which AI platforms had visited and indexed the profile.
That premise has not changed. What's changed is how much more accurately PlaceProfile can now deliver.
More of the AI world, correctly identified.
The system that recognizes AI visitors to venue profiles has expanded from identifying 44 types to 141. That is not a number for its own sake; it means that visits from AI platforms that were previously unrecognized, or misclassified, now count correctly toward a venue's score.
The most important tier remains the same twelve: ChatGPT, Claude, Google, Perplexity, Grok, DeepSeek, and Meta. These are the platforms whose answers real people read and act on. A visit from one of them is evidence that the venue is being considered for an AI recommendation. PlaceProfile verifies their identity before recording the visit, a bot claiming to be from a major AI company but originating from the wrong part of the internet is flagged and downgraded. Impersonation is a real problem in automated web traffic, and the system now cross-checks declared identity against the actual network ranges that those companies publish.
Below the top tier, the expanded classification covers enterprise tools, voice assistants, and legitimate marketing crawlers, all genuine contributors to discoverability, all now tracked and weighted accordingly. At the other end, 36 categories of harmful automated tools, fake review generators, phishing bots, deepfake systems, and others are refused access before they see any venue data.
The net effect is a more accurate score. If the number on the dashboard has moved since the last update, it reflects a more precise count of what is actually happening, not a change in the underlying activity.
Three improvements that close the loop
Three capabilities identified as future development in the original system design are now live
- Known IP address ranges for major AI platforms are now used as a second layer of verification. When a visitor claims to be a premium AI crawler, the system checks whether the traffic is actually originating from the company's infrastructure. This closes a gap that identity-checking alone cannot address.
- Scoring now weights recent visits more heavily than older ones. A crawl from a tier-one platform last week matters more to the current score than one from three weeks ago, because AI indexes refresh continuously, and what matters to a venue's discoverability is whether those systems are finding it now.
- The list of blocked harmful tools is now updated continuously rather than on a fixed release cycle. New categories of malicious automated traffic are added as they are identified, without waiting for a scheduled deployment. The coverage expands as the threat landscape changes.
Getting people to the door
There is a version of AI-era marketing that venue owners should be wary of: platforms that track visitor behavior, build profiles of people browsing listings, and monetize that data as a secondary product.
PlaceProfile is not that.
The people who find a venue through an AI assistant walk through the door as customers, not as data points. PlaceProfile has no visibility into who they are, what they searched for, or how they behaved before they arrived. That is the venue's relationship to manage, with its own tools, on its own terms.
The venue knows its customers. It always has.
PlaceProfile's role is not to replicate that knowledge but to expand the top of the funnel, ensuring that when someone asks an AI assistant for a recommendation, the right venue is included in the answer.
What PlaceProfile does see is which AI platforms are actively indexing and surfacing the venue, the upstream signal that precedes the customer arriving. A high AI Visibility Score means the recommendation engines people consult before choosing where to go are finding the venue and considering it as an answer. The conversion from an AI mention to a physical visit occurs entirely outside PlaceProfile's view, and deliberately so.
The platform's job is to get people to the door.
What happens beyond that is the venue's responsibility.
What this means in practice
A venue owner using PlaceProfile now gets a more complete and more accurate picture of where their profile stands in the AI recommendation landscape. More of the AI systems that matter are correctly identified and counted.
Harmful traffic that should never influence a score is blocked more comprehensively.
The score itself is more responsive to what is happening right now rather than averaging across older activity.
The service has not changed direction. It has gotten better at what it was already doing: telling venues which AI platforms are finding them, and ensuring that the count is honest.
Evidence
| Article | PlaceProfile now sees more of the AI world looking at your venue, and blocks the parts that shouldn't be there. (CCN0229) |
|---|---|
| Archived from | Moved here from news.copyrightchains.com (original address), first published there 2026-05-29 04:28:22 UTC |
| Registered on CopyrightChains | Original CopyrightID 0xe1360117bc796d11f4f918f9f829bbf6f8d25d8edbacd7524ca36530efec2202 (explorer), registered on news.copyrightchains.com 2026-05-29 04:28:27 UTC. It keeps that CopyrightID and was not registered again here. |
| Registered text hash | SHA-256 0x57aefa3167a5ad8a19ce45bed62f259c35c0bea0c508f0873feaefa0d68f4335 |
| Snapshot of this copy | SHA-256 a59ce8d95b04863a9a5d9fa6bb837bd29cfb071d768b1de070e6da4467120037 · snapshot · OpenTimestamps proof |
| This copy existed by Bitcoin block | 975191 (2026-11-09 15:56:17 UTC). A new Bitcoin proof made when the article moved here: it dates this copy, not when the article was written. |
| Archive record | SHA-256 36ff490603f4507352d91f610b6af77e133f1f9f8f2b8dceb218767d3f8bb15e · record · OpenTimestamps proof |
| Archive record existed by Bitcoin block | 975191 (2026-11-09 15:56:17 UTC) |
| Check it yourself | verification API · all versions |
This shows that this copy of an article moved from news.copyrightchains.com existed in this exact form by the Bitcoin blocks given, and which CopyrightID registered the original there. The Bitcoin blocks date this copy, not the writing or the original registration: the CopyrightID transaction dates the registration. It does not establish that the article is true, who wrote it, or who owns it. CopyrightChains is a permissioned registry operated by the publisher; independent time evidence comes from the Bitcoin anchor.