BlackFriday

50% offon all annual plans

00d00h00m00s
Explore plans
Your AI Agents can now act on comments added in BugSmash with our MCP. See How it works.
Bricks Builder logo

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.

https://

Use the published frontend URL, not the Bricks builder. Saving an unpublished draft does not publish it; use the Publish control when the page is ready.

Knauf
Radancy
Frontier
City of Boroondara
Berlin Heart
GVBOCES
Bville
Frost Collective
Mediapilote
Medwiki
Musaffa
Sharp Guys Web Design

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:

  1. 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.

  2. 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.

  3. 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.

  4. 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

1

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.

2

Send one review link

Paste the published WordPress URL into BugSmash and share the resulting link without granting every reviewer builder access.

3

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 URLReview by URLWhat to do
Public published Bricks page WorksPaste the visitor-facing page URL and start the review.
Public WordPress staging frontend WorksUse the staging URL after confirming the intended published state is reachable.
Site protected by supported Basic Auth WorksUse the browser-accessible Basic Auth URL; BugSmash lists Basic Auth-protected websites as supported.
Saved but unpublished Bricks draft Not publishedPublish the page to an accessible frontend before starting external review.
Frontend behind login or SSO Use the WidgetPasting 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 surfaceShare 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.

Turn Bricks feedback into trackable work

Route actionable frontend comments to the team with their visible location and browser context preserved.

Context stays attached from comment to completion.

Send to your workflow

The destination changes. The context does not.

Jira
ClickUp
Monday
Asana
Trello
Slack
Linear
Todoist
Notion
Airtable
Zapier
Make
n8n
Webhooks

The Bricks page is one deliverable. Review the complete launch together.

Keep the website beside campaign graphics, PDFs, videos, presentations, and other client assets with one approval trail.

  • Website
  • HTML
  • Widget
  • Video
  • Audio
  • Image
  • PDF
  • PPT
  • Doc
  • Email
  • 3D Model
  • CAD
  • Mobile App
  • Canvas

Bricks Builder feedback, answered

How often does Bricks autosave?

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.

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 website review interface with comment controls