Writing / SEO Ops
SEO Ops

Enterprise SEO Audit: What to Check When You Inherit a Messy Site

A systematic four-layer enterprise SEO audit framework: find site-breaking issues, protect revenue pages, and build a 90-day plan you can actually run solo.

On this page

You just inherited an enterprise website. Maybe it’s post-acquisition chaos. Maybe your predecessor left for “new opportunities.” Maybe you’re staring at four different properties that needed SEO management yesterday.

The site has 50,000 pages. Half of them might be broken. The other half are competing with each other. You don’t know what’s working, what’s killing performance, or where to start digging.

Standard audit checklists don’t work here. They’re built for clean, single-property sites where you can review everything by hand. Enterprise sites need a different approach. You have to separate the site-breaking issues from the nice-to-haves, find what’s actually driving revenue, and build a plan that won’t take six months to run.

Here’s the audit framework I use when inheriting enterprise SEO chaos. I’ve run it across four properties post-acquisition as a one-person team. It works.

The enterprise audit framework: work in four layers

Most audit guides treat every issue as equal priority. That’s a mistake on enterprise sites. You work in layers, each one building on the last.

  • Foundation layer: what can kill you. Technical issues that tank the whole site.
  • Traffic layer: what’s actually working. Revenue pages and conversion paths.
  • Content layer: what needs attention. Gaps, cannibalization, optimization.
  • Growth layer: what to build next. Competitive opportunities and links.

You don’t skip ahead. Growth initiatives are pointless if the foundation is on fire.

Foundation layer: the site-breaking issues

Start here. Everything else can wait.

Run the technical infrastructure checks first

Pull a crawl. Screaming Frog for smaller enterprise sites, Botify for anything over 100k pages. You’re hunting the stuff that breaks everything.

Server errors come first. Any 500-level responses need immediate attention. They tell Google your site is unreliable. One site I inherited had a misconfigured server throwing 503 errors on the highest-traffic category pages. Traffic dropped 40% over three months while the previous team kept optimizing content. They were polishing the chocolate while the pipes were leaking.

Check robots.txt and XML sitemaps next. I once found an enterprise site accidentally blocking its entire blog from indexing. Two years of content, zero organic visibility. One misplaced line in robots.txt.

Assess indexing and crawlability

Run site searches for each major section. Compare what’s indexed to what should be. A typical enterprise site has 30-40% of pages providing no traffic, but first you need to know which pages Google isn’t even seeing.

Look for crawler traps: infinite scroll, session ID parameters, faceted navigation without controls. These waste crawl budget and confuse Google about your structure.

If you have server log access, use it. What is Google actually crawling versus what you assume it crawls? The gap is where your technical SEO breaks down.

Check Core Web Vitals and performance

Use PageSpeed Insights and the Core Web Vitals report in Search Console. Poor Core Web Vitals correlate with meaningfully lower conversion rates, and on a site processing thousands of daily conversions that’s real money.

Focus on your money pages first: homepage, key product pages, main conversion paths. Don’t try to fix every page at once. Prioritize by traffic and revenue impact.

Check mobile separately. Enterprise sites often have desktop-first builds that fall apart on mobile, and mobile users abandon slow pages fast.

Traffic layer: follow the money

Once you know the site won’t implode, find what’s actually working.

Identify the revenue-driving pages

Connect Google Analytics to Search Console. Sort pages by conversion value, not just traffic. The page with 50,000 monthly visits might convert at 0.1%. The page with 500 visits might convert at 15%.

Pull the top 50 pages by organic revenue over the last 12 months. These are your untouchables. Any technical change, tracking update, or content edit needs extra care here.

Map conversion paths. Enterprise buyer journeys are messy. A prospect might enter on a blog post, hit three product pages, download two resources, then convert on a demo form. Understand the full path, not just the last click.

Read your traffic sources and patterns

Split brand versus non-brand organic. Heavy brand dependency means you’re exposed to reputation risk but protected from algorithm swings. Heavy non-brand means the opposite.

Check seasonality. B2B enterprise sites often swing 30-40% on buying cycles, conference seasons, and fiscal years. Account for that in your reporting and goals before you set them.

Look for traffic cliffs. Sudden drops usually mean technical issues, manual penalties, or algorithm hits. Gradual declines usually mean content decay or rising competition.

Map the conversion paths

Use Multi-Channel Funnels to see how organic fits with other channels. Enterprise buyers rarely convert from a single organic visit.

Separate assist pages from last-click pages. Content that assists conversions is just as valuable as content that closes, but most audits only look at the closers.

And check your attribution. Enterprise tracking is often a mess. Make sure you’re measuring the right things before you optimize for them.

Content layer: signal vs noise

Now you can look at content.

Inventory and classify everything

Export all pages from your crawl. Classify by type: blog posts, product pages, landing pages, resource downloads, company pages. Each type needs a different approach.

The top 10% of pages typically drive 35-40% of organic traffic on enterprise sites. Find your top performers and figure out why they win: topic choice, depth, keyword targeting, internal links.

Flag thin content. Under 300 words, no unique value, auto-generated. Beef it up or kill it. I’ve deliberately killed pages driving tens of thousands of visits because they attracted the wrong people. Precision over volume.

Check publication dates. One site had 500 blog posts about features that no longer existed, competing with current product pages for branded searches.

Detect keyword cannibalization

Use Search Console to find pages competing for the same queries. Sort by impressions, then look for multiple pages from your site showing up for the same keyword.

One enterprise site I inherited had 15 different pages targeting “project management software.” None ranked well because Google couldn’t tell which was primary. After consolidating into three clear pages with distinct intent, all three improved.

Check internal linking for conflicting signals too. Linking to different pages with the same anchor text creates confusion about topical authority.

Run a content gap analysis

Compare your coverage to your main competitors with Ahrefs or SEMrush. Find keywords they rank for that you don’t.

Prioritize gaps in your core product areas. If you’re a project management tool with no content around “team collaboration,” that’s a bigger problem than missing a trending topic.

Check for format gaps. Maybe competitors have video, interactive tools, or downloadable resources where you only have blog posts.

Growth layer: size the opportunity

The fun part. Now you think about growth.

Assess the competitive landscape

Identify your top 5-10 organic competitors. These may differ from your business competitors. The sites ranking for your target keywords are your SEO competition.

For SaaS specifically, study their content strategy. Bottom-funnel comparisons? Alternative pages? Integration content? Feature-focused posts? Then check their backlink profiles. What earns them links? That informs your content and outreach.

Review backlinks for toxic patterns with Ahrefs or Majestic. Enterprise sites accumulate spammy links over years of existing online.

Audit internal link architecture. Complex enterprise structures dilute PageRank flow. Map how authority moves from your homepage to your key conversion pages.

Fix broken internal links. Your crawler flags them. On large sites they waste crawl budget and hurt experience.

Find emerging keyword opportunities

Check Search Console for keywords ranking 11-20. Those are usually easier to push up than ranking for new terms from zero.

Use Google Trends to spot when target keywords peak, then plan your calendar and campaigns around it.

Review question-based and conversational queries. They’re growing fast for B2B research, and your content may need restructuring to capture them, especially as buyers move to AI search.

The 30-60-90 day action plan

The audit is done. Now you need a system to implement fixes without breaking things.

Days 1-30: Foundation only. Server errors, indexing issues, Core Web Vitals. Nothing else matters until these are resolved.

Days 31-60: Traffic protection and consolidation. Fix cannibalization, update your highest-traffic pages, strengthen internal linking to money pages.

Days 61-90: Growth. New content, link building, competitive gap filling.

The one-person approach works here because you’ve systematized the foundational work. You’re not reacting to everything at once. You’re running a sequence.

Track everything. An enterprise audit is pointless if you can’t measure the impact of your changes. The systems-led move isn’t doing the audit once. It’s building workflows that turn audit findings into compounding fixes over time.

If you want the playbooks behind this kind of solo-operator system, start on the blog or book a call and we’ll map your first 90 days.

Related reading: How to Build an SEO Strategy Your Skeleton Crew Actually Owns · score yourself with the matching audit · start with an audit · read the manifesto

Frequently asked questions

How long does a complete enterprise SEO audit take?

Plan for two to three weeks if you work in layers and stay focused. Agency audits often stretch to four to eight weeks, but most of that time goes into documentation nobody reads. You don't need a 90-page deck. You need actionable insights and a prioritized list. Audit fast, fix sooner.

What tools do I actually need for an enterprise audit?

Three: Google Search Console, Google Analytics, and a crawler. I use Screaming Frog for sites under 100k pages and Botify for anything larger. Everything else (Ahrefs, SEMrush, Majestic, server logs) is helpful but not required to get started. Don't let tool paralysis delay the audit.

Should I fix everything before creating new content?

No. Fix the foundation issues first (server errors, indexing, Core Web Vitals), but you can work on content while you do. Just don't pour budget into promoting new content while your technical foundation is broken. You'll be amplifying a leaky system.

How do I prioritize when everything looks urgent?

Use the revenue impact test. Ask what traffic or conversions you lose if you don't fix a given issue. Fix high-impact, low-effort items first, then work through the bigger projects systematically. Urgency is not the same as importance.

What if I find issues that need developer resources I don't have?

Document everything with screenshots and a plain-English explanation of the business impact. Most technical issues have workarounds that don't require custom dev. Focus on what you control, and build the case for resourcing with numbers, not complaints.

What does a 30-60-90 day plan look like after the audit?

Days 1-30: foundation fixes only (server errors, indexing, Core Web Vitals). Days 31-60: traffic protection and content consolidation (cannibalization, money-page updates, internal linking). Days 61-90: growth (new content, link building, competitive gaps). Foundation first, growth last.

NT
Nathan Thompson
Practitioner, not a guru. I built the growth engine at Copy.ai from scratch, then left to build Systems-Led Growth: the system that runs a company's go-to-market with one operator instead of a department. I document what I build.
Start with an audit →
Barely Shipping

I build the whole thing in public.

The podcast and newsletter where I show the frameworks, the real numbers, and the parts that don't work yet. No hustle-culture, no fluff.