Where your enterprise SEO audit starts, and where a free scan stops.

What does an enterprise SEO audit cover?

Your enterprise SEO audit covers technical SEO, crawl budget and indexation, website performance, content quality, keyword and search intent analysis, and internal linking. It also takes in JavaScript rendering, structured data, your international SEO where it applies, backlink analysis, competitor research, and your analytics and SEO governance. That is a long list, and every item on it has an owner somewhere in your organization.

Open the Page Indexing report in your Search Console and check your sitemap. Those two screens show whether crawl budget is a problem for your site. Google's crawl budget guide is written for very large and frequently updated sites. Do your pages get crawled the same day you publish them? Then a current sitemap and regular checks of that report are enough. And if they do, you can stop worrying about it.

Your findings need a shape. A useful one says what is wrong, why it matters, how much of your site it hits, and what fixing it could mean for your business. Your readers differ, though. Your leadership wants a short view of risks and opportunities, while your SEO, content, development and analytics teams need evidence and implementation steps. One document rarely serves both well.

What can a free automated scan establish for an enterprise site?

The free assessment gives you a baseline score out of 100, built from your homepage and up to eight of your sampled pages. You see the evidence: your response headers, markup, structured data, headings, script and image weight, plus robots and canonical signals. Each item ties to one of your eight weighted pillars. And that means your number always arrives with its reasons attached (no mystery scores here). Treat it as your baseline, not your audit.

Your score is weighted: architecture 15%, performance 15%, security 12%, search 12%, schema 10%, AI readiness 10%, editorial experience 10% and operational health 16%. Score 80 to 100 and you are in good standing. At 60 to 79, your site is constrained. Land at 40 to 59 and you are at risk. Between 0 and 39, you are in legacy condition, a polite name for a site that needs real work from you. So start with your lowest pillar. That is usually where you gain the most for the least cost.

Run it on each hostname you own. Google treats different hostnames as separate sites, so a baseline per hostname matches how your sites are crawled. And it costs you nothing. Your result arrives in about two minutes, and you get three checks per hour per connection. That lets you baseline three hostnames an hour, which is plenty for most inventories you will scope.

Where does a public read of your site stop?

A public read of your site stops at everything behind your logins, inside your tools, or in someone's head. Open your Search Console and your analytics. Then check whether your users in one country land on the wrong localized page, such as your UK users seeing only the US page. The assessment won't show you that, and you shouldn't expect it to. A public scan can't see what only your own data reveals.

The assessment does not log in, read your analytics, run your field performance data, or interview anyone. So you can't size a problem by the share of your pages or your search demand it affects. Nor can you record the baseline of impressions, clicks and indexed pages you need before your change ships. Without that, you are guessing at your impact, and a guess is hard to defend in a review.

The assessment also reads a sample of your URLs, not every one. Your hreflang is the clearest case. Test a single page and you can miss return links and report false positives. Full validation means auditing your entire implementation and every one of your canonical URLs. Treat the assessment as a pointer to what you should check, not a verdict on your site. A pointer helps. But it isn't proof.

How do you scope an audit across many domains and languages?

You scope an audit across many domains and languages by treating each of your hostnames as its own site. Audit your templates plus a sample of your highest-value pages, not every one of your URLs. (Yes, that feels like cutting corners. It isn't.) Templates usually show you the same issues faster than a full URL pass ever could. So give your sheet one row per hostname, language folder and brand, plus the templates you use. Google treats your hostnames as separate sites with separate crawl budgets, and your sheet and your brief should do the same.

Put your hreflang rules in your brief. Your language codes must be ISO 639-1 and your region codes ISO 3166-1 Alpha 2, so UK and EU fail as region codes, and a country code can't stand alone. Reciprocity matters too: if your page links to another, that page must link back to yours, or Google may ignore your annotations. And place your tags in your page's head, because tags outside it may not be read. The mistakes here are small, and they quietly cancel your whole setup.

Ask every vendor you shortlist whether they validate your whole implementation or test your pages one at a time. Their answer isn't a detail, it's the label on the audit you are buying.

What evidence should an enterprise SEO audit produce?

Your enterprise SEO audit should give you three things: a sized list of problems, an owner for every item on that list, and a sequence of what ships first, what waits, and what you deliberately leave unfixed. Ask your auditor to size each problem in pages or search demand affected on your site, using your Search Console data where possible. Before you ship any change, record a baseline of impressions, clicks and indexed pages for the affected sections. Without it, the post-release conversation turns into opinion, and opinion rarely settles anything.

You should get a findings tracker, an executive summary of up to 15 slides, a technical report and developer tickets with clear instructions, as published scopes list. Priority levels such as P1 to P4 tell you and your teams what to do first. You can test your plan against one published table: crawl traps, widespread noindex errors, major redirect loops and broken tracking in the first one to two weeks. Does yours match? Have Core Web Vitals failures? Then you should see a 30-day sprint in your plan. If you don't, ask why.

How long does an enterprise SEO audit take?

Plan for four to eight weeks, though published ranges for your enterprise audit run from two weeks to as long as 60 days. Ask each vendor to show how your audit splits into phases. Does your site have 50,000 to 500,000 pages? One published breakdown gives you three to four weeks. One week goes to collecting your data, one to two to analyzing it, and one to your deliverables. And if your vendor can't show you that split (a surprisingly common gap), they probably haven't planned one.

Running a larger site or a complex international implementation? You may need five to six weeks. Multi-site or multi-region work can reach six to eight. Scope drives that range. Every hostname, language and template you add costs you weeks, so your answer to "how long" starts with your inventory, not with your vendor's calendar.

Run the free assessment on your site before kickoff. It takes about two minutes, and you can hand the report link to whoever you brief. Published guidance recommends repeating your audits quarterly. Your first audit is your baseline, because every later comparison starts there. So get that first number early: until you have it, you can't say whether your site improved or just changed.

Questions, answered.

Your next read.

1. 01Website audit checklistThe eight pillars as a list you can run yourself.
2. 02AI SEO auditCrawl access, extractable passages, schema, llms.txt.
3. 03Website redesign SEOBaseline before, reconcile after.