WEBSITES

Fast, findable websites. Technical foundation in order.

A slow or poorly structured site is a leaking bucket. Visitors bounce on mobile, Google ranks you lower and AI engines avoid you as a source. We get the technical foundation in order: Core Web Vitals in the green, structured data for AEO and AI Overviews, clean canonicals and sitemaps. Sometimes that means a rebuild, often a solid refactor is enough.

Book a tech call Take the Maturity Scan

What you get

90+
PageSpeed Insights after optimisation
3 wks
From audit to live optimisations
100%
Structured data for AEO ready

The observation

Most B2B sites fail on precisely the tech checks that carry the most weight now.

Core Web Vitals, structured data, hreflang and sitemap hygiene are not a nice to have. They are the foundation SEO leans on, and since AI Overviews also the foundation AEO leans on. We do it differently: we start with an audit that shows what can be resolved in days and what requires structural work, embedded in the broader websites offering. No all-or-nothing rebuild when a refactor delivers 80 per cent of the gain. These are the four patterns we see in almost every audit.

LCP above 4 seconds

Uncompressed hero images, render-blocking scripts, no CDN. An LCP of 4 to 6 seconds on mobile is not the exception. Google ranks you lower, visitors bounce.

No or incomplete schema.org

No Organization, no FAQ, no BreadcrumbList. AI engines such as ChatGPT and Perplexity avoid you as a source, and Google AI Overviews pick your competitor.

Incomplete sitemap or robots.txt

The XML sitemap is missing key pages, robots.txt incorrectly blocks productive content, or lets staging environments through. Indexation clutter.

No measurement infrastructure

Search Console not configured, no rank tracking, no Lighthouse CI. Decline only becomes visible once the organic pipeline has been dropping for two months.

Approach

From audit to green Core Web Vitals in four to five weeks.

First week is the audit, then two to three weeks of implementing the highest-leverage fixes, one week of monitoring setup. After that, Lighthouse CI runs inside our RaaS retainer so a Google update does not come as a surprise.

01 01

Audit

PageSpeed Insights, Lighthouse, Search Console and Screaming Frog. A complete picture of technical health, with the top 5 levers laid out.

02 02

Performance

Image compression (WebP/AVIF), lazy loading, code splitting and CDN setup. Target: LCP below 2.5s, INP below 200ms, CLS below 0.1 on mobile.

03 03

SEO Tech

XML sitemap, robots.txt, canonicals, hreflang, breadcrumbs and internal linking. The foundation that strengthens every content SEO action.

04 04

AEO

Schema.org per page type: Organization, Service, FAQ, BreadcrumbList. Plus clear question-and-answer structures that LLMs can cite from.

05 05

Monitoring

Lighthouse CI, rank tracking and Search Console alerts. Detect decline before it shows up in the pipeline.

Who helps you

Three specialists on your technical foundation.

Designer, content strategist and CMS architect work together on tech optimisations. Performance and SEO touch design, content and code at the same time.

For the data foundation underneath, see CRM architecture.

Sander Adriaanse

Webdesign / Frontend lead

Optimises frontend performance. Image compression, CSS bundling, animations without layout shifts. Makes sure performance fixes do not require design compromises.
Dante Zwanenburg

Content & Ads Specialist

Delivers SEO and AEO keyword strategy. Which questions you want answered in Google and in AI citations, and which FAQ structure supports that in schema.
Carsten Huiskamp

CMS Architect (lead)

Leads the tech engagement. SEO tech, structured data, indexation and monitoring. Builds the Lighthouse CI and Search Console alerts so a setback is no longer a surprise.

Case · B2B mid-market

From red Core Web Vitals to AI citations in Perplexity

A B2B organisation with a large content library had seen declining organic traffic for three consecutive months. PageSpeed on mobile below 40, LCP around 5 seconds, no FAQ schema, no Service schema, no Organization schema. Google AI Overviews consistently cited competitors instead of their pillar content.

In four weeks we set up image compression, lazy loading and a CDN, plus a full schema.org implementation per page type, in line with our SEO and AEO approach. PageSpeed reached 92, all Core Web Vitals in the green. Two months later organic traffic recovered and citations of their content appeared in Perplexity answers for 7 of their top 15 keywords.

What clients usually ask.

The questions that come up before a tech engagement starts.

What Core Web Vitals score is good enough?

For B2B websites we aim for 90+ on PageSpeed Insights mobile, and all three Core Web Vitals in the green: LCP below 2.5s, INP below 200ms, CLS below 0.1. That is what Google classifies as "good". On desktop that is usually easier, mobile is where the gain is. Not sure where you stand? Take the maturity scan.

What is AEO and why does it matter now?

AEO is Answer Engine Optimisation: being found by AI engines such as ChatGPT, Perplexity and Google AI Overviews. AI Overviews reduce click-through on classic search, so visibility in AI answers is becoming more important. Structured data and clear question-and-answer structures make your content interpretable for LLMs.

Do you also do content SEO or only tech?

Tech is the focus of this page. Content SEO (keyword research, topic clusters, content production) falls under our Marketing services, where Dante takes the lead. Both tracks often run in parallel.

How long does a tech optimisation take?

The audit takes one week. Performance and SEO tech implementation two to three weeks. Monitoring setup one week. Total four to five weeks. After that, monitoring continues in a retainer format so you do not find out something changed only when a Google update hits.

We had a Google update drop, what now?

First week is diagnosis. We look at Search Console data, ranking history and which page types were affected. Often it comes down to content thinness, technical signals or a combination. Sometimes the right advice is: do nothing, wait for the next core update. We will say so when that is the case.

Do you work on WordPress or headless too?

Yes. Tech quick wins such as image compression, lazy loading, schema markup and sitemap hygiene are platform-independent. For deeper refactors we prefer working in HubSpot CMS because that is where we have the most levers, but we also work with WordPress, Webflow and headless setups.

What does a tech optimisation cost?

Our services are custom. The audit is a one-off block, the implementation depends on the number of templates, languages and domains. Ongoing monitoring usually sits inside a RevOps as a Service retainer. Book a call for a quote tailored to your situation.

Ready to start?

Ready for a fast, findable website?

Start with a conversation. We look at your PageSpeed, structured data and Search Console. After that you get an honest scope, even if most of the gain sits in image compression and sitemap hygiene rather than a complete rebuild.