Writing and publishing articles

Updated Oct 20, 20265 min read
English
On this page

Writing a help center article is straightforward: rich text editor, title, slug, category, body, publish. The editor supports headings, lists, quotes, links, images, embedded videos and code blocks. Drafts let you collaborate before going live. Articles take their SEO metadata (description, OpenGraph) from the article's title and description; override it per article in the SEO tab. The AI bot can use published articles as knowledge once you switch that on in the bot settings or add the help center in the Training Hub.

Help center articles are the building blocks of your knowledge base. A well-written collection of articles empowers your customers to find answers on their own, reduces repetitive support tickets, and helps Deskwoot's AI bot deliver accurate, instant responses. This guide walks you through creating, formatting, and publishing articles effectively.

Creating an article

  1. Navigate to the Help Center section in your Deskwoot dashboard.
  2. Click "New Article".
  3. Enter a clear, descriptive title that reflects the question or topic your customers are searching for.
  4. Select an appropriate category so the article is easy to discover (every article needs one).
  5. Write your content using the built-in editor. You can add headings, lists, images, videos and links to structure your article for readability.

Writing effective content

The way you write an article matters just as much as the information it contains. Keep these best practices in mind:

  • Lead with the answer. Place the most important information at the top so readers get value immediately.
  • Use short paragraphs and headings. Break content into scannable sections. Most readers skim before they read.
  • Include step-by-step instructions with numbered lists whenever you're explaining a process.
  • Keep language simple. Avoid jargon and write as if you're explaining the topic to someone encountering it for the first time.
  • Add visuals when helpful. Screenshots or short descriptions of what users should see on-screen can reduce confusion.

Draft and publish

New articles are saved as drafts by default, so you can work on them without affecting your live knowledge base. When you're ready:

  1. Check your article for formatting, links, and overall readability.
  2. Set the status to Published and save to make the article live and visible to customers. Publish all drafts on the Articles tab publishes every draft at once.

You can return to any published article later to edit or revert it back to draft status if it needs significant updates.

Common pitfalls to avoid

  • Vague titles: A title like "Setup" is harder to find than "How to set up email forwarding." Be specific.
  • Uncategorized articles: Articles without a category may not appear in your portal's navigation, making them difficult for customers to locate.
  • Outdated information: Schedule periodic reviews of your articles to ensure instructions and screenshots still match your current workflows.

Frequently asked questions

Can I edit an article after it has been published?
Yes. Open the published article, make your changes, and save. Updates are reflected on the live portal immediately.
Does the AI bot use my help center articles?
Yes, once you turn on Use Help Center articles as knowledge base in the bot settings or add your help center as a source in the Training Hub. Deskwoot's AI bot then references your published articles to provide accurate answers to customer questions, so keeping your content up to date directly improves automated support quality.
How should I organize articles across categories?
Group articles by topic or product area. Aim for categories that mirror the way your customers think about their questions,for example, Billing, Getting Started, or Account Settings.
How do I create my first article?
Help Center → New Article. Title, slug (auto-generated from title, editable), category, body, status (Draft / Published). Save. Published articles appear immediately on the public help center.
Should I use the WYSIWYG editor or HTML mode?
The editor is rich text only; there is no HTML mode. The toolbar has headings (H2, H3), bold, italic, strikethrough, bullet and numbered lists, quotes, code blocks, links, Insert image and Embed video.
What's a 'slug' and can I change it?
The slug is the URL-friendly identifier (e.g. 'how-to-reset-password' → URL https://yourslug.deskwoot.com/how-to-reset-password, or the same path on your custom domain). Auto-generated from the title; editable on the English tab, and all languages share it. Changing the slug after publishing breaks any external links pointing to the old URL, so be careful.
How do I add images?
Click Insert image in the toolbar and paste the image's https URL. The editor does not upload files, so host the image somewhere first. Compress large images, because they slow page load.
Can I add a FAQ accordion?
Not in the article editor. It has no HTML view and no accordion block. Use H2 or H3 headings with short answers instead.
How does article SEO work?
The SEO tab has SEO title (the article title when empty) and SEO description; without an SEO description the article's Description is used. The URL is https://yourslug.deskwoot.com/article-slug (or your custom domain). Schema.org markup is auto-generated, and every help center has its own sitemap.xml to submit to Google Search Console.
Will the AI bot read drafts?
No. Only published articles are indexed by the bot. Drafts stay invisible to both customers and the bot until you publish them.
Can I translate articles?
Yes. Per article you can have multiple locale versions. The article editor has a 'Translate from English' button (Startup and up, $0.06 per translation from the prepaid balance) or you can write each locale manually.
Should I structure articles with H1, H2, H3?
Yes. H1 = article title (auto). H2 = main sections (3-5 per article). H3 = subsections. Don't skip levels (no H1 → H3 directly). Headers help SEO and readability.
How long should an article be?
Depends on the topic. Setup guides: 300-800 words. Concept explainers: 600-1500 words. FAQ-style: 150-400 words plus the FAQ list. Quality > length: a tight 300-word article beats a rambling 2000-word one.
Can I get analytics on which articles get read?
There is no per article view count. Under Reports, the Article feedback section shows the thumbs up and thumbs down votes readers gave your articles in the chat widget. Use it to spot articles that need work.

Was this guide helpful?

Keep reading

Ask Fynn about this guide

Get a short answer from this guide and the rest of the help center.

Still need help?

Fynn answers from these guides in the chat, and you can reach the team there too.

Email us