Website build — Fast, readable, quotable
A site that loads fast, that Google understands and that AI can quote. Designed for visibility from the wireframe, not optimised afterwards.
Optimized to be cited in
Most sites are designed to look good in a mockup, then optimised for engines once live. That is the wrong order. A site built from the start to be fast, structured and readable without JavaScript needs no catching up — it starts with the advantage others will spend a year closing.
What changes in how we build
Server rendering
Content is served as HTML, not assembled by the browser. AI crawlers see all of it.
Editorial structure
Hierarchical headings, self-contained passages, formal definitions — the material engines can extract.
Full markup
JSON-LD schema, breadcrumbs, marked-up FAQ. Laid at build time, not bolted on later.
Performance
Core Web Vitals held from launch, not rescued six months in.
Redirects
On a rebuild, every existing URL is mapped and redirected. Nothing is lost.
The watch point on a rebuild
A rebuild is when search equity is most easily lost. URLs change, redirects are forgotten, tags disappear in the migration. We treat this as a workstream in its own right: full inventory before the switch, permanent redirects one by one, then indexing monitoring in the following weeks.
What we measure
Field Core Web Vitals, indexing rate of published pages, and — on a rebuild — month-on-month retention of organic traffic after the switch. The goal of a successful rebuild is simple: lose nothing, then grow.
The LUWIZ Method — 4 steps
Diagnosis
AI & SEO visibility audit, mapping of target queries across Google, ChatGPT, Perplexity, Gemini and Claude.
Foundation
Technical structure and citable content: JSON-LD schema, llms.txt, ~150 word passages, siloed architecture.
Authority
E-E-A-T signals, external mentions and citations, internal linking that consolidates your topical authority.
Steering
AI share of voice measurement, monthly reporting and continuous optimization of your citations.
Frequently asked questions
Because most visibility problems are born at design time. A site built without thinking about server rendering, heading structure or schema markup then takes months to catch up. By designing the site and its visibility together, you avoid paying twice: once for the build, once for the fix.
We favour server rendering, because generative AI crawlers do not execute JavaScript: a site whose content only appears after execution is invisible to them. The exact choice depends on your needs — brochure site, e-commerce, application — but readability without JavaScript is not negotiable.
Count two to four months for a full brochure site, depending on how much content has to be produced and how many approval rounds are needed. A rebuild at equivalent scope goes faster if existing content can be reused. We set the schedule at kick-off, with clear approval milestones.
This is the riskiest part of a rebuild, and the most often neglected. We map the existing URLs, put permanent redirects in place one by one, and monitor indexing in the weeks following the switch. A badly redirected rebuild can erase years of search equity in days.
It is included in Direction digitale 360° (from €1,490/month), which covers a full build or rebuild. It can also be delivered as a separate project, quoted on scope.
Explore next
Free GEO audit — report in 48h
Your site’s AI visibility score. Gap analysis vs 3 direct competitors. 5 priority optimizations. Delivered as a PDF, no commitment.
Reply within 24h · No commitment · contact@luwiz.io