Key takeaways
- An enterprise SEO consultant works on the system that produces pages (templates, URL rules, internal links, releases), not on one page at a time.
- The job is as much about people as code: product, engineering, content, legal and regional teams all change what search engines see.
- Google’s crawl budget guide is written for sites with roughly 10,000+ fast-changing or 1 million+ pages. That is where crawling and indexing become a real constraint.
- Release checks matter more than audits: on a large site one template change can add or break thousands of URLs overnight.
- Report by page type and market, so each team can see its own numbers and act on them.
An enterprise SEO consultant is hired for a different problem from a small-business SEO. On a site with tens of thousands of URLs, nobody fixes pages one at a time. The work is in the templates that generate those pages, the rules that create URLs, the release process that changes them, and the teams who own each part. Get those right and thousands of pages improve at once; get one wrong and thousands break at once.
I have done SEO for more than 16 years, much of it on technical problems that only show up at scale. This article sets out what the enterprise role covers, how it differs from consulting for a small site, and how to tell whether your company needs one.
What an enterprise SEO consultant actually owns
The short answer: the parts of the site and the organisation that decide what search engines can crawl, render, index and rank, across every page type at once. In practice that breaks down into five areas.
| Area | What the consultant does | Who they work with |
|---|---|---|
| Templates and page types | Reviews each template (product, category, article, location, search results) for indexable content, headings, links and structured data | Product owners, front-end developers |
| Crawling and indexing at scale | Manages the URL inventory: parameters, duplicates, faceted URLs, redirects, sitemaps | Back-end and platform teams |
| Rendering | Checks that content and links exist in the rendered HTML Google sees | Front-end and JavaScript teams |
| Releases | Adds SEO checks to tickets, staging review and post-release monitoring | Engineering managers, QA |
| Reporting and priorities | Reports by page type and market, ranks the backlog by value | Marketing, leadership, regional teams |
None of this is unusual SEO knowledge. What is different is that every item touches several teams, and the consultant’s job is to make the work happen through them.
Why large sites need a different kind of SEO
Crawling becomes a constraint
On a small site, Google usually crawls everything that matters without help. On a large one, it may not. Google’s guide to managing crawl budget is written for “Large sites (1 million+ unique pages) with content that changes moderately often”, for “Medium or larger sites (10,000+ unique pages) with very rapidly changing content”, and for sites with many URLs in the “Discovered – currently not indexed” state. Google calls those numbers a rough estimate, but they are a useful line: below it, crawl budget is rarely your problem.
Google explains that a site’s crawl budget “is determined by two main elements: crawl capacity limit and crawl demand”, and its advice is mostly about not wasting it: manage your URL inventory, consolidate duplicate content, return 404 or 410 for removed pages, eliminate soft 404s, keep sitemaps up to date and avoid long redirect chains. One detail I often have to explain to teams: a noindex tag doesn’t save crawling, because Google says it “will still request, but then drop the page”. On a large site, that difference decides whether you fix the URLs or just hide them.
Rendering can hide content
Many large sites run on JavaScript frameworks. Google’s JavaScript SEO basics says it processes JavaScript apps in “three main phases”: crawling, rendering and indexing, and that “server-side or pre-rendering is still a great idea”. When a product team ships a template that loads its main content or links only in the browser, the effect is site-wide. An enterprise consultant checks the rendered HTML of each template, not just the source. Our article on rendering problems on JavaScript sites goes deeper.
On a large site, SEO isn’t a set of pages to fix. It is a set of systems to keep from breaking.
The people side: many teams, one search result
On a small site, the SEO and the person making changes are often the same person. In a large company, the people who change what Google sees include product managers, developers, content teams, translators, legal reviewers and regional marketers. Most of them have never been told how their decisions affect search.
A good enterprise SEO consultant spends a large part of the week on this:
- Writing SEO requirements into tickets in the language engineers use, with acceptance criteria that QA can test.
- Training teams on the few rules that matter most for their part of the site (writers on titles and internal links, developers on status codes, canonicals and rendering).
- Agreeing ownership: who owns robots.txt, sitemaps, redirects, structured data and each template.
- Managing access. Search Console Help explains the permission levels: an owner “Has full control over properties in Search Console”, a full user “Has view rights to all data and can take some actions”, and a restricted user “Has simple view rights on most data”. It also says “A property can have a maximum of 100 non-owners.” In a large company, a clear list of who has which level, and why, prevents accidents.
Releases: where most enterprise SEO is won or lost
The single most valuable habit I bring to large sites is checking releases before they go live. An audit tells you what went wrong last year. A release check stops the next problem before it reaches thousands of URLs.
The release check I run on large sites
- Status codes: do changed and removed URLs return what they should (200, 301, 404 or 410)?
- Indexing signals: are robots.txt, meta robots and canonical tags unchanged unless the change is intended?
- Rendering: does the rendered HTML still contain the main content, headings and internal links?
- Internal links: did navigation, breadcrumbs or pagination change?
- Structured data: is it still valid on each affected template?
- Redirects: are new redirects single-hop, with no chains?
- After launch: watch crawl stats, indexing and rankings for the affected page types.
If your company is planning a domain or platform change, migration work is its own project. I explain how to track rankings after a website migration in a separate guide.
Reporting that each team can act on
Leadership wants one number; teams need their own. An enterprise consultant reports by page type and by market, because a fall in “organic traffic” across a large site is usually a fall in one template, one country or one category. Splitting it that way turns a vague worry into a ticket for the team that owns it.
The other half of reporting is honesty about uncertainty. Google states that “No one can guarantee a #1 ranking on Google”, and it suggests asking any SEO whether they will share every change they make and explain why. On a large site, a change log tied to the reports is the only way to know what caused what.
Enterprise SEO consulting vs a technical SEO for a smaller site
The skills overlap, but the weight is different. A technical SEO consultant for a smaller site spends most of the time finding and fixing issues directly. An enterprise SEO expert spends more of it designing rules, writing requirements, reviewing releases and getting other people to do the work. If you want the smaller-site version, see what I look at in the first hour as a technical SEO consultant.
| Smaller site | Large site | |
|---|---|---|
| Unit of work | A page or a fix | A template, a URL rule, a release |
| Main risk | Missed opportunities | One change breaking thousands of URLs |
| Who implements | Often the consultant or one developer | Several teams, through their own backlogs |
| Reporting | Site-wide | By page type and market |
When does a large company need an enterprise SEO consultant?
From what I see, the clearest signs are these:
- Organic traffic is large enough that a bad release costs real money, but nobody checks releases for SEO.
- Search Console shows many valid pages “Discovered” or “Crawled” but not indexed, and nobody owns the URL inventory.
- Teams argue about SEO because no one has the authority or the evidence to decide.
- A re-platform, merger or new market is coming and SEO hasn’t been part of the plan.
- You have an in-house SEO who needs a senior second opinion on architecture, or support getting engineering time.
If you are deciding between a single consultant and a larger firm for this, our comparison of technical SEO consultants and agency services covers the trade-offs. Whichever you choose, the work should end with your own teams able to keep the site healthy.
FAQ
What does enterprise SEO consulting include?
Usually a review of templates and page types, management of crawling and indexing at scale, rendering checks, SEO requirements in the release process, team training and reporting by page type and market. The exact mix depends on where the site is losing most.
What is the difference between an enterprise SEO expert and an in-house SEO?
An in-house SEO knows the company and works on it every day. An enterprise SEO consultant brings experience from other large sites and an outside view, and is often brought in for architecture decisions, migrations or to support the in-house team rather than replace it.
Do enterprise SEO consultants write code?
Some do, but on a large site the consultant’s main output is usually requirements, reviews and decisions that developers implement. What matters is that they can read the rendered HTML, the server responses and the templates well enough to write tickets engineers accept.
How do you measure an enterprise SEO consultant’s work?
By the page types and markets they worked on: indexing of the pages that matter, rankings for agreed keyword groups, organic visits and the revenue or leads those pages bring, plus the number of SEO problems caught before release.
If you run a large site and want a second opinion on its templates, releases or crawling, tell me what is changing next and we can look at it together.
Eugen Platon · SEO consultant with 16+ years in SEO and digital marketing · free 10-minute first call