Who this is for
Teams whose organic traffic pays the bills and who suspect the site itself is in the way: slow templates, structured data that does not match the page, a migration that lost rankings, a redesign that broke tracking. It also fits teams that want the measurement side done properly, so the numbers in GA4 mean what they say.
I have worked in SEO for more than a decade; the technical side, where the templates, the server and the crawler meet, is where I stayed.
Typical situations
- Core Web Vitals are red in Search Console and the last three fixes were plugins.
- A redesign or migration went live and impressions dropped in the weeks after.
- Rich results disappeared, or the structured data describes a page that no longer exists.
- GA4 shows numbers nobody trusts, and Tag Manager has forty tags nobody owns.
- Product or category pages get crawled but not indexed, and nobody knows why.
- Four language versions, and hreflang points somewhere else.
What I deliver
- Technical audit: crawl, indexing, canonicals, hreflang, redirects, sitemaps, robots, pagination and the rendering of JavaScript-heavy templates.
- Core Web Vitals work at the source: templates, images, fonts, scripts and caching, not a plugin that hides the symptom.
- Structured data that matches the page: Article, Product, FAQ, Breadcrumb and Organization, generated from templates and validated on every release.
- Migrations and redesigns with a redirect map, a pre-launch crawl and a post-launch comparison.
- GA4 and Google Tag Manager: event design, consent handling, server-side tagging where it is worth it, and a tracking plan the team can maintain.
- Readiness for AI answer engines: clean HTML, stable anchors, llms.txt and content that can be quoted with its source.
How it goes
Crawl and compare. I crawl the site, read the templates and compare what the crawler sees with what Search Console and analytics report. The first output is a list of issues with the URL, the cause and the fix, ordered by impact.
Fix at the source. Changes go into the templates and the server configuration, on staging first. Tracking changes get a test plan with the events, their parameters and the reports they feed.
Watch the result. After release I follow indexing, vitals and the reports for a few weeks and hand over a short document of what to watch. Measurement can continue on a retainer.