Date: 2026-08-08 22:59 Summary: Detailed explanation of one-URL multi-scenario long-tail coverage vs Omni-style URL splits.
[question] 一页吃长尾场景，不拆页：这个详细说明
[try to solve] “One page eats long-tail” means one canonical URL per calculation intent. Near-synonyms and scenario variants go into Use cases, FAQ, unit toggles, parameter options, and Examples on that page—not a thin page per query.
Why: Google doorway/scaled content, Bing duplicate and crawl waste; authority stays concentrated; maintenance stays manageable. Omni counterexamples to merge here: bmi-men/women/kids, percentage-increase/decrease, 90/95/99-CI, 16:9/4:3 aspect-ratio, state-tax / auto-loan EMI splits.
On-page layout: primary formula + calculator (above the fold) → Rules/boundary table → numeric Example → Use cases (3+ real scenarios: up/down %, male/female, confidence levels, etc.) → FAQ (long-tail phrasings) → YMYL disclaimer/References. Slug/title lock one primary intent; secondary terms go in description/FAQ, never a second URL.
Split-page bar (all required): materially different function/algorithm/parameters; bodies still clearly different after stripping titles; each meets information-gain bar; not a swap-word matrix. Examples: BMI vs BMR/TDEE may split; male vs female BMI must not; compound interest vs ROI may split; percentage increase/decrease must not.
Visible copy must not say “we don’t split pages / doorway” SEO meta-narration. Traffic comes from one page matching related queries via snippet/understanding signals—share from scenario coverage and CTR, not page count.
Existing seeds: percentage-change FAQ/usecases already cover up/down and percentage points; BMI FAQ already mentions athletes/children/pregnancy—can strengthen long-tail Qs such as “same formula for men and women” while keeping a single URL.
[actions]
- No code changes