Your AI Agents can now act on comments added in BugSmash with our MCP. See How it works.
Collect visual feedback on a website built with Strapi. Create a BugSmash Website project with a public URL or a site protected by Basic Auth, then share its review link for contextual comments. Other application logins, SSO, CAPTCHA, VPN and network restrictions may require the Feedback Widget or HTML workflow. This is not a native Strapi integration: BugSmash reviews the resulting browser page and does not connect to Strapi itself. Use the separately implemented frontend or a configured Preview link. The Strapi admin panel, Draft & Publish state, API permissions and frontend authentication remain separate controls. https://your-strapi-powered-site.com Platform clarification: this is a generic BugSmash Website project workflow, not a native Strapi integration. Public URLs and supported Basic Auth sites can use the Website project workflow.
Get client feedback on your Strapi-powered frontend
Paste the deployed website or an accessible configured preview URL, send one review link, and collect contextual comments on the rendered front-end application.
Loved by1,250+Agenciesand companies in 100+ countries
Strapi manages content and APIs. Review happens on the connected frontend.
Strapi separates the admin panel, Content APIs, Draft & Publish state, Preview configuration and the visitor-facing application.
Four documented boundaries matter before stakeholder review:
01
The frontend application must already exist.
Strapi Preview connects the Content Manager to a front-end application. The documentation requires that frontend to be created and set up before Preview is configured.
02
Preview requires project configuration.
The admin configuration enables Preview, restricts embedding with allowedOrigins, and supplies a handler that returns the correct frontend URL for each supported content type.
03
Draft & Publish is configured per content type.
The feature is available but disabled by default. When enabled, Strapi separates draft, modified and published content states.
04
Live Preview has plan and maturity limits.
Full-screen Preview is available on the Free plan. The enhanced Live Preview is available on Growth and Enterprise plans and is currently documented as experimental.
BugSmash keeps feedback on the browser result:
share the accessible frontend or configured preview URL, retain page context, and leave Strapi content, permissions and publication state unchanged.
How it works
Three steps to a reviewed Strapi-powered release
11
Prepare the frontend state
Deploy the frontend for published content, or configure Strapi Preview and the framework-specific preview route needed to render a draft.
22
Send one BugSmash link
Paste the accessible frontend or copied preview URL into BugSmash and share the generated review link with stakeholders.
33
Publish and verify the approved result
Apply the approved content or frontend changes, publish the intended entries, and verify the resulting visitor-facing page.
Review the Strapi-powered frontend, not the admin panel
Comment on the rendered frontend
Attach feedback to the page location visitors see rather than describing a Content Manager field in a separate message.
Review published entries
Use the normal deployed frontend when the review should reflect Strapi’s published content state.
Review configured draft previews
Use a preview URL only after the project’s frontend route and draft-aware data fetching have been implemented.
Check responsive layouts
Review desktop, tablet and mobile presentation and retain the viewport with each comment.
Capture technical context
Keep the page URL, browser, operating system, viewport and screenshot with each website comment.
Keep admin access separate
External reviewers can comment on an accessible frontend without receiving a Strapi administrator account.
Which Strapi-related URL should I review?
Use the separately implemented frontend or a deliberately configured preview URL. Strapi admin access, API permissions, preview secrets and frontend authentication remain separate.
Your URL
Review by URL
What to do
Public Strapi-powered frontend
Works
Paste the visitor-facing website or application URL into BugSmash.
Accessible staging frontend
Works
Use the staging URL after confirming every intended reviewer can open it.
Configured Strapi preview link
Works when accessible
Copy the draft or published preview link after the project’s preview handler and frontend route are configured.
Live Preview inside the admin panel
Strapi access required
Use a configured frontend preview link for external review; Live Preview remains embedded in the Content Manager.
Protected or authenticated frontend
Access-dependent
Authenticate in the review session or use the Feedback Widget. A pasted URL does not bypass frontend authentication.
Strapi admin or Content API URL
Not the visitor website
Review the frontend application that renders the content instead of the admin panel or an API response.
Using the Feedback Widget on a Strapi-powered frontend
Add the BugSmash Feedback Widget to the rendered frontend when reviewers must stay inside an authenticated or stateful experience. Install it in the front-end application, not in the Strapi admin panel or Content API.
The feedback workflow for teams using Strapi
Keep content modeling and editing in Strapi while clients, product teams and QA review the connected browser experience.
Ship faster togetherThe all-in-one workspace for product teams.
Get started free
MayaMake this hero image full-bleed
Live WebsiteURL
product-launch.mp4
0:42 / 3:15
LeoTrim the intro to 0:03
VideoMP4
sneaker.glb
AvaSmooth these edges a bit
3D ModelGLB · GLTF
Quarterly Review
Q3 Performance
Revenue up 24%1.2k new usersNPS score 62Churn down 3%
BugSmash3 / 18
SamUpdate the Q3 numbers
Slide DeckPPT
Your summer sale starts now 🌞
A
Acme Store
to you
9:24 AM
Up to 40% off
Summer essentials, restocked
Shop the sale
NoahStronger CTA copy here
EmailHTML
9:41
Good morning
Dashboard
Balance
$4,280
ZoeAlign the chart legend
Mobile AppAndroid · iOS
Annual Report2025 in review
This 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.
Fig 1. Coastal expansion, 2025
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.
Which URL should I send for a Strapi-powered site review?
Send the separately implemented frontend URL. For draft content, use a preview link only after the Strapi handler and the frontend’s draft-preview behavior are configured.
Does Strapi create the visitor-facing frontend?
No. Strapi’s Preview documentation requires a front-end application to be created and set up, then connects that application to the Content Manager.
How is Strapi Preview configured?
The project enables Preview in its admin configuration, declares allowedOrigins for the frontend, and implements a handler that returns the appropriate preview URL.
How does Draft & Publish separate content states?
When enabled for a content type, the editable draft can differ from the read-only published version. Publishing makes the saved draft the published version.
Is Strapi Preview available on the Free plan?
Yes. Strapi documents full-screen Preview as a free feature. The enhanced side-by-side Live Preview is available on Growth and Enterprise plans.
Is Strapi Live Preview experimental?
Yes. Strapi currently labels the enhanced Live Preview as experimental and documents limitations including unsupported dynamic-zone fields and no double-click editing with GraphQL.
Can Preview switch between draft and published content?
Yes. When Draft & Publish is enabled, the Preview interface can switch between draft and published versions, and the frontend must fetch the matching state.
Does BugSmash publish entries or change Strapi permissions?
No. Strapi continues to control content, publication state, API access, users and preview configuration. BugSmash records contextual feedback on an accessible rendered frontend.
Ship Strapi-powered sites without chasing feedback
Paste an accessible deployed frontend or configured preview URL and send a focused review link.
BugSmash keeps feedback on the browser result:
Jira
ClickUp
Monday
Asana
Trello
Slack
Linear
Todoist
Notion
Airtable
Zapier
Make
n8n
Webhooks
MayaMake this hero image full-bleed
product-launch.mp4
LeoTrim the intro to 0:03
AvaSmooth these edges a bit
SamUpdate the Q3 numbers
Up to 40% off
NoahStronger CTA copy here
ZoeAlign the chart legend
EllaTighten this paragraph
TheoBoost the warm tones
MiaCut the dead air at 1:12