Get client feedback on your Astro site

Q: Can I review a static Astro site?

Yes. Static is Astro's default output mode. Build and publish the output, which is written to dist by default, then use the hosted URL.

Q: Can I review Astro routes rendered on demand?

Yes when the route is deployed with the appropriate adapter and is accessible to the reviewer. Test on the intended runtime because the server handles those requests.

Q: Should I share astro preview with clients?

astro preview is a local server for checking built static output and is not designed for production. Use a deployment URL or intentionally expose a secure HTTPS tunnel.

Q: Does every Astro host support on-demand rendering?

No assumption should be made. Astro requires an appropriate adapter for on-demand rendering, and each adapter can have its own configuration. Check the selected adapter and host documentation.

Q: Can I review a protected preview?

A preview protected by supported Basic Auth can use BugSmash's website review flow. Other application logins, SSO, CAPTCHA, VPN or network controls still require permitted access and may be better suited to the Feedback Widget.

Q: Can reviewers test several routes and responsive sizes?

Yes. Include every route and state that needs approval, and use the captured viewport, browser and page URL to keep reports reproducible.

Q: Do reviewers need repository or hosting access?

No. They review the deployed browser interface. They still need permission to open any protected deployment or application route.

Paste a browser-accessible Astro deployment, send one review link, and collect comments on the pages and interactive states people will actually see. Every note keeps its page, browser, device and screenshot context.

See how it works

Loved by1,250+Agenciesand companies in 100+ countries

Astro controls how pages are rendered and deployed. Review happens on the accessible result.

Astro's build output uses static mode by default. Pages can instead use on-demand rendering, which requires an adapter for the chosen server runtime. A normal build writes to dist by default.

Those choices change what a reviewer can open. Four boundaries matter:

Local servers are not deployed review environments.
astro dev runs a local development server. astro preview serves the built static directory locally and Astro explicitly says it is not designed for production. Deploy the build or intentionally expose a secure HTTPS tunnel.
Static and on-demand routes have different runtime needs.
Static mode prerenders pages by default. On-demand rendering requires an adapter and a host that supports the selected runtime, so review on the intended deployment target.
A successful build does not publish itself.
astro build creates deployment output, in dist by default. A hosting service or server must publish that output at an address reviewers can reach.
Access controls remain in charge.
Pasting a URL does not bypass deployment access, application authentication, or hosting controls. Supply permitted access or use the Feedback Widget inside the browser-facing site when appropriate.

BugSmash adds a review layer around the deployed site:

review the browser-visible routes, keep comments attached to the rendered page, and preserve an approval trail separately from Astro and the hosting provider.

How it works

Three steps to a reviewed Astro site

Deploy the rendering mode you plan to ship

Publish the static build or adapter-backed on-demand build, then verify every route in scope opens from the review environment.

Send one review link

Paste the accessible deployment URL into BugSmash and share the generated link. Reviewers comment on the rendered site without repository or hosting-dashboard access.

Resolve feedback with its page context

Each item keeps the page URL, selected element, screenshot, browser and device so the team can reproduce and route the change.

Review the deployed Astro site, not the local development server

Comment on rendered pages

Attach a note to the visible interface instead of translating it into a component or file description.

Review responsive layouts

Check desktop, tablet and mobile views and retain the viewport with each comment.

Capture browser context

The page URL, browser, device and screenshot arrive with the report.

Cover static and dynamic routes

Review prerendered pages and accessible on-demand routes on the same deployment mode intended for release.

Keep release sign-off

Preserve review decisions independently of later builds, adapter changes or hosting updates.

Route work to the right owner

Turn visual feedback into work for content, design, frontend or platform teams with its original context.

Will it work on my Astro deployment?

BugSmash reviews a browser-accessible Astro deployment. Rendering mode, hosting configuration and access controls determine what reviewers can open.

Your URL	Review by URL	What to do
Public Astro static deployment	Works	Paste the hosted site URL and review the pages included in the build.
Public adapter-backed on-demand deployment	Works	Use the deployed URL after verifying the adapter and runtime behave as intended.
Accessible hosting preview	Works	Share the preview URL after confirming reviewers can open every route in scope.
Preview protected by supported Basic Auth	Works	Provide the permitted Basic Auth credentials through the supported review flow.
astro dev or astro preview on localhost	Not directly	Deploy the build or expose the local server through a secure HTTPS tunnel.
Site behind application login or SSO	Use the Widget	Install the Feedback Widget in the site so reviewers can comment while remaining inside the authenticated browser session.

Using the BugSmash Feedback Widget in an Astro site

Add the BugSmash script to the browser-facing Astro output when reviewers need to remain inside authenticated or stateful routes. Install it in the rendered site, independent of whether the route is static or rendered on demand.