Technical foundation
Crawlability, render behaviour, speed, sitemap accuracy and structured data. Unglamorous, and the ceiling on everything else.
SEO / AEO / GEO
BuildRanking is no longer the finish line. Being cited is.
Technical foundations, content that answers real questions, and structure that lets answer engines quote you — because a growing share of searches never produce a click.
Typical stack
- Google Search Console
- Screaming Frog
- Ahrefs
- Schema.org
- GA4
- Looker Studio
Written for: A marketing owner watching organic traffic fall while their content investment stays flat.
Who it is for
Is this built for a business like mine?Built for businesses whose buyers research before they buy.
Search compounds where the purchase involves comparison, and it is close to worthless where it does not. These are the cases where the compounding is real.
What we see
Buyers evaluate for weeks, read comparisons and documentation, and increasingly ask an assistant to summarise the options.
What we build
Documentation and comparison content structured so that both crawlers and answer engines can quote it accurately.
The detail that matters
We optimise for being quoted correctly, which is a different problem from ranking.
What we see
Patients search a symptom or a procedure long before they search for a provider.
What we build
Condition and procedure content that answers the question honestly, with the sourcing and structure that health-related results demand.
The detail that matters
Written to withstand the higher scrutiny applied to health content, not around it.
What we see
Practice-area pages compete against directories and aggregators that outrank every individual firm.
What we build
Question-shaped practice content plus the technical foundation that makes a single firm legible against a directory.
The detail that matters
Aimed at the specific long-tail questions directories answer generically and badly.
What we see
Local pack position decides the phone calls, and the site has no service-area structure at all.
What we build
Service-area architecture and local signals built on real operating areas rather than a page farm.
The detail that matters
One page per genuine service area. A location farm is the oldest thin-content pattern there is.
What we see
Category pages are outranked by marketplaces and product data is invisible to structured results.
What we build
Category and product structure with product schema generated from the same source as the page.
The detail that matters
Schema comes from the content model, so it cannot drift out of sync with the page.
What we see
Prospective students search the qualification, the career outcome and the entry requirements months before they search for a provider.
What we build
Course, career-outcome and eligibility content written to answer directly, structured so an assistant summarising options can quote the entry requirements correctly.
The detail that matters
Entry requirements and fees are versioned content — being quoted with last year’s numbers is worse than not being quoted.
What we see
Portals and aggregators own every head term, and individual firms compete against them on their own ground and lose.
What we build
Area, building-type and process content aimed at the long-tail questions aggregators answer generically, plus the service-area structure that makes a single firm legible locally.
The detail that matters
We do not bid or optimise for terms the portals have already won. That is a spend decision, not a capability gap.
And who it is not for
If you need revenue in six weeks, this is the wrong channel and we will point you at paid search. Search compounds, and compounding takes time to start.
The problem
Do they understand what is actually going wrong?The click is disappearing from the search.
A growing share of searches are answered on the results page or inside an assistant, and never produce a visit. A page that ranks and is never quoted is losing ground to a page that is quoted and never visited — and most sites are structured for the first outcome, because that is what the last decade rewarded.
Rankings hold steady and sessions decline, quarter after quarter.
Assistants answer questions about your category and cite somebody else.
Content was written for a keyword rather than for a question anyone asks.
The technical foundation is broken in ways nobody has looked for — render-blocked content, no structured data, a sitemap listing pages that no longer exist.
What we build
What exactly would I be buying?Three surfaces, one foundation.
Classic search, the answer box and generative assistants reward overlapping but different things. The foundation is shared; the optimisation is not, and treating them as one job is why most SEO work now underperforms.
Question-shaped content
Written around what people actually ask, with the answer stated directly and early enough to be extracted rather than buried under an introduction.
Citation-ready structure
Clear claims, attributable sources, stable headings and machine-readable markup, so an assistant can quote you without misrepresenting you.
Authority, earned off-site
Citations come from being referenced elsewhere. Directories, industry publications and genuinely useful data assets — no link buying, which is a liability with a delay on it.
How it works
How does this actually function?How a page becomes a citation.
Being quoted is a chain, and it breaks at the weakest link. Most sites break at the second stage and spend their budget on the fourth.
Crawlable
Parseable
InvisibleAnswers a question
Attributable
Cited
Server-rendered HTML matters more than it did. An assistant that cannot execute JavaScript sees nothing on a client-rendered page.
A direct answer inside the first sentence of a section is extractable. The same answer after three paragraphs of preamble is not.
Structured data and stable headings are what let a machine attribute a claim to you rather than paraphrase it anonymously.
What changes
What is different afterwards?What is different afterwards.
The foundation stops leaking
Technical problems suppressing every page at once are found and fixed first, because content investment on a broken foundation is wasted.
Crawl, render and structured-data issues resolved and re-verified.
You appear in answers
Content structured for extraction and attribution, so assistants can quote you rather than a competitor with worse information.
Citations tracked across assistants, not just rankings.
It keeps paying
Earned position does not stop when spend stops, which is the entire reason to do this instead of buying more ads.
Organic contribution sustained through spend changes.
How we deliver
How does this start, and what do I get at each step?Six stages, and every one has an exit.
You can stop after any stage with something useful in hand. That is the point of naming the artefacts rather than the activities.
- 01
Technical audit
Crawl, render, speed, structured data, sitemap accuracy, indexation. The ceiling is found before anything is built under it.
- Prioritised technical findings
- Render comparison, JavaScript on and off
- Indexation and crawl report
- 02
Question research
What people actually ask — from search data, from your support queue, and from what assistants currently answer badly.
- Question inventory by intent stage
- Current answer quality per question
- Gap analysis against competitors
- 03
Structure
Site architecture, internal linking and schema, so authority flows to the pages that should have it.
- Information architecture
- Internal linking plan
- Structured data specification
- 04
Content build
Pages written to answer directly, structured for extraction, sourced so a claim can be attributed.
- Published pages
- Schema live and validating
- Answer-format verification
- 05
Off-site
Directory accuracy, industry citations and data assets worth referencing. Slow, and the part that actually compounds.
- Directory and citation audit
- Placement plan
- Data asset concept
- 06
Measurement
Rankings, sessions and citations tracked together, because any one of them alone now tells a misleading story.
- Reporting view
- Assistant citation tracking
- Quarterly review
Questions
But what about the thing that worries me?The questions people actually ask.
What is the difference between SEO, AEO and GEO?
SEO earns a position in a results list. AEO earns the answer box above it. GEO earns a citation inside a generative assistant’s response. They share a technical foundation and diverge in content structure — a page written to rank is not automatically a page that gets quoted.
How long before we see results?
Technical fixes can move things within weeks. Content and authority compound over six to twelve months. Anyone promising first-page results in thirty days is describing paid search or something worse.
Do you buy links?
No. It is a policy violation with a delayed and severe cost, and the recovery is worse than the original problem. Citations come from directory accuracy, genuine industry placement and publishing something worth referencing.
How do you know if an assistant is citing us?
We query the major assistants on your priority questions on a schedule and record what they return and who they attribute. It is sampling rather than a complete measure, and it is currently the honest version of tracking this.
Can you work on a site you did not build?
Yes, and most engagements are exactly that. The technical audit tells us what the platform will allow — some make certain fixes impossible, and we say so early rather than bill against a wall.
The other half
Organic traffic asks questions at midnight.
Search sends people who are researching, from every timezone, at every hour. They arrive with specific questions and leave if nobody answers. The chat and email queues that catch them are work we run — which is also why we know exactly which questions your buyers ask, and can write the content that answers them.
Email SupportStart
What is the next step?Tell us the problem, not the specification.
A short call is usually enough to say which half of the business your problem belongs to, roughly what it costs, and whether it is worth doing at all.
Related services
- DevelopmentWebsite DevelopmentFast, accessible, search-legible websites built on a performance budget — and handed over as a codebase you own, not a platform you rent.
- Digital MarketingDigital MarketingChannel strategy and execution that starts from capacity — because demand you cannot answer is spend you have already lost.
- Digital MarketingGoogle AdsCampaigns built to capture demand that already exists — measured against booked revenue rather than against the platform’s account of itself.