Fix templates, not pages
One template change lands on ten thousand URLs. We work at the template and component level so the effort scales, and we quantify the aggregate impact before asking engineering for the slot.
SEO for large sites: template-level optimisation, crawl budget management, and the governance that stops six teams undoing each other’s work.
Free proposal · No contracts over 30 days · Reply within one business day
The problem
On a large site the bottleneck stops being knowledge and becomes coordination. A change that would take an afternoon on a small site needs three teams, a release train and a stakeholder who does not report to you — and meanwhile another team ships a redesign that drops the internal links you spent a quarter building.
One template change lands on ten thousand URLs. We work at the template and component level so the effort scales, and we quantify the aggregate impact before asking engineering for the slot.
Log file analysis shows where crawlers actually go. On large sites a large share of that goes to pagination, filters and stale URLs while new content waits. Reclaiming it is often the single biggest available win.
Documented standards, automated checks in CI, and an SEO review step in the release process. Without it every quarter starts by re-fixing last quarter.
Requests written as tickets with estimated revenue impact, effort and a test plan. Competing for sprint capacity against feature work requires the same evidence any other team has to bring.
Tools we use
Still deciding
A fully-loaded in-house hire costs more than most retainers. The real question is whether you have enough work to keep a specialist busy.
The three we are called in to fix most often. If any of these describe your current setup, that is the first thing we would change.
SEO competes for engineering capacity against revenue features. A ticket that says "add breadcrumbs" loses to one with a projected number attached. Every request needs the same evidence any other team has to bring.
A redesign ships and quietly drops the internal links built over two quarters. Without automated checks in the pipeline, every quarter starts by re-fixing the last one.
On a large site, a large share of crawl goes to pagination, filters and stale URLs while new content waits. That is invisible in every tool except server logs, and it is usually the biggest available win.
Agreed before we start, so progress is visible in the months before it shows up in revenue.
The questions we get asked most, answered without the sales gloss. If yours is not here, ask us directly — you will get a straight answer either way.
Still have questions?
Book 30 minutes with a strategist. No deck, no pitch — just answers about your situation.
Book a callLooking for pricing, contract terms or timelines?
Read all FAQsTell us what you are trying to grow. You will get a straight answer on whether we can help, and what it would cost, within one business day.