Paste Markdown, choose heading levels and bullet style, then copy anchor links generated from the document structure.
The review follows the source or generated Markdown for this tool, checks structural handoff risks, and keeps CommonMark/GFM/host-specific boundaries visible before copy or export.
—
Review summary will appear here.
CommonMark defines the core syntax, while GitHub Flavored Markdown and publishing systems add extensions such as tables, task lists, autolinks, footnotes, front matter and renderer-specific raw-HTML behavior. This review is local and never fetches links.
Generate a Markdown TOC with heading-depth controls, GitHub-style anchors, duplicate-slug collision checks and marker handoff.
Markdown portability depends on the exact source and the renderer that consumes it.
Review fences, headings, links, extension syntax and generated output before publishing; source-level checks do not prove remote links or repository-specific style rules.
Use the tool first, then apply these checks to verify the inputs, interpret the result, and hand it off without displacing the primary workflow.
Markdown itself does not define one universal heading-ID algorithm. GitHub, GitLab, MkDocs, Docusaurus, Jekyll, and custom documentation systems can differ on punctuation, Unicode, duplicate headings, and explicit IDs. Use the generated TOC as a renderer-specific draft and verify at least one built page when links matter.
Two headings with the same visible text can produce colliding or numbered anchors. A TOC that looks correct in plain text may still send both links to the first section if the renderer handles duplicates differently. The collision audit is a prompt to verify the final rendered IDs, not a guarantee across every Markdown engine.
A generated TOC can expose skipped levels such as H2 directly to H4. That may render, but it usually signals a document-structure problem that affects navigation and accessibility. Fix the heading hierarchy in the source when possible instead of hiding the symptom by excluding levels from the TOC.
Generate from the exact Markdown that will be committed or published, not from an older draft copied into another editor. Code fences, generated sections, includes, and front-matter processing can change which headings reach the final page. Re-run the TOC after structural edits and test a few links in the rendered output.
WebToolArc