Launch copy (English)
WebTrustEngine R50 is live: evidence-first web governance across ten score domains. 319 working checks, a 2,033-item reference catalog kept deliberately apart, reversible SafeFix packages and a Deploy-Verify loop that proves changes in production.
WebTrustEngine turns website quality from a feeling into a file set. A Review produces an evidenced baseline without touching a file; SafeFix applies low-risk fixes inside a working copy and writes every change to fix and rollback manifests; Build generates a schema-ready static surface; Deploy-Verify pulls live headers and hands teams recipes for independent tools such as PageSpeed, SSL Labs and Search Console.
The release is defined by its number discipline. The 2,033-item figure is a reference catalog — a signal map — and is never presented as automated checks. The working detection layer is 319 checks (80 core, 239 granular), counted from code, with 68 static security patterns, 26 SafeFix generators, 21 runtime verification bridges and 24 external action recipes. The open roadmap is zero: every item sits in its correct artifact class.
Equally firm are the boundaries. WebTrustEngine is not a penetration test and says so on every relevant surface; active testing happens only under written authorisation. It issues no live pass, no ranking or traffic promise, no AI-citation guarantee and no compliance certification — it produces readiness, evidence and classification, and leaves grades to independent tools. The public set ships as a 46-page capability guide, an executive brief, a technical trust note and a one-pager, each published with its SHA-256 digest in the Evidence Hub.
Pricing is not published; scope is settled through the routing on the contact page. Direct press contact details are not published on this site; requests are routed by topic from the contact page.
The full launch narrative186 words
Four documents anchor the launch and ship with SHA-256 digests: a 46-page public capability guide, an executive brief, a technical trust note and a one-pager, each in Turkish and English. A 40-piece bilingual visual system, a 22-size banner set and full logo variants are available for editorial use from the Brand Center, with usage notes attached to every card.
Suggested angles for coverage: the number contract as an honesty mechanism in a market of inflated check counts; the reversible-fix workflow as an alternative to rebuild-first agencies; and the Deploy-Verify stance that a file on disk proves nothing until headers are pulled live. Each angle maps to a documented section, so quotes can be checked against the published guide rather than a spokesperson memory.
Behind the launch sits a sealed production discipline: the public set is versioned, its file inventory is written to a manifest and every file carries a SHA-256 digest published in the Evidence Hub — so any journalist can verify that the document they quote is bit-for-bit the released one. The same discipline governs this website itself, which ships with its own checksum records.
Evidence-first communication templates
Five short copy-ready templates; all pass the claim-safety filter.
Executive email
Subject: Web asset — baseline report ready. Body: The 10-domain score, top three findings and suggested SafeFix scope are attached; no files were changed, and I prepared two options for the decision meeting.
Proposal paragraph
The engagement covers the Review baseline, a SafeFix package within approved scope, a Deploy-Verify pass and the first Monitor comparison. Deliverables ship as an evidence package; no ranking/traffic guarantee is given.
Acceptance note
The delivery ZIP passed Review; findings were classified and acceptance criteria met. Remaining external-action items are assigned in the attached recipe.
Status update
This month: 2 SafeFix runs, 41 files changed (rollback archived), live verification clean; of the external actions, DMARC was applied in the panel — verification attached.
Press line
WebTrustEngine R50 is a web governance engine that evaluates web assets across 10 domains with evidence and verifies change after deployment.
NUMBER CONTRACT
Correct usage in coverage
Claim safety
Please never write '2,033 checks': 2,033 is the reference catalog, the working layer is 319. Guarantees, live-pass wording and pentest claims contradict the product language.
MEDIA ASSETS
12 ready downloads
LOGO USAGE
Short rules
The system
Primary identity: hexagon-shield + check symbol with the "WebTrustEngine" wordmark ("Trust" in gold).
Variants: primary horizontal · primary stacked · symbol-only (gold/white/black/navy) · wordmark-only · compact (WTE) · monochrome (black) · document header · social avatar · app icon · watermark · favicon master.
Colors
- Navy:
#0F1E33(ground) · Panel:#1A2E4A - Gold:
#C9A227(accent) - White / White:
#FFFFFF· Gri / Gray:#AAB3C2
Minimum size
Below these, use the symbol only.
Clear space
50% of the symbol height on all sides.
Background rules
- Dark:
*_dark_bgveyamonochrome_white.
Misuse (don't)
No distortion, recoloring, shadows/glows/gradients, rotation, re-typesetting, or low-contrast placement.
Typography
Placement
- header:
primary_horizontal_dark_bg(SVG). - Footer
- document cover:
document_headerveyaprimary_stacked. - social profile:
social_avatar(400-1080 px). - app icon:
app_icon+ maskable set. - Watermark
Favicon
brand/favicon/: favicon.ico (16+32+48) · favicon-16/32/48 · app
The full usage guide ships in Turkish as the sealed source document; the binding rules above are excerpted in English. When in doubt, the proportions in the downloadable SVG masters are authoritative — scale them, never redraw them.
EDITOR NOTES Five practical notes for editors
The right name
The product name is one word: WebTrustEngine. 'Web Trust Engine' counts as a finding in brand audits.
Expanding R50
On first mention, 'R50 (the engine's 50th release cycle)' is the suggested expansion; plain R50 thereafter.
Quoting numbers
'319 working checks' and 'a 2,033-item reference catalog' are safe patterns; merging them into '2,033 checks' is wrong.
The boundary line
One boundary sentence suffices in coverage: 'The product performs no penetration testing and issues no live pass.'
Image sourcing
Preferring the Brand Center's VA visuals over screenshots guarantees print quality and language accuracy.
Press FAQ
Where do interview/stat requests go?
Through the press lane on the contact page; answers rely only on the published number contract.
Are embargoes or private data offered?
No; what is public is exactly what is available to press.
May I use screenshots?
Yes; visual-system files are available from the Brand Center.
Pricing questions?
Pricing is unpublished; 'settled via contact' is the accurate phrasing.
May the logo/colors be altered?
No; keep the proportions and colors in the usage guide.