Use Buddy with your website evidence

Ask Buddy about saved site evidence and distinguish its advice from the platform's reviewed article and CMS publishing actions.

On this page

Select the right context

Buddy is the PB agent for explaining approved product knowledge and available account evidence. Choose the website before asking a site-specific question. Include the feature, affected URL, evidence date and expected behavior. Keep passwords, complete API keys, payment details and unrelated personal data out of messages.

Ask evidence-focused questions

Ask Buddy to explain a Health warning, interpret saved visibility evidence, discuss an article opportunity, clarify why a feature is unavailable, or identify what should be verified next. Follow up when a date, denominator, source or recommendation is unclear.

Available evidence is bounded. Open the original feature view for details that were not supplied to Buddy; an explanation does not establish that a fresh check was run.

Know the boundary

Buddy does not autonomously generate, approve, schedule or publish articles, change settings, repair websites, connect ad accounts or spend money. Its advice is a next-step suggestion, not evidence an action was performed. Deleting a chat does not restore usage already consumed.

This is Buddy's action boundary. Prerender Buddy has separate full-article generation, review and publishing workflows. With an eligible account and configured supported destination, you can send an approved article as a CMS draft, explicitly publish it or confirm its publication schedule. See the article and calendar guide and publishing integrations.

Use the right tool for an action

The web application and Developer API provide reviewed publishing actions with their own requirements. Hosted MCP can prepare proposals and generate explicitly confirmed, unapproved article drafts with authorized content-write access; it does not approve or publish them. The published local MCP package supplies public diagnostics and workspace reads. See the developer tools overview for the different surfaces.

When evidence is unavailable, open the relevant feature or rerun the appropriate check instead of treating absence as a result. Verify any applied change through the relevant workflow and its recorded result.