Enterprise SEO Services for Sites Nobody Can Change in One Go
At a few hundred pages, SEO is a list of fixes. At a hundred thousand, it is a question of templates, owners and approvals. The work stops being about what is wrong and starts being about who can change it, and how many pages change with it.
What is enterprise SEO?
Enterprise SEO is search work on sites large enough that no change can be made page by page. Pages are generated from templates, published by several teams, and shipped through an approval process — so the job is less about finding problems than about finding the one template, and the one owner, that can fix thousands of pages at once.
The difference is not difficulty. A small site can have harder problems. The difference is that at scale nothing is a one-off, and everything has somebody else’s name on it.
Every page is a template
You are never editing a page. You are editing a pattern that forty thousand pages inherit, which makes each decision cheap to deploy and expensive to get wrong.
Four teams publish to one site
Marketing, product, regional and whoever built the legacy section. They create URLs independently, and nobody has the full picture of what exists.
A one-day fix takes six weeks
Not because it is hard. Because it needs a ticket, a sprint, brand approval and a release window. Sequencing matters more than the fix list.
One number hides everything
Organic traffic is flat, so nothing looks wrong. Underneath, one division is up thirty per cent and another has quietly lost half its visibility.
Find the template. Find the owner. Ship once.
Every recommendation has to survive this path. A fix list that ignores the middle column is a fix list that never ships.
1 · The pattern
Which template generates the problem, and how many URLs inherit it.
2 · The owner
Whose backlog it sits in, and what they need in order to say yes.
3 · The deploy
One release, thousands of pages, and a way to prove it worked.
Range of enterprise SEO services we deliver.
Scoped to how your site is actually built and governed, not to a page count.
Enterprise SEO Audit
Site-wide and template-level rather than page-level. Every finding is tied to the pattern that causes it and the number of URLs it affects, so priority is arithmetic rather than opinion.
Template & Pattern Optimisation
Titles, headings, schema and internal links rewritten at the template so one deploy moves every page built from it.
Information Architecture
Category depth, faceted navigation and pagination rules — the decisions that determine how much of a large site gets crawled at all.
Multi-Location SEO
Location page systems that stay distinct instead of becoming three hundred near-duplicates, with the local signals that make each one rank in its own area.
Multi-Brand & Multi-Domain
Portfolio-level architecture — which brands share a domain, which need their own, and how to stop them competing for the same terms.
Migration Planning
Replatforms, redesigns and consolidations: URL mapping, redirect logic, staged QA and a rollback plan. The single highest-risk event in enterprise search.
Internal Linking at Scale
Programmatic linking rules that push authority to the pages that earn revenue, rather than a hand-built set that goes stale in a quarter.
Governance & Enablement
The standards, review gates and training that keep the next four thousand pages from repeating the problems we just fixed.
Six things that only go wrong at scale.
None of these appear on a two-hundred-page site. All of them appear on nearly every site past about ten thousand URLs.
| Symptom | What is actually causing it | Why it only happens at scale |
|---|---|---|
| Half the site is not indexed | Crawl budget spent on faceted URLs, filters and parameters that should never have been crawlable. | A small site gets crawled fully whatever you do. A large one forces Google to choose, and it chooses badly by default. |
| Hundreds of near-duplicate pages | A location or product template generating pages with the same copy and one word swapped. | Nobody writes three hundred pages by hand. They are generated, which means the duplication is generated too. |
| Your own pages compete | Two teams built pages for the same intent, on the same domain, without knowing about each other. | At scale nobody can hold the full URL inventory in their head, so the overlap is invisible until it is measured. |
| Traffic is flat, nothing is wrong | Reporting rolls everything into one organic line, so gains and losses cancel out. | One site, many businesses. The blend only hides something when there is enough underneath it to hide. |
| The fix list never ships | Recommendations written for an SEO, not for the team that has to implement them in a sprint. | On a small site the person reading the audit can make the change. Here they have to convince three other teams. |
| Every migration loses traffic | URL mapping done late, redirects written from a spreadsheet nobody validated, no staged QA. | Mapping fifty URLs is an afternoon. Mapping fifty thousand is a project, and it is usually treated as an afternoon. |
The same fix, done two ways.
This is the whole argument for working at template level, and it is why enterprise SEO looks expensive per engagement and cheap per page.
It also explains why our audits read differently. Every finding carries the template behind it and the URL count it affects, because on a site this size that arithmetic is the prioritisation.
A fix list your engineering team will actually accept.
The most common reason enterprise SEO fails is not bad recommendations. It is good recommendations written in a format nobody can put into a sprint.
Every finding carries the template, the URL count, the owner and the effort. Sorted by pages-per-hour-of-work, not by severity.
Each row names the template, the team that owns it and whether it is a config change, a template change or a build.
Broken is one problem. Unmanageable is another.
If your site has crawl errors, slow pages and missing schema, that is technical SEO and it is a cheaper, faster engagement. Enterprise SEO is for when the problems are understood and the difficulty is getting anything changed across templates, teams and release cycles. Plenty of sites need the first and think they need the second.
Send us your sitemap index.
We will tell you how many URLs you have, how many are indexed, and which templates are responsible for the gap. No call required.
Get the Index Gap CheckFive steps from audit to shipped.
Inventory and template map
Every URL crawled and grouped by the template that generated it, so the site is understood as nine patterns rather than a hundred and eighty thousand pages.
Audit at pattern level
Findings tied to templates and URL counts, prioritised by pages corrected per hour of engineering time rather than by severity label.
Owners, tickets and sequencing
Each fix written for the team that has to implement it, pre-cleared with brand and legal where needed, and sequenced around release windows.
Ship, stage and verify
Template changes QA'd on staging against a sample of affected URLs, deployed with a rollback defined, then verified live rather than assumed.
Segment reporting and governance
Performance reported by brand, region and template, with standards and review gates so the next four thousand pages do not repeat the problem.
$ mdg crawl --group-by template
✓ 186,400 URLs grouped
✓ 9 templates identified
✓ Findings mapped to owners
✓ Sorted by pages per dev-hour
✓ Segment reporting enabled
_
How big does a site have to be for this?
There is no page count that makes it enterprise. There are three conditions, and you need at least two of them.
Generated, not written
Most of your pages come out of a template rather than being written individually. That is usually true somewhere past ten thousand URLs, but a five-thousand-page location site qualifies and a fifty-thousand-page blog might not.
More than one team publishes
If several groups create URLs independently, you have a coordination problem whatever the page count. If one person owns the whole site, you probably do not need us at this level.
Changes need a release
If you cannot edit a title tag without a ticket and a sprint, the sequencing is the work. If you can change anything yourself this afternoon, buy technical SEO instead and spend the difference elsewhere.
Start with the index gap.
Send us your sitemap index and read access to Search Console. We will come back with how many URLs exist, how many are indexed, which templates account for the difference, and what the first three fixes would be worth in pages corrected. If the answer is that you need technical SEO rather than an enterprise engagement, we will say so.
Enterprise SEO, explained plainly.
What is enterprise SEO?
Enterprise SEO is search work on sites large enough that no change can be made page by page. Pages are generated from templates, published by several teams and shipped through an approval process, so the job is finding the one template and the one owner that can correct thousands of pages at once.
How is enterprise SEO different from regular SEO?
The tactics overlap almost entirely. What changes is the unit of work and the constraint. On a small site you fix pages and the constraint is knowledge. On a large one you fix templates and the constraint is coordination — whose backlog the change sits in and when it can be released.
How many pages before SEO becomes enterprise?
There is no fixed number. Three conditions matter more: whether pages are generated from templates rather than written individually, whether more than one team publishes to the site, and whether changes require a development release. Two of those three usually means an enterprise engagement is the right shape.
How do you handle SEO across multiple locations?
With a location page system rather than a set of pages. The template has to produce genuinely distinct content per location — local inventory, staff, service area, reviews — or it generates hundreds of near-duplicates that compete with each other. That plus consistent local signals for each individual location.
Can you work with our existing development and content teams?
That is the normal arrangement. We write findings as implementation-ready tickets with the affected URL count and the owning team named, sit in the relevant sprint ceremonies where it helps, and QA template changes on staging before release. We are not trying to replace anyone who already has site access.
How do you report enterprise SEO?
Split by segment — brand, region, template or business line — rather than as a single organic figure. On a large site one blended number routinely hides a division growing strongly and another losing half its visibility, and the whole point of the reporting is to make that visible.
Most large sites have half their pages missing from the index.
Not because the pages are bad — because a handful of templates are quietly spending the crawl budget somewhere else. Send us a sitemap index and we will show you which ones.
REPLY WITHIN ONE BUSINESS DAY · NO SPAM, EVER
