Answer-first page architecture
We restructure each priority page so the direct answer sits in the first hundred words, followed by the evidence, the caveats and the detail. Assistants quote passages, so passages are what we write.
Performance Marketing · 14 GEO & AI Optimisation
Generative engine optimisation is content architecture and machine readability: answer-first pages, consistent entity data, structured markup and the crawler access you choose. We agree the prompts your buyers ask, then report your share of answer every month.
You own accounts, data and IP Monthly reporting Reply within one business day
AI answer - assistant result
For a Vancouver build, shortlist studios that
own delivery end to end. OlDevs1 pairs
engineering with search optimisation.2
Sources
14
Prompts tracked
68%
Answer share
3
AI assistants
OlDevs delivers generative engine optimisation, also called AI optimisation or AIO.The work of making an organisation citable inside AI assistant answers and AI overviews rather than only ranked in classic search results. It is content architecture and machine readability, not a trick. We restructure pages so the direct answer comes first, make your entity data consistent across the site and the wider web, publish Organization, FAQPage and Service structured data, add an llms.txt file, and set robots rules for the major AI crawlers to the access you approve. We then track an agreed set of buyer prompts across ChatGPT, Perplexity, Google AI Overviews, Claude and Copilot, and report share of answer monthly. Clients own every page, file and account.
Key facts
14 · GEO & AI Optimisation
What we deliver in GEO & AI Optimisation
We restructure each priority page so the direct answer sits in the first hundred words, followed by the evidence, the caveats and the detail. Assistants quote passages, so passages are what we write.
Passage structure · Question headings · Summary blocks · Definitions · Tables · Internal links
One spelling of your name, one description, one address, one set of credentials, repeated identically across your site, profiles and directory records, so a model resolves you to one entity instead of guessing between several.
Entity mapping · NAP consistency · sameAs profiles · Author bios · Directory records · Disambiguation
Organization, WebSite, Service, FAQPage, Article, Person and Breadcrumb markup written by hand, validated, and kept in sync with the visible copy so nothing on the page contradicts the data underneath it.
Organization · FAQPage · Service · Article · Breadcrumb · Validation
We publish an llms.txt map of your canonical sources, then audit robots rules, firewalls and bot protection so the crawlers you allow, from GPTBot to PerplexityBot, can reach the pages you want quoted.
llms.txt · robots.txt · GPTBot · ClaudeBot · PerplexityBot · WAF rules
Original reference material an assistant has reason to cite: definitions, methodology notes, comparison tables, specification sheets, glossaries and dated data pages, each written to stand on its own without the rest of the site.
Definition pages · Comparison tables · Glossaries · Methodology notes · Original data · Citations
We agree a set of buyer prompts, run them on a schedule across the major assistants, and log whether you were named, cited, linked or absent, and which competitor was quoted instead.
Prompt sets · Share of answer · Citation logs · Competitor mentions · Baseline runs · Monthly reporting
Process
Baseline
We run your prompt set across the major assistants before changing anything, record who gets cited today, and crawl the site for the structure, schema and access problems behind it.
Map
We define the entity: your canonical name, description, services, locations and people. Then we decide which pages should be the quotable source for each question buyers ask.
Rebuild
Priority pages are rewritten answer-first, structured data is added and validated, llms.txt is published, and crawler access is set to the rules you approve, then tested request by request.
Publish
We add the source pages that are missing: definitions, comparisons, methodology and data, each one written to answer a real prompt completely and to be quoted without context.
Measure
The prompt set reruns on schedule. Each month you see share of answer by assistant, which pages were cited, what changed, and what we are fixing next.
How we work
The baseline prompt run happens first, so you can see exactly where you stand in AI answers before we scope the work and before anyone claims an improvement.
We do not hide instructions in your markup, serve different content to bots, or try to talk to the model. Those tactics get found out, and the brand carries the damage.
Structured data mirrors visible copy. If a claim is not on the page for a reader, it does not go in the markup, and the two never drift apart.
We date pages, name authors, cite our methods and link to primary evidence, and we remove claims your team cannot stand behind. Unverifiable copy is a liability in an answer and in a sales call.
Answer engines still read crawlable, fast, well-linked pages. Where those foundations are weak we fold in the SEO and content discipline, because a page no crawler can render is a page no model can quote.
Pages ship to WCAG 2.2 AA, with clean heading order and real semantics. Where you serve both official languages, English and French versions carry matched entity data and schema.
Who it's for
The question is no longer only where you rank. It is whether the answer a buyer is handed mentions you at all, and whether what it says about you is right.
Large sites where the brand, the product names and the legal entity are described five different ways. We reconcile the entity, then make the pages that matter quotable.
Bodies that need to be the authoritative source when a member or a citizen asks an assistant, in English and French, rather than watching a third party answer for them.
Multi-location brands where assistants confuse one location with another, quote closed branches, or return hours from a stale directory. We make the location data consistent and structured at the source.
Founders in new categories where assistants have no settled answer yet. Publishing the clearest definition and the most useful reference pages early is a real advantage.
12+
Years of studio experience since 2014
5
AI assistants we run prompt sets across
EN/FR
Languages we optimise and mark up
Works well with
Technical audits, keyword and intent research, and an editorial engine that ranks and converts — on Google and in the AI answers your buyers increasingly trust.
Explore02GA4 and server-side tracking that capture every conversion, attribution modelling that shows which channels earned it, and a continuous conversion-rate optimisation programme that turns those insights into measurable lift.
Explore03Earned media, story development, crisis communications and stakeholder relations, planned and measured alongside your paid and owned channels.
ExploreInsights
Practical writing from the team that would be doing it.
Passwords gave way to passkeys, privacy law arrived in force, accessibility got deadlines and AI added new risks. What changed through 2026 and the checklist to…
Attribution decides which marketing gets credit for a sale. No model is perfect; the aim is a fair, consistent method that shows where budget actually works.
Model fees are the smaller share of a copilot's running cost. Tokens, latency, monitoring and guardrails are the larger one, and they decide whether it stays…
FAQ
It is a different layer on the same foundation. Classic SEO earns a ranked link; GEO earns a citation inside a generated answer, which is a different unit of visibility. The overlap is real: crawlable, fast, well-structured pages help both. The differences are answer-first passage structure, consistent entity data, hand-written schema, llms.txt, AI crawler access, and measurement by share of answer rather than by position. We run the two together for that reason.
Share of answer is the headline number: across an agreed set of buyer prompts, how often an assistant names you, cites a page, links to you, or leaves you out. Each month you get that figure broken down by assistant, the specific pages cited, the competitors quoted instead of you, any factual errors an assistant repeated about you, and referral sessions from assistant traffic in GA4. We also report the classic signals underneath, because they move first.
No, and nobody honestly can. Assistants generate answers probabilistically, from sources they choose, using models that change without notice. The same prompt can return different answers on the same day. What we can do is remove every mechanical reason you are not eligible to be cited, publish the source material worth citing, and show you the measured change in share of answer over time. An agency that guarantees a citation is guaranteeing something it does not control.
You do, all of it. The copy, the structured data, the llms.txt file and the robots rules live in your repository or CMS and are yours on publication. Prompt sets, the full citation history, dashboards and audit findings are handed over in editable formats, usually a spreadsheet and a document, not a portal we control. Any tool accounts are opened under your organisation with OlDevs added as a user, so removing us removes nothing.
Weeks for the mechanical problems, longer for the rest. If a crawler was blocked or your entity data was contradictory, citations sometimes appear within weeks of the fix. Building genuine source authority in a competitive category takes more time, and we would look for a clear trend in share of answer over roughly three to six months. Assistants also cache and refresh at different rates, so one engine often moves well before another.
That is a business decision, and we present it as one rather than deciding for you. Blocking GPTBot or Google-Extended protects content from training use but also removes you from the answers your buyers read. Most organisations open the marketing site and keep proprietary material, gated research and customer data closed. We map every bot, show what each one is used for, and implement the rules your legal team approves.
It depends on the size of the site, how many prompts and assistants you want tracked, how much of the entity data needs reconciling, and how many source pages have to be written, so we do not publish a rate card. We run a short scoping call, do a baseline prompt run and a technical read of the site, then send a written proposal with named deliverables and a clear scope. Request a quote and we reply within one business day.
Let’s connect
Tell us what you’re building. We’ll reply within one business day with next steps and a tailored quote — no obligation.
Thanks — we’ll reply within one business day.