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 Bricks Builder. 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 Bricks Builder integration: BugSmash reviews the resulting browser page and does not connect to Bricks Builder itself. Use the published Bricks frontend URL, not WP Admin or the builder. Saving an unpublished draft does not publish it, and Bricks builder access remains a separate permission decision. https://your-site.com Platform clarification: this is a generic BugSmash Website project workflow, not a native Bricks Builder integration. Public URLs and supported Basic Auth sites can use the Website project workflow.
Get contextual feedback on your published Bricks frontend
Paste the browser-accessible WordPress URL, send one review link, and collect comments on the Bricks-built page visitors will actually see.
Loved by1,250+Agenciesand companies in 100+ countries
Bricks saving, publishing, revisions, and builder access are separate.
Bricks runs its editing workflow inside WordPress. BugSmash reviews the rendered frontend selected for the review round rather than the builder interface.
Four documented boundaries matter before sharing the page:
01
Autosave is not publication.
Bricks creates an autosave every 60 seconds by default when the current builder area has unsaved element changes. That backup does not publish a draft.
02
Saving a draft does not change its status.
An unpublished page remains unpublished when saved. Bricks requires the Publish control when the page is ready to go live.
03
Manual saves create revision snapshots.
When changed Bricks data or page settings are saved, Bricks creates a revision or snapshot using the standard WordPress Revisions API.
04
Builder access has separate permission levels.
Bricks documents Full access, Edit content, and No access profiles, plus customizable builder capabilities.
BugSmash keeps stakeholder review on the frontend:
share the published page, keep Bricks permissions with the build team, and, when the script is installed on the rendered frontend, use the Feedback Widget for an authenticated state a pasted URL cannot open.
How it works
Three steps to a reviewed Bricks page
11
Save and publish the intended state
Use the Bricks save workflow for the intended revision, then publish the page when stakeholders should be able to review it on the frontend.
22
Send one review link
Paste the published WordPress URL into BugSmash and share the resulting link without granting every reviewer builder access.
33
Resolve comments and publish updates
Use the attached page, selected location, screenshot, browser, operating system, and viewport context to make and publish the next change.
Review the published Bricks frontend
Comment on rendered pages
Attach each note to the visible frontend rather than describing an element name or builder panel.
Check responsive breakpoints
Review the output around the documented Desktop, Tablet portrait, Mobile landscape, and Mobile portrait breakpoints.
Capture technical context
Keep the page URL, screenshot, browser, operating system, and viewport with every report.
Separate review from builder roles
Collect frontend feedback without assigning Full access or Edit content permissions to external reviewers.
Align feedback with revisions
Use an intentional saved and published state so the reviewed frontend can be related to the relevant WordPress-backed revision.
Use the widget for gated experiences
When the rendered frontend permits the BugSmash script to be installed, use the Feedback Widget inside a session the reviewer is already authorized to use.
Which Bricks URL should I review?
Choose a visitor-facing WordPress URL representing the published state. Bricks builder permissions do not make an inaccessible frontend public.
Your URL
Review by URL
What to do
Public published Bricks page
Works
Paste the visitor-facing page URL and start the review.
Public WordPress staging frontend
Works
Use the staging URL after confirming the intended published state is reachable.
Site protected by supported Basic Auth
Works
Use the browser-accessible Basic Auth URL; BugSmash lists Basic Auth-protected websites as supported.
Saved but unpublished Bricks draft
Not published
Publish the page to an accessible frontend before starting external review.
Frontend behind login or SSO
Use the Widget
Pasting a URL does not bypass application login or SSO. If the script can be installed on the rendered frontend, use the Feedback Widget inside the authenticated session.
Bricks builder or WP Admin URL
Not the review surface
Share the rendered frontend instead of changing builder permissions for visual feedback.
Installing the Feedback Widget on a Bricks site
Where the WordPress frontend permits the BugSmash script to be installed, use it when authorized reviewers need to comment inside a logged-in or stateful experience. Existing site access still controls which pages they can reach.
The feedback workflow for teams using Bricks Builder
Keep building, revisions, WordPress permissions, frontend review, and approval distinct while every comment stays on the rendered page.
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.
By default, Bricks creates an autosave every 60 seconds when the current builder area has unsaved element changes. The interval can be changed or disabled in Bricks settings.
Does saving an unpublished Bricks page publish it?
No. Bricks says the draft status does not change when the page is saved. Use the Publish control when it is ready.
How are Bricks revisions created?
Saving changed Bricks data or page settings creates a revision or snapshot through the standard WordPress Revisions API.
What are the default Bricks responsive breakpoints?
The documented defaults are Desktop, Tablet portrait below 992px, Mobile landscape below 768px, and Mobile portrait below 478px. Bricks also supports custom breakpoints.
How do responsive styles inherit?
Bricks documents styles cascading from the base breakpoint to smaller breakpoints unless a value is changed at a smaller breakpoint.
What builder access profiles does Bricks provide?
Bricks documents Full access, Edit content, and No access profiles, as well as custom capability controls.
Do reviewers need Bricks builder access?
No. They can review the published WordPress frontend. Builder permissions remain separate from the browser review.
Can BugSmash bypass a login?
Pasting a URL does not bypass application login or SSO. If the script can be installed on the rendered frontend, use the Feedback Widget inside a session the reviewer is authorized to access.
Ship Bricks-built pages without chasing feedback
Paste a published WordPress frontend URL and send a focused review link without opening the Bricks builder to every stakeholder.
BugSmash keeps stakeholder review on the frontend:
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