Using Section Headings to Separate Verified Facts from Claims to Remove or Revise on a Brand Introduction Page

When editing a brand introduction page, it is crucial to distinguish between established facts and statements that need further verification. This guide explains how to use clear section headings to organize content, ensuring readers and stakeholders can easily identify which parts are confirmed and which are under review.

Setting the Stage: Why Clear Headings Matter for Brand Content

This is a hypothetical editing scenario. A writer has inherited a brand introduction page for a small workshop that restores vintage mechanical clocks, and the page has been quiet for two years. The draft she is given has no headings at all, just eight long paragraphs. Somewhere in the third paragraph a sentence claims the workshop “has served collectors on four continents,” and in the sixth a line asserts that every restoration uses “only period-correct components.” She cannot tell from the page itself which of these came from a documented source and which were added by a previous contributor hoping to sound impressive.

Her first move is to sketch headings that separate what she can stand behind from what she cannot yet. She drafts three candidate labels for the page: “What the Workshop Says About Its Work,” “What We Can Confirm,” and “Claims Under Review.” The first would hold the workshop’s own self-description; the second would hold only statements tied to a dated document, such as a 2019 newspaper profile or a repair log she has actually seen; the third would gather the continent claim, the period-correct claim, and a vaguer line about “museum partnerships” that names no institution.

The trade-off is not obvious. If she keeps “What the Workshop Says About Its Work,” the page stays honest to the original voice but risks presenting self-description as if it were verified. If she drops it and hangs everything under a single “Verified Information” heading, she must either delete the self-descriptive lines or push them into prose that no longer signals who said them. She is also unsure whether “Claims Under Review” belongs on a public page at all, since it may read as an internal note left visible by mistake.

The separate question she has not resolved is what to do with the museum partnerships sentence. No document names a museum, so it cannot sit under confirmed facts, but silently deleting it would erase a claim whose origin she has not traced. She considers placing it under the review heading with a short line explaining that the source is being checked, then decides that choice can wait until she has looked through the remaining correspondence.

Using Descriptive Headings to Label Verified Facts

Technique G130 describes descriptive section headings as labels that identify each section in relation both to the whole page and to the other sections on the same page. The stated purpose is to give users an overview of the content and its organization, help them find specific content, and help them orient themselves within the page.¹

The technique also suggests authors consider placing the most important information at the beginning of each heading. This is said to help users skim headings to locate the content they need, and is described as especially helpful when browsers or assistive technology allow navigation from heading to heading. In the technique's examples, the level 2 headings put the distinguishing word first, as in “Flood preparation” and “Fire preparation” rather than “Preparation for floods.”¹

A practical next step is to take your existing list of verified facts and give each group a heading that names the kind of evidence behind it, rather than a heading that sounds promotional. Suppose your notes contain three confirmed items: the workshop opened in 1987, it repairs mechanical clocks, and it employs two technicians. A label like “Workshop Details” tells a reader almost nothing, while “Confirmed Workshop Details” signals both the content and its status. You can keep the wording plain and let the noun do the work.

You might also compare two candidate labels for the same material before choosing. “What We Can Confirm” reads as a promise about evidence; “Workshop Facts” reads as a neutral category. The first is clearer about the boundary between verified and unverified material, but the second is shorter and less repetitive if several headings follow the same pattern. Consider which fits the rest of your page and whether a reader scanning only the headings would understand why this section exists.

A useful self-check is to read each heading alone and ask what a reader would expect underneath it. If the heading could sit above a claim you have not confirmed, revise it until it could only introduce checked details. You can note that revised wording beside your draft and decide later whether to adopt it.

Structuring Sections for Claims Under Review

Take one paragraph you already know is solid—say, the sentence about the workshop’s founding year—and pair it with one sentence you are still unsure about, such as a claim that the workshop “trained a generation of local apprentices.” Place both under a working heading, then ask whether that heading promises more than the confirmed sentence can support. You might consider a label like “Workshop History” for the solid material and “Statements Under Review” for the unconfirmed sentence; the second heading tells you, and any collaborator, that the paragraph is provisional rather than settled.

You can also make the revision visible inside the paragraph itself. Leave the confirmed sentence as written—“The workshop opened in 1962”—and draft the uncertain claim with a hedge that matches what you actually know, for example “The workshop has long been described as training several local apprentices.” Then choose whether the hedged version belongs on the page at all, moves to a separate section, or waits until someone can point to a record. The choice is yours; the heading only makes the decision easier to see.

For material that may need removal, try a short heading such as “Claims to Verify or Cut.” Under it, keep the original sentence verbatim and add one line to yourself naming what would settle it, like “no names or dates found.” That way the sentence stays intact for a later decision instead of being silently softened or deleted. If you prefer fewer headings, you might instead mark these sentences with a single consistent note in your own draft and group them under one heading at the end.

Compare two possible orderings before committing. Putting confirmed facts first lets a reader meet the page’s strongest material immediately; putting claims under review last keeps the main narrative clean. Read both versions aloud and notice which one makes the uncertain sentences feel like an appendix rather than part of the story. Your own preference should decide, provided every heading still accurately describes what sits beneath it.

Maintaining Logical Hierarchy in Content Organization

The W3C Web Accessibility Initiative explains that headings communicate the organization of page content and can support in-page navigation by browsers, plug-ins, and assistive technologies. It advises nesting headings by rank, where an equal or higher rank starts a new section and a lower rank starts a subsection of the higher-ranked section.²

Skipping ranks can be confusing and should be avoided where possible, so an h2 element should not be followed directly by an h4 element. The page notes an exception: skipping ranks is acceptable when closing subsections, such as an h2 beginning a new section after an h4 closes the previous one.²

“What We Can Confirm,” “What the Workshop Says,” and “What We Still Need to Check” place different obligations on the reader. You can apply one new action to your own page: before finalizing any heading, write a one-line note beneath it describing what belongs there and what does not. For example, under “What the Workshop Says,” you might note: “Claims attributed to the workshop; no independent evidence required.” This makes the heading a boundary rather than a label.

You can then test the hierarchy by moving a single sentence between sections. Take “The workshop opened in 1962” and place it under confirmation; take “Our methods are trusted by museums” and place it under claims. If either sentence can sit under two headings without friction, one heading is probably doing too little work. You might revise the weaker heading rather than the sentence.

Consider whether your subheadings repeat the same job at different scales. A section called “What We Can Confirm” containing only “Confirmed Facts” adds a layer without adding a distinction; you can collapse it or rename the inner heading to name a category, such as founding details or materials. The choice is yours, but the reader should be able to predict what changes between levels.

Ensuring Accessibility Through Proper Heading Nesting

The guidance advises using short headings to group related paragraphs and describe each section clearly, so the outline itself conveys structure. For documents longer than three or four paragraphs, headings and subheadings matter for usability and accessibility: they help readers grasp the overall outline and navigate to specific information. Headings are classified into levels one through six, with Level 1 often corresponding to the page title or major document section.³

A heading's appearance is not enough. Visual readers spot headers by scanning for larger or differently styled text, but assistive technology users cannot see those changes, so styling alone is not a sufficient cue. Headings must be semantically tagged so assistive technology can identify them and use them for navigation, which the guidance describes as one of the most important tools for screen reader users. Tagging usually triggers a visual formatting change that can be adjusted in many documents.³

For accessibility, heading level should follow the actual hierarchy of your page, not the visual size you want. You can take one draft section — say, “What We Can Confirm” — and list its heading and any subheadings on a separate line with a number showing each level. If a subheading feels like it belongs at the same level as its parent, that is a sign your outline has a gap or an extra layer, and you can choose whether to merge the sections or promote the subheading.

Consider whether each jump from h1 element to h2 element to h3 element is earned by a real change in subject. A page might use an h1 element for the brand name, an h2 element for “What We Can Confirm,” and an h3 element only when a section genuinely splits, such as confirmed founding facts versus confirmed workshop practices. If you find an h3 element that contains one sentence and no sibling, you might fold it back into the parent section.

You can also record, for yourself, which heading introduces the material you plan to keep, revise, or remove. That note is for your revision, not a page requirement.

Final Checklist for Heading Consistency

A final check for heading consistency can start with one concrete sentence from your draft rather than the whole outline. Take a claim you have already decided to keep, revise, or remove, and read the heading above it as though you were a first-time visitor. If the heading promises confirmation and the paragraph beneath it contains a sentence you still need to verify, you can either move that sentence under a heading that admits uncertainty or reword the heading so it describes the workshop's own account rather than your evidence. This is a hypothetical editing choice; the point is to make the heading and the sentence agree before you publish.

You might also compare two headings side by side for the same block of text. "What We Can Confirm" sets an evidentiary expectation, while "What the Workshop Says" signals attributed speech. Neither is automatically better; consider which one matches the sentence you actually have. If the original wording is a quotation from the workshop, the second heading may fit without further editing. If you have a documentary source for the same sentence, the first heading becomes available to you. You can record the reason for your choice in your own notes so that a later revision does not quietly change the heading's meaning.

A useful last pass is to read every heading in sequence and ask whether each one still describes the material immediately below it after your latest edits. Moving a single sentence between sections can leave a heading overstated. You can check this by covering the paragraphs and predicting what each heading promises, then uncovering them one at a time. Where the prediction and the content diverge, you might revise the heading rather than the sentence, or move the sentence to a section whose heading already fits. You can decide which change is smaller for your page.

For hierarchy, consider whether a heading only restates its parent's job; a section called "What We Can Confirm" that contains only "Confirmed Facts" adds a layer without adding information, and you can collapse it. The final decision about how many levels to keep remains yours, based on how much material each level actually separates.

Frequently asked questions

How can I use my existing list of verified facts when organizing headings?

A practical next step is to take your existing list of verified facts and give each group a heading that names the kind of evidence behind it, rather than a heading that sounds promotional. Suppose your notes contain three confirmed items: the workshop opened in 1987, it repairs mechanical clocks, and it employs two technicians.

How can I check whether a heading promises more than my confirmed details can support?

A useful self-check is to read each heading alone and ask what a reader would expect underneath it. If the heading could sit above a claim you have not confirmed, revise it until it could only introduce checked details.

What can I do to keep an uncertain claim visible for later checking rather than deleting it?

For material that may need removal, try a short heading such as “Claims to Verify or Cut.” Under it, keep the original sentence verbatim and add one line to yourself naming what would settle it, like “no names or dates found.”