International travel SEO works when market URLs are deliberate before hreflang is added. Choose a structure you can maintain, localise what travellers actually need, then annotate equivalents with reciprocal hreflang. Broken annotations on a messy URL plan split demand instead of clarifying it.
ccTLD, subdomain, or subfolder
Travel brands often inherit a mix: a .com for global English, country domains from old campaigns, and language folders added later. Pick a primary model for new markets and consolidate when you can. Subfolders on one strong domain are often easiest to maintain for SEO. ccTLDs can make sense for strong local brands with local teams, but they multiply technical overhead.
Subdomains sit in the middle and frequently become neglected. Whatever you choose, document which URL is the canonical home for each market and language pair. Autogenerated language switchers that point at thin or machine-translated pages create more problems than they solve.
For delivery support on this problem set, see international and multilingual travel SEO.
Implementing hreflang correctly
hreflang tells search engines which language or regional URL is the equivalent for a user. Annotations must be reciprocal, use valid language and optional region codes, and include a self-reference. Every URL in the set should list the full set, or you should use a sitemap implementation that stays complete as pages change.
Do not annotate URLs that are noindexed, canonicalised elsewhere, or blocked. Do not point hreflang at a homepage when the equivalent is a destination or itinerary page. Mismatched equivalents are a common travel failure because catalogues differ by market.
x-default is useful for a selector or global fallback when no market matches. It is not a licence to leave every market on English forever. Use it intentionally.
| Model | Strength | Risk |
|---|---|---|
| Subfolders | Consolidated domain authority; simpler ops | Weak localisation if content is copied |
| ccTLDs | Clear local signal and branding | Split equity; higher maintenance |
| Subdomains | Technical separation | Often orphaned; inconsistent SEO ownership |
| Translated params only | Fast to launch | Usually poor for SEO and hreflang hygiene |
hreflang code example
Illustrative HTML link annotations for a destination hub available in English (global), English (United Kingdom), and German (Germany). Adapt paths to your real market structure.
<link rel="alternate" hreflang="en" href="https://www.example.com/destinations/lisbon/" />
<link rel="alternate" hreflang="en-gb" href="https://www.example.com/en-gb/destinations/lisbon/" />
<link rel="alternate" hreflang="de-de" href="https://www.example.com/de-de/reiseziele/lissabon/" />
<link rel="alternate" hreflang="x-default" href="https://www.example.com/destinations/lisbon/" />The same relationships can live in XML sitemaps for large catalogues. Whatever the delivery method, keep self-canonicals aligned with the URL you annotate. Canonical A plus hreflang to B while B canonicalises back to A is a classic conflict.
Geo-targeting and localisation
Geo-targeting in Search Console (where available for the property type) is a hint, not a substitute for content and hreflang. Localisation for travel means more than translation: currency presentation, departure airports, holiday calendars, tone, and which products exist in that market. A US itinerary page and a UK itinerary page may need different inclusions and different FAQs.
Avoid doorway country pages that only swap a flag and a phone number. If you cannot maintain a market, do not pretend it is fully supported. Closing or consolidating weak locales is often healthier than leaving broken hreflang sets online.
Destination templates still need uniqueness inside each locale. Thin translated duplicates fail for the same reasons thin English duplicates fail. See destination page SEO without thin duplicates.
QA habits that catch breakage
Sample view-source on anonymous sessions after releases. Confirm reciprocal sets for a mix of homepage, destination, and product URLs. Check that language switchers never send users to 404s or to a different product. Monitor Search Console international targeting and hreflang reports when they surface errors.
Coordinate with the team that adds markets. A new locale launched without sitemap and annotation updates will create orphans. Put SEO acceptance checks next to localisation launch checklists. For broader technical foundations, travel technical SEO covers crawl and index issues that often appear beside hreflang projects.
Be honest about maintenance. Ten languages with one part-time owner will drift. Prefer fewer markets done well. Expand when you have writers, reviewers, and engineering capacity to keep equivalents true.
Translation memory and SEO briefs should travel together. A linguist who only sees strings will recreate thin duplicates in a new language. Give them the uniqueness fields, the product differences, and the queries that matter in that market. Where a market uses different trip names, decide on a primary label and keep it stable across the site and hreflang set.
Currency, units, and date formats are localisation signals travellers notice immediately. They are also easy to get wrong in shared templates. Test checkout and enquiry paths per market, not only the marketing copy. A correct hreflang tag cannot save a booking flow that still shows the wrong departure airport list.
When retiring a locale, remove it from hreflang sets, sitemaps, and navigation in the same release. Leaving ghost annotations to deleted URLs creates long-lived Search Console noise. Redirect users to the closest equivalent when one exists, and avoid bounce redirects that send every deleted locale to the global homepage without context.
Document the decision log: why subfolders were chosen, which markets are fully supported, and who approves a new locale. Future teams will thank you. International SEO debt usually comes from forgotten exceptions, not from the first architecture choice being imperfect.
Legal and compliance copy also differs by market: cancellation terms, package travel regulations, and consumer notices. Localise those blocks rather than hiding a single global legal page behind every locale. Travellers notice when the commercial page is translated but the rules that protect them are not. Consistency between marketing and legal localisation supports trust and reduces support load.
Run a yearly hreflang debt spring-clean even if no new markets launched. Products retire, URLs move, and language switchers accumulate exceptions. A scheduled clean is cheaper than an emergency project after rankings fragment across locales.
Treat language switchers as SEO surfaces. They should point to true equivalents, use human-readable labels, and never strand users on automatic redirects that fight hreflang. A switcher that lies will undo careful annotations in the HTML head.
Sample log files or CDN logs by market host when you can. They reveal whether bots prefer the locale you intended. Combine that evidence with Search Console before rewriting hreflang again. Measurement beats guesswork on international systems.
Translation quality is part of international SEO even when engineers own the tags. Machine-translated doorway pages create thin equivalents that confuse both travellers and ranking systems. If a market cannot fund human review for product and planning pages, keep that market out of the hreflang set until it can. A smaller accurate cluster beats a wide inaccurate one.
Align commercial teams on which markets truly sell. Marketing sometimes wants language flags for brand theatre while operations only fulfil bookings in two countries. Geo-targeting and content investment should follow fulfilment reality. Otherwise you rank into demand you cannot serve cleanly, and support costs rise while conversion falls.
Monitor international Search Console properties for hreflang errors after every template or URL change. Reciprocal annotations break quietly when one locale ships a new slug pattern and others do not. Treat hreflang as a release checklist item, the same way you treat redirects when retiring a destination hub.
Takeaway
Structure first, localise second, annotate third. Reciprocal hreflang on real equivalents helps travellers land in the right market. Annotations on a messy plan only document the mess.