Case study · website

TaxiGhis, a taxi website rebuilt with its search rankings carried over page by page.

A local brochure website on WordPress, rebuilt in Next.js with one page per service and a booking form. The old addresses are redirected, and search rankings carried over page by page. Client named with its consent.

01/BackgroundWhere we started

A WordPress site that had hit the limits of its tool

The site had supported the business since its early days, and its tool was holding it back. For each sticking point, what the new site does.

  1. 01Performance was declining despite caching plugins, and images were not served in modern formats.Pages generated in advance, images and fonts optimised at build time, caching at the front-end server.
  2. 02Plugins to update every month, vulnerabilities to watch, a theme licence to renew.No more plugins or licences: all the content lives in the code, versioned and deployed by the delivery pipeline.
  3. 03The theme held back search rankings: titles too long, descriptions buried, scripts out of control.One address per service, titles and descriptions written by hand, local business structured data.
  4. 04Changing websites loses rankings built up over years.Every old address permanently redirected, sitemap submitted, old site archived and kept out of search indexes.
02/What we builtDelivered so far

A local brochure website, written page by page

Each page is written as a deliverable, and the site is instrumented to catch a regression before customers do.

  • 01
    One page per service. High-speed rail station, airport, approved patient transport, events, deliveries: one address per need.
  • 02
    Booking. Addresses completed from the French national address database, an immediate estimate, the ride accepted or declined by the driver with one click in the e-mail they receive.
  • 03
    Confirmation e-mails. Transactional and signed, with an anti-bot check that asks nothing of the customer.
  • 04
    Structured data. Local business and taxi service, with address, opening hours and catalogue, for local search.
  • 05
    Editorial style. Serif headings on a black background, champagne gold and burgundy, designed for the phone first.
  • 06
    Migration without loss. Typed permanent redirects, a carefully prepared sitemap and robots file, the old WordPress archived on a non-indexed subdomain.
  • 07
    Legal pages. Privacy policy and terms and conditions; no audience measurement cookies.
  • 08
    Observability. Traces, logs and metrics exported to our own instance; each deployment carries its version identifier.
03/Three screensThe live site, nothing blurred

Three screens, actual size

Screenshots of the site as it is online. These pages are public; nothing is blurred.

Home page of the new TaxiGhis website: headline on a black background, menu, online booking and phone number
Screen 01The home page, as it is online. The number shown is the taxi's own.

The phone number and booking on the very first screen

A taxi customer wants to call or book, straight away. The first screen puts both within reach, then says where the taxi goes: station, airport, approved patient transport.

TaxiGhis booking form: pick-up address, suggested destinations and fare estimate
Screen 02The booking form, as it is online. On a phone, the departure point and the destinations.

One request, one estimate, one answer from the driver

Customers enter their addresses, completed as they type, and see an estimate. The driver receives the request by e-mail and accepts or declines it with one click.

Service page for the Belfort-Montbéliard TGV station on the TaxiGhis website
Screen 03One page per service, here the TGV station, as it is online. On a phone, the top of the page.

One page per need, one address per page

Each service has its own page, with its title and description written by hand. That is what makes it possible to hold a ranking on a specific search, and to win others.

04/TechnologiesWhat we chose, and why

A static site, monitored like an application

Choosing Next.js came down to two needs: pages written as deliverables, and regressions visible before customers see them.

  • InterfaceNext.js and TypeScript, pages generated in advance, reusable editorial components (service page, article, form).
  • BookingAddress completion from the French national address database and a routing service; signed links for the driver's answer.
  • Search engine optimisationLocal business structured data, generated sitemap and robots file, typed permanent redirects.
  • ObservabilityTraces, logs and metrics exported to an instance we host; each version identified by its commit.
  • DeliveryMulti-stage Docker image, zero-downtime deployment behind the front-end server, automatic certificate.
  • HostingOn our servers in France, on the same foundation as our other websites.

What next

A brochure website to rebuild without losing your search rankings?

Tell us about your site, the tool it runs on today and what it needs to do. We will tell you what is feasible, with a timeline and a rough price.

Discuss your project

Reply within 24 working hours, from one of the two founders. Or by phone: +33 7 59 96 14 99.