Prepare the rendered site state
Deploy the Statamic application or static output, or implement the preview target and token-aware frontend needed for work-in-progress content.
Paste the deployed site, an accessible staging environment, or an implemented headless preview target and collect contextual comments on the rendered experience.












Loved by1,250+Agenciesand companies in 100+ countries
Statamic separates its Control Panel, work-in-progress Live Preview, published frontend, optional content APIs and deployment configuration.
Four documented boundaries matter before stakeholder review:
Statamic Live Preview uses the currently loaded template, updates while an editor works, supports configured device sizes and can be opened in a separate window.
A collection can define one or more preview targets, such as an entry page and an index page. Without targets, Statamic uses the entry URL.
For a frontend framework, Statamic can point a preview target at a custom URL and automatically append a token query parameter that the frontend passes back when requesting preview content.
When enabled, Revisions adds unpublished, working-copy, revision and published states so editors can review, restore and publish changes without editing the live entry directly.
How it works
Deploy the Statamic application or static output, or implement the preview target and token-aware frontend needed for work-in-progress content.
Paste the accessible deployed, staging or implemented preview URL into BugSmash and share the generated review link.
Publish the approved entry or deployment, clear or warm caches when the project requires it, and verify the resulting visitor URL.
Attach feedback to the page location visitors see instead of describing a Control Panel field in a separate message.
Use the browser URL of a Statamic application deployed like a standard Laravel application.
Use the deployed static URL when the project generates and hosts Statamic as a static site.
Use a configured preview route after the frontend knows how to consume Statamic’s preview token.
Review desktop, tablet and mobile presentation and retain the viewport with each comment.
Keep the page URL, browser, operating system, viewport and screenshot with each website comment.
Use the deployed frontend or a deliberately implemented preview target. Control Panel access, preview tokens, content protection and hosting rules remain separate.
| Your URL | Review by URL | What to do |
|---|---|---|
| Public deployed Statamic frontend | Works | Paste the visitor-facing website URL into BugSmash. |
| Accessible staging frontend | Works | Use the staging URL after confirming every intended reviewer can open it. |
| Implemented headless preview target | Configuration-dependent | Use the preview target after its token-aware frontend data flow is working. |
| Live Preview in the Control Panel | Control Panel workflow | Use Live Preview for editorial work; use an accessible frontend or deliberately configured preview target for stakeholder review. |
| Protected or authenticated frontend | Access-dependent | Authenticate in the review session or use the Feedback Widget. A pasted URL does not bypass Statamic content protection. |
| Statamic REST API endpoint | JSON, not the rendered site | Review the frontend that presents API content instead of the read-only JSON response. |
Add the BugSmash Feedback Widget to the rendered Statamic frontend when reviewers must stay inside an authenticated or stateful experience. Install it in the website, not in the Control Panel or a REST API response.
Keep content authoring and revisions in Statamic while clients, developers and QA review the rendered browser experience.

Use Live Preview and, when enabled, Revisions for authoring, then collect stakeholder comments on the relevant rendered site state.
See how
Share the deployed frontend or implemented preview target while keeping Control Panel access and preview-token handling within the project.
See how
Review responsive pages, cached output and content-driven flows with the browser context needed to reproduce each issue.
See howRoute an actionable website comment with its page URL, selected location, screenshot, browser, operating system and viewport context preserved.
Context stays attached from comment to completion.
Send to your workflow
The destination changes. The context does not.
Keep the website beside content PDFs, images, videos, presentations and release materials, with feedback and approval in one project.

product-launch.mp4
Up to 40% offThis year marked our strongest period of growth to date. Revenue climbed 42% year over year while our customer base expanded across eleven new markets, driven by continued investment in product.

Operational efficiency improved as automated workflows reduced manual review time by nearly a third. Looking ahead, we plan to double down on infrastructure, deepen key partnerships, and ship the roadmap our customers have been asking for.

Send the deployed frontend URL. For work-in-progress content, use a preview target only after its route and token-aware frontend behavior are configured.
Paste an accessible deployed frontend or implemented preview target and send a focused review link.
