Two post types carry the whole site
The vendor describes GoTravel around a Tour custom post type and a Destination custom post type. That single decision shapes everything else in the theme. A tour is an entry with a bookable page; a destination is a container you attach tours to. You are not building a page per trip in a page builder and hoping the structure holds — you add tour entries and group them under places.
On top of that structure the author lists booking functionality with a PayPal connection, custom review criteria, and a user dashboard for logged-in visitors. Reviews are not one star rating: you define the criteria, which on a tour site can separate the guide from the itinerary from the value.
These are the author's stated features. The demo is where you would check how the booking flow and dashboard actually behave.
Where tours appear is a placement choice, not a template
The tour elements are described as shortcodes and widgets: a Tours List, Tours Carousel, Tour Type List, Tours Filter and Destinations Grid, plus a Destination Tours widget and a Tour Items widget. Read that set as parts that go where you put them. A carousel can carry featured trips across the top of a homepage, a filter block can sit above a listing, and a destination grid can act as the way into a regional catalogue.
The widgets cover the repeat case. Slot the Destination Tours or Tour Items widget into a header, side area or footer and that block shows tour data without being rebuilt on each page. A weather widget is also listed, which is a more natural fit for this subject than most widget sets.
The practical point: these elements are built for the theme's own post types, so they surface tours you have already entered rather than arbitrary content.
The tour search is the piece that has to match your catalogue
An advanced tour search with filtering is the feature that decides whether a large catalogue is usable. Visitors arrive knowing a region, a month or a kind of trip far more often than a tour name, so the filters need to cover the fields your tours actually vary on. That is a question for the demo, not the feature list.
The release history shows translation work aimed at that specific page. Version 2.2, dated 17 December 2025, added a WPML config file and compatibility with the Polylang plugin for the Tours Search Page. WPML also appears in the marketplace compatibility attributes. If you plan to publish in more than one language, those entries are more specific than the general "translation ready" claim.
A filtered search is also where a theme like this differs from a general-purpose WordPress theme with a booking plugin added afterwards: the search, the tour entries and the booking records come from the same place.
Feed widgets the changelog has already removed
The feature list still advertises Twitter and Instagram social widgets. The changelog says otherwise. Version 2.2 records that the Mikado Instagram Feed plugin was removed because of Instagram API changes, and that the Mikado Twitter Feed plugin was removed for the same reason. Version 2.3, dated 15 October 2026, records removing a twitter-connect script and its enqueue.
What remains is the optional social share feature the theme lists for posts, which is a different thing from pulling a feed into a widget. If a live Instagram strip in the footer is part of your plan, treat the feature-list line as out of date and plan to supply that feed another way.
This is also the clearest reason to read the changelog before sizing up a Mikado feature list: the two documents do not always agree, and the changelog is the later one.
WPBakery, section-level styling and the header settings
Pages are built with WPBakery Page Builder, which the vendor says is included, with Slider Revolution bundled for sliders. Much of the visual work happens at section level: video background sections, background images, parallax sections with an optional fullscreen treatment, and the ability to change the header skin from one section to the next.
Headers carry more settings than usual. Separate logos are provided for the regular, sticky and mobile headers, and the dark and light header skins get their own logo variants. There are header top and bottom widget areas, and the mobile header can be styled on its own. Footer layout goes up to four columns with an uncovering footer option and a separate footer bottom area. The theme is marked child-theme ready, which matters if you intend to modify templates.
One caveat comes straight from the vendor: the demo photographs are licensed for presentation only and are not included for use on your site. On a travel theme that is not a minor detail, because the imagery does most of the persuading.
What the compatibility statements do and do not cover
Marketplace attributes recorded on 4 November 2026 list WordPress 6.5.x through 7.0.x, WooCommerce 9.x and 10.x, WPBakery Page Builder and WPML as compatible software, with a responsive layout, widget-ready areas, high-resolution assets and PHP, CSS and JS files in the package. Those are the author's declarations, not results of independent testing, and a compatibility list is a snapshot that says nothing about releases arriving afterwards.
WooCommerce appears in that list, and the theme lists a dropdown shop cart widget and a Contact Form 7 integration. That indicates support for selling through WooCommerce; it does not make GoTravel a store-building theme, and not every demo depends on the shop. Tours and booking run on the theme's own post types and the PayPal connection instead.
If your WordPress or PHP version sits outside the declared ranges, the check belongs on a staging copy before you commit, not after your tour catalogue is already entered.
Questions & answers
Do I need WooCommerce to sell tours with GoTravel?
The vendor describes booking functionality with a PayPal connection as part of the theme, separate from the WooCommerce integration, and tours come from the Tour custom post type. WooCommerce support is listed for shop-style selling alongside the dropdown cart widget. Confirm your intended payment path in the demo before relying on it.
Can tour listings be translated?
The theme is described as translation ready, WPML appears in the compatibility attributes, and version 2.2 added a WPML config file plus Polylang compatibility for the Tours Search Page. Those entries point at multi-language work on the tour search specifically, so check your own language setup against the current release rather than assuming every string is covered.
Are the demo images included with the theme?
No. The vendor states that the demo images are used for presentation only and require a separate stock licence if you want to use them. Budget for your own licensed photography.
