Choose the frontend state
Publish the page or select another browser-accessible frontend URL that accurately represents the review round. Keep draft and editor access separate.
Paste the browser-accessible frontend URL, send one review link, and collect contextual comments on the page your visitors will see—without adding reviewers to the Elementor editor.












Loved by1,250+Agenciesand companies in 100+ countries
Elementor includes contextual Notes for collaboration inside its site workflow. BugSmash provides a separate review link for a browser-accessible frontend.
Before choosing a review URL, four documented boundaries matter:
Elementor explicitly notes that its Preview link differs from the actual page link. Use the URL that represents the frontend state you want reviewers to evaluate.
A published Elementor page can be edited and saved as a draft without changing the published page. A draft or private page still requires the reviewer to have the necessary site access.
Elementor Notes can pin contextual feedback to elements, but they are designed for logged-in users on the site. A user without access to a draft or private page cannot be mentioned in its Notes.
Elementor Role Manager can block a role from opening the editor or limit it to editing existing content. External review should not require changing those editor permissions.
How it works
Publish the page or select another browser-accessible frontend URL that accurately represents the review round. Keep draft and editor access separate.
Paste that URL into BugSmash and share the resulting review link. Reviewers can comment on the rendered page without entering WordPress or Elementor.
Use the attached browser, operating-system, viewport and page context to make changes, then save or publish the next Elementor revision for review.
Attach feedback to the browser-accessible Elementor frontend instead of describing the issue in a separate message.
Review desktop, tablet and mobile viewport widths alongside Elementor Responsive Mode and any custom breakpoints configured by the build team.
Keep the page URL, browser, operating system and viewport size with each website comment.
Let clients review the frontend without changing WordPress roles or Elementor Role Manager permissions.
Elementor creates revisions when a page is saved or published; BugSmash keeps discussion tied to the frontend state sent for that review round.
Add the BugSmash Feedback Widget when reviewers need to comment inside a logged-in or stateful frontend that a pasted URL cannot open.
Choose a URL based on what the reviewer can reach in a browser. Elementor editor access and frontend review access are separate decisions.
| Your URL | Review by URL | What to do |
|---|---|---|
| Public published Elementor page | Works | Paste the actual public page URL and start the review. |
| Public Elementor site on a custom domain | Works | Use the browser-accessible frontend URL served on the domain. |
| Elementor Preview link | Access-dependent | Elementor says the Preview link differs from the actual page link. Confirm the intended reviewer can open it, or use the actual frontend URL. |
| Draft or private Elementor page | Access-dependent | Users without access cannot open a draft or private page. Use the Feedback Widget on an authorized review 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 authenticated experience. |
| Local or otherwise inaccessible page | Use an alternative | Use the Feedback Widget in the environment or upload a static export that reviewers can reach. |
Add the BugSmash script to the WordPress frontend when reviewers need to comment on a draft, staging state, or authenticated flow they are already authorized to use. Elementor Notes can remain the logged-in site-user workflow; the widget keeps feedback on the rendered experience.
Keep build permissions, frontend review, and client approval distinct while everyone comments on the same rendered page.

Send clients a frontend review link without granting access to WP Admin or expanding Elementor editor permissions.
See how
Review page copy, layout and responsive behavior on the published or staging frontend with every comment in context.
See how
Receive the URL, browser, operating system and viewport details needed to reproduce issues before the next publish.
See howRoute an actionable website comment to the team with its page, selected location, browser, operating system and viewport context preserved.
Context stays attached from comment to completion.
Send to your workflow
The destination changes. The context does not.
Keep the website beside the campaign images, PDFs, videos, presentations and other launch 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.

Use the URL that represents the frontend state you want reviewed. Elementor explicitly says the Preview link is different than the actual page link, so confirm access before sending either one.
Paste the browser-accessible frontend URL and send a focused review link without opening the Elementor editor to reviewers.
