Scope. Articles published on Us Weekly + Woman’s World that point back to a Trend Hunter deepener via rel="canonical" (the “purple-tier” pattern per the C&P 2026-05-04 framework). Distinct from O&O sister-market variants (which use the same trend but may share keywords more tightly).
Why this page exists. Strict keyword enforcement designed for O&O variants over-constrains bridge content. Bridges localize the trend for an audience that doesn’t necessarily search for the same keywords as the deepener’s primary audience. The “Bridge stays within trend but doesn’t require exact-keyword match” rule is the editorial governance for that asymmetry.
A bridge article must stay within the deepener’s trend (the topical territory the canonical TH piece is about). It does NOT need to:
A bridge article must:
th-csa provenance tag + the appropriate per-vertical TH Q-tag (th-mind / th-living / th-exp)—see the pre-launch tagging convention frameworkThe recurring concern was: if bridges duplicate the deepener too closely, Google may flag McClatchy under the scaled-content-abuse rubric. The 2026-05-14 bridge-similarity probe (data-headlines/dev-docs/bridge-variant-similarity-2026-05-14.md) measured bridge-cluster headline similarity against an O&O-only cluster baseline:
| Population | n | head_blend mean | body_blend mean |
|---|---|---|---|
| Bridge clusters (O&O + USW/WW) | 32 | 0.370 | 0.225 |
| O&O-only baseline | 33 | 0.376 | 0.227 |
Bridges differentiate at the headline level at parity with O&O variants—there’s no special-case duplication risk. The strict-keyword rule was over-constraining without adding scaled-content protection. Per-cluster similarity gates (the p23 weighting + threshold work) apply to bridges identically to other variants; this rule loosens an enforcement layer that wasn’t doing useful work.
| Check | Default (O&O variants) | Override (bridges) |
|---|---|---|
| Primary keyword in at least one H2 | Required | Not required |
| Primary keyword in headline | Required | Not required (use the bridge-angle phrasing) |
| Front-loaded keyword pattern | Required where applicable | Not required |
| Trend-relevance (the deepener’s trend) | Required | Required (same) |
| Cross-link to deepener | Optional | Required |
rel="canonical" to deepener |
Optional | Required |
th-csa + per-vertical TH Q-tag |
Optional | Required |
The override fires when platform_content_type = bridge per the conflict-register entry on headline.h2_keywords (and downstream rules will inherit similarly).
A bridge article is identified in CSA by:
platform_content_type = bridge (the editorial classification)publication ∈ { us-weekly, womans-world } (the destination outlet)When both selectors apply, the override kicks in. When only publication matches (e.g., a non-bridge piece directly published on USW), the default O&O keyword rules apply.
Retires: the p4-governance next-action “Loosen CSA strict-keyword-rule for bridge variants: stay within trend, no exact-keyword match required. Codify in governance.”—DONE; codified in the register entry on headline.h2_keywords (v1.9.11) + this doc.
Does not retire: the broader cluster-similarity / weighting / threshold work (p23). Bridges still pass through the same per-cluster similarity gate as any other variant; they’re just not held to a separate stricter keyword rule.