Publish and verify the intended page
Publish the page, then open its URL in a different browser or incognito window to confirm the visitor-facing state without the admin preview banner.
Paste the visitor-facing URL for a published Kajabi website or landing page, send one review link, and collect comments on the experience visitors will actually see.












Loved by1,250+Agenciesand companies in 100+ countries
Kajabi provides page and device previews for site owners, while the visitor and customer experiences depend on publication, login, purchases, grants, and membership.
Four documented boundaries matter before sharing a review:
Kajabi says its preview displays a preview link and banner. To test as a visitor, log out and use a different browser or incognito/private window.
Kajabi states that an unpublished page cannot be tested by entering its link in an incognito or private window.
Kajabi can set Template Home, Login, a Landing Page, or the Store as the root homepage, so confirm which browser experience the domain currently opens.
A test customer can be used to preview the customer experience. Products that were purchased or granted appear in that customer's Library.
How it works
Publish the page, then open its URL in a different browser or incognito window to confirm the visitor-facing state without the admin preview banner.
Paste the published public URL into BugSmash and share the generated link with stakeholders who can reach that page.
Use the attached page, selected location, screenshot, browser, operating system, and viewport context, then retest public and customer-only states separately.
Attach feedback to the visitor-facing page instead of describing a section in a separate message.
Use the full published Landing Page URL selected for the campaign or review round.
Review mobile browser widths alongside the device views available in Kajabi's page and product previews.
Keep the page URL, screenshot, browser, operating system, and viewport with every website comment.
Use a controlled test customer to inspect the Library and products that have been purchased or granted.
When the rendered experience permits the BugSmash script to be installed, use the Feedback Widget for an authorized test customer or member inside a logged-in product or community.
Choose the URL and account state that represent the intended audience. Public pages and logged-in customer areas require different review setups.
| Your URL | Review by URL | What to do |
|---|---|---|
| Public published Kajabi website page | Works | Paste the visitor-facing URL after checking it in a different browser or incognito window. |
| Public published Kajabi landing page | Works | Use the full published landing-page URL selected for the campaign. |
| Public homepage set to Template Home, Landing Page, or Store | Works | Review the root domain after confirming the homepage selection in Kajabi. |
| Admin page or product preview | Preview only | Use it for owner-side checks, then publish and test the visitor or customer experience separately. |
| Library, product, course, coaching, or community behind member login | Use the Widget | Pasting a URL does not bypass member login. If the script can be installed on the rendered experience, use the Feedback Widget inside an authorized test-customer or member session. |
| Unpublished page opened in incognito | Unavailable | Publish the page first; Kajabi says an unpublished page cannot be tested this way. |
Where the rendered Kajabi experience permits the BugSmash script to be installed, use it when an authorized test customer or member needs to comment inside a Library, product, course, coaching, or community session.
Keep site editing, admin preview, public-page review, and authenticated customer testing distinct while comments stay attached to the intended browser experience.

Review published website and landing-page copy, layout, and mobile presentation before promotion.
See how
Use controlled test customers or members for product, Library, coaching, and community checks.
See how
Verify the visitor experience outside the admin browser and keep public and authenticated reports clearly separated.
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 website pages beside course assets, campaign graphics, PDFs, videos, and presentations 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.

No. Kajabi says preview displays a preview link and banner. Log out and use a different browser or incognito/private window to test the visitor experience.
Paste a published visitor-facing URL and send a focused review link, then test customer-only experiences with controlled access.
