The Tag and the Look Are Two Decisions

The Baseline Is Good, So Look Elsewhere

A published Webflow site is static HTML served from a CDN. The text is in the response, the URLs are real, and a crawler receives the page without running anything.

That closes the question most platform modules spend their first lesson on. Run the fetch test once to confirm it and then move on:

curl -s https://example.com/your-page | grep -i "the sentence you want cited"

Where Webflow sites lose answers is one level up: the page is present and its structure does not say what the design says.

Two Decisions That Look Like One

On a visual canvas you choose a text element and you choose how it looks. Those are separate, and either can be set without the other.

So a line can carry heading styling while being a paragraph or a div, and a real heading can be styled to look like body text. A designer working visually has no reason to notice, because the canvas shows the result of the styling and says nothing about the tag in the output.

The consequence is the one from Optimizing for AI Discovery: headings are the strongest structural signal a page has, and a page whose headings are not headings has thrown that signal away while looking perfectly organised.

The Other Half Of The Same Problem

Levels skipped for visual reasons. A section heading styled smaller gets built as an h4 because h4 happened to have the right size, and the document now claims a nesting that does not exist.

The fix is to separate the two decisions deliberately: pick the tag from the document's structure, then style that tag to look however the design requires. A class does the visual work; the tag does the structural work; neither has to compromise.

Sections That Depend On The Layout

The third symptom is subtler and follows from designing in columns.

A two-column block where the left says "What it does" and the right says "Three sizes, eight colours" reads correctly on screen because the eye pairs them. Lifted out on its own, the right column is a fragment with no subject. A system taking one passage takes it without the column beside it.

The test is the one from the extraction pass: read each block with nothing above or beside it. If it stops meaning anything, the meaning was in the layout rather than in the text, and layout does not survive extraction.

The Hour That Finds All Three

1. View source on your five most important pages and list the heading tags in order.
2. Compare that list against what looks like a heading on the rendered page, and note every disagreement.
3. Check for skipped levels, and for any h1 that is not the page's subject.
4. Read each block of copy with nothing above or beside it and mark the ones that lose their meaning.
5. Fix the tags first. It is the cheapest of the three and it changes the most.

Key Takeaways

• Webflow publishes static HTML, so presence is rarely the problem and structure usually is.
• On a visual canvas the tag and the styling are separate choices, so text can look like a heading without being one.
• A page whose headings are not headings has discarded its strongest structural signal while appearing well organised.
• Pick the tag from the document structure and use a class for the appearance. Neither decision has to compromise the other.
• Copy that depends on a neighbouring column loses its meaning when one passage is lifted out.