Publish the intended page state
Choose the built-in publishing domain or a connected custom domain, publish the page, and copy the URL that represents this review round.
Paste the browser-accessible landing-page URL, send one review link, and collect contextual comments on the page visitors will see—without adding reviewers as Leadpages account users.












Loved by1,250+Agenciesand companies in 100+ countries
Page Studio provides editing, device views, preview and publishing controls. BugSmash reviews the browser-accessible page state that you choose to share.
Before sending a landing page for review, four documented boundaries matter:
A page moves from Draft to Published when you publish it. If you unpublish it, the URL returns a 404 while Leadpages preserves the page content in the account.
Leadpages says its built-in lpcontent.net Preview URL is a live, fully functional page that can collect leads or sales. The banner recommends a custom domain; it does not make the page a private preview.
Leadpages says Page Studio supports Core integrations only, is not integrated with the Leadpages WordPress plugin, supports Global Scripts only in Classic Builder, and has split testing for Page Studio in development.
Current Leadpages documentation says account users have administrator permissions. Do not add an external reviewer expecting a restricted view-only role.
How it works
Choose the built-in publishing domain or a connected custom domain, publish the page, and copy the URL that represents this review round.
Paste the browser-accessible page URL into BugSmash and share the resulting review link without creating Leadpages administrator access for reviewers.
Use the attached browser, operating-system, viewport and page context to update Page Studio, then publish the finished changes for the next review.
Attach feedback to the browser-accessible Leadpages page instead of describing the location in a separate message.
Review desktop, tablet and mobile viewport sizes alongside the Page Studio device views and responsive settings used by the build team.
Keep the page URL, browser, operating system and viewport size with each website comment.
Collect external feedback without adding reviewers as Leadpages users who currently receive administrator permissions.
Leadpages marks when a live page has draft changes since its last publish; send the published state intended for the review round.
Add the BugSmash Feedback Widget when reviewers need to comment inside an authorized, logged-in or stateful experience.
Choose a published page URL that represents the state reviewers should see, and verify that they can reach it in their browsers.
| Your URL | Review by URL | What to do |
|---|---|---|
| Published page on the built-in domain | Works | Copy the published URL from Leadpages and use it for the review. |
| Published page on a custom domain | Works | Use the connected-domain URL intended for visitors. |
| lpcontent.net “Preview URL” | Works | Despite the banner, Leadpages says this is a live and fully functional published page. Share it only when it is the intended review URL. |
| Draft or unpublished Leadpages page | Not publicly available | Publish the intended state first. An unpublished page returns a 404, although its content remains saved in Leadpages. |
| Page 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 experience. |
| Local or otherwise inaccessible work | Use an alternative | Publish an appropriate browser-accessible state, use the Feedback Widget in the environment, or provide a static export reviewers can reach. |
Add the BugSmash script to a frontend where reviewers already have authorized access when a logged-in or stateful experience cannot be reviewed from a pasted URL. Leadpages account permissions remain separate from frontend feedback.
Keep page building, published-page review, and stakeholder approval distinct while every comment stays attached to the rendered landing page.

Review landing-page copy, layout and responsive presentation on the published URL before sending campaign traffic.
See how
Send clients one frontend review link instead of adding them as Leadpages users with administrator permissions.
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 Leadpages page beside 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.

Send the published URL that represents the page state you want reviewed. It can use the built-in Leadpages publishing domain or a connected custom domain.
Paste the browser-accessible published URL and send a focused review link without adding reviewers as Leadpages administrators.
