> For the complete documentation index, see [llms.txt](https://tmniche-docs.keywordrush.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tmniche-docs.keywordrush.com/building-a-site/generate-articles.md). # Generate & publish articles Once your Topic Map is ready, you turn its articles into real WordPress posts — on demand, one click at a time. Nothing is written until you press **Generate**. ## Where to generate Same **Generate** button, two places: * **Plan details** — work through the articles in a single plan. * **Content Queue** — every article across all your plans in one list, with filters (plan, status, format, intent) and search. Best for working through a backlog. ![The Content Queue with its filters](/files/sumojdQ70OKPmiHYWoLk) ## Generate an article Find an article and click **Generate** (on the row, or inside its drawer). A progress indicator runs while it works; a single article takes a couple of minutes. When it finishes, the post is created in WordPress. What status the post gets: * By default it's **published**. You control this with the **Post status** setting in your Generation Preset (publish, draft, or pending). * If the article's **target publish date is in the future**, the post is created as **Scheduled** for that date instead. Then use **Edit Post** or **View Post** to open it. ![A queue row generating, with progress](/files/EoSiVplowhMvnONOmxiY) ## Review and publish A generated article is an ordinary WordPress post — Gutenberg blocks in your own site. Open it with **Edit Post**, review and adjust anything, then **Publish** as you would any post. A draft is one click to publish; an article that arrived **Scheduled** (a future target date) is published automatically by WordPress on that date. You don't need to maintain the product or conversion blocks by hand: **prices, links, images, and CTA/contact details refresh at view time**, so they stay correct after publishing — and update on their own when a product or your profile changes. Avoid replacing those with hardcoded values. ## Generating many at once (concurrency) You don't have to wait for one article to finish before starting the next — click **Generate** on as many as you like. They queue up, and the server generates a fixed number **in parallel**; how many run at the same time is your plan's **concurrency limit**. The rest wait and start automatically as slots free up. **Keep the plan or Content Queue page open while articles generate.** That page polls the server for progress and pulls each finished post into WordPress. Generation still completes on the server if you navigate away — but you'll need to reopen the plan or Content Queue for the finished posts to load and their status to update. ## Credits and Premium models Each generated article uses one **article credit** from your monthly allowance. With a **Premium** model (your own API key), an article costs **½ credit** — doubling how many you can generate. Your usage is shown on the **License** page. * [Plans & limits](/account-and-licensing/plans-and-limits.md) * [Premium models (bring your own API key)](/account-and-licensing/byo-api-key.md) ## If generation fails * **Read the error message first.** It usually explains exactly what went wrong — for example, that no relevant products could be found. Often there's no point retrying as-is; fix the underlying issue (edit the article's details) before trying again. * Click **Retry** to try again. After three failed attempts the button changes to **Edit to Retry** — open the article, adjust it (for example, clarify the title or the **Instructions for AI**), and try again. * For **affiliate** and **e-commerce** money articles, **Generate** stays disabled until the article has a **product source**. Set one on the plan, or attach products to the article — see [Curate products](/building-a-site/curate-products.md). ## Next * [**Curate products**](/building-a-site/curate-products.md) — control which products appear in an article. * [**SEO titles & meta descriptions**](/building-a-site/seo-meta.md) — titles and descriptions are written as each post is generated. * [**Interlinking**](/core-concepts/interlinking.md) — how internal links work. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://tmniche-docs.keywordrush.com/building-a-site/generate-articles.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.