What does broken HTML structure mean in a description?
Shopify descriptions can contain rich text and HTML. Misnested tags, unexpected element placement, or fragments introduced through copy/paste can be repaired tolerantly by a browser or editor in a way that differs from the author’s intent. The same source can look acceptable in one context and render differently in another.
The detector looks for a structural condition; it does not score the quality of the marketing copy. A finding localizes the portion that fails the check criteria so the merchant can compare the source with the rendered result before accepting an edit.
Examples of structure that needs review
These fragments are illustrative and simplified. Browsers and editors can repair invalid markup tolerantly, so the exact outcome must be checked in the real description context.
<p><strong>Material</p></strong>[inconsistent closing order]A parser may reconstruct the structure; the merchant should confirm the intended visual result.
<ul><li>Red<li>Blue</ul>[incomplete or implicitly repaired markup]Some omissions are tolerated by HTML, so a finding is not a guarantee of a visible error.
<div><p>Details</div>[structurally overlapping elements]Automatic repair can change hierarchy; preserve the text and verify the final form.
What does PROVEN check?
Checks whether the description formatting structure can be parsed without structural errors.
Why does it matter?
Broken structure can make content hard to interpret or produce unintended rendering.
Why does this matter for catalog maintenance?
Shopify cautions that HTML in the rich text editor can cause storefront display errors and provides a code view for troubleshooting. In a catalog fed by several sources, locating suspicious structure can reduce the time spent finding fragments behind inconsistent rendering.
Not every unusual fragment is automatically broken and not every invalid structure renders the same way in every theme. The detector provides reproducible evidence and context rather than assuming a visual outcome or an SEO impact.
What can PROVEN do?
PROVEN can locate the problem and show evidence; repairing the structure remains a reviewed edit.
How PROVEN handles suspicious HTML structure
Detection and remediation stay separate because restructuring markup can change both formatting and text boundaries.
- Locate the structural problemPROVEN preserves the observed markup and the position where the structure fails the check criteria.
- Compare content with intended renderingThe merchant reviews the text, hierarchy, and storefront before accepting a structural rewrite.
- Prepare a reviewed structurePROVEN can prepare a controlled correction, but the result is reviewed to prevent loss of intended text or formatting.
Why not repair every HTML fragment blindly?
HTML parsing is tolerant, and browsers can reconstruct a different tree from imperfect source. A technically cleaner rewrite can still move text, lists, or emphasis.
Check the storefront, original copy, and any import source. The finding does not prove that every theme already displays a visible error.
What this page does not tell you
- The detector does not emulate every browser, theme, or Shopify editor transformation.
- An unusual fragment does not automatically mean shoppers see an error.
- Structural remediation should not delete useful text or elements merely to simplify markup.
- Examples are simplified and do not reproduce a full browser parser.
- This page does not attribute SEO or conversion effects to a particular HTML error.
Frequently asked questions
Doesn’t the browser repair HTML automatically?
Browsers are tolerant and try to build a DOM, but their repair may not match the structure the author intended.
Can Shopify change HTML automatically?
Shopify documents sanitization and automatic formatting corrections in the rich text editor, so observed source should be compared with actual storefront behavior.
Will PROVEN strip all formatting?
No. A proposal should preserve useful content and change only the problem supported by evidence.
Is this finding a security issue?
Not necessarily. This detector concerns structure that cannot be interpreted correctly; risky elements and attributes have separate checks.
Sources and independent context
The sources below explain the relevant platform or web standards. They provide context for interpretation but do not by themselves show that your store has this finding.
- Shopify — Using the rich text editorShopify cautions that HTML can cause display errors and documents code editing and sanitization.
- MDN — Debugging invalid HTMLMDN explains permissive HTML parsing and shows that browsers can automatically repair incorrectly written markup into a different structure.
- Shopify — Product details pageShopify confirms that the product description uses rich text and is customer-facing product content.