From topic to published article
-
Topics per persona and stage
Problem guides, how-tos, checklists, buyer’s guides, comparisons, objection answers, use cases and rollout plans, planned from each persona’s pains, jobs, objections and keywords. Competitors are named only if your brand allows comparative copy, and topics that match an existing post are skipped.
-
Draft
With AI, an outline first and then 900 to 1,600 words using only facts from your profile and approved claims. Sentences with a number, a superlative or a competitor name that no approved claim covers are dropped. Without AI, a deterministic writer builds a post of the right type (sections, steps, criteria, a checklist, objections, a rollout plan, an FAQ) that passes the lint and the AI-tell check unchanged.
-
SEO pass
The target keyword goes into the title, the introduction, one subheading and the meta description where it fits; the slug comes from the keyword; internal links point to your crawled pages (pricing, customers, security, integrations, docs); an FAQ and a call to action to the persona’s offer page are added. The editor lists anything still missing next to the policy issues.
-
Cover and editor
A 1200 × 630 cover image is rendered in your brand design. The article editor previews it in that design, with a title of up to 70 characters and a meta description of up to 155.
-
Approve and publish
Publishing is an action in your inbox, for now or for a set time. It needs a person below autonomy level 4, which covers every plan short of Enterprise. The copy is cleaned and linted again at publish time, and a blocking issue stops it.
-
Promotion
The first publish creates organic posts on the persona’s networks among LinkedIn, X, Facebook, Bluesky and Reddit, and a nurture e-mail, all linking to the article and scheduled through the normal pipelines.
Where articles are published
| Target | Connection | What to know |
|---|---|---|
| Hosted blog | Nothing to set up | Index, sitemap, RSS, canonical and Open Graph tags, BlogPosting and FAQPage structured data and your tracker, in your fonts and colours |
| WordPress | REST API with an application password | Categories and tags found or created, cover uploaded with alt text, native scheduling; structured data needs a user allowed to post unfiltered HTML |
| Webflow | Data API v2 with a site token | Field mapping you configure; code blocks arrive as plain paragraphs; Demander handles scheduling |
| Ghost | Admin API key | Call to action as an HTML card, structured data in code injection, native scheduling |
| HubSpot CMS | Your HubSpot connection with the content scope | Tags found or created, draft then push live, native scheduling |
| GitHub | A fine-grained token for one repository | Markdown with front matter for Hugo, Jekyll, Astro or Next.js, committed to the branch or opened as a pull request |
| Webhook | Your endpoint and a shared secret | Signed JSON carrying HTML, Markdown and structured data |
Nothing reaches a CMS outside live mode: sandbox and dry runs return the requests Demander would send. The first public copy sets the article’s canonical URL, the slug locks once a post is live, and later edits wait as a “publish the edit” prompt. Taking a post down is the undo, and it cancels promotion posts not yet published. Setup per CMS is on the CMS integrations page.
Articles inside the funnel
A visit that lands on a published article counts as one blog touch for that article, unless a paid, organic or e-mail touch already owns the visit. Every read adds a signal to the account, weighted by stage (awareness 4, consideration 7, conversion 8) with a half-life of 21 days. A fresh consideration read moves an aware account to engaged, which puts it on the case-study nurture list for retargeting.
Awareness campaigns for content offers (a checklist, a benchmark report) land on a published article automatically, and any draft campaign can be pointed at one. Timelines and conversion paths show the article title.
Landing pages
-
01
Built from the conversion message
A hero with the headline and call to action, the problems the persona has, how the product helps, proof from your site, an FAQ from the persona’s objections, and the offer. The claims check applies as on every creative.
-
02
In your design
A complete, responsive page with proper headings, your fonts, colours, corners, buttons, logo and brand image. Cards appear only if your brand draws cards, and FAQ items open and close.
-
03
Editable
SEO title (60 characters), meta description (160), slug, and sections you add, remove, reorder or retype. The preview shows desktop, tablet and phone widths before you save.
-
04
Strict by default
No inline script and one stylesheet whose hash goes into the page’s Content Security Policy. Your website tracker is included.
-
05
Hosted or exported
Approved and live pages are served at a public Demander URL. Any page can be exported as an HTML file to host on your own domain, and the brand fonts stay available to it.
-
06
Variants
Save as new variant keeps the persona, stage, message and journey and links back to the source page. Automatic traffic splitting between landing page variants is not available yet.
Questions people ask
Can I publish to our own WordPress site?
Yes. Create an application password for a user who can publish posts and connect the site under Integrations. Demander finds or creates categories and tags, uploads the cover with alt text and uses WordPress’s own scheduling. For the FAQ structured data the user needs permission to post unfiltered HTML.
Who approves an article before it goes live?
A person. Publishing an article needs autonomy level 4, and Starter, Growth and Scale run at levels 1 to 3, so every article goes through the approval inbox. You can publish at once or schedule it.
Can I take an article down?
Yes. Taking it down is the undo of the publish action: on WordPress the post goes back to draft, and promotion posts that have not gone out yet are cancelled.
Can landing pages run on our own domain?
Export the page as an HTML file and host it wherever you like; its fonts are served to any domain. Otherwise approved pages are served at a public Demander URL.