Prepare a reachable frontend
Save the intended Oxygen design, use the Preview Menu to open or copy the frontend URL, and confirm that the reviewer is authorized to reach it.
Send one review link for the browser-accessible frontend and collect contextual comments on the rendered WordPress experience—without giving reviewers Oxygen access.












Loved by1,250+Agenciesand companies in 100+ countries
Oxygen installs as a WordPress plugin and opens its builder from WordPress. Its documentation treats builder access as privileged, while BugSmash can keep review on the rendered site.
Four documented boundaries matter before you invite reviewers:
The documented workflow starts in WordPress Pages and uses Edit in Oxygen to open the builder. That is an editing path, not a public review surface.
Oxygen’s canvas is a live preview inside the builder. The Preview Menu can open the currently previewed item in a new tab or copy its URL for the frontend view.
Oxygen includes five default breakpoints and supports custom breakpoints, with canvas previews and breakpoint-specific style changes.
Oxygen warns that anyone with Oxygen access can use the Code Block element to execute arbitrary PHP and says not to grant Oxygen access to untrusted users.
How it works
Save the intended Oxygen design, use the Preview Menu to open or copy the frontend URL, and confirm that the reviewer is authorized to reach it.
Paste the reachable frontend URL into BugSmash. Reviewers comment on the rendered page without entering WordPress or using Edit in Oxygen.
Use each comment’s page and environment context to make changes. Oxygen revisions preserve saved versions that can be loaded, restored and saved again.
Pin feedback to the page visitors use instead of asking external reviewers to navigate the Oxygen builder.
Review responsive behavior while the build team checks Desktop, Tablet Landscape, Tablet Portrait, Phone Landscape, Phone Portrait and any custom breakpoints.
Keep the page URL, browser, operating system and viewport size with each website comment.
Collect frontend feedback without giving reviewers access to WordPress, Oxygen or its PHP-capable Code Block element.
Oxygen’s revisions list saved versions of a page and lets the build team load, restore and save a selected revision.
Install the Feedback Widget inside a stateful or gated frontend when the pasted URL cannot open the authorized user experience.
Choose the rendered frontend the reviewer can reach. The WordPress editing path and Oxygen builder are not external review surfaces.
| Your URL | Review by URL | What to do |
|---|---|---|
| Public deployed Oxygen frontend | Works | Paste the public frontend URL and start the review. |
| Public Oxygen site on a custom domain | Works | Use the browser-accessible frontend URL served on the domain. |
| Frontend opened or copied from Preview Menu | Access-dependent | Confirm the intended reviewer can reach the URL outside the builder, then use it for the review. |
| WordPress or Oxygen builder screen | Do not share | Review the rendered frontend instead. Oxygen explicitly warns against granting Oxygen access to untrusted users. |
| 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. |
| Local or otherwise inaccessible design | 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 rendered WordPress frontend when reviewers need to comment in a local, staging, draft or authenticated state they are already authorized to use. Keep Oxygen access restricted to trusted builders.
Let stakeholders review the rendered experience while trusted builders retain control of WordPress, Oxygen and saved revisions.

Collect client comments on the frontend without handing over Oxygen or WordPress administration access.
See how
Review copy, layout and responsive behavior at the browser URL intended for the current release.
See how
Receive page, browser, operating-system and viewport context, then use Oxygen’s revision workflow while applying fixes.
See howRoute an actionable comment to the delivery 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 campaign images, PDFs, presentations, videos 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 reachable rendered frontend you want assessed. Oxygen’s Preview Menu can open the currently previewed item in a new tab or copy its URL; confirm the reviewer can reach it outside the builder.
Paste the reachable frontend URL and collect contextual review comments without granting Oxygen access.
