Technical Infrastructure and Core Web Vitals: pillar one of SQA-200

What the technical pillar covers in SQA-200

The technical pillar covers the layer beneath every other pillar: server response, resource delivery, rendering, indexability, mobile layout and transport security. Its scope stops where editorial judgment begins. Nothing in these forty checkpoints asks whether a page is good; they ask only whether a machine can obtain it in full and a reader can use it on a phone.

That narrow scope is deliberate. A technical checkpoint has to be answerable by measurement rather than by opinion, because the framework's promise is that two auditors scoring the same site reach the same number. Every one of the forty items therefore names a threshold, a header, a tag or a file, and the pass condition is written so that the answer is yes or no.

Why the technical pillar is audited first

The technical pillar is audited first because the framework's core axiom says a single technical or entity bottleneck creates lead leakage that compounds across everything downstream. Points earned in later pillars are not independent of this one. An excellent answer-first page that a crawler renders without its body text scores thirty points in pillar four and delivers nothing.

This ordering is also the reason the thirty-day roadmap spends its entire first sprint here. Restructuring content on an infrastructure that drops requests, blocks resources or serves a blank document object model to a bot is work whose result nobody can measure, and unmeasurable work is exactly what the framework exists to eliminate.

The three Core Web Vitals thresholds and what each one measures

Three checkpoints in this pillar carry the Core Web Vitals thresholds, and they measure three different things that teams routinely collapse into the word speed. Largest Contentful Paint measures how long the largest visible element takes to render and passes under 2.5 seconds. Interaction to Next Paint measures how long the page takes to respond visually after an interaction and passes under 200 milliseconds.

Cumulative Layout Shift measures unexpected movement of content during load and passes under 0.1. The distinction matters when remediating: Largest Contentful Paint is usually an asset and server problem, Interaction to Next Paint is almost always a main-thread JavaScript problem, and Cumulative Layout Shift is nearly always missing width and height attributes on images and embeds. One fix rarely moves more than one of the three.

Crawl budget and the checkpoints that protect it

Crawl budget is the finite attention a search engine spends on a site, and roughly a third of the technical checkpoints exist to stop that attention being wasted. Redirect chains, soft 404 responses, parameter noise, unfiltered internal search results and staging paths all consume crawl budget without producing an indexable URL, and none of them are visible to a reader.

The checkpoints that protect crawl budget work as a set rather than individually. A clean sitemap listing only canonical URLs that return 200, a robots file that blocks the known waste, self-referencing canonical tags and resolved redirect chains together tell the crawler where the site ends. Passing three of those four still leaves the crawler a route into the part that was supposed to be closed.

The forty technical checkpoints

Below are the forty itemized checkpoints of pillar one, each carrying exactly one point. The weighting is deliberately flat here and in no other pillar: at the infrastructure layer the framework treats a broken image and an unresolved redirect chain as equally binary, because both are either present or absent and neither requires a judgment call to score.

How to score the technical pillar

Scoring the technical pillar is addition. Each of the forty checkpoints is worth one point, awarded only when the written verification standard is met across the site rather than on a sample page, and the pillar total is the count of items passed. A partial pass is not available, which is the point of writing the standard as a threshold.

Two scoring rules prevent the most common inflation. First, a checkpoint that applies to every indexable page is scored against every indexable page, so alt text present on the homepage and absent on four hundred articles fails. Second, a checkpoint the site cannot yet be measured against is scored zero rather than skipped, because a skipped item silently raises the percentage of everything else.

What the technical pillar hands to Entity Verification

The technical pillar hands the next pillar a site a machine can actually read, which is the precondition for declaring anything about identity. Structured data that a crawler never fetches, or that sits in a document object model only a browser assembles, declares nothing at all. Pillar two's twenty checkpoints all assume the markup they describe is reachable in the served HTML.

Continue to pillar two, Entity Verification and Semantic Schema, which turns a readable site into a named and corroborated entity.