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 Drupal. 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 Drupal integration: BugSmash reviews the resulting browser page and does not connect to Drupal itself. Review the publicly accessible frontend website powered by this CMS. The CMS dashboard, unpublished content and authenticated editor previews are separate from the website URL. https://your-site.com Platform clarification: this is a generic BugSmash Website project workflow, not a native Drupal integration. Public URLs and supported Basic Auth sites can use the Website project workflow.
Get client feedback on your Drupal site
Paste the public site or an accessible staging URL, send one review link, and collect comments on the rendered pages your visitors will use. Every note keeps its page, browser, device and screenshot context.
Loved by1,250+Agenciesand companies in 100+ countries
Drupal controls publishing. Client review still happens on the rendered site.
Drupal core provides Workflows, Content Moderation and Workspaces for moving revisionable content through controlled states and staging changes before they reach the live site.
Those tools manage publishing inside Drupal. Four review boundaries still matter:
01
Content Moderation manages states and transitions.
It can keep a published version live while a separate working copy moves through review. It does not place client annotations on the rendered page.
02
Drafts and staged changes remain permission-controlled.
A reviewer must have the Drupal access needed to see an unpublished revision or Workspace. A public visitor normally sees the published version.
03
Workspaces stage a set of changes.
They provide a parallel copy of the live site that authorized users can preview and deploy, but they do not create an external visual-feedback queue.
04
The Drupal project may not be the whole frontend.
A decoupled Drupal build serves content to another application. Review the deployed browser frontend, not the administration screen or content API.
BugSmash complements Drupal's editorial workflow:
review the accessible frontend in a real browser, keep visual comments tied to the rendered page, and preserve an approval record outside the CMS.
How it works
Three steps to a reviewed Drupal site
11
Prepare an accessible review version
Publish the revision to an appropriate staging environment or make the relevant frontend accessible to the reviewers who need to see it.
22
Send one review link
Paste that browser URL into BugSmash and share the generated link. Reviewers comment on the rendered page without needing a BugSmash account.
33
Resolve comments before publishing
Each item carries the page, selected element, screenshot, browser and device. Assign it, update its status, or send it into the team's delivery tools.
Review the Drupal frontend your visitors will actually use
Comment on rendered components
Attach a note to the page element instead of describing a block, field or view in an email.
Review responsive layouts
Check desktop, tablet and mobile states from one link and keep the viewport with the comment.
Capture browser context
Browser, device, screenshot and page URL arrive with every report.
Keep revision sign-off separate
Record what was approved even after content moves through another moderation state or deployment.
Review decoupled frontends
Use the deployed website URL whether Drupal renders the page or supplies content to a separate frontend.
Route fixes to the right owner
Turn visual feedback into work for editors, site builders, themers or application developers.
Will it work on my Drupal setup?
BugSmash reviews a browser-accessible frontend. Drupal's own access controls still decide whether a particular revision, Workspace or protected environment can be opened.
Your URL
Review by URL
What to do
Public Drupal website
Works
Paste the public URL and start the review.
Accessible Drupal staging site
Works
Use the staging URL after confirming the reviewer can open it.
Staging protected with shared Basic Auth
Works
Open the shared gate in the review window, authenticate, and continue.
Content Moderation draft or latest revision
Access-dependent
The reviewer needs a Drupal account and permission to view that revision. Otherwise publish it to an accessible staging environment.
Drupal Workspace preview
Access-dependent
Authorized users can review the Workspace. For external clients, expose an appropriate staging version instead.
Site in Maintenance mode
Access-dependent
Visitors without the bypass permission see the maintenance message. Use an authorized account or a separate accessible staging site.
Public decoupled Drupal frontend
Works
Paste the deployed frontend URL rather than the Drupal administration or API URL.
Using the BugSmash Feedback Widget on a Drupal frontend
Add the BugSmash script to the rendered frontend when reviewers need to stay inside an authenticated or stateful flow. For a decoupled build, install it in the frontend application that visitors actually open.
The feedback workflow for teams using Drupal
From editorial staging to release QA, keep agencies, content teams and platform owners reviewing the same rendered Drupal site.
A comment on the rendered site becomes a task with the URL, selected element, screenshot, browser and device context already attached.
Context stays attached from comment to completion.
Comment captured
Hero section
Mobile
Context travels with it
Nothing gets lost in translation
Page URL
Clicked element
Screenshot
Browser and device
Task ready
Feedback with full context
Visual evidenceScreenshot attached
EnvironmentBrowser and device included
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 Drupal site is one deliverable. Review the rest of the launch with it.
Keep the site, migration report, content PDF, walkthrough video, campaign creative and release presentation in one review project with one approval trail.
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.
No. Content Moderation controls revision states and transitions inside Drupal. BugSmash adds contextual review and approval on the rendered browser page.
Can a client review an unpublished Drupal revision?
Only if your Drupal configuration and permissions let that client see it. For external review, publishing the revision to an appropriate accessible staging environment is usually clearer.
Can I review a Drupal Workspace?
Authorized Drupal users can preview a Workspace under the permissions you configure. BugSmash can review the resulting frontend only when that browser session can access it.
What happens when the site is in Maintenance mode?
Drupal shows the maintenance message to users without the permission to bypass it. Use an authorized account or review a separate staging environment that is available to the client.
Does this work with a decoupled Drupal site?
Yes when the deployed frontend is browser-accessible. Review that frontend URL; the Drupal administration and content API are not the visitor experience.
Do reviewers need a Drupal account?
Not for a public or shared-gate staging page. They do need the appropriate Drupal account and permissions for protected drafts, Workspaces or other restricted content.
Can reviewers check mobile and desktop layouts?
Yes. They can review responsive layouts from the same link, and each comment keeps the viewport and device context.
Where does the approval record live?
It stays in the BugSmash project, independent of later Drupal revisions, state transitions or deployments.
Ship Drupal sites without chasing feedback
Paste an accessible Drupal frontend URL and send the first review link in under a minute.
BugSmash complements Drupal's editorial workflow:
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