notion-publish-generated-markdown

AI-generated markdown publishes as raw text in Notion because escaped HTML entities like < and & are not converted back to literal characters before publishing. You must unescape these entities and preserve renderable block syntax to fix broken page rendering.

To publish Mermaid diagrams to Notion successfully, you must clean the drafted markdown and resolve reserved-word collisions with identifiers like graph, end, or subgraph. This prevents silent diagram failures during the publishing workflow.

The best way to fix broken callouts and tables in Notion is to apply entity unescaping and validate that Notion-flavored markdown block syntax is preserved before publishing. This prevents raw markup from appearing as plain text on your pages.

Notion MCP does support verifying parent-child page relationships after publishing markdown. You can validate cleaned content and request post-publish confirmation to ensure that pages and child pages actually rendered and landed correctly.

You can use AI-drafted design documents for fan-out publishing workflows in Notion by unescaping entities, fixing Mermaid reserved-word collisions, and verifying that all parent and child pages landed and rendered correctly.

Limitations of publishing AI-generated markdown directly include raw callout and table markup rendering as plain text, broken Mermaid diagrams from reserved identifiers, and silently failed page landings. You must validate cleaned content to avoid these issues.