BlackFriday

50% offon all annual plans

00d00h00m00s
Explore plans
Your AI Agents can now act on comments added in BugSmash with our MCP. See How it works.
Craft CMS logo

Get client feedback on your Craft CMS frontend

Paste the deployed frontend or, with Craft Team or Pro, a valid tokenized Preview Target URL, send one review link, and collect contextual comments on the rendered experience.

https://

Craft can render its own frontend or supply content to a decoupled application. Review the browser URL configured for that frontend.

Knauf
Radancy
Frontier
City of Boroondara
Berlin Heart
GVBOCES
Bville
Frost Collective
Mediapilote
Medwiki
Musaffa
Sharp Guys Web Design

Loved by1,250+Agenciesand companies in 100+ countries

Craft previews drafts. BugSmash organizes review on the rendered frontend.

Craft drafts power Live Preview, while Craft Team and Pro support tokenized URLs through Preview Targets. Deployment remains part of the project’s hosting workflow.

Four documented boundaries matter before client review:

  1. Live Preview is an editorial interface.

    Craft splits the screen between a simplified editor and the frontend preview, refreshing it when the provisional draft is auto-saved.

  2. Shared preview URLs contain temporary tokens.

    In Craft Team and Pro, a tokenized Preview Target URL can be opened by someone without a Craft account, but it reflects the draft state when accessed and does not auto-refresh like Live Preview.

  3. Shared-preview token lifetime is configurable.

    Craft says shared preview tokens expire after one day by default. The defaultTokenDuration setting controls that duration.

  4. Decoupled previews require frontend support.

    A decoupled frontend must detect the token parameter and pass the same token with the content request so Craft can return the previewed content.

BugSmash keeps feedback on the browser result:
share the deployed frontend or a valid preview URL, preserve the page context, and leave Craft drafts, permissions and deployment controls unchanged.

How it works

Three steps to a reviewed Craft CMS site

1

Prepare the frontend URL

Deploy the Craft frontend to an accessible environment, or use Craft Team or Pro to create a tokenized URL for the entry and Preview Target under review.

2

Send one BugSmash link

Paste the deployed or preview URL into BugSmash and share the generated link with the client or QA team.

3

Apply and deploy approved work

Update the Craft draft or project, publish the content, complete the deployment, and verify the resulting browser URL.

Review the deployed Craft frontend, not only the control panel

Comment on the rendered frontend

Attach feedback to the page location rather than describing an entry or template in a separate message.

Review tokenized draft previews

With Craft Team or Pro, use a valid Preview Target URL when a stakeholder needs to see unpublished entry content.

Cover decoupled applications

Review the deployed Vue, React or other frontend after it has been configured to request the correct Craft content.

Check responsive layouts

Review desktop, tablet and mobile presentation and retain the viewport with every comment.

Capture technical context

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

Keep control-panel access private

External reviewers can use an accessible frontend or, with Craft Team or Pro, a tokenized Preview Target URL without receiving a Craft control-panel account.

Which Craft CMS URL should I review?

Use the rendered frontend or, with Craft Team or Pro, a valid Preview Target URL. Craft control-panel permissions, token lifetime and frontend access rules continue to apply.

Your URLReview by URLWhat to do
Public Craft CMS frontend WorksPaste the public page URL and start the review.
Accessible staging frontend WorksUse the staging URL after confirming every reviewer can open it.
Tokenized Craft Preview Target URL (Team or Pro) Works until expiryShare the URL while its temporary preview token remains valid.
Decoupled frontend preview Configuration-dependentConfirm the frontend forwards Craft’s token when it requests preview content.
Craft Live Preview in the control panel Editor access requiredFor Craft Team or Pro, use a tokenized Preview Target URL for external review instead of sharing the control-panel interface.
Protected or authenticated frontend Access-dependentAuthenticate in the review session or use the Feedback Widget. A pasted URL does not bypass the frontend gate.

Using the Feedback Widget on a Craft CMS frontend

Add the BugSmash Feedback Widget to the rendered frontend when review must remain inside an authenticated or stateful experience. Install it in the frontend visitors actually open, including a decoupled application.

Turn Craft CMS page feedback into trackable work

Route an actionable website comment with its page URL, selected location, screenshot, 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.

Jira
ClickUp
Monday
Asana
Trello
Slack
Linear
Todoist
Notion
Airtable
Zapier
Make
n8n
Webhooks

The Craft CMS site is one deliverable. Review the complete launch together.

Keep the frontend beside content PDFs, images, videos, presentations and release materials, with feedback and approval in one project.

  • Website
  • HTML
  • Widget
  • Video
  • Audio
  • Image
  • PDF
  • PPT
  • Doc
  • Email
  • 3D Model
  • CAD
  • Mobile App
  • Canvas

Craft CMS website feedback, answered

Which Craft CMS URL should I send for review?

Send the deployed frontend URL. With Craft Team or Pro, you can use a Preview Target URL containing Craft’s temporary preview token for unpublished entry content.

Ship Craft CMS sites without chasing feedback

Paste an accessible Craft frontend or valid preview URL and send a focused review link.

BugSmash website review interface with comment controls