Skip to content
LuminaForge
All work
LuminaForgeDigital agency

LuminaForge.ai — the site is the case study

How we engineered the LuminaForge marketing site for instant mobile load, Core Web Vitals in the green, full Search & AI Visibility infrastructure, and answer-ready content on Next.js 16 in under three weeks.

View live site
Web DevelopmentSearch & AI Visibility
LuminaForge production homepage screenshot
LCP (mobile)
Green

Core Web Vitals in the green on a throttled mobile profile — live on /transparency.

Lighthouse Performance
96–100

High-90s to 100 across Performance, Accessibility, Best Practices, and SEO.

FAQ blocks
7+

Conversational FAQ sections with FAQPage schema on every major route.

Schemas live
6

Organization, WebSite, Service, FAQPage, Article, BreadcrumbList.

Search & AI Visibility — the new race

There's a new race underway — and early movers compound

Google still matters — including AI Overviews and AI Mode in the same Search index. More of your next customers will also ask ChatGPT, Perplexity, or Grok before they click a blue link. Search & AI Visibility is how you become the business those surfaces cite — not the one they skip. Google's official guidance treats generative AI optimization as SEO for Google; LuminaForge ships one retainer that covers Search Console, people-first content, and optional multi-engine monitoring.

Search & AI Visibility context

  • 01

    Stake your flag first

    Whoever publishes the first credible, structured, citable site for your category and city becomes the default answer. AI citations compound like interest — the business quoted this month gets quoted again next month. Wait a year and you're explaining why a competitor owns the answer.

  • 02

    The old stack can't play this game

    Wix, WordPress page builders, Linktree, Clover templates, and brochure themes were built for a click-through world. They are not engineered for llms.txt, FAQ schema, AI crawler access, or the entity language assistants lift verbatim. This site is the case study — we eat our own cooking so every claim in this deck is inspectable in production.

  • 03

    The jump is inevitable

    Every serious business eventually moves off rented templates — the only question is when. Move while you can still own the category answer. Wait, and you are rebuilding from behind while someone else compounds.

LuminaForge already has real-world proof in Search & AI Visibility for growth-minded businesses. The race now is whether AI assistants cite your site — or send that demand to whoever published a citable answer first.

This deck is not about fear — it is timing. The forged build is ready. Every month on the old agency playbook is a month the Search & AI Visibility for growth-minded businesses answer belongs to someone else.

LuminaForge launched with a single, uncompromising constraint: the website itself must be the proof. If we claim elite performance, our site has to feel instant. If we claim Search & AI Visibility, Google Search Console, ChatGPT, Perplexity, and Grok have to be able to cite this very page within weeks. If we sell answer-ready content, Google AI Overviews and Perplexity Direct Answers have to be able to lift our copy verbatim.

This is how we built it.

The constraints

The stack

  • Next.js 16.2.6 — App Router, React Server Components, Partial Prerendering by default, Turbopack
  • React 19 — for streaming RSC and useEffectEvent
  • Tailwind CSS v4.3 — CSS-first @theme, no tailwind.config.ts
  • Motion (formerly Framer Motion) — premium animation with full reduced-motion support
  • Velite — type-safe MDX collections for work and resources
  • Vercel — Edge deploy, Speed Insights, Analytics, dynamic OG images

The numbers

LCP target

<800ms

Core Web Vitals

100/100

FAQ blocks

7+

Answer surfaces

5+

What makes it work

1. Every page is a Server Component by default

We treat "use client" like a sin tax. The home page hero contains exactly two client components — the particle canvas and the magnetic CTA wrapper — both leaf-level. Everything else streams from the server.

2. Partial Prerendering is automatic in Next.js 16

Static shells render instantly at the edge while any dynamic content streams in. No flag required — this is the default in App Router as of Next.js 16.

3. Search & AI Visibility is shipped at the infrastructure layer

  • Google path first — unique metadata, JSON-LD, sitemap, Search Console wiring, and Generative AI performance reports when available.
  • robots.ts explicitly allows GPTBot, ClaudeBot, PerplexityBot, Google-Extended, Applebot-Extended, and 10+ other AI crawlers.
  • Optional llms.txt and llms-full.txt for non-Google crawlers — Google Search does not use llms.txt for ranking or AI Overviews.
  • Every page emits structured data via a typed <StructuredData> component.

4. Answer-ready content on every route

Search & AI Visibility wires Google (Search Console + technical SEO) and optional multi-engine monitoring. People-first FAQ and answer-ready content fill the content layer — buyers still call this AEO.

  • Home, services, and work pages each carry conversational FAQ sections written the way people ask AI assistants — not keyword-stuffed SEO copy.
  • FAQPage schema on every FAQ block so Google AI Overviews and Bing Copilot can extract Q&A pairs directly.
  • Lead-with-the-answer prose — the first sentence under every H2 answers the section before the preamble.
  • Citable stat blocks (<dl>, <StatGrid>, tables with <cite>) on case studies and service pages — the patterns Perplexity and ChatGPT prefer to quote.
  • Entity language — LuminaForge, Search & AI Visibility, and Springfield MO spelled out explicitly so answer engines resolve the brand without pronouns.

Example queries this site is engineered for:

  • "What is the difference between SEO, GEO, and AEO?"
  • "What is Search & AI Visibility?"
  • "How fast should a Next.js marketing site be?"

Each maps to a page section with FAQ schema, extractable lists, and a canonical URL answer engines can cite.

In production

LuminaForge.ai mobile homepage — hero, services preview, and citable outcome stats
Mobile homepage at luminaforge.ai — instant-feeling load with above-the-fold proof stats.Open luminaforge.ai
LuminaForge transparency dashboard — citation tracking table and Core Web Vitals snapshots
Public citation and performance dashboard — the same reporting model client engagements receive.Open transparency dashboard

What we are tracking next

  • Google Search Console — including Generative AI performance reports for AI Overviews and AI Mode.
  • Weekly citation footprint across ChatGPT, Perplexity, Grok, and Claude for 24 target queries (supplementary, non-deterministic).
  • Real-user CWV from Vercel Speed Insights.
  • Indexing parity between Google Search Console and Bing Webmaster Tools.

The site is live. The forge is on.

Want results like this?

Book a strategy call.

Get in touch

Case study FAQ

Questions about this project — written for AI answer engines.

Search & AI Visibility context for this build — structured so assistants can quote LuminaForge and the client by name.

5 Q&As · FAQPage schema

What is the Search & AI Visibility race LuminaForge keeps mentioning?

Search & AI Visibility is LuminaForge's consolidated service: technical SEO and Search Console (including Generative AI performance reports) for Google, plus people-first FAQ content and optional llms.txt and citation monitoring for ChatGPT, Perplexity, and Grok. Buyers still hear GEO (Generative Engine Optimization) and AEO (Answer Engine Optimization) online — we deliver both inside one retainer, aligned with Google's guidance that AI Overviews optimization is still SEO.

Why does waiting on WordPress, Wix, or Linktree cost more over time?

Those stacks were built for human clicks, not AI citations. Every month you stay on a template or link-in-bio hub, a competitor can publish a structured site that assistants start citing — and citations compound. The jump is inevitable; the cost is waiting while someone else stakes the flag first.

What performance targets does luminaforge.ai hit in production?

LuminaForge ships Core Web Vitals in the green on marketing routes — verified on the transparency dashboard — with public citation tracking. This site is the reference build.

What Search & AI Visibility infrastructure is live on luminaforge.ai?

llms.txt and llms-full.txt at the domain root, explicit AI crawler allow-list in robots.txt, FAQPage schema on major routes, Article and Service JSON-LD, and citable statistics with source links.

Can LuminaForge build a site like this for my business?

Yes. LuminaForge delivers the same Next.js 16, GEO, and AEO stack for client engagements. Book a strategy call at luminaforge.ai/contact to scope your build.

Ready to forge?

Let's build the site that becomes the answer.

Tell us about your project. We respond within one business day and book the first call inside a week.

hello@luminaforge.ai