Get contextual feedback on your published Instapage page

Q: Is Page Demo intended for a live campaign?

No. Instapage describes pagedemo.co as a testing option and says it does not recommend running ads or campaigns to those URLs.

Q: What limits apply to Page Demo?

Instapage documents a limit of 30 requests per minute per IP and says free-trial Page Demo pages are automatically unpublished. Its official publishing articles currently give different durations, so this page does not state one as definitive.

Q: How do I push Instapage edits live?

Click the orange Update button. Instapage says it can take a few minutes for the changes to appear on the live page.

Q: Can I review a page before using my custom domain?

Yes. A published Page Demo URL can be used for testing, subject to its documented limits. It should not be treated as the recommended campaign URL.

Q: Does Instapage have its own collaboration mode?

Yes. Its real-time collaboration supports page comments and View, Edit, or Manage permissions. BugSmash is a separate review workflow for the published browser page.

Q: Who can push changes live?

Instapage separates team permissions. An Editor can edit and save but cannot push changes live, while publishing and domain access depend on the assigned permissions.

Paste the browser-accessible landing-page URL, send one review link, and collect contextual comments on the page your campaign visitors will see.

See how it works

Loved by1,250+Agenciesand companies in 100+ countries

Instapage preview, collaboration, Page Demo, and live publication are different.

Instapage provides builder previews, in-product collaboration, and several publishing methods. BugSmash reviews the browser-accessible published URL selected for the review round.

Four documented publishing boundaries matter:

Page Demo is a testing option.
Instapage provides pagedemo.co for testing before publishing to a custom domain and does not recommend running ads or campaigns on it.
Page Demo has documented limits.
A Page Demo URL is limited to 30 requests per minute per IP. Instapage also says free-trial Page Demo pages are automatically unpublished, although its official articles currently disagree on the exact duration.
Saved edits need Update to go live.
After editing an already published page, the orange Update button pushes the changes live; Instapage says the live page can take a few minutes to update.
Collaboration permissions are separate.
Instapage real-time collaboration and View, Edit, or Manage permissions govern its workspace workflow. They do not replace a visitor-facing page review URL.

BugSmash keeps external feedback on the rendered page:

share the appropriate published URL, retain Instapage workspace permissions for the account team, and, when the script is installed on the rendered frontend, use the Feedback Widget for a gated flow a pasted URL cannot open.

How it works

Three steps to a reviewed Instapage landing page

Publish the intended page state

Choose Custom Domain, WordPress, Drupal, or Page Demo as appropriate, and confirm the resulting visitor-facing URL opens the intended revision.

Send one BugSmash link

Paste that published URL into BugSmash and share the generated review link without adding every reviewer to the Instapage workspace.

Resolve comments and update the page

Use the attached URL, selected location, screenshot, browser, operating system, and viewport context, then click Update when changes should reach the live page.

Review the published Instapage experience

Comment on the rendered page

Attach feedback to the visitor-facing landing page instead of describing an element in a separate message.

Choose the right publication target

Review the Custom Domain, WordPress, Drupal, or Page Demo result intended for that round.

Check desktop and mobile

Review the rendered page across viewport sizes alongside the builder's Desktop and Mobile editing modes.

Capture technical context

Keep the page URL, screenshot, browser, operating system, and viewport with every website comment.

Separate external review from roles

Collect stakeholder feedback without assigning View, Edit, or Manage workspace access to everyone.

Use the widget for gated flows

When the rendered frontend permits the BugSmash script to be installed, use the Feedback Widget inside an authorized logged-in or stateful campaign flow.

Which Instapage URL should I review?

Choose a published URL based on the page's purpose and the publishing method. Page Demo is useful for testing but is not the recommended campaign destination.

Your URL	Review by URL	What to do
Published page on a Custom Domain	Works	Paste the visitor-facing custom-domain URL and start the review.
Published WordPress or Drupal page	Works	Use the full published CMS URL that opens the Instapage landing page.
Published Page Demo URL	Testing only	Use it for a controlled review while respecting the request limit and free-trial unpublishing rule.
Builder preview or unpublished page	Not a published URL	Publish the intended page state before starting an external browser review.
Page behind login or SSO	Use the Widget	Pasting a URL does not bypass application login or SSO. If the script can be installed on the rendered frontend, use the Feedback Widget inside the authenticated session.
Page a reviewer lacks domain permission to publish	Permission-dependent	Use an authorized account owner or manager to publish; domain access and external page review are separate.

Using the Feedback Widget in an Instapage-connected flow

Where the rendered frontend permits the BugSmash script to be installed, use it for reviewers who already have authorized access when a login or stateful journey cannot be opened through a standalone pasted URL.

The feedback workflow for teams using Instapage

Keep page building, Instapage collaboration, publication, and external approval distinct while every comment stays attached to the rendered landing page.