Semantic Coherence: Human Rights Watch โ€“ Signal Evidence & AI Readability

Human Rights Watch

(https://hrw.org) ๐Ÿ“ธ Data Snapshot: May 30, 2026
Semantic Coherence โ€” The Lens

Pull the main entities out of the H1, then check whether they actually recur through the body. A page that announces one thing and then talks about another drifts. Headings with no real sentences underneath read as pseudo-substance.

Semantic Coherence Homepage promise vs. Sub-page reality.
7 Impact Weight: 20 / 100
35% Reputation

There is a complete mismatch between the homepage identity implied by the domain and the H1 Error 403 Forbidden that was actually delivered. The primary signal suggests a high-authority global NGO, yet the substance delivered is a server-side permission error from a Varnish cache server. Because no sub-pages were successfully crawled, cross-page messaging consistency cannot be measured, but the drift between brand expectation and delivered evidence is total. The heading hierarchy is incoherent, consisting only of generic technical error codes that fail to communicate any organizational purpose.

Semantic Coherence is read from the heading hierarchy first: what each page announces in its H1 and headings, then whether the body actually delivers on it. Below is the structure the engine mapped, followed by the clean text to check for drift between promise and reality.

๐Ÿ—๏ธ Semantic Structure โ€” heading hierarchy & page identity (the promise the page makes)
HOMEPAGE 403 Forbidden (https://hrw.org)
Title

403 Forbidden

H1 Error 403 Forbidden
H3 Error 54113
๐Ÿ“ The Narrative โ€” clean text per page (homepage promise vs. sub-page reality)
HOMEPAGE ยท THIN (https://hrw.org) 403 Forbidden
[H1] Error 403 Forbidden
Forbidden
[H3] Error 54113
Details: cache-man4149-MAN 1780139561 3942326958
Varnish cache server
124 chars