Skip to main content

SEO & AI Visibility

In one line: Every page is built to rank locally (GMB + NAP consistency), pass 100% Lighthouse SEO, carry server-side JSON-LD, follow an answer-first content pattern, and be fully readable by AI crawlers via llms.txt and agent-friendly API routes.
Royal Glow is a location-based premium business — local search is the primary customer acquisition channel alongside Meta ads. Every page is built to rank locally, pass 100% Lighthouse SEO, and be fully readable by AI agents and search crawlers from day one.
These are non-negotiable implementation standards, not optional enhancements. Lighthouse SEO = 100 is a hard CI gate — PRs that drop below it are blocked.

Local SEO Strategy

  • Fully complete the GMB listing: name, address, phone, hours, category (Beauty Salon / Day Spa), photos
  • GMB booking link points to https://theroyalglow.in/?book=1&utm_source=gmb — Google Maps users open the homepage booking dialog with source attribution
  • In-store QR posters point to https://theroyalglow.in/?book=1&utm_source=walkin
  • Respond to all Google reviews within 24h
  • Post weekly GMB updates (offers, new services, events)

Structured Data (JSON-LD)

All JSON-LD is injected server-side via Next.js generateMetadata() — never client-side.

LocalBusiness + BeautySalon (every page)

The homepage carries the full LocalBusiness + BeautySalon + DaySpa schema including geo-coordinates, opening hours, amenity features, and payment methods.

Service Schema (each service page)

Additional Schemas

Sitemap & Robots

sitemap.xml

Generated by Next.js 16 built-in app/sitemap.ts. Static routes hardcoded + blog posts fetched from Payload REST API at build time. Excluded: /admin/*, /api/*, /profile/*, /book (Meta ad lead page — no SEO value)

robots.txt

All AI crawlers are explicitly allowed — Royal Glow benefits from maximum AI visibility:

AI Search Visibility (Google AI Overviews, ChatGPT, Perplexity)

Google AI Overviews pull from pages that directly answer questions in the first 2–3 sentences, use structured content, and have strong E-E-A-T signals.

Answer-First Content Pattern

Every public page leads with a direct answer, not a marketing intro.
Buries the facts an AI Overview needs behind brand fluff.

FAQ Strategy

FAQs have the highest citation rate in AI Overviews. Each FAQ is also marked up in FAQPage JSON-LD — this triggers Google’s FAQ rich result AND feeds AI Overviews. Required topics and their answer patterns:

llms.txt — AI Agent Discovery

llms.txt is the robots.txt for AI models — a plain-text file at the site root that helps AI systems understand the site quickly. Served at https://theroyalglow.in/llms.txt and https://theroyalglow.in/llms-full.txt (detailed version with full service list and prices). Both files are served via Next.js API routes that pull live data from Neon DB so prices stay current without manual updates.

Agent-Friendly Build Standards

Semantic HTML (Non-Negotiable)

  • Use <header>, <nav>, <main>, <section>, <article>, <address>, <time>, <figure>
  • Never <div onClick> — always <button> for actions
  • One h1 per page, no skipping heading levels
  • Contact info wrapped in <address> tag
  • Dates: <time datetime="2026-01-15">15 January 2026</time>

Metadata — Every Page

Agent-Exposed API Endpoints

E-E-A-T Signals

Google AI Overviews heavily weight Experience, Expertise, Authoritativeness, Trustworthiness:

Performance & Core Web Vitals

All public pages are server-rendered or statically generated. Core content is readable without JavaScript.
Last modified on June 29, 2026