Generate and publish reviewed articles

Use a completed question, mention, recommendation, competitor or source pattern from AI Visibility. A missing mention alone does not justify a new article. Decide whether to fix a technical issue, update an existing page, consolidate content or create an article.

Review the article opportunity, intended angle and available evidence. Recorded provider answers, the website and business context, and readable cited sources where available inform the draft. Generation requires eligible retained answer evidence and readable owned-page context.

Confirm generation using your workspace's article allowance. PB saves a complete article draft for review, not just a brief or outline. A proposal or generated draft has not been approved or published. Read how article generation uses this evidence for the complete content workflow.

Read the full article. Check its title, angle, factual claims, supporting links and fit with the business. Remove unsupported claims and internal notes, and review rights and brand requirements before approving it.

An existing-page improvement may still need an authorized person to apply the text through the website's normal process. Article connectors do not establish arbitrary website editing or technical repair.

Publishing connections are available on current Starter, Growth and Pro. Choose the website and configure an authorized, supported destination before delivery. Effective account access and connector health determine the available controls.

Supported destinations are WordPress, Webflow, Shopify blogs, Wix blogs, Ghost, Astro and Keystatic. A publishing webhook can deliver to a custom endpoint. Read the integration options for prerequisites and differences.

After review and article approval, send the article as a CMS draft where supported, or explicitly confirm its release. A CMS draft is not a live page.

Astro keeps drafts in PB until approved feed release and a hosting rebuild request. Keystatic creates a content pull request and supports an approved Git release. Hosting deployment remains separate; see the Keystatic publishing guide. A custom webhook's acceptance must be verified at its destination.

An editorial calendar date and workflow status organize work. They do not publish an article.

A publication schedule is a separate action: review and approve the article, configure its destination, choose the publication time and confirm the schedule. PB can execute that approved release at the selected time. A changed article or destination, or revoked authorization, can stop execution. Review an edited article again before releasing it.

The automation workflow guide explains the corresponding scoped API actions. Autopilot publishing is not enabled.

Check the final URL and live content after publication. A successful CMS action, Git merge, accepted webhook or rebuild request has its own scope; verify that the intended page is actually available and contains the reviewed article.

Use website Health and Monitoring to check the relevant public page and crawler-readable response. Revisit the relevant AI Visibility questions over time. Later answer changes are observations, not proof that an article caused them.

Follow the complete platform workflow to connect measurement, diagnosis, creation, publication and monitoring.