Project 09Build
This site
Built, not bought, and optimised for both classical search and the answer engines that increasingly sit in front of it.
- Next.jsapp router
- SEO+GEOoptimised
- 100%hand-built
01
At a glance
The whole project in three steps.
- The problem
A marketer who claims technical range and then ships a template has answered the question before it was asked.
- What I did
Designed and hand-built this site in Next.js, structured for classical search and for AI answer engines.
- The result
Structured data and metadata on every route. The live audit on this page reads the page you are on.
Skills it shows
- SEO and GEO
- Front-end build
- Structured data
- Web performance
- Design systems
Tools
- OpenAI
- Semrush
- Google Analytics 4
- Claude AI
02
The challenge
Why the project had to happen.
A marketer who claims technical range and then ships a template has answered the question before it was asked. This site is the argument: every component is hand-built, and the SEO and GEO work from the Search & GEO rebuild is applied to it rather than described from a distance.
Read the full context
It also has a job. It has to survive a recruiter skimming it in ninety seconds, and it has to be legible to the AI answer engines that are increasingly the first thing between a person and a search result.
03
How I did it
4 steps. Open any one for the detail.
Build the structure search can read
Server-rendered routes, one h1 per page and structured data, settled before any styling.
How
Server-rendered routes, one h1 per page, no skipped heading levels, and Person / CreativeWork structured data. Most of what makes a site citable is unglamorous and settled before any styling happens.
Write for extraction
Wrote self-contained claims with figures attached, applying the same GEO discipline to myself.
How
Self-contained claims with figures attached, so a passage lifted out of context still says something true. This is the same GEO discipline from the Search & GEO rebuild, turned on myself.
Earn the performance budget
Built the 3D hero, comet and video marquee against a performance budget.
How
A 3D hero, a scroll-driven comet and a video marquee are expensive. They stay because each was built against a budget: compositor-only properties, adaptive DPR, animations paused when nothing is looking at them.
Design a signature, then hold it
Reused one gradient, one comet and one type system instead of reinventing per section.
How
One gradient, one comet, one type system, reused everywhere rather than reinvented per section. Coherence is cheaper than novelty and reads as more expensive.
04
See it
Read from this document, live
Not a screenshot of an audit — the panel inspects the page it is rendered on. The same discipline is applied to every route on this site, including the five case studies beside this one.
05
What it achieved
Surfaces in Google Search and in AI answer engines. The GEO work is verifiable rather than asserted.
Structured data, sitemap and per-page metadata across every route, including each of these case studies.
Hand-built throughout: the scroll system, the comet, the loading sequence and the chatbot are all bespoke.
06
What I took from it
Most of what makes a site citable is unglamorous and settled before any styling happens.
Self-contained claims with figures attached mean a passage lifted out of context still says something true.
Coherence is cheaper than novelty and reads as more expensive.