Myth-Busting Posts: Complete Content Specification
Build a myth-busting post that states each belief fairly, tests every claim with proportionate evidence, and replaces misinformation without amplifying it.
A myth-busting post tests a recognizable belief without caricaturing it. Its contract is accurate claim, evidence, calibrated verdict, and replacement model. Without a better explanation, the original belief remains available to return.
State the strongest version that people actually believe, including its scope and conditions. Do not automatically repeat a dangerous or obscure claim in the title, headings, summary, and social copy: familiarity can make it feel plausible. First decide whether correction creates more value than further exposure.
This format belongs in the SEO post types system when awareness depends on correcting the reader’s mental model rather than teaching a procedure or listing errors.
Questions it answers
The reader is trying to resolve uncertainty rather than confirm a predetermined “false” label:
- “Is this claim true, false, exaggerated, outdated, or true only under specific conditions?”
- “What is the most accurate version of the claim?”
- “What evidence supports the verdict, and how strong is that evidence?”
- “Why did the belief become plausible or popular?”
- “What should I believe or do instead?”
Give the verdict and its boundary immediately. “This is a myth” is usually too crude. A useful opening is: “Publishing more pages does not automatically create more organic traffic. Additional pages help only when they satisfy distinct demand, add useful information, and can be discovered and maintained.” This corrects the overclaim while preserving the reasonable intuition behind it.
When to use this post type
Use myth-busting when a documented belief changes understanding, choice, or behavior, and sufficient evidence exists to test it. Find the belief in query research, conversations, internal search, surveys, communities, or AI answers; editorial annoyance is not prevalence evidence.
Choose the format only after passing three gates:
- Prevalence: the audience already encounters it.
- Consequence: it can cause confusion, waste, risk, or a poor decision.
- Evidence: suitable sources can test its scope and stakes.
Use a confusable sibling when the reader’s job is different:
| Post type | Choose it when the reader needs | Core answer shape | Boundary from myth-busting |
|---|---|---|---|
| Myth-busting | A belief evaluated and replaced | Fair claim → evidence → verdict → better model | This is the reference type |
| mistakes-to-avoid post | Several preventable behaviors corrected | Tempting reason → cost → correction | The unit is an action or omission, not a belief |
| what-is-X page | A neutral definition and broad explanation | Direct definition → mechanism → relevance → examples | It teaches the concept without organizing the page around a disputed claim |
| beginner introduction | A safe first model of an unfamiliar subject | Essential concepts → first application → next learning step | Misconceptions may be supporting notes, not the spine |
| ultimate guide | Complete coverage of a broad subject | Mental model → major subtopics → application → deeper routes | Myth-busting may be one chapter, not the whole information architecture |
Do not manufacture conflict around wording, attack a competitor, or turn nuance into clickbait. If credible evidence supports several interpretations, frame the article as a question and publish a conditional verdict.
Best for these business types
This ranking reflects recurring misconceptions, credible evidence access, and the value of a better mental model. Demand and review capacity still decide whether to publish.
- Media publishers and affiliates . Contested claims, outdated advice, and purchasing assumptions reward editorial synthesis. Sources must be transparent and separate from monetization.
- B2B services . Specialists can correct beliefs about strategy, implementation, procurement, and measurement without implying that hiring the author is the only solution.
- SaaS . Category, workflow, security, and feature misconceptions fit when evidence remains useful outside the pitch.
- Healthcare and pharmacy . The correction can matter greatly, but so do amplification risk, authoritative evidence, clinical review, and care boundaries.
- Finance, fintech, and insurance . Cost, protection, eligibility, return, and risk claims require jurisdiction, current terms, uncertainty, and an education-versus-advice boundary.
- Ecommerce . Material, care, compatibility, ingredient, and performance myths can educate buyers; never invent one to favor stocked products.
Search intent
Search intent is the outcome a searcher wants from a query. For this post type, the intent is awareness-stage verification: the reader has encountered a claim and wants a credible answer before forming or revising an opinion.
A search engine results page may contain direct answers, fact checks, forums, videos, institutional explainers, and uncritical repetition. The mix reveals whether the query expects a binary answer, context, recent evidence, or expert consensus; it does not decide the verdict.
AI answers compress nuance. Make each claim self-contained: subject, condition, verdict, evidence, and date where freshness matters. Keep limitations beside the claim; a source list cannot repair a sentence whose qualification disappears in extraction.
Record the query, market, language, device, date, signed-in state, and interface. One capture documents an observed result shape; it does not establish permanent intent or consensus.
Page structure
Target 1,900–3,000 words for one substantial myth or three to seven related misconceptions. Evidence complexity controls length.
| Section | Word range | Purpose | Status |
|---|---|---|---|
| Hero and direct verdict | 70–120 | State the accurate conclusion, audience, scope, and most important qualification without suspense | Required |
| Claim and steelman | 100–180 | Reproduce the belief fairly, define its terms, and explain the reasonable observation that makes it plausible | Required |
| Amplification-risk decision | 60–140 | Record why public correction is warranted and where the myth may safely appear | Required internally; visible when the risk is material |
| Evidence standard and method | 120–220 | Define the claim units, source hierarchy, date range, exclusions, and verdict scale before presenting findings | Required |
| Evidence by claim | 500–900 | Test each factual component with matched evidence, limitations, and conflicting findings | Required |
| Verdict | 100–180 | Label the claim false, misleading, outdated, unproven, context-dependent, or supported, then explain the boundary | Required |
| Replacement model | 220–420 | Give the reader a more accurate rule, mechanism, example, and decision test | Required |
| Practical implications | 150–280 | Explain what changes in behavior or choice and what does not follow from the verdict | Conditional |
| Sources and review record | 120–240 | Make every decisive claim traceable and state author, reviewer, dates, and known gaps | Required |
| FAQ | 250–450 | Resolve residual scope and evidence questions without repeating the main verdict | Required; 5–7 questions |
| CTA | 40–90 | Offer one awareness-stage verification or monitoring action | Required |
For a multi-myth page, repeat claim → evidence → verdict → replacement model for every entry. Do not place all myths first and all corrections later; extraction, scanning, and memory can separate the false claim from its correction.
Verdict vocabulary
Use a defined scale so editorial confidence does not become a binary performance:
| Verdict | Use when | Required wording behavior |
|---|---|---|
| False | Reliable evidence directly contradicts the bounded claim | State what the evidence contradicts and avoid extending the verdict beyond that boundary |
| Misleading | A true observation is used to support an overbroad or wrong conclusion | Preserve the true part, then identify the unsupported leap |
| Outdated | The claim described an earlier state but no longer matches current rules, products, or evidence | State when or under which version it was accurate and what changed |
| Unproven | Available evidence cannot establish the claim | Say “not established,” not “proven false” |
| Context-dependent | The answer changes by audience, condition, implementation, or definition | Name the conditions that change the answer |
| Supported | The belief survives the test within the stated scope | Publish that result even when it weakens the planned headline |
Required elements
| Element | Status | Exact position | Why it belongs there |
|---|---|---|---|
| Direct answer block | Always | First visible content | Readers and answer systems need the calibrated verdict before repetition of the misconception |
| Quick overview and table of contents | Conditional | After the method, before the first evidence section | Use it for several myths or long evidence chains so readers can move directly to a claim |
| Comparison table | Conditional | After the method or before the replacement model | Compare claim, verdict, evidence strength, and accurate replacement without reducing nuance to icons alone |
| Warning box | Conditional | Before repeating or acting on a high-risk claim | Change behavior before health, safety, financial, legal, or reputational harm; do not use it as decoration |
| Sources block | Always | After the analysis, before related content | Myth-busting makes an evidentiary promise, so every decisive claim needs a traceable source and review date |
| Related content block | Always | After sources, before FAQ | Route the corrected reader to a neutral definition, procedure, or deeper model without interrupting the evidence chain |
| FAQ structure | Always | After related content, before CTA | Address remaining boundaries, uncertainty, and application questions in standalone answers |
| CTA block | Always | Final content block | Offer one proportionate next action after the reader understands the verdict |
Frontmatter
Follow the frontmatter specification
and set entity = "post-type-myth-busting". It identifies the document shape; add a subject entity through the approved model without replacing this identity.
Use schemaType = "Article" by default. FAQPage requires matching visible questions and [[faq]] records plus current policy support. ClaimReview requires a formal fact-checking process, eligible publisher, visible method, accountable reviewer, identified claim and verdict, and compatible implementation.
Also include title, seoTitle, description, keywords, type, date, lastReviewed, the playbook fields, elements, and businessTypes. Record the evidence cutoff, reviewer, and verdict scale. Update lastReviewed when sources or rules change.
Full example
The following skeleton is copy-pasteable. It keeps the accurate conclusion ahead of the repeated myth and makes claim-level evidence, uncertainty, and the replacement model mandatory.
# Does publishing more website pages always create more organic traffic?
No. Publishing more pages creates more potential entry points only when those pages satisfy distinct demand, add useful information, can be discovered, and remain accurate. Near-duplicate or unsupported pages can increase maintenance and divide attention without helping a new reader.
## The claim, stated fairly
**Claim:** “A site that publishes more indexable pages will receive more organic traffic.”
Every useful page can match previously unanswered queries. The overreach is treating page count as the cause while omitting demand, value, discovery, authority, and maintenance.
## Why this claim is worth correcting
[Record representative queries, customer wording, internal-search themes, conversations, and AI answers. Explain why correction outweighs repetition.]
## How we tested it
- **Claim units:** more indexable pages; automatic traffic increase; all other conditions omitted.
- **Evidence window:** [start date] to [cutoff date].
- **Preferred evidence:** direct documentation, inspectable data, and studies whose methods match the claim.
- **Exclusions:** anecdotes without comparable demand, quality, discovery, or time windows.
- **Verdict scale:** false, misleading, outdated, unproven, context-dependent, or supported.
## Evidence
### 1. A page must answer distinct demand
[Present the strongest evidence, its limits, and credible conflicts. Keep the citation beside the claim.]
### 2. Discovery and indexing are not the same as selection
[Separate technical eligibility from ranking or citation. Define every measured state and preserve the source's scope.]
### 3. Additional pages create maintenance and overlap decisions
[Show which costs or conflicts can be observed without implying that every additional page is harmful.]
## Verdict: misleading
The claim preserves one reasonable idea—useful new coverage can attract demand—but removes the conditions that make a page useful and discoverable. Page count alone is not a reliable publishing objective.
## Use this model instead
Publish a new page when it serves a distinct reader question or decision, has a clear relationship to existing pages, contributes information worth selecting, and has an owner for review. Before publication, ask:
1. What demand or user need is not adequately served now?
2. Why should this be a separate page rather than a section on an existing page?
3. What evidence, example, or utility makes it meaningfully distinct?
4. How will users and crawlers discover it?
5. Who will update, consolidate, redirect, or retire it when conditions change?
## What changes in practice
[Name the decision the corrected model changes, what teams should stop doing, what they should continue doing, and what evidence would change the verdict.]
## Sources and review record
[For every source: author, title, date, URL, access date, supported claim, method, and limitation. Name the reviewer and next review trigger.]
## FAQ
[Add five to seven residual questions about scope, exceptions, evidence, and application. Do not restate the headline six ways.]
## Verify the belief in your own context
[Offer one awareness-stage action: inspect the relevant data, compare the claim with current authoritative guidance, or track a representative question over time.]
Bracketed fields are production instructions, not optional filler. Replace each with topic-specific research before publication. If a field cannot be completed, narrow the claim or withhold the verdict.
Design gallery
Every variant must keep the correction visually attached to the claim and must show evidence quality with words, not color alone.
Do not place the myth in a large decorative quote while shrinking the correction beneath it. Visual prominence changes what a scanning reader remembers.
Quality checklist
A publishable page can survive a skeptical reader checking the claim, sources, qualification, and replacement model independently.
- The belief is documented in audience or query evidence; the page does not invent a strawman.
- The claim is quoted or paraphrased with its real scope, terms, and strongest reasonable interpretation.
- The editor has assessed whether publication will correct an existing belief or amplify an obscure harmful one.
- The accurate verdict appears before or immediately beside the first prominent repetition of the myth.
- Each claim unit has evidence proportionate to its consequence, specificity, geography, and freshness.
- Direct and authoritative sources are preferred, with secondary synthesis used for context.
- Conflicts, uncertainty, definitions, sample limits, and dates remain beside the qualified conclusion.
- “Unproven” is not rewritten as “false,” and correlation is not rewritten as causation.
- The verdict uses the declared scale and can be narrower than the headline premise.
- The replacement model explains why the myth felt plausible and gives a rule the reader can apply.
- High-stakes content has appropriate specialist review.
- Sources map to claims and include a review date and update trigger.
- FAQ and CTA add boundary cases and a proportionate next action.
Common mistakes
The defining failure is strawmanning: weakening or stripping conditions from a belief so it is easy to defeat. A reasonable believer should recognize the stated claim before evidence appears.
Other failures are specific to this type:
- Amplifying an obscure myth. Repeating a harmful claim across titles, metadata, images, and social posts can spread it farther than the correction. Confirm prevalence and lead with accuracy.
- Using a suspense reveal. Hiding the verdict increases unsupported exposure and weakens extraction. Give the calibrated answer first.
- Calling nuance a myth. A statement can be directionally true but conditional. Preserve the true part and label the overreach rather than declaring the whole idea false.
- Treating missing proof as disproof. “We found no evidence” can mean the research is absent, inaccessible, underpowered, or poorly matched. Use “unproven” unless evidence directly contradicts the claim.
- Counting sources instead of weighing them. Derivative articles repeating one study are not independent evidence. Trace the origin and assess method, relevance, date, and independence.
- Cherry-picking the weakest version. Test the claim real readers encounter and include credible contrary evidence. If a stronger version survives, revise the verdict.
- Overextending a study. Evidence from one population, product version, country, or time window cannot silently support a universal conclusion.
- Correcting without replacing. A verdict that only says “wrong” leaves a gap. Explain the mechanism, boundary, practical rule, and example that should take the myth’s place.
- Using ridicule as authority. Mocking believers hides why the claim was plausible and discourages honest questions. Correct the information, not the reader’s identity.
- Turning evidence into a sales trap. A product may be the next step, never proof of the verdict.
- Letting the verdict age. Policies, evidence, and products change. Define review triggers and update the record.
Internal linking
Link out when another page owns a neutral definition, complete process, or broader learning path. Keep the evidence-led verdict on this page.
- A mistakes-to-avoid page may explain a behavior caused by the belief, but it owns tempting reason, cost, and correction—not the full fact-check.
- A what-is-X page may acknowledge a misconception after defining the concept, but it owns the neutral explanation rather than a disputed-claim narrative.
- A beginner introduction may correct one high-frequency misunderstanding to protect the first mental model, but it should not reproduce every evidence section.
- An ultimate guide may summarize the verdict and link to this page; it owns comprehensive topic coverage, not repeated myth analysis.
- A sources element defines evidence presentation, while this page owns why each source supports or limits a specific verdict.
Do not create separate “myth,” “misconception,” “truth about,” and “debunked” pages for the same claim and audience. Split only when evidence, audience, or replacement model materially differs.
How to measure results
Measure discovery for verification questions, citation selection, answer accuracy, engaged reading, and the next action. Follow how we measure results to define the baseline, comparison window, segments, and limits.
In AmICited, use Prompt Tracking for the belief, its question form, and its replacement. Record which engines repeat it, their qualifications and sources, and whether your brand appears. After publication, inspect wording and citations in open Prompt Tracking . The strongest editorial signal is an answer that preserves the correct verdict and boundary.
On-site, examine movement from verdict to evidence, source use, replacement-model reading, and the final action. A click, ranking change, or changed AI answer does not prove belief change; look for consistent contribution signals across observations.
FAQ
How many myths should one myth-busting post cover?
Cover one central myth when it needs a careful evidence chain or several tightly related misconceptions when they share the same audience, scope, and replacement model. Do not combine unrelated beliefs merely to reach a round number.
Should the headline repeat the myth?
Only when the exact belief already has meaningful demand and the headline can frame it as a question or disputed claim. If repetition could introduce or reinforce a harmful belief, lead with the accurate conclusion and address the myth later.
What counts as enough evidence to call something a myth?
The evidence must match the claim’s scope and stakes. Prefer direct, current, independent sources; distinguish absence of evidence from evidence of absence; and use a qualified verdict when findings are mixed or context-dependent.
Can a myth-busting post conclude that a claim is partly true?
Yes. Often that is the most accurate verdict. State which part holds, under what conditions, which part overreaches, and what model the reader should use instead.
How is myth-busting different from a mistakes-to-avoid post?
Myth-busting evaluates a belief through evidence and replaces the reader’s mental model. A mistakes-to-avoid post examines observable behaviors, explains why each is tempting, and provides a correction.
What schema should a myth-busting post use?
Use Article by default. Use FAQPage only when visible questions exactly match the structured records and current search-engine policy supports it. Do not use ClaimReview unless the organization has the required fact-checking process, eligibility, and markup implementation.
Verify the claim before you repeat it
Choose one documented audience misconception, record the current answer and cited sources, then open Prompt Tracking to see whether the published correction becomes part of the answer without losing its qualification.
More tutorials in this section
Ready to put it into practice?
Free check · 7-day trial · no credit card