Entrovix AI

Technical SEO checklist: 50 checks that are worth running

Fifty checks grouped by what they protect, each with how to verify it and how much it actually matters. Not everything on this list deserves your afternoon.

Entrovix AIAug 12, 2026 14 min read

Technical SEO checklists have a habit of treating every item as equally urgent, which is how people end up adding structured data to a site that has a noindex tag in production.

These fifty are grouped by the stage they protect: reaching your pages, keeping them, understanding them, serving them, and noticing when something breaks. Each one says how much it matters, and several say that the honest answer is not very much.

How to read the priority column

RatingMeans
CriticalBroken, this removes pages from search. Check it today.
HighA measurable loss. Worth fixing this month.
MediumA genuine improvement with a modest return.
LowCorrect to do, rarely the reason anything changed.

1. Crawling: can Google reach the pages?

Nine checks. If any of the critical ones fail, nothing further down this page will help you.

#CheckHow to verifyPriority
1robots.txt exists and returns 200Visit /robots.txt directly. A 500 error can be treated as a blockCritical
2No Disallow: / left over from stagingRead the file. This single line removes a whole siteCritical
3CSS and JavaScript are not blockedGoogle needs them to render the page as a user sees itHigh
4An XML sitemap existsVisit /sitemap.xml, and check Search Console has itHigh
5The sitemap is referenced in robots.txtA Sitemap: line with an absolute URLMedium
6The sitemap lists only indexable 200 URLsNo redirects, no 404s, no noindexed pagesHigh
7Correct status codesMissing pages return 404 or 410, not a 200 with an error message on itHigh
8No redirect chainsEach redirect should reach its destination in one hopMedium
9No redirect loopsA loop makes the page unreachable entirelyCritical

2. Indexing: will Google keep them?

Eight checks. This is where the expensive, invisible mistakes live, because a page can look perfect and still be excluded by one attribute.

#CheckHow to verifyPriority
10No stray noindex in productionView source, search for noindexCritical
11No X-Robots-Tag noindex headerCheck response headers, not the HTML. Invisible in the sourceCritical
12Each page has a self-referencing canonicalIt should name its own URLHigh
13Canonicals are absolute URLsRelative canonicals get misinterpretedMedium
14Exactly one canonical per pageTwo canonicals means Google ignores bothHigh
15Parameter URLs are not generating duplicatesFilters and sorts creating thousands of URLsHigh
16Pagination is handled coherentlyPage 2 should not canonicalise to page 1Medium
17Search Console Pages report reviewedCompare indexed against not-indexed and read the reasonsCritical

3. URLs and architecture

Eight checks. Mostly one-off decisions that are painful to change later and cheap to get right at the start.

#CheckHow to verifyPriority
18One canonical version of the sitehttp, https, www and non-www should all redirect to oneCritical
19HTTPS with a valid certificateCheck the expiry date, and that renewal is automatedCritical
20No mixed contentAn https page loading http assetsHigh
21Consistent trailing-slash policyBoth versions resolving separately is duplicationMedium
22Readable URLsLowercase, hyphenated, no session identifiersMedium
23Important pages within three clicks of homeDepth correlates with how often a page is crawledMedium
24No orphan pagesA page linked from nowhere is barely a pageHigh
25Breadcrumbs where a hierarchy genuinely existsDo not invent one for markup's sakeLow

4. On-page structure

Nine checks. This is the part every audit tool is good at, which is why it tends to be over-represented in reports and over-weighted in effort.

#CheckHow to verifyPriority
26Every page has a unique titleDuplicates across a site are a common template faultHigh
27Titles front-load the meaningful wordsRoughly 60 characters show; put the point firstHigh
28Meta descriptions present and distinctNot a ranking factor. It is the advertisement for the clickMedium
29One H1 per pageMatching what the page is actually aboutMedium
30Heading levels are not skippedH2 to H4 with no H3 is a structure problem and an accessibility oneMedium
31Internal anchor text describes the destinationClick here tells a reader and a crawler nothingMedium
32Images have meaningful alt textDescribe the image. Decorative images take an empty altMedium
33Images have width and height attributesThis is what prevents layout shiftHigh
34The page declares its languageA lang attribute on the html elementLow

5. Rendering and performance

Eight checks. Measure the field data rather than the lab score. Core Web Vitals are assessed from real visits at the 75th percentile over a rolling 28 days, which is why a good PageSpeed score and a failing metric can coexist.

#CheckHow to verifyPriority
35Content is in the server HTMLCompare view-source with the rendered pageHigh
36Largest Contentful Paint at 2.5s or lessField data in Search Console, not the lab scoreHigh
37Interaction to Next Paint at 200ms or lessUsually third-party JavaScript when it failsMedium
38Cumulative Layout Shift at 0.1 or lessAlmost always images or ads without reserved spaceHigh
39Images sized to their display sizeA 4000px image in a 600px column is the usual faultHigh
40Modern image formatsWebP or AVIF, typically a quarter to a third smallerMedium
41font-display set on web fontsOtherwise text stays invisible while the font loadsMedium
42Cache headers on static assetsRepeat visits should not re-download unchanged filesMedium

If several of these fail at once, the cause is usually one thing rather than eight. Why your website is slow works through the four underlying causes and which fix belongs to which.

6. Structured data and sharing

Six checks, and one deletion. Structured data is worth adding where it describes something genuinely on the page, and worth ignoring where the feature it targeted no longer exists.

#CheckHow to verifyPriority
43Structured data validatesGoogle's Rich Results Test, or the Schema Markup ValidatorMedium
44Markup matches the visible contentMarking up a rating that is not on the page is a policy violationHigh
45Organization and WebSite markup, onceSite-wide, not repeated per page with different valuesLow
46Breadcrumb markup where breadcrumbs existOne of the few types that still produces a visible resultLow
47Open Graph tags for shared linksTitle, description and imageMedium
48og:image exists and is reachable1200x630 is the size everything is designed aroundMedium

The deletion: FAQ markup added for rich results is no longer doing that job. Google stopped showing FAQ rich results in May 2026 and has withdrawn support for the feature. The markup remains valid and harmless, so there is no urgency to remove it, but adding it now for search appearance is work with no destination. HowTo rich results went the same way back in 2023.

7. Security and monitoring

#CheckHow to verifyPriority
49Security response headers presentHSTS, X-Content-Type-Options, a Content-Security-PolicyMedium
50Search Console connected and actually readMonthly: indexing errors, manual actions, sudden dropsCritical

What is deliberately not on this list

Four things that appear on most checklists and have not earned their place.

  • Keyword density. There is no target figure. Writing to hit one makes the page worse.
  • The meta keywords tag. Unused by Google for well over a decade.
  • A perfect PageSpeed score. The lab number is a diagnostic, not the thing being assessed.
  • Submitting your site to search engines. Google finds sites by following links; paid submission services sell nothing.

A sensible cadence

WhenWhat to run
MonthlyItem 50, plus a glance at indexed page count and any new 404s
QuarterlySections 1 and 2 in full
AnnuallyThe whole list
After any deploy that touches URLsSections 1, 2 and 3, immediately

That last row is the one that matters most. Redesigns and migrations cause more sudden traffic losses than algorithm updates do, and the cause is almost always an unfinished redirect map. How to run an SEO audit covers the full process, and if you would rather work from symptoms than from a list, start with why a page is not ranking.

Need this built rather than explained?

We design and build websites, applications and automation — with a written proposal before anyone starts.

Browse Free Tools