Service
Most SaaS marketing sites lose rankings to rendering, routing, and indexation problems long before they lose them to content. We work in your repo, not around it.
The problem
Modern SaaS marketing stacks break search in specific, repeatable ways. Client-side routing that never emits a real URL. A CMS that publishes canonical tags pointing to staging. Faceted pages generating 40,000 near-duplicate URLs. A docs subdomain fighting the marketing site for the same query.
None of it shows up in a content audit. All of it caps how much of your work can rank.
We audit against the actual rendered DOM and real crawl logs, then hand your engineers something they can merge.
You probably recognise
What you get
A full crawl with JavaScript execution, compared against the raw HTML, so we can see exactly what a crawler receives versus what a user sees.
Where crawl budget is actually being spent. Almost always on pages you do not care about.
A deliberate decision for every URL pattern on the site: index, noindex, canonical, or block. Most sites have never made these decisions explicitly.
URL structure, internal link distribution, and hub design so authority reaches the pages that make money.
Real fixes — image pipeline, font loading, third-party script budget, hydration strategy — not a Lighthouse screenshot.
Organization, Product, SoftwareApplication, FAQ, and Article markup implemented correctly, which matters more now that AI systems parse it directly.
Pre-launch redirect mapping, staging QA, and post-launch monitoring. Replatforming without this is how companies lose half their traffic in a week.
How we run it
Same order every time, because the steps depend on each other. Skipping ahead is the most common reason these programs underperform.
Full site crawl with and without JavaScript, plus Search Console and log data.
Every issue scored by traffic impact against engineering effort. You get a ranked list, not 90 undifferentiated findings.
Reproduction steps, expected behaviour, acceptance criteria. Written for your issue tracker, in the format your team already uses.
We open PRs on Astro, Next, Nuxt, and Webflow-adjacent stacks, or pair with your engineers if you prefer to keep the commit history in-house.
Re-crawl and confirm each fix landed. Roughly a fifth of fixes regress on the next deploy without this step.
CI checks and a pre-deploy checklist so the same class of bug does not reappear next quarter.
Questions
Related reading
Rendering failures, canonical bugs from headless CMSs, docs subdomains competing with marketing, and the replatform checklist that stops you deleting half your traffic.
Jun 30, 2026
Where authority actually accumulates on a software marketing site, how to route it to pages that convert, and the URL structure decisions that are painful to reverse.
Apr 28, 2026
The difference between a page set and a doorway, how to test the idea before writing any code, and the index-rate monitoring that tells you when to stop expanding.
Jul 21, 2026
No cost, no call required first
Send a URL. Four working days later you get a recorded walkthrough of what is holding the site back and a plan for the next two quarters.
Get my free teardown
