Most large-site ranking problems trace back to one root cause: nobody’s actually looking at what Google is doing on the site, only at what tools guess it’s doing.
Two things worth checking that don’t always make it onto a standard checklist:
Audit Your Server Logs, Not Just Your Crawler Tool
A crawler simulates what Googlebot might do. Your server logs show what Googlebot actually did. When you’ve got 50,000+ pages, that gap matters — we’ve found sites where Google was spending most of its crawl budget on pagination and filtered search URLs while ignoring the pages that actually drive revenue. Pull your raw logs and see where the bot’s real attention is going before you assume you know.
Two Issues That Get Missed at Scale
JavaScript rendering: if your site leans on a JS framework for key content — an “About the Dean” page built as a single-page app, for instance — there’s a real chance Google’s crawler gives up before it finishes rendering. Test with Search Console’s URL Inspection tool, not just a visual check in your own browser.
Hreflang for multi-region sites: if you’re running a university with international campuses or an agency serving multiple regions, misconfigured or missing hreflang tags cause Google to show the wrong regional version to the wrong audience — diluting visibility everywhere at once.
One real example: a state university system we worked with had over 15,000 broken internal links — not external, internal, on their own site — simply because nobody had ever audited at that scale.
For the full foundational checklist — crawlability, HTTPS, Core Web Vitals, canonical tags, schema, and more — see 10 Technical SEO Audit Things Large Orgs Can’t Ignore.
