ITI Digital AI-Ready Events & Places
ITI Digital AI-Ready Events & Places

ITI Digital AI-Ready Events & Places

0/5 (0 ratings) 30 active installs Updated Nov 3, 2026
General plugin connection and configuration settings.

General plugin connection and configuration settings.

SEO-friendly Events, Places, Itineraries, and Travel Planner integration for WordPress powered by the ITI Digital platform.

AI-ready tourism content delivery for WordPress with server-side rendering, SEO-friendly URLs, structured data, dynamic sitemap support, llms.txt support, optional WordPress search integration, module-status synchronization, cache management, and real-time content updates.

Features

  • API key support for authenticated ITI Digital API requests
  • Server-side rendered HTML optimized for SEO and AI-assisted search discoverability
  • Clean, SEO-friendly URLs using WordPress rewrite rules
  • Dynamic XML sitemap for Event and Place content
  • Canonical URL caching for improved SEO
  • Support for detail base pages with structured URLs:
    • Events: /e/
    • Places: /p/
  • Staging mode to safely test canonical and sitemap URLs
  • Automatic trailing slash handling based on WordPress settings
  • Automatic sitemap exclusion support for internal SSR layout pages
  • Automatic cache refresh for SSR listing pages
  • Manual cache refresh and URL purge tools
  • Authenticated webhook endpoint for Event, Place, Itinerary, and module-status updates
  • Dynamic route cache exclusion recommendations
  • Optional WordPress search integration for Event and Place results
  • Theme-overridable search templates for frontend customization
  • Itineraries listing and embedded detail content support
  • Travel Planner integration with configurable frontend placement and loading rules
  • /llms.txt support for Event, Place, and Itinerary discovery pages
  • Optional public custom post type support for Events, Places, and Itineraries

Important Notes

  • Save Permalinks after changing routes
  • Avoid creating child pages under the selected base pages that use the reserved paths /e/ (Events) or /p/ (Places), as they may conflict with dynamic detail URLs.
  • Staging mode should not be used on production sites
  • /llms.txt may be cached by the hosting provider or CDN. If possible, reduce the cache duration for this URL, or clear the site/CDN cache after adding, removing, or changing configured Event, Place, or Itinerary pages.