What an AI agent reads on Why We Live Travel
An assistant's crawler fetches the page once, without running JavaScript, and reads the text, the structured data and the links. Below is what it gets from whywelivetravel.com, taken from the copy the scanner kept.
561
characters of text without JavaScript
Organization
structured data for the business
0
of 3 AI crawlers turned away at the edge
The words an agent gets
Title: Why We Live TravelClose modal window · language en-US. First 561 of 561 characters:
Why We Live Travel Home About Us Group Adventures Personalized Trips Contact Book Trip Blogs and Inspiration Menu WHY WE LIVE TRAVEL Embark on Your Next Adventure to Redefine How You Live Ready to Explore? WE LIVE FOR ADVENTURE We Believe in the Power of Active Experiences to Inspire & Motivate Ready for Adventure? WE LIVE FOR CONNECTIONS We Seek to Connect Authentically With Local People & Local Experiences Ready to Connect? WE LIVE FOR Great Food We Promise an Incredible Gastronomic Journey that Complements the Richness of Each Destination Ready to Eat?
What it can say about the business
| A business type in JSON-LD | Organization |
| Name | Why We Live Travel |
| Telephone | (352) 812-2860 (a tel: link, not structured) |
| Address | no |
| Opening hours | no |
| Menu or price list | nothing |
| Cuisine in structured data | no |
| JSON-LD blocks | 1 (BreadcrumbList, EntryPoint, ListItem, Organization, SearchAction, WebPage) |
The links it would act on
| Link | Role | Where it goes |
|---|---|---|
| schedule.nylas.com/whywelivetravelconsultation | booking | an unrecognised third party |
Everything here comes from fetching the homepage once as a crawler. The report turns it into a score and a list of fixes, with code to paste.