Royal Court has run banquet halls opposite Madurai Railway Junction since 2004. We replaced its old WordPress site with a fast, photo-led website that helps families pick the right hall by guest count — without losing a single old link or competing with the hotel's own website.
By Dhanasekaran Thangavel · Updated
Client
Royal Court Banquet Hall, West Veli Street, Madurai
What we delivered
Redesign, content, hall pages, WordPress migration, SEO schema, hosting
Live since
3 September 2026
Pages
Home, halls overview and a dedicated page for each of the 5 halls
The owners also run Hotel Royal Court, whose website already has a banquet section describing the same five halls. If the new banquet site said the same things in the same words, Google would treat the two as duplicates and quietly drop one of them.
The old banquet site was a WordPress install with only a handful of pages. Families planning a wedding or reception had to call just to learn which hall fits 120 guests, whether there is a dance floor, or where the buffet goes.
The client was clear about the look, too: use the logo's green and gold, keep the photos bright and clear, and do not make it feel dark or busy.
Screenshots of the live site, taken 14 September 2026.
Step 1 · Homepage
A full-width film of the halls, the founding year, the guest range and two actions — check availability or explore the halls. Google rating and phone number are visible without scrolling.
Step 2 · Choose by guest count
Instead of a brochure, the halls page starts with a table: guest range, what each hall is built for, and the one detail that usually decides it. Families self-select before they ever call.
Step 3 · Hall page
Every hall has its own page, written from how events really run there — where the stage sits, how the buffet queue flows, what the window looks out on — beside a quick "at a glance" card for capacity, AV, parking and catering.
Step 4 · Reserve
The booking section gives the bookings line, reservations line and email with directions. Floating WhatsApp and call buttons stay on screen on every page.
Every feature answers a question families ask before they book a venue.
Majestic, Viceroy, Charminar, Panorama and the Cave Board Room each have their own URL, photos, capacity card and FAQs.
A comparison table that maps guest numbers to the right hall, so enquiries arrive already qualified.
Old WordPress pages, sitemaps and feeds redirect to their new homes; WordPress system paths return "410 Gone" so bots stop probing them.
EventVenue and LocalBusiness data with opening hours, geo-coordinates, amenities and FAQs, tied to the hall's own Google Business Profile.
No filters or overlays on the hall photography; captions sit below images, and hero text uses a gradient that fades before the picture.
Floating WhatsApp and call buttons on every page, and bookings, reservations and email contacts in the reserve section.
Most of the SEO value in this build came from what we chose not to do.
The risk
Copying the hotel's banquet copy would make Google see two near-identical pages for one business and drop one.
What we did
All copy was written from scratch around planning detail, with no hotel-room content at all. The site uses the banquet hall's own Google Business Profile and venue schema — never the hotel's.
The risk
Moving off WordPress normally breaks every old URL that Google, directories and WhatsApp forwards still point to.
What we did
Each legacy page, sitemap and feed URL was mapped to its closest new page with a permanent 301 redirect, set at the server before launch.
The risk
A public staging copy can outrank the real site for its own name if Google finds it.
What we did
The build decides whether it is indexable from its own address: any staging host serves noindex and blocks crawlers, while production opens up automatically.
The risk
First drafts on a near-black background read as "too dark" to the client.
What we did
We rebuilt the palette on the logo's bottle green and gold, removed hairline rules and kept every photograph untreated — exactly the notes the client gave.
Two sites can both rank — if they are truly different
Different angle, different entity, different schema. Same words would have cost one of them its place.
Redirects are part of the design
A migration plan is not finished until every old URL has somewhere sensible to go.
Venue buyers compare, so help them compare
A guest-count table does more selling than another paragraph of adjectives.
We redesigned and rebuilt royalcourtbanquethall.com: new design and copy, a dedicated page for each of the five halls, a guest-count comparison, venue schema, and a migration from the old WordPress site with every legacy URL redirected. The new site went live on 3 September 2026.
Yes, if each site is a genuinely different entity with different content. Royal Court Banquet Hall has its own Google Business Profile and venue-focused copy, while the hotel website keeps its own banquet overview. No text is shared between them.
List every URL the old site had, map each to the closest new page with a 301 redirect, move old sitemaps to the new sitemap, and set it all up before the domain switches. Retired WordPress system paths should return 410 Gone.
Because people search for specific needs — a 250-guest wedding hall, a 100-guest party hall, a board room. A separate page per hall can answer that search directly with the right photos, capacity and FAQs.
Yes. We design and build websites for banquet halls, hotels and event venues, including hall pages, booking CTAs, Google Business Profile alignment and local SEO.
Not yet. The site launched in September 2026, and we only publish numbers once there is enough data to be meaningful. This case study covers the build and migration; results will be added when they are real.
Written & verified by
Dhanasekaran ThangavelFounder & Director, Rank You Higher
Building and marketing websites for businesses in Madurai since 2016. Credentials
How we checked what is on this page
Send us your current site. We will list every URL worth keeping and show you the new structure before anything moves.
