Your AI Agents can now act on comments added in BugSmash with our MCP. See How it works.
Collect visual feedback on a website built with Umbraco. Create a BugSmash Website project with a public URL or a site protected by Basic Auth, then share its review link for contextual comments. Other application logins, SSO, CAPTCHA, VPN and network restrictions may require the Feedback Widget or HTML workflow. This is not a native Umbraco integration: BugSmash reviews the resulting browser page and does not connect to Umbraco itself. Use the rendered website or an implemented external preview environment. Umbraco Backoffice, Delivery API authorization, Cloud Portal access and frontend protection remain separate controls. https://staging.your-umbraco-site.com Platform clarification: this is a generic BugSmash Website project workflow, not a native Umbraco integration. Public URLs and supported Basic Auth sites can use the Website project workflow.
Get client feedback on your Umbraco website
Paste the public site, an accessible staging deployment, or an implemented external preview URL and collect contextual comments on the rendered experience.
Umbraco documents both server-side URL generation and a client-side Backoffice extension for external preview options; an external preview can also require its own authentication.
BugSmash keeps feedback on the browser result:
share the accessible rendered website or implemented preview environment, preserve page context, and leave Backoffice, publication and API controls unchanged.
How it works
Three steps to a reviewed Umbraco release
11
Prepare the rendered environment
Use the normal rendered website, deploy an accessible staging environment, or implement an external headless preview that can retrieve the intended draft content.
22
Send one BugSmash link
Paste that accessible browser URL into BugSmash and share the generated review link with stakeholders.
33
Publish or deploy the approved result
Save and publish the approved content, deploy required schema or code changes, and verify the resulting visitor-facing page.
Review the rendered Umbraco website, not the Backoffice
Comment on the rendered page
Attach feedback to the page location visitors see rather than describing a content-tree item in a separate message.
Review published pages
Use the normal website URL when the review should reflect content that has been saved and published.
Review an implemented headless preview
Use an external preview URL after its server, client and authenticated draft-data path have been configured.
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.
Keep Backoffice access separate
External reviewers can comment on an accessible website without receiving Umbraco Backoffice or Cloud Portal accounts.
Which Umbraco-related URL should I review?
Use the rendered website or a deliberately implemented preview environment. Backoffice permissions, Delivery API keys, Cloud Portal access and frontend authentication remain separate.
Your URL
Review by URL
What to do
Public rendered Umbraco website
Works
Paste the visitor-facing page URL into BugSmash.
Accessible staging website
Works
Use the staging URL after confirming every intended reviewer can open it.
Implemented external preview environment
Configuration-dependent
Use the generated external preview URL after its draft-content and authentication flow is working.
Default preview from Backoffice
Backoffice workflow
Keep editor preview in Backoffice, or configure an external preview option for the intended review environment.
Protected or authenticated website
Access-dependent
Authenticate in the review session or use the Feedback Widget. A pasted URL does not bypass website access controls.
Content Delivery API endpoint
JSON, not the rendered site
Review the website or headless frontend that presents Delivery API content to users.
Using the Feedback Widget on an Umbraco website
Add the BugSmash Feedback Widget to the rendered Umbraco website or headless frontend when reviewers must stay inside an authenticated or stateful experience. Do not place it in a Delivery API response.
The feedback workflow for teams using Umbraco
Keep content editing and environment management in Umbraco while clients, designers and QA review the browser experience produced by the site.
Ship faster togetherThe all-in-one workspace for product teams.
Get started free
MayaMake this hero image full-bleed
Live WebsiteURL
product-launch.mp4
0:42 / 3:15
LeoTrim the intro to 0:03
VideoMP4
sneaker.glb
AvaSmooth these edges a bit
3D ModelGLB · GLTF
Quarterly Review
Q3 Performance
Revenue up 24%1.2k new usersNPS score 62Churn down 3%
BugSmash3 / 18
SamUpdate the Q3 numbers
Slide DeckPPT
Your summer sale starts now 🌞
A
Acme Store
to you
9:24 AM
Up to 40% off
Summer essentials, restocked
Shop the sale
NoahStronger CTA copy here
EmailHTML
9:41
Good morning
Dashboard
Balance
$4,280
ZoeAlign the chart legend
Mobile AppAndroid · iOS
Annual Report2025 in review
This 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.
Fig 1. Coastal expansion, 2025
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.
Send the rendered website URL. For a headless draft review, use an external preview environment only after its URL generation, client integration and draft-data authorization are implemented.
What is the difference between Save, Save and preview, and Save and publish?
Save stores edits without publishing them. Save and preview shows the changes before they go live. Save and publish publishes the changes.
Is the Umbraco Content Delivery API enabled automatically?
No. Umbraco documents the Content Delivery API as an opt-in feature that must be enabled through project configuration.
How does a headless frontend request unpublished Umbraco content?
It sends the Preview header as true and supplies the configured key in the Api-Key request header. Without that key, unpublished content is not included.
Can Umbraco provide more than one external preview option?
Yes. Umbraco documents registering multiple preview options, each backed by the required URL-provider and Backoffice extension implementation.
What environments does Umbraco Cloud provide?
Umbraco Cloud documents structured Development, Staging and Live environments as part of its built-in deployment workflow.
How do schema and content move in Umbraco Cloud?
Umbraco Cloud deploys schema through Git or the Cloud Portal, while content and media are transferred through the Umbraco Backoffice.
Does BugSmash publish content or change Umbraco access?
No. Umbraco continues to control Backoffice users, publishing, deployments, preview implementations and API authorization. BugSmash records contextual feedback on an accessible rendered website.
Ship Umbraco websites without chasing feedback
Paste an accessible rendered website or implemented preview URL and send a focused review link.
BugSmash keeps feedback on the browser result:
Jira
ClickUp
Monday
Asana
Trello
Slack
Linear
Todoist
Notion
Airtable
Zapier
Make
n8n
Webhooks
MayaMake this hero image full-bleed
product-launch.mp4
LeoTrim the intro to 0:03
AvaSmooth these edges a bit
SamUpdate the Q3 numbers
Up to 40% off
NoahStronger CTA copy here
ZoeAlign the chart legend
EllaTighten this paragraph
TheoBoost the warm tones
MiaCut the dead air at 1:12