Keep the article connected to the reason for writing it
Visibility gap → available competitor and source evidence → website and business context → article opportunity → full draft → human review → CMS workflow → crawler-readable page → future visibility measurement.
PB connects article generation to evidence already available in the workspace: tracked questions, recorded provider answers, cited sources and the business website. A proposal helps establish the angle; confirmed generation produces a full article draft. Read how the complete platform workflow fits together.
Choose an article when the evidence calls for one
Start with a relevant question and a successful recorded answer in AI Visibility. Review how the answer describes the problem, which businesses appear and what sources support it. An absent mention is a reason to investigate, not an automatic instruction to create another page.
Look at what your own website already covers. A clearer existing page, a technical repair or further research may be the better action. Use an article opportunity when a useful customer question needs a complete explanation that fits the business.
Use source evidence and the website's real context
The writing workflow uses retained provider-answer evidence, readable owned-page context and available cited-source context. Competitor and source evidence can help identify what an answer covers, but it is not available equally for every question.
Review the proposed title, angle and outline against the business's actual offering. Add editorial direction where useful. Preserve the evidence behind the choice so a reviewer can distinguish an observed gap from a generated suggestion. A returned source is not necessarily an explicit answer citation.
Generate a complete article draft
After reviewing the proposal, confirm generation using the shared workspace article allowance. PB runs its writing and quality-review steps and saves the full draft for review. The result is a complete article body, not only a content brief, outline or calendar entry.
Generation requires eligible retained answer evidence and readable owned-page context. If those are missing, resolve the evidence or page-access problem first. The proposal and generation stages do not approve or publish the article.
Review the article before release
Read the full text and check its facts, examples, product claims, links and suitability for the business. Edit the writing, remove unsupported statements and confirm rights and brand requirements. Automated writing and quality checks do not replace your editorial judgment.
Approve the reviewed article in the publishing workflow. If the text changes later, review it again before release. The article and calendar guide explains the generation, review and delivery steps.
Use the publishing path that fits your website
With a configured supported destination, send an approved article as a CMS draft where supported or explicitly confirm its release. An editorial calendar date only organizes work; a separately confirmed publication schedule can execute an approved release at the chosen time.
| Destination and setup | Draft or review path | Approved release |
|---|---|---|
| WordPressConfigured WordPress application-password connection. | Send a reviewed article as a CMS draft. | Explicitly publish the approved article.The CMS confirms its article status; verify the live page. |
| WebflowConfigured CMS collection, credentials and field mapping. | Send a reviewed article as a CMS draft. | Explicitly publish the approved article.The CMS confirms its article status; verify the live page. |
| Shopify blogsConfigured Admin API token, selected blog and author. | Send a reviewed article as a CMS draft. | Explicitly publish the approved article.The CMS confirms its article status; verify the live page. |
| Wix blogsConfigured API credentials, site and blog author. | Send a reviewed article as a CMS draft. | Explicitly publish the approved article.The CMS confirms its article status; verify the live page. |
| GhostConfigured Ghost Admin API connection. | Send a reviewed article as a CMS draft. | Explicitly publish the approved article.The CMS confirms its article status; verify the live page. |
| AstroPrivate article feed, @prerenderbuddy/astro setup and a hosting rebuild hook. | Keep the draft in PB until release. | Release approved feed content and request a hosting rebuild.The host still needs to complete deployment. |
| KeystaticAuthorized GitHub repository, supported collection/file mapping and publication branch. | Create a content pull request for Git review. | Merge the approved content into the publication branch.Git release is confirmed; the host still needs to deploy. |
| Publishing WebhookConfigured custom publishing endpoint and its own publication workflow. | Draft handling depends on your endpoint. | Deliver the approved article to the configured endpoint.Endpoint acceptance does not confirm a live page. |
Connections require authorized credentials and the appropriate website configuration. Review the integration prerequisites. Astro rebuild requests, Keystatic Git releases and custom endpoint acceptance have their own boundaries; verify hosting publication separately.
These connectors support their article workflows. An improvement to another existing website page may still need an authorized person to apply the text through that website's normal process. Autopilot publishing is not enabled.
Verify the page and revisit the question
Check the final URL, live article text, response status, metadata and crawler-readable HTML. Website Health and Monitoring helps inspect the page and follow recorded issues. Add crawler rendering when a measured JavaScript delivery gap needs it; complete server HTML may already be sufficient.
Keep the publication date with the action, then revisit the relevant AI Visibility questions over time. Compare equivalent question sets, providers and reporting periods. A later mention or citation is an observation, not proof the article caused it. PB does not guarantee rankings, citations, recommendations, traffic or revenue.
Choose how to use article generation
Article generation and publishing connections are available to eligible current Starter, Growth and Pro accounts. The shared article allowance covers generation in the application and authorized tools; trial and legacy limits can differ. Review current plans and allowances in your account.
Use the web application to prepare, generate and review articles. Hosted MCP can prepare proposals and generate explicitly confirmed, unapproved drafts with authorized content-write access. It does not approve or publish them. The Developer API provides separate scoped review, delivery and scheduling actions for approved workflows.
Buddy can explain available evidence and help choose a next step; it does not autonomously generate or publish articles. The published local MCP package remains a diagnostic and workspace-read surface. See the wider platform workflow for the roles of the different tools.