What the first ninety days of enterprise SEO involve
This timeline describes the work, not outcomes.
Week 1: access and a first look at crawling
We request read access to Search Console, analytics and server logs. The first report we open is Search Console's Crawl Stats report, which shows Google's crawling history on your site: how many requests it made, what your server returned, and whether Google hit availability problems. Google aims that report at advanced users and says sites under a thousand pages generally don't need it.
Month 1: decide whether crawl budget is your problem
Google's guide to managing crawl budget on large sites defines crawl budget as the set of URLs Google can and wants to crawl. It is set by two things: the crawl capacity limit, which depends on how your servers respond, and crawl demand, which depends on size, update frequency, quality and relevance. Google says the topic mainly concerns sites with roughly a million or more pages, sites with ten thousand or more pages that change daily, or sites with many URLs reported as "Discovered, currently not indexed". Below that, the roadmap focuses elsewhere.
By the end of the month you have a prioritized ticket list. Typical items from Google's list: consolidate duplicate content, block unimportant URLs in robots.txt, return 404 or 410 for removed pages, fix soft 404s, keep sitemaps current and shorten redirect chains.
Month 3: fixes in production, checks in the release process
The first template fixes have shipped, and we confirm Google has recrawled them. Not every crawled page will be indexed, so we track key sections, not totals. If a migration is planned, Google's site move documentation sets the rules we plan around: map every old URL to a new one, expect temporary ranking fluctuation, and keep redirects generally at least one year. Much of this stage is technical SEO applied at scale, reported alongside your wider enterprise digital marketing.
