The Travelity booking widget is a client-rendered app mounted in an iframe — great for booking, invisible to search engines. This plugin fixes that.
It syncs the products from your Travelity workspace into WordPress and serves real, crawlable pages for each of them:
- Server-rendered product pages with title, description and cover image — indexable by search engines.
- Structured data (JSON-LD
Product/AggregateOffer,TouristTripfor tours,BreadcrumbList), meta description and Open Graph tags. Plays nicely with Yoast SEO and Rank Math: in the default mode it defers meta/OG output to them and only adds the structured data they don’t. - The booking widget embedded on every product page, bound to that product — live prices, availability and booking stay in the widget, where they are always current.
- A real booking funnel: the plugin creates Checkout, Booking Result and Wishlist pages, and the widget navigates to them instead of routing inside its iframe — so every funnel step is a real URL your analytics can see.
- A product archive page listing all synced products, plus a “Travelity Booking Widget” block and a
[travelity_widget]shortcode for placing the full widget anywhere. - Packages too — multi-day bundles from your workspace get their own server-rendered pages and archive, each with the widget bound to that package, exactly like products.
- Multilingual, following your site — if your site uses Polylang or WPML, product and package pages are automatically served under each language’s URL prefix (e.g.
/hy/…) with their text machine-translated (and cached) via Travelity, in step with your site’s own language switcher. Nothing to configure. - Optional listing pages — turn the product and package listing (archive) pages on or off independently, for operators who prefer to build their own catalogue page.
- Stable product links: each product also answers on
/t/{id}and redirects to its current pretty permalink, so links from the widget keep working even if you edit a page’s slug. - Products removed in Travelity are set to draft, never deleted — their URLs are preserved.
- Pages inherit your Travelity widget theme (colors, font) automatically, with per-site overrides.
A Travelity account is required. The plugin does nothing without a Travelity workspace and its widget API key (Travelity admin Integrations Widget). Learn more at travelity.app.
Content flows one way, Travelity WordPress. The plugin never writes anything back to your Travelity workspace.
External services
This plugin connects to the Travelity platform. It does not work without it.
Travelity API (https://api.travelity.app)
- What it is: the Travelity workspace API that owns your product catalogue and workspace configuration.
- What is sent and when: your widget API key (as an authorization header) on every request. Requests happen when you save the plugin settings (to validate the key), on the scheduled sync (hourly / twice daily / daily, as configured), and when you press “Sync now”. Product cover images are downloaded into your media library during sync.
- No visitor data is ever sent to this endpoint — only your server talks to it.
Travelity widget (https://widget.travelity.app)
- What it is: the Travelity booking widget application, loaded in your visitors’ browsers on pages where the widget is embedded.
- What is sent and when: the visitor’s browser loads the widget script and communicates with Travelity to show live prices and availability and to complete bookings; booking details entered by the visitor (contact and payment information) are handled by Travelity. Gallery images on product pages are also served from the Travelity CDN.
Travelity terms and privacy policy: https://travelity.app/legal/terms · https://travelity.app/legal/privacy
Google Fonts (https://fonts.googleapis.com)
- What it is: Google’s web font service.
- What is sent and when: only when your Travelity widget theme (or the plugin’s font override setting) specifies a Google-hosted font, visitors’ browsers request that font file from Google, which involves their IP address as with any web request. If no such font is configured, no request to Google is made.
- Google’s terms: https://developers.google.com/fonts/terms