Most technical SEO checklists you'll find online are written once and never touched again, so half the items are outdated by the time you read them. This one is the actual sequence RankMesh's Technical SEO agents run against a new client site, in the order they run it, because the order matters almost as much as the items themselves.
Start with crawlability, not speed
It's tempting to jump straight to Core Web Vitals because that's what shows up in PageSpeed Insights screenshots. Don't. If Google can't crawl your important pages, a fast page that never gets indexed is worthless. Check these first:
- Does
robots.txtexist, and does it accidentally block anything important? A strayDisallow: /left over from staging happens more often than you'd think. - Does an XML sitemap exist and actually list your real, current pages, not a snapshot from a year-old migration?
- Are there orphan pages with no internal links pointing to them? Google can still find them through the sitemap, but they rank worse without internal link equity.
Fix indexing problems before content problems
Open Google Search Console's Pages report and look at the "why pages aren't indexed" breakdown. The usual suspects:
- Duplicate without user-selected canonical. Common on e-commerce sites where the same product is reachable through three different category paths.
- Crawled, currently not indexed. Often a content quality signal, not a technical one. Google crawled it and decided it wasn't worth indexing.
- Soft 404. A page that returns a 200 status but reads like an error page (empty search results pages are a frequent cause).
Core Web Vitals, with realistic targets
Google's thresholds are LCP under 2.5 seconds, CLS under 0.1, and INP under 200 milliseconds, measured at the 75th percentile of real visits. The biggest wins on most sites:
- Convert the largest above-the-fold image to WebP or AVIF and add explicit width and height attributes to stop layout shift.
- Defer or remove third-party scripts that aren't load-bearing for the page's core function. Chat widgets and review-platform embeds are common offenders.
- Preload (don't lazy-load) the actual LCP element. Lazy-loading it is one of the most common mistakes we see, and it directly hurts the metric it's supposed to help.
Schema markup, in priority order
Not every schema type matters equally. For most sites, the priority order is Organization (homepage), Product or Article (depending on business type), BreadcrumbList, and then anything else. Validate every implementation with Google's Rich Results Test before you consider it done; a typo in JSON-LD fails silently and just doesn't show up anywhere.
Internal linking audit
Run a crawl and look at the click depth of your most important pages. If a page that should be converting customers is five clicks deep from the homepage, that's a structural problem no amount of on-page optimization will fix. Pull your highest-traffic blog posts and make sure they link to the commercial pages they're topically related to.
What we automate versus what still needs a human
RankMesh's agents handle the mechanical parts of this list directly: image compression, schema implementation, broken link fixes, sitemap maintenance. What still benefits from a human pass is judgment-heavy work, like deciding whether a "crawled, not indexed" page is worth improving or worth removing entirely. The checklist doesn't change. Who executes each line does.