Advanced SEO Checklist: The Essential Best Practices
An advanced SEO checklist starts where the basics stop: not “did you write a title tag” but “does Googlebot actually reach, render, and trust the pages you’ve built.” The items below are the ones we come back to on every large or technically complex site we touch at Salterra, because they’re the ones that quietly decide whether a site’s real quality ever gets discovered.
This isn’t a beginner’s punch list. It assumes your on-page fundamentals are already solid and you’re now troubleshooting why a site with good content still underperforms, or hardening a large site against the failure modes that only show up at scale. Work through it section by section, and treat it as a recurring audit rather than a one-time exercise.
Log File Analysis
- You’ve pulled at least 30 days of raw server logs (not sampled analytics data) and isolated verified Googlebot hits by reverse DNS or IP range.
- You know which sections of the site get crawled daily, which get crawled weekly, and which haven’t been touched by a crawler in over a month.
- You’ve cross-referenced crawl frequency against your XML sitemap and indexation reports to spot pages that are crawled but never indexed.
- You can identify crawl spend wasted on parameterized URLs, redirect chains, soft 404s, and low-value archive pages.
- You track crawl frequency changes after major site changes (migrations, new sections, internal link additions) to confirm the crawler noticed.
Log files are the only data source that tells you what a crawler actually did, as opposed to what your sitemap or robots.txt asked it to do. Search Console’s crawl stats give you aggregates; logs give you the URL-by-URL truth, including the requests that never show up anywhere else, like AI crawlers hitting your resource files or bots stuck in a redirect loop.
If you’ve never opened a raw log file, start small: grab a week from your CDN or hosting provider, filter to a known bot user agent, and just look at what it requested. The patterns that jump out — a crawler hammering a filtered category page thousands of times while your best content sits untouched — are usually the fastest wins on the whole list.
Crawl Budget Allocation
- Faceted navigation and filter combinations are either blocked, canonicalized, or parameter-handled so they don’t multiply into thousands of near-duplicate URLs.
- Internal search results pages, calendar/date-archive pages, and session-ID variants are excluded from crawling, not just from indexing.
- Your XML sitemap contains only canonical, indexable URLs — no redirects, no noindex pages, no 404s.
- Redirect chains longer than one hop have been flattened site-wide.
- Low-value pages that still need to exist (old promotions, thin tag pages) are noindexed and, where crawl waste is severe, disallowed.
Crawl budget is a real constraint on any site past a few thousand URLs, and it’s a myth on a 200-page brochure site. The skill is knowing which category you’re in. If Search Console shows Googlebot requesting far more URLs than you have indexable pages, or your “Discovered, not indexed” count is climbing, you’re spending budget on the wrong things and it’s actively costing you coverage on pages that matter.
JavaScript Rendering
- You’ve confirmed, via the URL Inspection tool’s rendered HTML, that your critical content and links actually appear after JavaScript execution — not just in the raw source.
- Internal links are real anchor tags with href attributes, not onclick handlers or div-based navigation that only works after client-side hydration.
- Critical above-the-fold content doesn’t depend on a third round-trip (client render, then a second render after data fetch) that delays what Googlebot sees.
- You’ve tested with JavaScript disabled to see what a crawler without rendering resources — including most AI crawlers — actually receives.
Google renders JavaScript, but rendering is a second, delayed pass that costs more compute than parsing raw HTML, and it isn’t guaranteed to happen quickly on every URL of a large site. Most non-Google crawlers, including the bots powering AI answer engines, render far less reliably or not at all. Server-side rendering or static generation for anything link- or content-critical remains the safest advanced play, not a legacy best practice you’ve outgrown.
Diagnosing rendering gaps
Compare the “View Source” HTML against the rendered DOM in Chrome DevTools for a handful of representative templates. If your primary content, headings, or internal links only exist in the rendered version, you’ve found a dependency worth removing or at least hedging with server-side rendering.
Internal Link Sculpting
- Your most commercially or strategically important pages receive more internal links, from more distinct pages, than your least important ones — deliberately, not by accident of navigation.
- Anchor text varies naturally across links to the same page rather than repeating one exact-match phrase everywhere.
- Orphan pages (no internal links pointing to them at all) have been identified via a full crawl and either linked in or deliberately removed.
- Link equity isn’t trapped in a footer mega-menu that dilutes weight evenly across hundreds of destinations regardless of importance.
Internal link sculpting is the practice of using your own site’s link graph to tell search engines what actually matters, and it’s still one of the highest-leverage things you control entirely in-house. A page three clicks deep with twelve contextual internal links from relevant content will consistently outperform an identical page sitting one click from the homepage but linked only from a generic nav.
Entity SEO & Structured Data
- Organization, Person, and Article/Product schema are implemented consistently and validated, not just present on a handful of templates.
- Named entities in your content (people, brands, products, places) are described consistently enough that they’re recognizable as the same entity across pages.
- Author bios connect to real Person schema and a consistent bio, reinforcing E-E-A-T signals that both traditional search and AI systems weight heavily.
Entity SEO has moved from a nice-to-have to core infrastructure. AI Overviews and chat-based answer engines lean on structured, unambiguous entity relationships when deciding what to cite, and that means the clarity of your markup matters as much as the clarity of your prose.
Indexation Hygiene
- Canonical tags point to the actual preferred version of every page, and you’ve spot-checked that Google’s “Google-selected canonical” agrees with your declared one.
- Pagination series don’t compete against each other for the same query intent.
- You monitor the Index Coverage report for spikes in “Crawled, not indexed” as an early signal of quality or duplication problems, not just outright errors.
Indexation problems rarely announce themselves loudly. They show up as a slow drift where a growing share of your pages sit crawled but unindexed, and by the time it’s obvious in traffic reports, months of content have been quietly excluded. Checking this monthly on any site over a few thousand URLs is non-negotiable at this level.
AI Crawler Access
- You’ve checked robots.txt for accidental blocks on GPTBot, PerplexityBot, ClaudeBot, and Google-Extended, since many sites disallow “all bots” rules that sweep these up unintentionally.
- You’ve decided, deliberately, whether you want your content available for AI training and retrieval, rather than inheriting whatever a template or plugin defaulted to.
- Content that you want cited by AI answer engines is structured so a passage can stand on its own — clear claims, defined terms, and self-contained sections.
This is a genuinely new checklist item, and we’ve found more sites blocking these crawlers by accident than on purpose. A blanket robots.txt rule written years ago to keep out scrapers can quietly cut off an entire emerging discovery channel without anyone noticing until a competitor starts showing up in AI answers you’re invisible to.
Frequently Asked Questions
How often should I re-run this checklist?
Quarterly for most sites, and immediately after any major change — a migration, a JavaScript framework switch, a large content push, or a robots.txt edit — since those are exactly the events most likely to introduce the problems this checklist catches.
Do I need log file access to do advanced SEO?
You can do meaningful advanced work without it, but you're working with partial information. Search Console approximates crawl behavior; raw logs show you the actual requests, including bots and patterns Search Console doesn't surface at all.
Is crawl budget really a concern for small sites?
Generally no. Crawl budget becomes a practical constraint once a site has many thousands of URLs, heavy faceted navigation, or a history of generating large volumes of low-value pages. A few hundred well-structured pages rarely hit a real crawl ceiling.
What's the single highest-impact item on this list?
For most sites we audit, it's internal link sculpting, because it's fully within your control, doesn't require new content, and can be implemented in days rather than months.
How do I know if JavaScript rendering is actually hurting me?
Compare raw source HTML to the rendered DOM for your key templates. If critical content or links only exist after rendering, and especially if they depend on a second data fetch, you have a rendering gap worth fixing regardless of how well the site otherwise performs.
Terry has 30+ years in software and SEO. He’s the founder of Salterra Digital Services and SEO Spring Training, host of the Roundtable SEO Mastermind, and lead instructor at SEO University — teaching the exact tactics his team uses on client work.
Continue learning
Ready to master this?
This guide is one lesson from the Advanced SEO Techniques course. Get every lesson, framework and checklist — plus the full 38-course catalog — inside SEO University.
Practitioner-focused training across the full digital marketing stack — from technical SEO to conversion optimization and the AI search era. By Salterra Digital Services, since 2011.