Skip to content
Browse docs

Languages & SEO

Your site can publish in English, Spanish and Catalan, and most of the search-engine work happens on its own. This page covers what you translate by hand, what gets translated for you, and the handful of settings worth filling in — under System → Settings and Content → Redirects.

Three languages, one catalogue

Everything customer-facing supports English (en), Spanish (es) and Catalan (ca). You are not maintaining three sites: a trip, a destination or a blog post is one item with a version of its text per language, and each language gets its own web address.

Wherever a field can be translated, you'll see a tab per language above it. Write the original in whichever language you work in, then use Auto-translate to fill the other tabs. It is a first draft, not a publication — read it before you publish, and edit the tab directly if you want different wording. A few text fields also offer Polish and Generate buttons, which rewrite or draft copy for you. Nothing is written or translated without you pressing the button.

If a page has no text for a language yet, visitors in that language still get a working page — but only fully translated pages are put forward to search engines as that language's own version.

Page titles and descriptions

Settings → SEO opens on Page SEO. Pick a page — Home, Trips, About, Contact, Terms, Privacy, Cookies, FAQ, Blog, Search, Destinations or eSIMs — then a language, and set:

  • Title — the blue line in search results. Aim for around 60 characters; the counter tells you when you're over.
  • Description — the grey summary underneath. Around 160 characters.
  • Keywords — comma-separated, optional.

Trips, destinations and blog articles carry their own titles and descriptions on the item itself, not here. This screen is for the fixed pages around them.

Telling search engines who you are

Two more cards on the same tab:

  • Business details for search engines describes your agency to search engines in a structured way: Areas served, a Business description and an Offer catalog name. Filling these in helps you appear as a travel agency rather than a generic web page.
  • llms.txt is a short plain-text summary of your agency, published for AI assistants that read it before answering questions about you. Write it the way you'd brief a new agent: who you are, where you sell, what makes you different.

What happens automatically

You don't have to manage any of this:

  • Sitemaps are generated and kept current as you publish.
  • Language tags tell search engines which page is the English, Spanish or Catalan version of the same content.
  • Search engines are notified when you publish or update a trip, destination or article, instead of waiting to be crawled.
  • Renames redirect themselves. Change a trip's or a destination's web address and the old one forwards to the new one, so shared links and search rankings survive.

Destinations and sub-destinations

Destinations can nest: a country page with region or city pages beneath it, each at its own address and each with its own hero, title, description and publish switch. This is the main way agencies grow search traffic on Taplany — one strong country page plus a page per place you genuinely sell.

Publish a sub-destination only when it has real content. An empty page competes with your good ones.

Fixing a broken address by hand

Content → Redirects — headed Slug redirects — is for the cases automatic renaming can't see, mainly when you delete something and recreate it rather than editing it.

  1. Choose the Type: Trip, Blog article, Destination or Sub-destination.
  2. Enter the Old slug and the New slug.
  3. Set Locale if the redirect applies to one language only. Leave it blank for your default address.
  4. Press Add.

What's next

Still stuck? Contact us.