Website relaunch for Royal Tandoor: From the old system to the new WordPress website
Royal Tandoor needed more than a new language version. We therefore rebuilt the existing website in WordPress, retained the familiar design and added an English version. At the same time, loading times fell, and the team can now maintain content itself.
Royal Tandoor: Bollywood flair meets fine dining
Royal Tandoor serves Indian cuisine in a dining room with a cherry-blossom tree and a Taj Mahal mural. Behind the restaurant is a family we directly support with digital matters. We coordinate decisions with the team without lengthy approval rounds. This means every technical change had to deliver tangible value in day-to-day operations.
Starting point: a good website with one limitation
The first Royal Tandoor website was built as a single-page app. Technically, it worked well and its design suited the restaurant. However, the content was embedded directly in the code. Even minor changes required developers. An English version for international guests would have been too expensive in this system. The team could not maintain the menu or photos itself either.
As a WordPress agency, we recommended moving to WordPress. We wanted to retain the existing design in full.
Why we moved from a single-page app to WordPress
WordPress separates content from technology. For a restaurant, that means:
- The team maintains menus, opening hours, photos and copy itself, without an agency ticket.
- Every section of the site is a standalone Gutenberg block, reusable for future subpages.
- Multilingual content, SEO and structured data can be maintained with mature tools. This also includes SEO for restaurants & hospitality.
- The website belongs to the restaurant. There is neither vendor lock-in nor a website-builder subscription.
Blocks reproduced pixel-perfect, one by one
Guests should not notice the change. Design and atmosphere remained the same. In the background, we rebuilt every section as a Gutenberg block: hero video, family introduction, menu slider, gallery, reviews and contact. We then compared each block individually with the original until no visible differences remained. The biggest improvement concerns the videos. Rather than 65 MB, they now require less than 11 MB, with no noticeable loss in image quality.
The English version with WPML
The request for an English version triggered the project. To implement it, we use WPML and our own AI translation plugin for WPML. It translates content with Claude or ChatGPT. The workflow includes pages, dishes, menus, image alt text and SEO metadata. Hreflang tags tell Google which language version is intended for which country. Because the technical setup is now in place, another language can be added through the same workflow. No second relaunch is necessary. We explain how we build projects like this under Creating a multilingual website.
More articles about website relaunches
More about the process: another client relaunch, our WPML workflow, the English-language version for GEO and the checks before going live.
Visible to Google and AI systems
When people search for a restaurant, ChatGPT and other AI systems now play a role alongside Google. We therefore set up the website for GEO. Generative Engine Optimization describes visibility in AI search systems. Before the relaunch, machine-readable information was missing. Now it has an llms.txt, content signals, Markdown outputs for crawlers and complete schema.org data of the “Restaurant” type. This includes opening hours, cuisine, reservations and directions. Cloudflare’s “Is Your Site Agent-Ready?” test rates the website at Level 5 “Agent-Native”. That is the highest level in the test. More about this approach: LLM, GEO & AI optimisation.
The measurements before handover
Before handover, we test every website with the same ten tools. The results are publicly verifiable:
SEO and GEO signals for the restaurant website
| Check | Result |
|---|---|
| Google PageSpeed (mobile) | Performance 96, Best Practices 100 |
| Accessibility | 100/100; AccessibilityChecker ‘Compliant’, 0 critical errors; AccessScan ‘Accessible’ |
| Security headers | Grade A+ (securityheaders.com) |
| AI readability | Cloudflare Agent-Ready Level 5 ‘Agent-Native’ |
| Structured data | schema.org Restaurant, validated without errors |
| Loading behaviour | First Contentful Paint 1.4 s; Total Blocking Time 0 ms |
The site feels the way a restaurant visit should begin: without waiting.
What changes for the team in day-to-day operations
For the team, the following changes in day-to-day work:
- The team maintains content itself, from the dish of the day to the gallery.
- New subpages (events, catering, lunch menu) are created from existing blocks.
- Additional languages are prepared. The translation pipeline is in place.
- AI systems and search engines receive reliable, structured facts.
- Measurable quality: Every change can be tested against baseline values.
The relaunch is not an end point. It gives the restaurant the technical foundation to develop its content and offers independently.
