Technical implementation for agencies and site owners

Technical SEO fixes when the problem sits between SEO and development.

I trace crawl, indexation, migration, rendering, Cloudflare, and conversion-tracking failures into the code or configuration that owns them, implement the correction, and verify the live result.

For defined technical failures with a named owner, a safe change boundary, and a production check.

Live diagnostic lane

Evidence required
  1. E
    ExpectedDefine the correct live behavior.
  2. O
    ObservedCapture the affected output and a healthy control.
  3. R
    OwnerLocate the application, CMS, edge, or tracking layer.
  4. C
    ChangeShip the smallest safe correction.
  5. V
    VerificationRetest the production after-state.
ILCrawler v0.32.1 IndexLane audit showing crawl health, URL, issue, link, asset, render, and review state.
Working system, not a stock mockup. Real v0.32.1 operator output from an IndexLane audit. Run state and evidence stay attached to the same audit.

Inspect the evidence

Interfaces built around work that has to be checked.

These are real screens from owned systems and public tools. They demonstrate operational depth; they do not imply traffic, ranking, or revenue outcomes.

Four implementation lanes

Start with the failure path you can see

Each lane stays narrow enough to identify the owning layer, make a safe correction, and verify production.

Measurement

When the conversion path is the failure

Trace the chain from user action through dataLayer, GTM, GA4, Google Ads, and the reporting state.

Paid-case proof

See the kind of handoff this work leaves behind

These records state the implementation boundary and technical verification. They do not claim rankings, traffic, or revenue lift.

Further inspection

Tools, plugins, and field notes

Use the browser tools and public notes to prepare evidence before a paid handoff.

Published notes

Technical symptoms and failure paths

New notes are linked here immediately and remain available through the complete notes index and Atom feed.

August 20, 2026 · 5 min read

Internal link weight distribution: menus, footers, and contextual links

Menus, footers, breadcrumbs, and contextual links serve different navigation roles. Map where important pages are linked and fix weak or inconsistent paths.

Read note →

August 13, 2026 · 5 min read

Pagination indexing when rel=next/prev no longer works

Google no longer uses rel=next/prev. Paginated content needs unique URLs, self-referencing canonicals, and crawlable links through the sequence.

Read note →

August 6, 2026 · 4 min read

Orphan page detection and remediation at scale

Find pages present in your CMS, sitemap, analytics, or search data but absent from the rendered internal-link graph, then decide whether to integrate, redirect, noindex, or remove them.

Read note →