Agentic Readiness Index

Understand and improve your ARI score

The ARI measures how well your website can be understood and used by AI agents — for search, recommendation, and automated booking. It evaluates 20 signals across 5 areas, each worth 5 points, for a maximum of 100.

Score ranges

90 – 100Excellent

Optimal infrastructure for AI agents. Your website is fully readable, bookable, and up to date. You are ready for the next generation of AI-driven travel discovery.

70 – 89Good

Well prepared for agentic indexing. Strong signals in place. A few gaps remain — addressing them would push you to Excellent.

40 – 69Fair

Partially readable by AI agents. Structural or execution gaps detected. Improvements to your booking flow and structured data will have the most impact.

0 – 39Low

Your website is difficult or impossible to use by AI agents. Foundational issues (HTTPS, mobile, booking flow) need to be addressed as a priority.

Structure

25 pts max

Technical foundation — security, mobile, and structured data.

HTTPS validEasy

What we check

Your website is served over HTTPS (secure connection). This is a baseline requirement for any modern website.

How to fix it

Contact your hosting provider or domain registrar. Most offer free SSL certificates (Let's Encrypt). In Squarespace, WordPress, or Wix, enable HTTPS in your domain settings.

Mobile friendlyEasy

What we check

Your website has a proper viewport meta tag and renders correctly on mobile devices. Detected via Google Lighthouse.

How to fix it

Add <meta name="viewport" content="width=device-width, initial-scale=1"> in your HTML <head>. Most modern website builders (Squarespace, Wix, WordPress) do this automatically. If your site looks broken on mobile, consider switching to a responsive theme.

Schema.org (JSON-LD)Medium

What we check

Your website contains structured data in JSON-LD format. This tells AI agents what your business is, where it is, and what it does — in machine-readable language.

How to fix it

Add a <script type="application/ld+json"> block in your page <head> with a LocalBusiness or TouristAttraction schema. Tools like Merkle's Schema Markup Generator can help. Many WordPress SEO plugins (Yoast, Rank Math) add this automatically.

Transactional schema (Offer/price)Hard

What we check

Your Schema.org data includes an Offer type with price and availability fields. This tells AI booking agents that a transaction is possible — not just that you exist.

How to fix it

Add an Offer block inside your schema: {"@type": "Offer", "price": "120", "priceCurrency": "EUR", "availability": "https://schema.org/InStock"}. This requires manual editing of your schema or a developer. Note: most booking engines (FareHarbor, Bokun) do not inject this automatically — it is a known industry gap.

Valid sitemapEasy

What we check

A sitemap.xml file is accessible at your domain root. This helps search engines and AI crawlers discover all your pages.

How to fix it

Most CMS platforms generate a sitemap automatically. In WordPress, install Yoast SEO. In Squarespace, go to Marketing → SEO → Sitemap. In Wix, it is generated automatically. You can verify at yourdomain.com/sitemap.xml.

Execution

25 pts max

Booking flow — can an AI agent find and use your booking system?

Booking engine detectedMedium

What we check

A recognized online booking engine (FareHarbor, Bokun, Rezdy, Peek, Checkfront, etc.) is detected on your page. This is one of the strongest signals that direct booking is possible.

How to fix it

If you use a booking engine, make sure it is properly embedded on your main booking page (not hidden behind a link to an external domain). If you do not have one yet, FareHarbor, Bokun, and Rezdy are popular options for tour operators.

Book / Reserve buttonEasy

What we check

Your page contains a clearly labeled call-to-action using words like "Book Now", "Reserve", "Check Availability", or their equivalents in French or Spanish.

How to fix it

Add a visible button or link on your homepage and tour pages with text like "Book Now", "Reserve your experience", or "Check availability". This should be above the fold (visible without scrolling) on desktop and mobile.

Booking calendar / iframeMedium

What we check

A booking calendar, date picker, or booking widget iframe is embedded on your page. This is a strong signal of a real-time booking flow.

How to fix it

Embed your booking widget directly on your website using the embed code provided by your booking engine (FareHarbor, Bokun, etc.). Avoid linking to an external booking page — the widget should load on your own domain.

Date parametersEngine-dependent

What we check

Your URLs contain date parameters (?date=, checkin=, start_date=, arrival=) — OR a recognized booking engine is detected (which handles dates natively in its iframe). This confirms that real-time availability is possible.

How to fix it

If you use FareHarbor, Bokun, or a similar engine, this signal is automatically credited. For custom booking forms, ensure your availability search form passes date parameters in the URL.

Direct booking confirmed (non-OTA)Easy

What we check

Your business has been manually verified as a direct operator — meaning travelers can book with you without going through an OTA (Airbnb, Booking.com, Viator, etc.).

How to fix it

This signal is set during verification. If you believe it is incorrect, contact us.

Completeness

25 pts max

Content richness — does your page answer the key questions an AI agent needs?

Price detectedEasy

What we check

A price or currency symbol ($, €, £, USD, EUR, MXN, etc.) is visible on your page. AI agents need to know the cost before recommending or booking.

How to fix it

Display your starting price clearly on your homepage and tour pages. Example: "From €120 per person". If prices vary by season, show a range. Avoid "Contact us for pricing" as the only option — this blocks AI agents.

Duration detectedEasy

What we check

Your page mentions the duration of your experience (hours, minutes, days). This is a key piece of information for travelers and AI agents planning itineraries.

How to fix it

Add duration information explicitly: "3 hours", "Full-day (8 hours)", "2 days / 1 night". Include it in your tour description or a dedicated details section.

Cancellation policyEasy

What we check

Your page mentions a cancellation policy, refund terms, or non-refundable conditions. AI booking agents need this to properly inform travelers before completing a transaction.

How to fix it

Add a visible cancellation policy section to your booking page. Example: "Free cancellation up to 48 hours before the experience. Non-refundable within 48 hours." This also builds trust with human visitors.

Languages mentionedEasy

What we check

Your page mentions languages spoken or offered (English, French, Spanish, German, etc.). This helps AI agents match travelers with operators who speak their language.

How to fix it

Add the languages you offer to your tour descriptions or a "Details" section: "Available in English, French, and Spanish." If your site has a language switcher, ensure the lang= attribute is set in your HTML.

Precise locationEasy

What we check

Your page contains a precise location reference: a Google Maps link, GPS coordinates, or a specific address. Vague location references (just a city name) do not count.

How to fix it

Add a Google Maps embed or a direct link (maps.google.com/...) to your meeting point or office. Include your full address in your contact section or footer. This also helps with local SEO.

Freshness

15 pts max

Content recency — is your website actively maintained?

Sitemap updated < 6 monthsEasy

What we check

The <lastmod> date in your sitemap.xml was updated within the last 6 months. This signals that your content is actively maintained.

How to fix it

Most CMS platforms update the sitemap automatically when you publish or edit content. If your sitemap has old dates, try re-publishing your key pages. In WordPress with Yoast, go to SEO → Tools → File editor to check.

dateModified in JSON-LDMedium

What we check

Your Schema.org structured data includes a dateModified field with a recent date. This tells AI crawlers that your information is current.

How to fix it

Add a "dateModified": "2025-01-15" field to your JSON-LD schema block, and update it each time you edit your content. Some CMS plugins (Yoast, Rank Math) do this automatically.

Dynamic content (price/date variable)Engine-dependent

What we check

Your page shows signs of dynamic content: prices or dates that vary based on availability, or a calendar that loads real-time data. This indicates a live booking system.

How to fix it

This signal is detected if your booking engine is present AND displays variable pricing, or if a calendar/datepicker library (Flatpickr, etc.) is active on your page. Ensure your booking widget is fully loaded and not hidden.

Performance

10 pts max

Speed — slow websites are ignored by AI agents and penalized by search engines.

PageSpeed > 80Medium

What we check

Your website scores above 80/100 on Google PageSpeed Insights (mobile). A slow site frustrates travelers and signals poor technical maintenance to AI agents.

How to fix it

Check your score at pagespeed.web.dev. Common fixes: compress your images (use WebP format), remove unused plugins, enable caching, use a CDN. If you are on WordPress, plugins like WP Rocket or Litespeed Cache can help significantly.

Response time < 800ms (TTFB)Medium

What we check

Your server responds within 800 milliseconds (Time to First Byte). A slow server delays everything — AI crawlers and real visitors alike.

How to fix it

TTFB is mostly determined by your hosting. Upgrade to a faster hosting plan or switch providers. Consider a CDN (Cloudflare is free). If you are on shared hosting, switching to VPS or a managed WordPress host (Kinsta, WP Engine) usually fixes this.

The ARI is recalculated on demand. After making improvements to your website, you can request a recalculation by contacting us. Scores are approximate — they reflect the state of your website at the time of the last scan.

Get verified on RootsTravel →