Technical SEO Engineer · WordPress, Next.js, crawl & indexing

Fix what blocks qualified discovery. Then measure what should grow next.

IndexLane diagnoses and implements crawl, indexation, rendering, migration, performance, and measurement fixes. Where the after-state and attribution are trustworthy, the work can continue into a controlled acquisition or conversion cycle.

The commercial model is bounded diagnosis or implementation first, a verified after-state, then either a separately qualified 30–60-day growth phase or a clean finish.

Technical entry

Start with a failure path that can be changed and checked

  • Pages not indexing after a release or migration
  • Next.js or headless routes leaking soft 404s, raw-output gaps, CMS URLs, or bad canonicals
  • Core Web Vitals regressions in code, cache, CDN, images, or scripts
  • Cloudflare rules blocking users, APIs, or verified crawlers
  • Tracking that does not match real conversions
  • SEO data spread across tools without an issue-to-fix workflow

Commercial boundary

Each phase has an observable finish

Diagnostics usually run $500–$750. Focused implementation sprints run from $750 to $2,000 depending on platform, release risk, and ownership.

The first phase ends with an implemented fix or evidence-backed implementation map, verification, and a written handoff. Growth work is funded separately only when a KPI, baseline, attribution path, implementation owner, and decision date exist.

Not a fit

This is deliberately accountable work

  • Backlink packages
  • Local SEO citation work
  • Activity-only retainers without implementation access, attribution, or a decision date
  • Content calendars without technical implementation
  • Guaranteed rankings or traffic claims

Published notes

Technical symptoms and failure paths

July 23, 2026 · 3 min read

A/B testing infrastructure that keeps search signals stable

Server-side splits, temporary redirects, and cookie-based variants each present different risks. Keep experiments crawlable without serving crawlers special content.

Read note →

July 18, 2026 · 3 min read

Canonical propagation delays in large sites

Fixing a canonical is not the end of the problem. Google must recrawl and reprocess the affected URLs, so visible convergence can take days or weeks.

Read note →

May 18, 2026 · 2 min read

Hreflang & multi-region sites: preventing duplicate content while serving the right locale

Multi-region sites need hreflang, canonicals, internal links, and sitemap structure to agree, or the wrong locale starts competing in search.

Read note →