WebTrustEngine
TREN
DEEP DIVE

Deploy-Verify

After upload, live headers, redirects, previews and external-tool results are confirmed with evidence.

Producing files is not enough

Seven-step deployment verification flow.
The Deploy-Verify loop: seven steps from upload to the diff report.

File produced ≠ working live. This inequality is the most commonly skipped gap in web work, and one of WebTrustEngine's strongest differentiators stands exactly here. An .htaccess being in the package does not mean hosting reads it; an OG tag being in the HTML does not mean the social platform cache sees it.

The intervening layers are enumerable and predictable: hosting cache, CDN cache, whether .htaccess is actually processed, social-preview caches, browser cache. Deploy-Verify turns each into an evidence step: live header fetch, redirect tracing, metadata/schema comparison, sitemap/robots/llms.txt reachability, social-preview debugger checks.

The external-tool layer is part of the loop: SecurityHeaders and Observatory grade headers; SSL Labs evaluates certificate/protocol; Lighthouse/PageSpeed produce lab metrics; Search Console and Bing Webmaster show indexing. The tools issue these grades; we pull the results and bind them to your report.

Runtime verification bridges

A runtime bridge connects the checks a static file cannot measure exactly to the tools that can. We write every measurement together with the tool that produced it. Offline, the bridge says it requires a live run and writes which tool measures which metric and how; live, it routes to the real measurement.

The bridge universe groups into 53 checks with typical examples: SecurityHeaders (header grade), Mozilla Observatory, SSL Labs (TLS grade), PageSpeed/Lighthouse (lab metrics), CrUX (field CWV), social-preview inspectors, redirect-chain tracing, uptime/response headers, the contrast runtime check, a link checker for broken external links.

The bridge binds each tool grade to your baseline and to the report, so you read a decision table in context instead of a lone score.

  • SecurityHeaders · Observatory · SSL Labs
  • PageSpeed · Lighthouse · CrUX
  • preview inspectors · redirect chain
  • uptime · response headers · contrast · link checker

We bind live measurements to real tools.


The grade stays with the tool; we report it and bind it to your baseline.

You get the bridge list, plus which tool measures which metric and how.

The source of your scores stays transparent.

Baseline-bound measurement fixes the context loss of a lone score.

Working protocol with independent tools

How we run and read the six main tools in the Deploy-Verify pass

SecurityHeaders

Enter the domain, read per-header; we map the gaps to the .htaccess recipe. If the grade is low, check cache/processing first.

Mozilla Observatory

Compare the post-scan suggestions with our header recipe; overlapping advice merges into one policy.

SSL Labs

Full analysis takes 1-2 minutes; read chain, protocol and OCSP rows. Server-side findings go to external recipes.

PageSpeed / Lighthouse


Write lab metrics into the readiness column; field (CrUX) data is a separate column. Never report the two as one score.

Rich Results Test

Test schema-bearing sample URLs; on errors re-audit type-page fit and required fields.

Search Console

After verification submit the sitemap; bind coverage and CWV reports to the Monitor rhythm.

The live verification timeline

Deploy-Verify Timeline

Producing files is not enough; the live effect is proven

  • Uploadfiles + root placement
  • Purge cachehosting + CDN
  • Live headerscompare to expected set
  • Redirect / 404behaviour test
  • Social previewinspector refresh
  • Tool passindependent measurement
  • Diff reportexpected ↔ live

No guarantees — readiness, evidence and verification. Number contract: 348 checks · 80 core + 268 granular.

EXTERNAL TOOLS

Who issues the grade?

Search Console

Indexing and rich-result signals; the sitemap is submitted here.

external verification

PageSpeed / Lighthouse

These issue performance grades; the engine only flags readiness.

external verification

SSL Labs

TLS grade comes from here; the engine classifies configuration readiness.

external verification

SecurityHeaders

Live header grade; the recipe is engine output, the grade is external.

external verification

Rich Results

Live confirmation of schema eligibility.

external verification

CDN / DNS

Cache and record layers; handled via external action recipes.

external verification
Six-link deployment verification chain.
The evidence chain: six links from the baseline record to the diff report.
THE LAYERS Hosting, DNS and CDN: three layers a file cannot see

A file root can be flawless and the answer reaching a visitor is still shaped by three layers. Hosting processes — or flattens — your headers; DNS decides which server your name resolves to; a CDN inserts its own cache and sometimes its own headers in between. The distance between 'works on my machine' and 'works in production' is exactly these three layers.

Deploy-Verify closes that distance with two instruments: runtime bridges pull the real live answer and compare it with the file expectation, while external action recipes describe the panel work — cache purge, record update, header rule — step by step. No step enters a panel on your behalf; it hands you the recipe and asks for the evidence.

THE HYGIENE PAIR sitemap and robots: small files, large consequences

The sitemap tells a search engine 'this is my inventory'; robots says 'look here, not there'. Inconsistency between the two — a mapped address blocked in robots, or an important page missing from the map — silently burns crawl budget. Two of the first post-deploy bridges read this pair live: is the file reachable, does its content match the published addresses one-to-one, has Search Console been notified.

NO LIVE PASS Why no 'live pass' is ever issued

The engine reports the evidence it pulls after publication, but under no condition stamps 'the site passed live'. The reason is principled: live grades drift with time, geography and intermediate layers; the header returned today can vanish tomorrow behind a CDN toggle. A permanent 'passed' would be a promise falsifiable the next morning.

Instead we deliver a pair: time-stamped live pulls ('at this date, this address returned this answer') and independent-tool recipes. The grade belongs to SSL Labs, PageSpeed or SecurityHeaders; the engine paves the road to that grade and proves the road was paved.

90 DAYS The first 90 days of measurement

What we measure when, and with which evidence, in the first quarter

What we measure when, and with which evidence, in the first quarter — 1
PeriodMeasuredEvidence
Day 0-15Baseline score + finding classificationReview report
Day 15-30Internal score delta after SafeFixbefore/after + rollback
Day 30-45Live header/preview confirmationDeploy-Verify diff report
Day 45-60Independent tool-pass resultsSecurityHeaders/SSL Labs/PageSpeed bridges
Day 60-75External-action application statusrecipe + panel verification
Day 75-90First Monitor comparisonperiodic diff + drift list

After ninety days you hold four evidence files and the loop is the organisation's rhythm; what follows is a decision of scale and depth.

CONTENT POLICY

The local policy check before deployment

Alongside the Deploy-Verify pass, a separate local step never touches the live site: the packaged static source is measured against written content and brand rules. A dedicated local command does that, and the operator calls it when they want it. The rule set, the site identity and the data source are supplied explicitly on every run, and every run writes to a new output path.

There are five rule kinds and each is measured on its own: required text, forbidden text, required element match, required attribute and required link. Element match and attribute fill are not the same rule. The element rule asks only whether the selector matched anything. The attribute rule adds a second condition on top: every matched node must carry that attribute with a non-empty value.

If the selector matches nothing, the attribute rule produces no result — the record stays 'unknown' and is never counted as passed. The forbidden-text rule behaves the same way, because a missing scope cannot prove that the text is absent.

Text rules search the document text for a case-insensitive match. They skip comments, script, style and template content; CSS-hidden text still counts. A link rule looks inside the matched scope for a link address exactly equal to the given one. Every rule carries a path scope, a severity and an owning team, and every failing page + rule record becomes a task with a stable identifier.

Three budgets run alongside: the failure count, the unknown count and the regression count. In enforcing mode a 'stop' result ends the command with an error code, and it still writes the evidence file.

The scope is narrow and the evidence states it: a local, static, UTF-8 HTML export. At most 100 rules and 1000 pages; 2 MiB per file, 64 MiB in total. Exceeding a limit, broken encoding, a symbolic link and a rule that matched no page are coverage gaps: they add to the unknown count and the measurement state is marked 'partial' rather than complete. The command scans no live address; a snapshot taken from a live address is rejected here, because response eligibility belongs to the authorized scan workflow. A live address is read only in the operator-triggered authorized read-only URL mode.

Scope: a content and brand rule measurement on the static source. Legal compliance, brand sign-off and publication stay separate decisions. The presence of HTML or CSS does not stand in for a visibility test or a browser-accessibility test, and rules run neither regular expressions nor code. The output is an operational evidence file, not an authorized WebTrustEngine report. This rule inventory is not added to the check inventory (348 checks); the two are separate inventories and are never summed.

The rules stay local; role, SSO and multi-tenant management stay on the service and operations side.

FROM THE FIELD

What Deploy-Verify looks like in practice

Deploy-Verify exists because the most common failure in web work is silent: files are produced, uploaded, celebrated — and the live site keeps serving the old cache, or the new headers never reach the browser, or DNS points somewhere subtly wrong. A file on disk proves nothing. Proof is a live pull.

Runtime bridges are small, repeatable checks that fetch the live URL and compare what production actually returns against what Build prepared — headers, redirects, canonical, sitemap reachability. External action recipes are step-by-step instructions for the platforms only you control: purging the CDN, submitting the sitemap in Search Console, re-scraping the OG card, reading an SSL Labs report. The engine never performs those actions in your accounts; it hands you the exact sequence and the record to compare against.


Boundary: Deploy-Verify is not a real-time security operations centre; it is a periodic evidence-verification rhythm. Live scores are produced by independent tools; the engine only bridges them.

FIRST 48 HOURS

The post-launch verification walk

Within the first hour: purge hosting and CDN caches, then pull live headers — is HTTPS redirecting, is HSTS present, are the security headers actually returned? In the same session open robots.txt, sitemap.xml and llms.txt one by one in a browser; existing on disk is irrelevant, the live URL must answer. For this site, also verify the published security reporting record at /.well-known/security.txt.

Within the first day: submit the sitemap in Search Console and run sample pages through the Rich Results test; refresh the OG card in the social debuggers. Day two is measurement: PageSpeed and SSL Labs run, and their outputs enter the evidence folder with dates and screenshots. The engine's contribution is the recipe that orders the walk and the static readiness record you compare against. The grade comes from outside, which is exactly why it can be believed.

VERIFIED LOCAL CLOSURE

A local retest does not stand in for live confirmation

A content-policy finding closes one way only: the same rule is remeasured against changed source and passes this time. The engine checks both fingerprints together — the rule fingerprint identical, the source fingerprint different. Edit the rule text and no closure is written for the old finding; the old finding stays open as 'not retested', and the edited rule is measured from the start as a new record.

A finding that leaves scope stays open. If the page is deleted, if the path scope no longer matches it, or if the file is skipped over an encoding or size limit, the record stays 'not retested': it is written into the unknown budget and, as long as the previous run's evidence file is supplied again, carried into the next run as well. Absence from the next report is not a closure. Open findings carry across runs for as long as the scope gap repeats.

One fixed example is not the closure of the group. Every finding is tracked as a page + rule pair under its own identifier; closure is written for that pair, not for the rule. The same rule's records on other pages wait for their own retests. The reverse direction is recorded separately: a rule that was passing and then fails is marked as a regression and draws on its own budget.

The closure here is a statement about the local static source. The engine touches no live site; the evidence writes this as 'no change was made on the live site'. A rule closed locally is not yet confirmed live; cache purge, live header comparison, preview refresh and the independent tool pass close that gap.

'Closed locally, awaiting publication' and 'not measured yet' stay separate records. Retesting is bounded by static content policies. Continuous monitoring, external notification and automatic publishing are outside this scope.

Quick answers

Why needed?

A file existing doesn't prove live effect.

Full answer in the FAQ

Who measures?

Independent tools; the engine bridges.

Full answer in the FAQ

After GoDaddy?

A 7-step flow: upload→purge→fetch→test→debug→tools→report.

Full answer in the FAQ

Real-time?
Output?

Diff report + tool-result bridges.

Full answer in the FAQ

Next step

After upload, live headers, redirects, previews and external-tool results are confirmed with evidence.