Keep the evidence and the next action connected
Measure → Diagnose → Create and improve → Publish → Deliver → Monitor → Measure again.
Start with recorded answers and website evidence, choose the work that is justified, and review it before release. Prerender Buddy connects these steps in one platform. Features and allowances depend on the account and its configuration; the product facts explain the current scope.
Measure your presence in AI answers
Track relevant buyer questions through the provider APIs available to your account. AI Visibility records the answers and evidence behind each collection.
- Brand mentions and recommendations, with supporting answer evidence.
- Explicit citations, alongside returned or searched sources with their different relationships.
- Tracked competitors and possible competitors detected in the answers.
- Recorded answers, provider context, market and collection dates.
- Changes over time, with successful and incomplete observations kept in scope.
These are controlled samples, not access to private consumer conversations or every answer a person might see. Compare like questions, provider sets and reporting periods before interpreting a change.
Diagnose what deserves attention
Connect a visibility finding with the relevant website and source evidence. Website Health helps you investigate access, readable content, rendering, metadata and discovery files. Crawler activity shows recorded classified visits and the delivery evidence available for them.
Review the page that answers the question, the competitors or sources mentioned, and any content gaps. A missing mention may lead to a technical repair, a clearer existing page, further research or no change. The evidence helps form a useful next step; it does not prove why a provider omitted the business.
Create full articles and improve existing work
Use retained answer evidence, website and business context, and available cited-source context to generate a complete article draft. Review the opportunity and confirm generation using the shared workspace allowance, then read and edit the full draft.
When an existing page is the better destination, use the findings to focus its improvement. Technical recommendations and generated discovery-file drafts need an authorized person to apply them. Creating another article is not automatically the right response to a visibility gap.
Where eligible, AI Ads can prepare copy and creative for a separate advertising workflow. Review and provider handoff remain necessary; an ad creative is not a published campaign.
Publish reviewed articles through a connected destination
Current Starter, Growth and Pro accounts support configured article publishing connections. Review and approve the article, then send a CMS draft where supported or explicitly confirm its release. Live publication and approved publication schedules have their own confirmations. A planning date alone does not publish.
| 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. |
The destination determines what PB can confirm. Verify a CMS page after publication; for Astro and Keystatic, the host still completes the deployment. A custom endpoint must provide its own publication workflow. See connections and prerequisites and the article workflow guide.
Edited articles need review again. Changes to the reviewed version, destination or authorizing access can stop a scheduled release. Autopilot publishing is not enabled.
Deliver content crawlers can read
Check that the approved page returns meaningful content, the intended status, title, description, canonical URL and crawlable links. A completed release step does not establish that every crawler can retrieve the result.
Managed prerendering delivers crawler-readable HTML when testing confirms a JavaScript rendering gap. A server-rendered or static website may already return complete HTML and need no additional rendering layer. Keep the existing website and hosting; connect rendering where the page evidence calls for it.
Monitor the website and measure again
Configure important public URLs, the available monitoring cadence and alert destination. Review dated health findings and incidents, recorded crawler-classified visits and later AI Visibility collections. Activity depends on the connected request path; a classified visit is not authenticated crawler identity or proof of an AI citation.
Keep the released URL and publication date with the work so you can revisit the relevant questions and compare observations. Scheduled page checks leave time between measurements. A later answer change is evidence to inspect, not proof that the article caused it or a guarantee of future recommendations.
Use the workflow that fits your team
- Web application: select websites, inspect evidence, create and review articles, connect publishing and follow results.
- CMS connections: deliver reviewed articles through the supported destination for the selected website.
- Buddy: explain available evidence and help choose a next step. It does not autonomously generate, publish, repair websites, change settings or spend money.
- Developer API: use scoped evidence, rendering and reviewed article actions, including confirmed generation, delivery and scheduling. Existing account allowances remain shared.
- MCP: the hosted server can prepare proposals and generate confirmed, unapproved drafts with authorized write access. The published local package provides diagnostics and workspace reads. Neither exposes article approval or publishing.
- CLI and browser extension: run focused public-page checks. They do not provide the complete authenticated publishing workflow.
- Open-source rendering engine: operate the rendering core in your own infrastructure. Hosted visibility, publishing, dashboard and billing workflows are separate.
- Optional account management: add setup help, monthly human review and reporting, bounded reviewed content outputs and approved publishing assistance. This is separate from managed rendering infrastructure.
Businesses, founders, marketers, agencies and technical teams can start with the relevant evidence and choose how much work to handle themselves. Review plans and effective access before choosing the workflows you need. PB does not guarantee indexing, rankings, citations, recommendations, traffic or revenue.