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 Contentful. 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 Contentful integration: BugSmash reviews the resulting browser page and does not connect to Contentful itself. Use the separately implemented frontend or an accessible configured content-preview URL. The Contentful web app, content environments, preview access tokens and frontend authentication remain separate controls. https://your-contentful-powered-site.com Platform clarification: this is a generic BugSmash Website project workflow, not a native Contentful integration. Public URLs and supported Basic Auth sites can use the Website project workflow.
Get client feedback on your Contentful-powered frontend
Paste the deployed website or an accessible configured preview URL, send one review link, and collect contextual comments on the rendered experience.
Loved by1,250+Agenciesand companies in 100+ countries
Contentful manages content. Review happens on the connected frontend.
Contentful separates its web app, Delivery and Preview APIs, content environments, and the website or application built to render that content.
Four documented boundaries matter before stakeholder review:
01
The frontend is a separate implementation.
Contentful delivers content to apps and websites through APIs. Content preview requires an online or local version of the website or app that knows how to render the selected entry.
02
Delivery and Preview APIs return different states.
The Content Delivery API is for published content. The Content Preview API also returns the latest draft content and uses its own preview access token.
03
Preview URLs must be configured.
An administrator configures preview URLs for eligible content types. Editors can then use Live Preview or open the configured preview in a new browser tab.
04
Live Preview embeds the configured website.
Contentful displays Live Preview beside the entry editor. The frontend must permit Contentful to frame it, and authenticated preview cookies need the documented cross-site cookie settings.
BugSmash keeps feedback on the browser result:
share the accessible frontend or configured preview URL, retain page context, and leave Contentful publishing, environments and API access unchanged.
How it works
Three steps to a reviewed Contentful-powered release
11
Prepare the rendered frontend
Deploy the website or application against published content, or configure an online preview implementation that retrieves the intended draft state.
22
Send one BugSmash link
Paste the accessible frontend or configured preview URL into BugSmash and share the generated review link with stakeholders.
33
Publish and verify the approved result
Apply the approved content or frontend changes, publish through the project’s normal workflow, and verify the rendered visitor URL.
Review the Contentful-powered frontend, not the content workspace
Comment on the rendered experience
Attach feedback to the page location visitors see instead of describing an entry or API field in a separate message.
Review published content
Use the deployed frontend backed by the Content Delivery API when the review should reflect the published content state.
Review configured draft previews
Use an accessible preview frontend configured to retrieve unpublished content through the Content Preview API.
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 Contentful access separate
External reviewers can comment on an accessible frontend without receiving membership in the Contentful organization or space.
Which Contentful-related URL should I review?
Use the deployed frontend or a deliberately configured preview URL. Contentful workspace access, preview-token handling, environment permissions and frontend authentication remain separate.
Your URL
Review by URL
What to do
Public Contentful-powered frontend
Works
Paste the visitor-facing website or application URL into BugSmash.
Accessible staging frontend
Works
Use the staging URL after confirming that every intended reviewer can open it.
Configured Contentful preview URL
Works when accessible
Use the configured online preview after confirming its draft-mode and access setup works for reviewers.
Contentful Live Preview pane
Contentful access required
Use the configured frontend URL for external review; the embedded Live Preview remains part of the entry editor.
Protected or authenticated frontend
Access-dependent
Authenticate in the review session or use the Feedback Widget. A pasted URL does not bypass frontend access controls.
Contentful web app or API endpoint
Not the visitor website
Review the frontend that renders Contentful content instead of the editorial workspace or JSON response.
Using the Feedback Widget on a Contentful-powered frontend
Add the BugSmash Feedback Widget to the rendered website or application when reviewers must stay inside an authenticated or stateful experience. Install it in the frontend, not in the Contentful web app or Content APIs.
The feedback workflow for teams using Contentful
Keep structured-content work in Contentful while content teams, clients and QA review the browser experience produced by the connected frontend.
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.
Which URL should I send for a Contentful-powered site review?
Send the separately implemented frontend URL. For unpublished content, use an accessible online preview URL that has been configured for the relevant content type.
What is the difference between the Content Delivery API and Content Preview API?
The Content Delivery API serves published content. The Content Preview API also returns the latest drafts so a preview implementation can render unpublished changes.
Does Contentful create the preview website?
No. Contentful requires an online or local version of your website or app and a configured preview URL that maps entries to that frontend.
What does a Contentful preview access token do?
It authenticates requests to the Content Preview API. Contentful documents it separately from the production delivery token, which does not work with the Preview API.
How does Contentful Live Preview display the page?
It displays the configured website beside the entry editor and can reflect changes as an editor types. The frontend must allow Contentful to embed it.
Why can an embedded Contentful preview fail to load?
A strict X-Frame-Options or Content-Security-Policy configuration can block the iframe. Contentful documents allowing its app origin in the frontend’s framing policy.
What are Contentful environments and environment aliases?
Environments isolate versions of content and configuration. An environment alias is a stable identifier whose target environment can be switched without changing the alias used by an application.
Does BugSmash publish content or change Contentful permissions?
No. Contentful continues to control entries, publishing, environments, preview configuration and access. BugSmash records contextual feedback on an accessible rendered frontend.
Ship Contentful-powered sites without chasing feedback
Paste an accessible deployed frontend or configured 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