SEO & AI Search Optimisation
Found by Google, and by ChatGPT.
Technical and content SEO, plus the newer work of being citable by AI answer engines - schema, structured data and the kind of clear source content those systems quote.
Tracking wired up before anything goes live
How we think about it
Search is splitting in two. Traditional rankings still send traffic, but a growing share of questions get answered inside ChatGPT, Gemini, Perplexity and Google AI Overviews, where there is no blue link to rank for. Being cited there rewards different things: clear structure, explicit answers, and schema that tells a machine what your page is actually about.
Technical SEO is inseparable from how the site is built, so rendering, structured data and the content plan are decided by one team.
What this covers
The work, specifically.
- 01
Technical SEO
Crawlability, speed, indexation and the structural problems that cap everything else.
- 02
On-page and content SEO
Pages built around real search intent, not keyword density.
- 03
GEO / AEO
Getting mentioned in ChatGPT, Gemini, Perplexity and AI Overviews, the search surface that is growing.
- 04
Schema and structured data
FAQ, product, organisation and article markup, which is how machines read your pages.
- 05
Backlinks
Earned through work worth citing, not bought from a network that gets deindexed.
- 06
SEO audits
What is broken, what it costs you, and the order to fix it in.
Need SEO & AI Search Optimisation for something specific?
Tell us what you're trying to ship and we'll say plainly whether this is the right service for it — including when the answer is no.
How it runs
The same four steps, whatever we're building.
No account-manager relay. The lead on your project is someone who builds, and they stay on it from the first call to the last deploy.
Scope
A week of hard questions. We map what you actually need and say plainly which parts we'd cut.
Prototype
Something real in front of you early, not a document about it. Opinions get cheaper.
Build
Two-week cycles, a demo at the end of each. You see progress, not status reports.
Hand over
Documentation, a walkthrough, and the keys. Support if you want it — never as a hostage.
Questions
The things people ask before they enquire.
It depends on scope, but we will give you a number before you commit to anything. Most engagements start with a paid discovery — a fixed fee, a week or two — which ends in a written scope and a real budget. If the budget does not work, you leave with the scope document and no obligation to continue.
A typical first ship is around six weeks. Larger builds run in two-week cycles after that, each ending in a demo of something that actually runs. You will know within the first cycle whether the timeline is holding, rather than finding out near the deadline.
The people you meet. The lead on your project is someone who builds, and they stay on it from the first call to the last deploy. There is no account manager relaying messages between you and an unseen team.
You own everything — code, assets, accounts, domains. We hand over with documentation and a walkthrough, and your team can run it without calling us. If you would rather we stayed on for maintenance or a next phase, that is a separate agreement, not something buried in the original contract.
Yes. Most of our work is remote, and we keep a few hours of overlap with your working day for calls. Timezone has not been the hard part; unclear scope has.
Where it meets the others