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.
Sanity logo

Get client feedback on your Sanity-powered frontend

Paste the separately deployed frontend or an enabled shared-preview URL, send one review link, and collect contextual comments on the rendered experience.

https://

Sanity Studio manages content. The customer-facing website is a separate frontend that you deploy and connect to Content Lake.

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

Sanity manages structured content. Review happens on the connected frontend.

Sanity Studio, Content Lake and the Presentation Tool support editorial work, while the website or application remains a separately deployed frontend.

Four documented boundaries matter before stakeholder review:

  1. Sanity Studio is an editorial application.

    Studio is a browser-based React SPA connected to Sanity APIs and Content Lake. A sanity.studio deployment is not automatically the customer-facing website.

  2. The Presentation Tool embeds a frontend.

    It renders the configured frontend in an iframe and can connect that preview to documents and fields in Studio.

  3. Draft mode requires a secure handshake.

    The frontend validates the preview secret, sets its draft-mode state and redirects the preview. This is separate from ordinary published-content access.

  4. Dataset visibility controls data reads.

    Anyone can query a public dataset, while a private dataset requires an authenticated user or a request carrying an authorized token.

BugSmash keeps external feedback on the rendered experience:
share the accessible frontend or enabled shared preview, retain page context, and leave Studio, dataset and application access under their existing controls.

How it works

Three steps to a reviewed Sanity-powered site

1

Prepare the frontend

Deploy the website or application frontend and confirm it can load the intended published content or authorized preview state from Sanity.

2

Choose published or preview review

Use the normal frontend URL for published content, or enable Sanity shared preview access when stakeholders need an authorized draft preview without Studio access.

3

Send and resolve the review

Paste that browser URL into BugSmash, collect contextual comments, update the content or frontend, and verify the rendered result.

Review the Sanity-powered frontend, not the content workspace

Comment on the deployed frontend

Attach feedback to the rendered website or application rather than a Studio document or Content Lake response.

Review an enabled shared preview

Use Sanity shared preview access when stakeholders without Studio access need to see draft-mode content.

Keep Studio access private

External reviewers can comment on an accessible frontend without becoming Sanity project members.

Check responsive layouts

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

Capture technical context

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

Review any connected frontend stack

Use the browser URL of the frontend configured to consume Sanity content, independent of where that frontend is hosted.

Which Sanity-related URL should I review?

Use the deployed frontend or a deliberately enabled shared preview. Studio, Presentation Tool, dataset and application access remain distinct.

Your URLReview by URLWhat to do
Public Sanity-powered frontend WorksPaste the public website or application URL into BugSmash.
Accessible staging frontend WorksUse the staging URL after confirming the reviewer can open it.
Sanity shared preview URL Works while enabledEnable shared preview access and share the resulting stakeholder preview while it remains active.
Presentation Tool inside Studio Studio access requiredUse shared preview access or the deployed frontend for stakeholders who do not have Studio access.
Frontend backed by a private dataset Implementation-dependentReview the rendered frontend after its server-side or authenticated data access is configured; never expose a private token in public browser code.
Frontend behind login or access protection Access-dependentAuthenticate in the review session or use the Feedback Widget. A pasted URL does not bypass frontend authentication.

Using the Feedback Widget on a Sanity-powered frontend

Add the BugSmash Feedback Widget to the deployed frontend when reviewers must stay inside an authenticated, personalized or stateful experience. Install it in the application, not in Content Lake.

Turn Sanity-powered 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 Sanity-powered frontend is one deliverable. Review the launch together.

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

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

Sanity website feedback, answered

Which URL should I send for a Sanity-powered site review?

Send the separately deployed frontend URL. A sanity.studio URL opens the editorial Studio, not automatically the customer-facing website.

Ship Sanity-powered sites without chasing feedback

Paste the accessible frontend or enabled shared-preview URL and send a focused review link.

BugSmash website review interface with comment controls