Choose the exact published step
Open the website, blog page, funnel step, or public school page intended for review and copy its complete visitor-facing URL.
Paste the complete browser-accessible website, blog, or funnel-step URL, send one review link, and collect comments on the page visitors will actually open.












Loved by1,250+Agenciesand companies in 100+ countries
Systeme.io can build multi-page sites with its Websites feature and also documents blog and sales-funnel methods. BugSmash reviews the specific browser-accessible page or flow selected for the review.
Four documented boundaries matter before sending the link:
In the Websites feature, a new page starts in Draft mode. Publish makes it visible to visitors, while Unpublish deactivates it so visitors can no longer see it.
Systeme.io recommends a blog for regularly published content and many pages, and a sales funnel for a simple site with fewer pages. Pages also have configurable URL paths.
The View funnel step action opens a specific variant for preview, and Systeme.io says A/B testing logic is automatically disabled during that preview.
Systeme.io says a Stripe test purchase cannot be performed. Its documented check is a real low-priced purchase followed by a refund, and third-party fees may apply.
How it works
Open the website, blog page, funnel step, or public school page intended for review and copy its complete visitor-facing URL.
Paste that URL into BugSmash and share the resulting review link with stakeholders who can reach the selected page.
Use the attached URL, selected location, screenshot, browser, operating system, and viewport context, then revisit the intended funnel or member journey.
Attach feedback to a published page from the Websites feature rather than describing an editor element or menu item separately.
Use the full URL for the opt-in, sales, order, or follow-up step chosen for that review round.
In the website editor, switch among Desktop, Mobile portrait, and Mobile landscape previews before reviewing the published browser page.
Keep the page URL, screenshot, browser, operating system, and viewport with every report.
Comment on the public course catalog at the documented school path when the course has a sales page connected.
When the rendered frontend permits the BugSmash script to be installed, use the Feedback Widget for an enrolled student commenting inside an authorized course or dashboard session.
Choose the exact published page or state. A public school catalog, a funnel-step preview, a checkout, and an enrolled-student dashboard do not have the same access or behavior.
| Your URL | Review by URL | What to do |
|---|---|---|
| Published Website page or public blog page | Works | Paste the complete visitor-facing URL and start the review. |
| Public published sales funnel step | Works | Use the full funnel-step URL, including its path. |
| Public school page | Works | Review the public course catalog after the relevant courses have sales pages connected. |
| Specific A/B variant opened with View funnel step | Preview only | Use it to inspect that variant, not to validate live A/B routing or conversion behavior. |
| Course or student dashboard behind member login | Use the Widget | Pasting a URL does not bypass member login. If the script can be installed on the rendered frontend, use the Feedback Widget inside an authorized enrolled-student session. |
| Live checkout test purchase | Transaction required | Follow the documented real-purchase and refund process; a Stripe test purchase is not available and fees may apply. |
Where the rendered frontend permits the BugSmash script to be installed, use it when an authorized reviewer needs to comment inside a course, student dashboard, or other stateful session. Existing enrollment and login rules still apply.
Keep editing, funnel routing, enrollment, transaction checks, and stakeholder approval distinct while comments stay attached to the visible page.

Review copy, layout, and links on the intended website or funnel step before sending traffic.
See how
Review the public school page separately from enrolled-student course and dashboard experiences.
See how
Identify the exact step or variant and handle checkout tests through the documented purchase and refund process.
See howRoute an actionable page comment to the team with its visible location and browser context preserved.
Context stays attached from comment to completion.
Send to your workflow
The destination changes. The context does not.
Keep funnel pages beside campaign graphics, PDFs, videos, presentations, and course assets with one approval trail.

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.

Yes. Systeme.io documents a multi-page Websites feature as well as blog and sales-funnel methods. It recommends blogs for regularly published content and many pages, and funnels for a simple site with fewer pages.
Paste the exact published website or funnel-step URL and send a focused review link with the page context preserved.
