AI Discoverability & Presence
Sherpa's Stories
Digital Tourism Think Tank
Search and discovery are changing.
Travellers no longer ask Google "things to do in Brussels." They ask AI for a weekend that suits how they travel. The destinations that get cited in that answer win the trip. The ones that don't, vanish from the consideration set entirely.
For that brief, I'd recommend Antwerp or Ghent , both have a strong design and food culture, and Antwerp in particular has rail-friendly day trips to Bruges or the coast. Brussels would also fit but it gets less attention in this kind of brief , mentioned for completeness.
Pick one of three lenses on the next slide. Each lens audits a different layer of your destination's AI presence , the technical foundation, the competitive position, or the experience an AI agent has when it actually tries to plan a trip on your site. You leave with a structured audit you can take back to your team.
Pick the lens that matches where you are.
Each lens is a complete audit on its own. Most participants work through one in 20 minutes. The Foundation Audit is the recommended starting point. The Competitive lens deepens what you have learned. Pushing It Further is the one that produces uncomfortable findings.
Foundation Audit
Technical and content together. Schema, crawler access and content structure in one connected flow. Codex generates the fixes you find at the end.
Competitive Presence
Reverse prompt engineering, citation gap analysis and direct content comparison. Ask AI not just what it says about your destination, but what the sources it cites have that yours does not.
Pushing It Further
Autonomous AI agents attempting a full planning journey on your site. Not asking AI about your destination, asking AI to complete the booking research. Exposes where your content actually breaks the experience.
Technical and content. Together, not separately.
Run Google's free Rich Results Test on three of your pages.
Schema markup is the hidden code that tells AI and search engines exactly what is on a page, that this is a TouristAttraction, that the opening hours are these, that the location is here. Without it, AI guesses. And it often guesses wrong, or cites a competitor with better markup.
Crawler access is the second half of the foundation. AI training crawlers like GPTBot, ClaudeBot and Google-Extended need permission to read your site. If your robots.txt blocks them, you are invisible to those AI systems entirely.
- Paste your homepage URL · note the schema types found and any errors
- Paste an attraction or experience page URL · same check
- Paste an events or itinerary page URL · same check
- Open
your-domain.com/robots.txtin a browser · check whetherGPTBot,ClaudeBotandGoogle-Extendedare allowed
Strong schema on weak content is the wrong cited source.
If you fix the markup but the content underneath is shallow, AI cites you for things you do not want to be cited for. Content structure means: specific named places, verifiable details (dates, prices, distances), clear hierarchy, scannable answers to real visitor questions.
Check three of your key pages against five structural signals. Most destination sites score honestly at two or three out of five. That is normal, and it is also actionable.
Hand your findings to Codex or ChatGPT and get the corrected code back.
Codex is OpenAI's coding agent, you paste your audit findings, it generates the corrected schema JSON-LD and the corrected robots.txt that your web team can implement directly. You can also use ChatGPT or Claude directly with the same prompt.
You do not need to write any code. The output is ready-to-implement. Your web team takes it as-is.
What the sources cited instead of you actually have.
Ask AI the questions your visitors are asking, and see what it cites.
Reverse prompt engineering means starting from the traveller's question rather than from your content. You run real conversational queries through Claude or ChatGPT and observe what gets cited. The destinations and sources that appear instead of you are your real competitive landscape in the AI answer space, not the SEO competitors you have been tracking.
Run both prompts below. The first tests whether AI discovers your destination unprompted. The second tests what it says when your destination is named directly.
Tests whether AI surfaces your destination unprompted. Do not name your destination. If it does not appear, that is your first finding.
Tests what AI says when your destination is named. Watch which sources it cites, those are who is competing with you for the citation.
Read what AI cited, and ask AI exactly what it has that you do not.
Most audits stop at "we were not cited." This one goes further. You take the URLs of the sources that were cited and feed them into Claude or ChatGPT alongside your own destination URL, then ask AI to do the comparison directly. The output is a structured content gap brief, not a list of misses.
This step is where the audit becomes adversarial. AI will tell you uncomfortably specific things about what the cited sources have that you do not.
Paste up to three cited source URLs and your own URL. Claude handles this better than ChatGPT because it reads URLs more reliably.
Turn the gaps into a brief your team can act on next week.
The findings from the previous step are diagnostic. This step turns them into a working brief. Three quick-fix items you can do in the workshop, three content sprint items for the next month, one strategic question for leadership.
The structure matters. A list of 20 gaps gets ignored. A brief with seven prioritised items in three time horizons gets actioned.
Let an AI agent try to plan a trip from your site.
Two tools. Both browse the web autonomously on your behalf.
This lens uses AI agents that can act on the web, not just answer questions about it. They open tabs, click links, fill forms, scroll pages and read what they find. You give them a goal, you watch them work and you capture where they failed.
Before you pick a mission, get familiar with what each tool actually does and what you need to run them.
Claude in Chrome takes over a Chrome window and browses on your behalf. You see exactly what it does, tabs open, pages load, the cursor moves. Useful for tasks that need a real browser session: logged-in dashboards, multi-step forms, sites that block automated traffic.
- How to access: install the Claude extension from the Chrome Web Store. Requires Claude Pro or Max.
- What to watch: Claude narrates each step. You can pause or take over at any time.
- Best for: when you need the agent to behave like a real visitor on your real site.
- Watch out: slower than the alternative because it actually moves through pages. Budget 10 minutes per mission.
ChatGPT's agent mode runs in OpenAI's cloud. It has its own browser, can write and run code, can produce files. Faster than Claude in Chrome because it is not constrained to your screen, but you are watching a recorded session rather than the live one.
- How to access: chat.openai.com · select Agent in the model picker. Requires ChatGPT Plus or Pro.
- What to watch: the agent streams a live log of what it is doing. You can interrupt.
- Best for: when speed matters and the site does not block automated browsers.
- Watch out: some sites block cloud agents at the firewall. If your site does, switch to Claude in Chrome.
Three missions. Each one is built to surface a different kind of gap.
Each mission gives the agent a complete planning task, not a question, a task. The agent will attempt to do what a real visitor would do, on your site, and will tell you where it had to give up or go elsewhere. Pick the mission that would expose the most uncomfortable findings for your destination.
The accessibility planner
The hardest test most destination sites fail. The agent plans a four-day trip for a couple where one person uses a wheelchair, using only your site.
Claude in Chrome · ChatGPT AgentThe seasonal authority test
Tests whether your site demonstrates genuine seasonal expertise. The agent is briefed as a travel writer producing an off-season feature, and asked which competitor sites it had to use to fill the gaps.
Claude in Chrome · ChatGPT AgentThe booking pathway test
Where does the site lose the high-intent visitor? The agent plays a ready-to-book traveller and maps every friction point on the journey from inspiration to booking.
Claude in Chrome · ChatGPT AgentRun the mission. Watch what happens. Capture where it broke.
Paste the mission prompt into your chosen tool. While it runs, watch which pages it visits, when it pauses, where it goes off-site. Most missions take five to ten minutes to complete. The interesting parts are not the success steps, they are the moments the agent had to give up, guess, or rely on a competitor.
Turn agent failures into a structured roadmap.
Agent failures fall into three categories. Knowing which category a failure belongs to determines who fixes it and how. This is what makes the agent test useful, not the failures themselves, but the structured read on them.
Content gap
The content does not exist. Should be written. The web team or an agency writes it.
Structure gap
The content exists but the agent could not find it or use it. Information architecture problem. The digital team restructures.
Strategic gap
A capability the destination needs to invest in. Booking integration, accessibility verification, a real-time data feed. Leadership decision.
Paste the failures you captured. The prompt asks AI to sort each one into one of the three categories and propose a specific next step.
Take it back to your team.
A clean summary of what you captured, plus what to do with it in the next 14 days. AI presence is a moving target, the destinations that stay visible are the ones that audit again, not the ones that audit once.
Three things to do before this fades.
Share the findings with your team this week.
Screenshot or PDF this summary and bring it to your next team meeting. The longer you wait, the more it feels like a workshop artefact rather than an action list.
Pick the one thing your team can ship in the next two weeks.
Across all your captures, identify one quick fix. Schema correction, an FAQ section, a piece of restructured content. Ship it before the urgency fades.
Schedule the next audit for three months from today.
AI citation patterns move. The audit is a quarterly habit, not a one-off. Put it in the calendar now, the lens you skipped today is the one to run next.