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.
Get client feedback on your published Divi 5 page
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
The Divi 5 Visual Builder is an editing workspace, not a guest review link.
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:
Visual Builder access starts in WordPress.
The documented Divi 5 flow opens a published or new page from the WordPress dashboard with Use Divi Builder. That workflow requires site access.
Preview removes the builder interface.
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.
Save as draft does not publish.
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.
Role Editor controls builder capabilities.
The Divi 5 Role Editor maps WordPress roles to builder permissions and can restrict features, settings tabs, modules and top-level options.
BugSmash keeps reviewers out of the builder:How it works
Three steps to a reviewed Divi 5 page
Send one review link
Paste the reachable frontend URL into BugSmash. Reviewers comment on the rendered page without opening the Visual Builder or WordPress dashboard.
Apply and verify updates
Use each comment’s page, browser, operating-system and viewport context to update the layout, then save or publish the next state for review.
Review the Divi 5 frontend without sharing builder access
Comment on the rendered page
Pin feedback to the frontend output instead of asking reviewers to describe a Visual Builder location in a message.
Check responsive layouts
Review desktop, tablet and phone widths while the build team uses Divi 5 device previews and any optional breakpoints it has enabled.
Preserve technical context
Keep the page URL, browser, operating system and viewport size with each website comment.
Protect builder permissions
External reviewers do not need a WordPress role or access to the Divi 5 Role Editor and Visual Builder.
Separate drafts from review releases
Divi 5 Save as draft does not publish. Send the frontend state that reviewers are actually expected to assess.
Handle gated experiences with the widget
Use the Feedback Widget inside an authorized frontend when a public or directly reachable URL cannot represent the review flow.
Which Divi 5 URL should I review?
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. |
Installing the Feedback Widget on a Divi 5 site
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.
The feedback workflow for teams using Divi 5
Review the rendered page while WordPress and Divi 5 permissions remain under the build team’s control.
WordPress agencies
Give clients a focused frontend review surface without assigning a role in the Divi 5 builder.
See how
Design and marketing teams
Comment on page copy, visual hierarchy and responsive behavior at the URL intended for release.
See how
Developers and QA teams
Receive page and environment context with each issue, then verify updates on the next published frontend state.
See howMore platforms
Explore more website feedback workflows
Read the published workflow guide for another website builder, CMS, framework or AI site platform.
- Webflow website feedback guide
- Framer website feedback guide
- WordPress website feedback guide
- Shopify website feedback guide
- Squarespace website feedback guide
- Wix website feedback guide
- Bubble website feedback guide
- Replit website feedback guide
- Lovable website feedback guide
- Claude Artifacts website feedback guide
- Next.js website feedback guide
- React website feedback guide
Turn Divi 5 page feedback into trackable work
Route 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.
Jira
ClickUp
Monday
Asana
Trello
Slack
Linear
Todoist
Notion
Airtable
Zapier
Make
n8n
WebhooksThe Divi 5 page is one deliverable. Review the whole launch together.
Keep the website beside campaign images, PDFs, presentations, videos and other release assets, with feedback and approval in one project.
Website HTML Widget Video Audio Image PDF PPT Doc Email 3D Model CAD Mobile App - Canvas
Divi 5 website feedback, answered
What URL should I send for a Divi 5 review?
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.
Do reviewers need the Divi 5 Visual Builder?
Can reviewers check desktop, tablet and phone layouts?
Can I review a Divi 5 draft?
How do history and undo or redo affect review?
Do I need to change the Divi 5 Role Editor?
Can BugSmash review a Divi 5 page behind application login or SSO?
Does BugSmash replace Divi 5 Preview?
Ship Divi 5 pages without chasing feedback
Paste the reachable frontend URL and collect focused review comments without sharing Visual Builder access.
