Modern Web Presence

Three things decide whether a website still holds up in five years or turns into something you have to rebuild.

It has to be fast, because load time drives both bounce rates and visibility. It has to be accessible and legally sound, because that is now an obligation rather than a nice extra. And it has to be maintainable, so that changes take minutes instead of a new quote.

I keep content and presentation cleanly separated (a headless architecture, for example with Strapi). That sounds technical, but the effect for you is simple. You maintain your own content without a developer. The site stays fast because there is no bloated system in the way. And if your requirements change in three years, I replace the frontend without rebuilding everything.

Accessibility cannot sensibly be added at the end. It belongs in the structure. I work to WCAG 2.2, the current standard, and build from the start so that your site works with a screen reader and by keyboard.

Which conformance level makes sense depends on your situation. Level AA is what legislation and public tenders normally refer to, and it is the right target for most company websites. Level AAA I implement where there is a reason for it, for individual criteria such as contrast or plain language. Taking an entire website to AAA is something the W3C itself advises against, because some criteria simply cannot be met for certain kinds of content. Anyone promising you blanket AAA for everything has not read the standard through to the end.

On the legal side, briefly: the European Accessibility Act has applied since June 2025, implemented in Germany through the BFSG, and it does not cover every website. Whether it applies to you is something we can settle in a first conversation, rather than making things expensive as a precaution.

A growing share of your visibility no longer happens on a results page but inside an answer. Anyone asking ChatGPT, Perplexity or Google's AI overviews gets a piece of text with a handful of sources. Either you are one of them or you are absent.

The term that has taken hold for this is Generative Engine Optimisation, or GEO. Most of it is not technically new: clean semantic HTML, a correct heading hierarchy, structured data following Schema.org, and content that sits in the source rather than being loaded in later by JavaScript. In other words, exactly what a properly built headless architecture produces anyway. What has changed is what depends on it. This technology used to decide your ranking. Now it decides whether a model can quote you at all.

There is a useful side effect here. The clean structure a screen reader needs is the same structure a machine needs in order to extract anything, so the accessibility work pays for itself twice.

Two things I will say plainly. GEO does not replace SEO, because most of what AI systems quote comes from sources that also rank well in the traditional sense. And nobody can guarantee you a mention in AI answers, because these systems do not publish how they weight things and change it constantly. What I can deliver is the technical foundation, without which it certainly won't happen.

If a page builder covers your needs and you rarely change anything, you don't need me, and I would rather say that openly. My work pays off when your website is a real tool: a lot of content, connections to other systems, and high expectations around speed and legal certainty.