When creating Help Center articles via the Articles API, there are a few limitations that make content structure difficult to manage:
- The article title is automatically rendered as H1, and the body also supports only H1 and H2.
- If you include an H1 in the body, the page ends up with two H1 headings, which is not ideal for accessibility and SEO.
- If you avoid H1 in the body, the first heading is automatically converted to H1, so the structure still becomes inconsistent.
Additionally, images must currently be referenced via external URLs, which can create concerns around long‑term availability and accessibility when articles are referenced by AI or other systems.
It would be very helpful if the API allowed:
- Full heading hierarchy (H1–H6) in the article body, or
- A way to prevent the title from being rendered as H1 when the body already contains one, and
- Native image upload support instead of requiring external URLs.