SEO & Performance

I work exclusively on the technical side. Content is always supplied by the client or by one of their suppliers, and this split is stated up front for a specific reason: they are two different trades, and whoever promises both usually does only one of them well.

In practice it means I make sure pages are reachable, crawlable, fast and correctly declared to search engines. Whether they then deserve to rank depends on what is written on them, and that responsibility stays with whoever produces the content.

The first block is indexing: which URLs are actually reachable, which respond with a redirect or an error, whether a single canonical form exists for each page, and whether the sitemap declares what the site actually serves. On a multilingual site this extends to the consistency of the hreflang cluster, one of the places where mistakes go unnoticed most often.

The second block is performance, measured against Core Web Vitals: image weight and format, render-blocking assets, rendering strategy. The choice between server-side rendering and static generation is not ideological here — it depends on how often the content changes and what it costs to serve.

The third block is structured data: schema markup consistent with what the page actually contains, rather than applied indiscriminately.

I don't publish organic traffic growth figures, and there is a reason. Ranking depends largely on content and domain authority, that is on variables technical work does not act on directly.

What technical work guarantees is that no technical obstacle is stopping pages from being crawled, indexed and served quickly. That is a necessary condition, not a sufficient one, and it is more honest to present it as such.