Which pages do you look at first?

The pages that carry revenue or enquiries: service, product, pricing and comparison pages. We read your Search Console data to see which of them are losing impressions and start the crawl audit there, not on the blog archive.

How is answer engine optimisation different from SEO?

SEO aims for a ranked link in a list of results. Answer engine optimisation aims for an accurate mention inside a generated answer, which depends more on clear facts and structured data than on ranking position. The technical foundation underneath is shared, which is why we run them as one line.

Can you guarantee our company will appear in AI answers?

No. Nobody outside the companies that run these assistants controls how they pick sources, and a promise of placement is a guess. What we can do is remove the reasons a system would skip or misquote you, then record whether mentions change.

Do you need write access to our website code or CMS?

Read access is enough for the audits. For fixes, we either open reviewed changes in your repository or hand your developers a written fix list. You choose which before the work starts.

Depth 02 · Service line

Search and AI visibility

Search and AI visibility is the work of making a company's website readable to the systems that decide who gets found: search engine crawlers, the indexes behind them, and the AI assistants that now answer questions by quoting web pages. It covers the technical layer those systems read first, the structured facts they extract, the content they rank, and the measurement that shows whether anything changed.

Inside this line

Four sub-services, from crawl access at the surface down to measurement across classic search results and AI answers.

Input: Read access to Google Search Console, your analytics account and the repository or CMS that produces the site, plus a plain list of the services and questions you want to be found for.
Method: We work from the crawler's side first, then the layer of facts and structured data, then content. The measurement baseline is recorded before anything changes, so every later change has something to be compared with.
Deliverable: A crawl and index audit, an entity and schema map and a topic cluster plan, each written as a document your team can act on, plus a measurement setup that keeps running after we step away.
Measured by: Indexed pages and query impressions from Google Search Console, Core Web Vitals against the thresholds Google publishes, and a fixed set of prompts checked in AI assistants on a schedule.

Level 3 · 01

Technical SEO foundation

Technical SEO foundation is the part of search work that decides whether a page can be fetched, rendered, recognised as unique and stored in a search index at all. When this layer fails, content and links cannot make the page appear, because the search engine never kept it.

Inside it

Crawl access and robots rules
JavaScript rendering checks
Canonical tags and duplicate handling
XML sitemaps and index coverage
Core Web Vitals

Measured by The share of submitted URLs that Search Console reports as indexed, and Core Web Vitals against the "good" thresholds Google publishes on web.dev (industry benchmark: LCP 2.5 seconds or less, INP 200 milliseconds or less, CLS 0.1 or less).

Technical SEO foundation, full page

Deliverable · Level 4→ Crawl and index auditCrawl and index audit: a ranked register of issues, each with its cause, the pages affected and the fix.

Level 3 · 02

Answer engine optimisation

Answer engine optimisation is the practice of making a company's facts easy for AI assistants and AI search features to find, trust and quote correctly. Tools such as ChatGPT, Perplexity and Google's AI Overviews build their answers from web sources. This work makes sure the sources they draw on describe you accurately, in a structure a machine can read without guessing.

Inside it

Entity inventory
schema.org markup in JSON-LD
Definitional page openings that can be quoted
AI crawler access and llms.txt
Consistent descriptions across public profiles

Measured by Whether a fixed set of prompts in the main AI assistants names your company and describes it correctly, checked on a schedule and recorded with dates. Markup is validated with Google's Rich Results Test and the Schema.org validator.

Answer engine optimisation, full page

Deliverable · Level 4→ Entity and schema mapEntity and schema map: every entity, its canonical description, the page that owns it and the structured data that marks it up.

Level 3 · 03

Content operations

Content operations is the system that decides what a company publishes, in what order, who writes and reviews it, and when each page is updated or removed. It turns content from a run of one-off posts into a maintained library organised around the questions buyers actually search for.

Inside it

Query and topic research
Cluster and internal link planning
Briefs and an editorial review workflow
Refreshing or retiring old pages

Measured by Impressions and clicks per cluster in Search Console, and the share of planned pages published and reviewed on schedule.

Content operations, full page

Deliverable · Level 4→ Topic cluster planTopic cluster plan: each cluster with its main page, supporting pages, target queries, internal links and a review date.

Level 3 · 04

Visibility measurement

Visibility measurement is the reporting layer that shows where a company appears in search results and AI answers, and whether that changes after work is done. Without a baseline recorded before the work, no later change can honestly be attributed to it.

Inside it

Baseline snapshot before any change
Search Console and analytics dashboard
Scheduled AI prompt checks
Monthly change log

Measured by Each month the report is compared with raw Search Console exports to confirm the figures match.

Visibility measurement, full page

Where this applies

Who this is for: Marketing and product leads whose site is live, but whose key pages are missing from search results or from AI answers, and who can name the queries they lose.

Sectors this line is set up for, not a list of clients.

B2B softwareIND 02: Documentation and feature pages structured so search engines index them and AI assistants can quote them.
Professional servicesIND 03: One page per practice area with schema that names the firm, the service and the jurisdiction.
EcommerceIND 05: Crawl budget spent on category and product pages rather than on filter combinations.
Payments and fintechIND 01: Clear, citable definitions of products in a field where assistants often answer with competitors' wording.

Shape of the work

Crawl and index flow: a crawler requests a page, the server answers, the page is rendered and parsed, then indexed and finally cited in an answer. A check sits between each stage.

What you get

02.1 · Technical SEO foundationCrawl and index audit: a ranked register of issues, each with its cause, the pages affected and the fix.
02.2 · Answer engine optimisationEntity and schema map: every entity, its canonical description, the page that owns it and the structured data that marks it up.
02.3 · Content operationsTopic cluster plan: each cluster with its main page, supporting pages, target queries, internal links and a review date.
02.4 · Visibility measurementA running dashboard and a documented prompt check routine, both owned by your team.

What we work with

Front end: React · TanStack Start · Next.js · Astro · Vite · Tailwind
Content systems: Strapi · Sanity · Contentful · WordPress for migrations · Notion as a source
Commerce: Shopify · WooCommerce · headless storefronts
Quality and observability: Playwright · Sentry · uptime monitoring · structured logging · error budgets
Search and measurement: Google Search Console · GA4 · Plausible · Umami · Looker Studio · Schema.org structured data · log file analysis

These are the tools we work with, not partnerships, certifications or resale agreements.

How this fits the other lines

14Web and product engineering
Most fixes we find are changes to templates and routes, which that line builds.
10AI engineering and automation
The same structured content that assistants cite can feed an internal retrieval assistant.

When this is not the right line

If you need traffic next month, buy advertising: indexing and citation changes take weeks to show and cannot be guaranteed. If the site is about to be rebuilt, start with the rebuild and add this work to its scope.

Questions about this line

Which pages do you look at first?: The pages that carry revenue or enquiries: service, product, pricing and comparison pages. We read your Search Console data to see which of them are losing impressions and start the crawl audit there, not on the blog archive.
How is answer engine optimisation different from SEO?: SEO aims for a ranked link in a list of results. Answer engine optimisation aims for an accurate mention inside a generated answer, which depends more on clear facts and structured data than on ranking position. The technical foundation underneath is shared, which is why we run them as one line.
Can you guarantee our company will appear in AI answers?: No. Nobody outside the companies that run these assistants controls how they pick sources, and a promise of placement is a guess. What we can do is remove the reasons a system would skip or misquote you, then record whether mentions change.
Do you need write access to our website code or CMS?: Read access is enough for the audits. For fixes, we either open reviewed changes in your repository or hand your developers a written fix list. You choose which before the work starts.

Send the queries you are missing from

Send the site address and three queries where you expect to appear. We reply with what we would check first and the access we would need.

Send three queries

An email exchange first, no call needed.