SEO freelancer in Frankfurt Rhine-Main who works in your website's code

Why a company website stays out of search

A company website gets few visitors from search for two reasons. A crawler cannot read its pages cleanly, or no page answers the search a buyer types. Both causes show up in data you can measure.

The technical causes sit in the code. A page forwards three times before it loads. Two addresses carry the same text. One title tag repeats across dozens of pages. A service description arrives through a script after the page has loaded. A crawler reads a website as data, and when the data contradicts itself, it has to guess which page counts.

The content causes sit in the page structure. A firm that lists six services on one page answers six searches with a single page. A buyer in Hanau who types a service and the town needs a page that names both.

One person for the findings and the fixes

SEO work often splits in two. A consultant writes a report, and a developer builds the changes later. I do both parts. When I find a fault, I fix it in the template, the page structure or the text.

I have built websites for more than twenty years, from order funnels of online shops to this site. Today Claude and Codex write much of the code under rules that a machine checks before each change. My part is the page structure, the data behind it and the review of each result.

The first week on your site

In the first week I check your site against the table below. Each row is one check, the way I test it and what your company gets from it.

Check	How I test it	What you get
Crawl	A crawler on my laptop fetches each page it can reach from the home page	A list of your pages with status code, title and word count
Robots and sitemap	I compare robots.txt and the XML sitemap with the crawl	Pages that are blocked by mistake or missing from the sitemap
Forwardings	I follow each forwarding to its last address	Chains and loops replaced by a single step
Duplicates	I group pages by title, description and main text	One address per content, with a canonical link on the copies
Titles and descriptions	I read them next to the search each page should answer	A title and a description for each service page
Internal links	I count the links that lead to each page	Service pages the site links to, and no page without a link
Speed	Lighthouse runs locally with phone and desktop settings	Largest Contentful Paint and layout shift per template, before and after
Structured data	I read the JSON-LD and compare it with the visible text	Markup for your company, services and questions that matches the page
Pictures	I check file names, alt texts and file sizes	Pictures whose names and alt texts say what they show
Searches per page	I list the searches your buyers type and match each to one page	A map of searches and pages, with gaps and overlaps marked
Region	I check whether service pages name the towns you serve	Pages for buyers who search with a town in Rhine-Main

The table describes the site as a crawler meets it. It says nothing about the position a page will reach. It lists the faults I can fix.

Search work I have done

At an insurance group in Frankfurt I built the web portals and ran their conversion optimization. From 2016 to 2021 I managed more than 100 top-level domains for the group. For a current client I optimize the website of a platform for search, conversions and agent readiness.

Next to the project work I took courses on link building, A/B testing and conversion optimization. This site is my own test case. It is a static Astro build that delivers its text in plain HTML, with JSON-LD in its pages.

Who I am

I am Michael Wutzke, an IT expert for data platforms in Frankfurt. I have spent more than twenty years from code to CIO in finance, e-commerce and real estate, with cloud platforms and data centers. Today AI agents speed up how I build and transform data platforms and websites. I hold the Google Analytics and the Google Mobile Sites certifications, and I teach practical work with Claude at Claude Hacker House.