XML / HTML Structure Fix
Catch the missing close tag that breaks your page or feed — privately, with no upload.
XML / HTML Structure Fix
Paste markup to catch unbalanced tags and well-formedness errors, with a best-effort suggestion for what to close.
Notes
HTML checking is a heuristic tag-balance test — it catches missing or mismatched close tags but does not validate attributes or nesting semantics the way a browser does. XML checking uses the browser’s strict parser and reports the exact error. The auto-close suggestion is a starting point, not a guaranteed fix.
When to use this
Markup breaks quietly: a forgotten </div> shifts your whole layout, a missing close tag in an RSS/Atom feed makes a reader reject it, or a hand-edited SVG won’t render. This tool finds unbalanced tags in HTML and reports the exact well-formedness error in XML, so you fix the right spot instead of scanning hundreds of lines.
Worked example
You paste a snippet where a <p> is never closed before its parent <div> closes. The HTML check reports “Unclosed tag(s): p” and suggests appending </p>. In XML mode, a missing closing tag on a node returns the parser’s own error message with the line, which is usually all you need.
What it checks and what it won’t
For XML it uses the browser’s strict parser — authoritative for well-formedness. For HTML it does a tag-balance heuristic that ignores void elements (img, br, meta, …) and doesn’t validate attribute syntax or semantic nesting. The auto-close suggestion is a convenience, not a validator; always eyeball the result. It does not reformat or pretty-print your markup.
FAQ
Why does my valid HTML show as “unbalanced”? The HTML mode is a rough balance test. If you omitted optional close tags that browsers allow (like </li>), it may flag them even though the page is fine. Use it to catch real mistakes, not to enforce strict XHTML.
Is my markup uploaded? No. Parsing runs locally in your browser.
Can it fix JSON too? No — that is the JSON Error Repair tool. XML/HTML and JSON have different rules.