Prepare the frontend state
Save and publish the Divi 5 page state intended for review, or open its frontend preview and confirm the intended reviewer can reach it.
Send one review link for the browser-accessible frontend and collect contextual comments on the Divi 5 page your visitors will see—not inside the Visual Builder.












Loved by1,250+Agenciesand companies in 100+ countries
Divi 5 provides builder previews, history and role controls for people working inside WordPress. BugSmash keeps external feedback on the rendered frontend.
Four documented boundaries shape the review workflow:
The documented Divi 5 flow opens a published or new page from the WordPress dashboard with Use Divi Builder. That workflow requires site access.
Divi 5 Preview opens the page in a new tab without the Visual Builder interface. It shows the rendered page but is not documented as an external approval system.
Divi 5 documents Save as draft as saving the page without publishing it. A draft therefore should not be treated as a public review URL.
The Divi 5 Role Editor maps WordPress roles to builder permissions and can restrict features, settings tabs, modules and top-level options.
How it works
Save and publish the Divi 5 page state intended for review, or open its frontend preview and confirm the intended reviewer can reach it.
Paste the reachable frontend URL into BugSmash. Reviewers comment on the rendered page without opening the Visual Builder or WordPress dashboard.
Use each comment’s page, browser, operating-system and viewport context to update the layout, then save or publish the next state for review.
Pin feedback to the frontend output instead of asking reviewers to describe a Visual Builder location in a message.
Review desktop, tablet and phone widths while the build team uses Divi 5 device previews and any optional breakpoints it has enabled.
Keep the page URL, browser, operating system and viewport size with each website comment.
External reviewers do not need a WordPress role or access to the Divi 5 Role Editor and Visual Builder.
Divi 5 Save as draft does not publish. Send the frontend state that reviewers are actually expected to assess.
Use the Feedback Widget inside an authorized frontend when a public or directly reachable URL cannot represent the review flow.
The Visual Builder, its preview controls and the deployed frontend are distinct surfaces. Choose the browser URL the reviewer is authorized to reach.
| Your URL | Review by URL | What to do |
|---|---|---|
| Public published Divi 5 page | Works | Paste the public frontend URL and start the review. |
| Public Divi 5 site on a custom domain | Works | Use the browser-accessible frontend URL served on the domain. |
| Divi 5 Preview in a new tab | Access-dependent | Preview removes the Visual Builder interface. Confirm the reviewer can reach that frontend URL before sharing it. |
| Draft or unpublished Divi 5 page | Not publicly reviewable | Save as draft does not publish. Publish an approved review state, use the Feedback Widget in an authorized environment, or provide a static export. |
| Frontend behind application login or SSO | Use the widget | A pasted URL does not bypass application login or SSO. Install the Feedback Widget inside the authorized frontend experience. |
| Local or inaccessible staging site | Use an alternative | Use the Feedback Widget in the environment or upload a static export that reviewers can access. |
Add the BugSmash script to the WordPress frontend when reviewers need to comment within a draft, staging build or authenticated flow they are already authorized to use. Keep the Visual Builder and Role Editor limited to the editing team.
Review the rendered page while WordPress and Divi 5 permissions remain under the build team’s control.

Give clients a focused frontend review surface without assigning a role in the Divi 5 builder.
See how
Comment on page copy, visual hierarchy and responsive behavior at the URL intended for release.
See how
Receive page and environment context with each issue, then verify updates on the next published frontend state.
See howRoute an actionable comment to the delivery team with its page, selected location, browser, operating system and viewport context intact.
Context stays attached from comment to completion.
Send to your workflow
The destination changes. The context does not.
Keep the website beside campaign images, PDFs, presentations, videos and other release assets, 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 browser-accessible frontend state you want assessed. Divi 5 Preview opens the page in a new tab without the Visual Builder interface, but you should confirm that the reviewer can reach that URL.
Paste the reachable frontend URL and collect focused review comments without sharing Visual Builder access.
