Use the Prerender Buddy Chrome extension

Add Prerender Buddy from the Chrome Web Store. Basic extension checks do not require a PB account.

The extension is a focused page-checking companion. The wider Prerender Buddy platform connects AI Visibility, website health, crawler evidence, full articles and reviewed publishing. Read How PB Works.

1. Open an appropriate public HTTP or HTTPS page in Chrome.
2. Select the extension to open its side panel. Opening the panel starts a check of the current supported page.
3. Review the score, summary and grouped checks.
4. After changing tabs or page URLs, use the check button to inspect the newly selected page. A changed URL resets the previous result.
5. Choose Open PB workspace when you want to add the website or continue with account features.

Browser-internal and non-HTTP pages are unsupported. Do not run checks on private dashboards, previews or URLs containing credentials or private tokens.

The current extension returns a score, summary and grouped signals for crawler access, crawler content, indexability and the available rendering comparison. These are bounded summaries; the extension does not display every raw measurement, heading or metadata field.

The toolbar badge shows the current result's score. A reset or loading badge is not a completed result, and an error indicator means the check did not complete.

A repeat check may use a cached public audit. Treat the score as a summary of that observation and use PB's detailed page evidence when diagnosing a recent deployment. An unavailable rendering comparison remains unavailable; it is not evidence that no gap exists.

The extension sends the selected page URL to PB's public page-check API. PB fetches public content and records bounded diagnostic events. It does not send the signed-in page's DOM, form values or browser cookies with that check, and does not modify the website.

The released extension uses active-tab, tab and side-panel access. Its manifest does not request Chrome's history or cookie permissions. Reading the selected URL and fetching public website content are still data handling; see the privacy policy and Chrome Web Store disclosure.

Crawler-profile diagnostics do not authenticate a crawler operator or prove indexing. A readability score does not measure brand mentions, citations or recommendations in AI answers and does not guarantee rankings, traffic or AI visibility.

The extension does not itself run workspace AI collections, generate articles or publish content. Those capabilities belong to authorized platform workflows. AI Visibility, Article Generation and publishing integrations explain them.

Use the public tools for a focused web-based check. For a rendering or access problem, follow setup and troubleshooting before changing the website.

If a check is temporarily limited, follow its retry guidance rather than treating it as a website failure. Account access and allowances apply when you continue into the web application.

Developer tools explains the separate CLI, hosted/local MCP and rendering-engine boundaries.