EDITORIAL POLICY / CONTROLLED UPDATES
How WTN route updates are reviewed
This policy governs route changes, status wording and corrections while keeping the seven canonical pages useful and semantically distinct.
DestinationWTN route handoff
ActivationVisible click only
Publication2026-11-04
01 / ROUTE UPDATE
Evidence required before the WTN handoff changes
The destination must be confirmed as an exact host and path, applied consistently to every CTA and rechecked on the public site. A release must not introduce an automatic, referrer-dependent or crawler-dependent redirect.
02 / INTENT OWNERSHIP
One leading question per canonical URL
HomepageCurrent WTN market link.
Mirror listCurrent, reserve and retired route roles.
Status journalLatest published route check.
Not loadingSymptom-led connection checklist.
Onion access errorsFailure at the route-to-Tor handoff.
03 / CORRECTIONS
Correct the claim, not only the date
A material correction updates the affected wording, structured data, visible date and related internal links. The site does not preserve inaccurate “live,” “verified” or “working” language merely because it once ranked for a query.
04 / RELEASE GATES
Checks required after publication
- All seven canonical URLs return their intended documents.
- Unknown paths return a genuine 404.
- Human, Bingbot and search-referrer bodies match.
- The WTN route opens only after a visible click.
- Sitemap and IndexNow receive the complete canonical set.
CONTINUE / CURRENT ROUTE
Use the published WTN handoff
The destination opens only after your click and is the same for every visitor.
