SEO & discoverability
The technical half of search — the part that is engineering rather than copywriting.
How I approach it
Most sites lose search traffic to structural problems, not to a shortage of keywords. One page trying to rank for eight different intents, canonicals pointing at redirects, a preview deployment competing with production for the same content — none of that is fixed by writing more.
The work starts with architecture: giving each thing you sell a page of its own, with content substantial enough to deserve the ranking. A page with three sentences on it is worse than no page.
Redesigns and domain moves are where rankings are usually lost, and it is avoidable. Old URLs get permanent redirects, canonicals point at the resolving host rather than one that redirects, and the sitemap is generated from the routes so it cannot drift.
This site is the worked example. Every claim above is implemented here, and you can view source.
What this covers
- Site architecture: pages that target what people actually search for
- Structured data, canonicals, sitemaps, and robots policy
- Core Web Vitals and the render path that decides them
- Migrations and redesigns that keep the rankings you already have
What you get
- An audit that names specific problems, not a score out of a hundred
- Structured data and metadata implemented, not just recommended
- A redirect map for anything that moves
- Search Console set up so you can see what changed
Relevant work
Other services
Need this on a project?
Describe what you are building and where it is stuck. The scoping call costs nothing, and you get a written scope and price before any work starts.