From thin WordPress to a cruise booking platform in 3 languages

Luxury cruises — and a website that didn't sell them

DanEri Yachts takes guests on luxury catamarans to the most beautiful bays of Greece and Cyprus. Bringing in customers from search, however, was the job of a WordPress site with all the typical ailments: thin pages with no depth, uneven content quality, fragmented URLs, outdated booking logic and almost no pages for specific destinations — exactly where real search demand lives.

An important nuance that keeps this case honest: by the time of the audit, the project had already begun migrating from old WordPress to a static architecture — and the migration itself left scars. The SEO audit revealed URL consolidation problems: canonical conflicts, lost redirects, sitemap and indexing issues. So the job wasn't just "build new pages" — it was also "diagnose and repair migration damage" and recover the money pages that had lost traffic.

Betting on organic search in travel is justified — search remains the main channel for trip planning:

Below is the path from thin content and sagging money pages to a multilingual booking platform: diagnosis, clusters, design, backend and safe deployment.

What the audit showed: demand exists, the site doesn't catch it

We built the diagnosis on Google Search Console data and demand analysis. The picture at the start (this is the diagnostic baseline the work began from — not the final results):

At destination level, demand was literally lying on the ground — the site just wasn't picking it up:

The conclusion: the problem isn't "too few articles". The problem is architecture — no destination clusters, no conversion pages for the "which cruise should I book" decision, and a technical base that needs repair after the migration. That became the plan.

The plan: repair, rebuild, scale

The work ran on all fronts at once — from migration repair to a full product platform:

271,947 words that sell cruises — not "fill the site"

We didn't "write articles" — we built a commercial content machine. Each cluster is assembled around a destination pillar page and covers the entire customer journey: from "where should we go" to "which exact cruise should we book":

• Destination guides — Rhodes, Milos, Paleochora, Ierapetra, Cyprus: pillar pages + routes, ports and cruise categories.
• Decision pages — "which cruise should you book": day vs sunset, catamaran vs party boat, Rhodes Marina vs Mandraki, Rhodes vs Symi.
• Practical guides — sea temperature by month (Rhodes, Milos, Cyprus), the best time for a cruise, "Rhodes in 4 days", beaches reachable only by boat.
• Family and occasion pages — cruises for proposals, anniversaries, holidays with kids.
• FAQ blocks and structured data — 162 pages with FAQ markup, 165 with JSON-LD; internal linking blocks in every article.

The content scale matches a serious publication — but every page works toward a booking:

And all of it in three languages. English, Russian and Greek: 21 translation memory and runtime localization files per language, a language switcher, localized paths and canonical handling. A Greek, a Russian and a Brit all see an equally polished site.

Luxury nautical: design people trust with their holiday

A template theme doesn't sell a cruise worth hundreds of euros. We built a custom design system: deep navy, coral accents, cream and ocean blue; premium cruise cards with prices and categories; visual hero sections; comparison tables; FAQ blocks; pricing grids; responsive mobile navigation and a redesigned header, footer and menu.

Live site · homepage

The daneriyachts.com homepage (snapshot 06/11/2026): a photo hero with a catamaran, "Luxury Sailing Since 2017" and direct cruise CTAs — a premium first screen instead of a template WP theme. The old version is in the Wayback Machine.

Pillar page · Rhodes

The "Rhodes" cluster pillar page: a hero over Anthony Quinn Bay, trust numbers (72+ cruises, 2,592 nautical miles, 698+ guests) and two CTAs. Below it — the cluster's 16 articles: from "Rhodes vs Symi" to "beaches you can only reach by boat".

The goal isn't "pretty" — it's conversion: the design helps people scan, compare and commit to a booking.

From a website to a booking system with an admin panel

The project grew from "a site with articles" into a commercial platform. On Supabase we built accounts (email/password + Google sign-in), a customer dashboard with bookings, a comparison cart, an affiliate program with tracking and payout requests, super admin / admin / content manager / partner roles, CMS-like product management and discount campaigns — in total 20+ database migrations covering accounts, carts, bookings, products, discounts, security and partner reports.

Booking runs through the LinkTwist integration: date, time and guest selection, a "Buy Now" flow, admin booking views and a discrepancy comparison tool for PDF/CSV/Excel. A purchase is confirmed with a PDF e-voucher sent by email (Sendpulse-based email infrastructure), and discount campaigns — like the temporary −15% — are injected statically: the discounted price is visible right in the HTML and snippets, not only after JavaScript runs.

Cruise cards · −15%

Premium cruise cards: category, route, duration and −15% discounted prices (struck-through old price) — the discount is injected statically and visible to search engines and previews, not only after JS loads.

sem.chat: an answer in any language within ~2 seconds

DanEri Yachts' guests write from all over the world — in English, German, French, Polish, Hebrew, Russian, Greek. No human operator covers that flow across dozens of languages, let alone at night, when a tourist is planning a holiday from another time zone. So we installed sem.chat on the site — an AI chat that detects the language automatically and answers any message in about 2 seconds, 24/7.

For a booking business this is critical: questions like "is this cruise OK for kids?" or "what if it's windy?" come up right before payment. With no answer, the visitor leaves to compare competitors. An instant answer in their own language keeps the customer in the funnel: they stay longer, read on, compare and reach the booking — not the closed tab.

AI chat · DanEri AI

The sem.chat widget ("DanEri AI") on the live site: a guest asks in their own language — and gets an answer in about 2 seconds, any time of day. The chat knows the cruises, routes and conditions, and walks the visitor toward a booking.

Infrastructure that protects every page

Content is useless if the technical base lets it down. So the SEO infrastructure is built into the build and deploy process itself:

• Hugo / static builds — 171 pages managed by the deploy config, 221 content files, staging and production deploy scripts with SFTP automation.
• Migration repair — redirects and legacy URL handling, passthroughs for category archives and nested legacy paths, canonical conflict resolution.
• Multilingual paths — localized EN/RU/EL URLs, a language switcher, hreflang handling, a canonical on every page.
• Markup — JSON-LD injection (165 pages), FAQ schema (162 pages), sitemap verification against live URLs (222 in the current sitemap).
• Environment safety — staging/production separation, staging noindex protection, GTM and the chat widget — without hurting speed.
• Media infrastructure — image manifests for 2,333 photos: control over weights, paths and alts.

In all honesty: the GSC numbers in the "Diagnosis" section are the baseline at the start of the work. The final trend should be judged on fresh Search Console data after the clusters are indexed — we don't quote it without verification.

One project — website, content, SEO and platform

The main outcome is a change of category. Instead of a thin WordPress site, DanEri Yachts now runs a single commercial system: content catches destination demand, design carries people to a decision, the platform closes the booking, and admin tools handle operations.

• A content machine built — 170 pages and 271,947 words (median 1,516), clusters of 71 articles across 5 destinations, internal linking and FAQs in every one.
• The migration healed — redirects, canonicals, sitemap and legacy paths put in order; commercial pages are recovering systematically.
• Three languages — EN/RU/EL with translation memory, localized paths and hreflang: an equally polished site for every market.
• Booking is a product — Supabase accounts, cruise comparison, the LinkTwist flow, PDF vouchers, discount campaigns, affiliates and 4 admin roles.
• Support is instant — the sem.chat AI assistant answers in any language within ~2 seconds, 24/7, and keeps visitors moving toward a booking.
• Deployment is safe — staging/production, SFTP automation, staging noindex protection, sitemap verification on every release.

Behind the result is the SEOquick team

A project like this isn't built by "a freelance copywriter". SEOquick has been in search marketing since 2008 and combines what's usually split across contractors: strategy, content production, development, localization, technical SEO, integrations and deployment — in one team and one process.

since 200817+ years in SEO

500+projects and clients

11countries served

4.6/560+ reviews · Google

CEO · SEO Strategy

Nikolay Shmichkov

18 years in digital, 500+ SEO articles and podcasts. Leads strategy, priorities, and final quality control of implementations.

Founder · AI & GEO

Anatolii Ulitovskyi

Founder of SEOquick and unmiss.com. Specializes in AI search, GEO, programmatic SEO, entity markup, and visibility growth analytics.

Similar growth stories

If this case resonated — see how we solved similar problems in other niches and regions.