Enterprise SEO services

Enterprise SEO services that get fixes shipped across a large site

We work inside your tracker and release process, so template fixes, crawl control and internal links reach thousands of pages with your teams’ approval.

Get your enterprise SEO review
Trusted by the world's fastest-growing brands

The firm record

The record behind the tickets and the report

These are Webzenia’s own numbers since 2018. On your site, results are measured in your own Search Console, analytics and order data, against a baseline set in the written scope.

200+
SEO campaigns delivered since 2018
320+
Engagements delivered since 2018
2.5M+
Leads generated for clients since 2018
38mo
Average client tenure, one team throughout

What enterprise SEO is

Three things that change when a site is large

Enterprise SEO services are search work run through templates, tickets and staging checks, because a site with this many URLs and owners can’t be fixed one page at a time.

Make title patterns uniqueENG-2041ReadyProduct page · 600,000 URLs · 38% of Googlebot− title: {name}+ title: {name}, {size} | {brand}Acceptance testTitles are unique on stagingLighthouse SEO audit passes on stagingChecked again after launch

Templates carry the pages

A handful of page templates produce thousands of URLs. A title rule or a link block fixed once in the template reaches the pages built from it.

Several teams change the site

Developers, content editors and brand teams all publish. SEO work has to arrive as a ticket an engineer can estimate and a check someone can run before release.

Crawling is something you can read

Your server logs record each request Googlebot makes. They show which URLs it spends its time on, which Search Console only summarizes.

How the work is delivered

Two ways to bring in enterprise SEO help

Large sites usually need a plan. What differs is how close the work sits to your release process.

Alongside itA roadmap and reviewsInside your release processTickets and release checks
What you receiveA prioritized roadmap and scheduled reviewsTickets written for your engineers, release checks and a leadership report
Who makes the changeYour team, working from the roadmapYour engineers and editors, working from our tickets and specs
How a release is checkedAt the next scheduled reviewTemplate checks on a staging copy, then again after launch
Best whenAn in-house SEO lead already runs the ticketsSEO fixes compete with other work in a shared backlog
Starting costAdvice only, which is our SEO consulting servicePart of SEO, from $2,500 a month, with enterprise scope written and quoted from that
The lighter option can be the right one

If your own SEO lead already writes the tickets and runs the checks, advice may be all you need. If SEO work waits behind other priorities, a team that works in your tracker fits better.

The rules

Six things Google says about crawling a large site

Crawl, sitemap and Search Console limits that matter at scale, each from Google’s own documentation.

  1. Crawl budgetGoogle

    Google’s crawl budget guide is written for very large sites.

    Its audience is sites with over a million unique pages that change weekly, or over 10,000 that change daily, and Google calls these rough estimates. It also says blocking pages in robots.txt won’t move budget to other pages unless the site is near its serving limit.

  2. noindexGoogle

    A noindex tag still costs a crawl.

    Google’s guide says not to use noindex to save crawl budget, because Google still requests the page and drops it only after seeing the tag. For pages that shouldn’t be crawled at all, the guide points to robots.txt instead.

  3. SitemapsGoogle

    One sitemap index can list up to 50,000 sitemaps.

    A single sitemap is limited to 50,000 URLs or 50MB uncompressed, and an index file may hold up to 50,000 loc tags. A site with 1,240,000 URLs needs at least 25 sitemap files, so we split them by template and submit one index.

  4. Crawl StatsGoogle

    Search Console’s crawl report covers 90 days at the root.

    The Crawl Stats report is available for Domain properties and root-level URL-prefix properties. It reports requests, download size, response time, responses, file types, crawl purpose and Googlebot type. Google calls it a report for advanced users and says a site with fewer than a thousand pages shouldn’t need it.

  5. AccessGoogle

    Search Console gives owners, full users and restricted users different rights.

    Owners can add and remove users and use all tools. Full users can view all data and take some actions. Restricted users have view rights on most data. The account sits in your company’s name, and levels are set for the work in the scope.

  6. ReportingGoogle

    Search Console data can be exported to BigQuery daily.

    Bulk data export lets you schedule a daily export of Search Console performance data to BigQuery. A large site can then query that data in BigQuery and chart it in Looker Studio.

The scope

The enterprise SEO scope, tied to what you receive

Six parts, built to run through your tickets and releases.

Crawl mapGooglebot · 30 daysProduct pages38%/p/drill-20v/p/shop-vac/p/gloves-l/p/ladder-6ftFilter URLs22%Category20%Blog, guides12%Brand8%Disallow

Crawl budget and log files

Server logs sorted by site section and response code, set beside Search Console’s Crawl Stats, to show where Googlebot spends its requests. You receive: a crawl map and a ranked list of URL groups to consolidate, block or redirect.

Template rulesTested on stagingProductCategoryGuidesFiltersBrand600,000 URLs built from itENG-2041Title pattern{name}, {size} | {brand}Canonicalself, parameters removedStructured dataProduct + OfferLink blockbreadcrumb, category

Templates and rules

Title patterns, canonicals, structured data and link blocks written once per page template, then tested on a staging copy. You receive: a spec per template that your engineers can build from.

Click depth from home<a href> linksHome1 click2 clicks3 clicks4 clicksOrphansHomeCategory pagesBrand pagesProduct pagesBlog and guidesENG-2070Blog and guidesOrphan pageslisted for review

Internal linking at scale

Link blocks on category, product and article templates that put the pages you want ranked within a few clicks of the home page, in plain <a href> links Google can follow. You receive: link rules per template and a list of orphan pages.

Release checkAwaiting your approvalTicketTemplate checkStagingENG-2041Unique titlesPassENG-2057Pagination linksBack to ticketENG-2063robots.txt rulePassENG-2070Category linkPass3 passed on stagingApprove 3 changes

Tickets and release review

SEO work written as tickets with an acceptance test, plus a check of the templates a release touches, before and after launch. You receive: the tickets and a release check sheet.

Roles sheetIn your company’s nameIn the CMSEngineersEditorsOur SEOPage titlesViewEditReviewRedirectsEdit–Reviewrobots.txtEdit–ReviewTemplatesEditViewReviewSearch ConsoleOwner · your teamFull · our SEO

Governance and access

Who can edit titles, redirects, robots.txt and templates in the CMS, and who holds which Search Console level. Where you run several brands or country sites, the same pass covers hreflang return links. You receive: a roles sheet and a short SEO rulebook for editors.

Leadership reportFrom your own dataOrganic revenue · this quarter$47,900,000Last quarter $41,200,000LastThisOrganic orders184,000215,000Googlebot on filter URLs22%9%Tickets waiting63

Reporting to leadership

Organic orders and revenue from your own data, with the crawl and ticket numbers behind them, in the format your leadership already reads. You receive: a report set in the written scope.

How it runs

Read the logs, map the templates, review releases, then report

A document closes each step, and each change goes live only after you approve it.

googlebot-log-summary.csv

Googlebot log summary

Sample · Sample Supply Co. · national online retailer
SectionShare of requestsAction
Product pages38%Keep
Category pages20%Keep
Blog and guides12%Keep
Brand and store pages8%Keep
Filter and sort URLs22%Disallow in robots.txt
Server logs, 30 days, share of Googlebot requests. The shares total 100%. The crawl found 1,240,000 URLs, listed by template in the next step.

Our stack

The tools behind the crawl, the tickets and the report

What we crawl, ticket and report with on a large site. Select a tool for what it does and where it fits in the work.

Google Search Console
Why Google Search Console

Search Console is Google’s own report on how it crawls, indexes and shows your site.

How we use it

We read the indexing report and Crawl Stats in your own account, and use the bulk export to BigQuery where your team turns it on.

Index healthCWV reportSource
Google Search ConsoleGoogle
Bing WebmasterBing
AhrefsEstimate
NoneNo

How the engagement runs

Audit at scale, fix the templates, then govern

Enterprise SEO runs as a program inside your organization. The work is writing rules into templates and keeping them in place while your teams keep releasing.

01Months 1 to 2Mapped

Audit the whole site, not a sample

We crawl the full site, read your server logs for Googlebot’s requests and sort the entire URL set by the template that built it. On a site this size the audit is a scaling problem in itself. It ends with a map of where crawl, index bloat and template issues cost the most, and the first tickets your engineers can estimate.

  • URLssorted by template
  • LogsGooglebot requests read
  • Ticketsscored on pages reached
02Months 3 to 6Shipping

Fix templates and rules, not pages

We work through the highest-impact template and crawl fixes, written as tickets and slotted into your sprints. Each change is checked on a staging copy before release and again after it, so a fix on one template doesn’t quietly break another, and every page that template builds gets the change.

  • Templateschecked on staging
  • Crawl wastecut at the rule level
  • Releaseson your sprint schedule
03OngoingMonitored

Keep the site healthy as it changes

A large site changes constantly, and any release can bring an issue back across thousands of pages. We review the releases you ask us to, keep the editor rulebook and access roles current, and report to leadership in the format they already read, so SEO health is measured instead of rescued.

  • Releaseschecked before and after launch
  • Rulebookkept current for editors
  • Reportsset in the written scope

Reported to leadership, starting from your own orders and revenue, in the format set in the written scope.

Leadership reporting
LogsRelease checksBigQuery

Our commitment

What we commit to, in writing

Enterprise engagements are large and easy to hide inside. These are the terms you can hold us to.

  • Your accounts stay yours

    Search Console, analytics, the domain, hosting and code stay in your company’s name. Each person on our side gets a named account at the level the scope sets.

  • We work through your teams

    Fixes arrive as tickets with an acceptance test, in the tracker your engineers already use, and nothing goes live without your approval.

  • One senior strategist

    The same senior strategist owns the program throughout. If a release breaks a template, you hear it from us first, the same US business day.

  • Nothing renews on its own

    Templates, teams and markets are priced in a written scope before work starts, and nothing renews on its own. Questions get a reply within 4 hours.

If the leverage is in a few templates rather than a long program, we’ll tell you that too.

Questions

Enterprise SEO, answered

Start here

See where a large site spends its crawl

Tell us your site address and how the site is run. We’ll crawl it, group the URLs by template, and send back what we would fix first and who would need to ship it.