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 Hugo. 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 Hugo integration: BugSmash reviews the resulting browser page and does not connect to Hugo itself. Use the hosted static website URL. If you only have the static build files, use BugSmash's HTML review workflow instead of a localhost or filesystem URL. https://your-site.com Platform clarification: this is a generic BugSmash Website project workflow, not a native Hugo integration. Public URLs and supported Basic Auth sites can use the Website project workflow.
Get client feedback on your published Hugo site
Paste the browser-accessible URL for your Hugo deployment, send one review link, and collect comments on the pages your visitors will actually open. Every note keeps its page, browser, device and screenshot context.
Loved by1,250+Agenciesand companies in 100+ countries
Hugo generates the site. Review happens on the hosted output.
The Hugo CLI builds the project into the public directory by default. That directory can be uploaded to a static host or deployed through CI/CD. The hugo deploy command can send it to a configured cloud-storage target when Hugo's deploy or extended/deploy edition is installed.
Four build and publishing details still shape the review:
01
hugo server is a local development server.
It builds and serves the site at a local address, watches project files, and refreshes the browser with LiveReload. Use a deployed URL for a durable external review.
02
The public directory can retain stale files.
Hugo overwrites existing build files but does not delete files from public by default. Clean the destination manually or use cleanDestinationDir when the review must represent only the current build.
03
Draft, future and expired pages are excluded by default.
Hugo omits pages marked as drafts, pages dated or scheduled for the future, and expired pages unless the corresponding build options are enabled. Descendants of draft, future and expired branch pages can still be published unless build options are applied through cascade.
04
The published location belongs in baseURL.
Hugo defines baseURL as the absolute published URL, including protocol, host, path and trailing slash. Configure it for the deployment so generated links and assets resolve from the reviewed location.
BugSmash adds the review layer around the hosted site:
review the published pages in a browser, keep comments attached to the visible output, and preserve an approval record outside the source repository and hosting service.
How it works
Three steps to a reviewed Hugo site
11
Build and deploy the intended release
Run the production build, clean stale output when required, and publish the resulting public directory or configured destination to the final host or an accessible preview.
22
Send one review link
Paste the deployed URL into BugSmash and share the generated link. Reviewers comment on the hosted pages without needing the Hugo project or repository.
33
Resolve feedback page by page
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 Hugo output visitors will actually browse
Comment on published pages
Attach feedback to the rendered page instead of translating it into a content file, shortcode or layout name.
Check responsive layouts
Review desktop, tablet and mobile states from one link and keep the viewport with each comment.
Capture browser context
Browser, device, screenshot and page URL arrive with every report.
Verify publication state
Review the build that uses the intended draft, future, expired and cascade settings for that release.
Catch stale generated files
Check the hosted output after cleaning or rebuilding public so removed pages and assets do not survive unnoticed.
Keep release approval
Preserve the review record independently of later builds, content updates or hosting changes.
Will it work on my Hugo site?
BugSmash reviews a browser-accessible Hugo deployment. The build settings, host and source-site access controls determine which pages a reviewer can open.
Your URL
Review by URL
What to do
Public Hugo site on a custom domain
Works
Paste the deployed URL and review the published site.
Public preview supplied by a hosting provider
Works
Use the preview URL after confirming it opens without repository or dashboard access.
Hugo site published below a URL path
Works
Use the full deployed path and configure baseURL for that published location.
Preview protected by supported Basic Auth
Works
Use the browser-accessible Basic Auth URL; BugSmash lists websites protected by Basic Auth as supported.
Local hugo server address
Not directly
Build the site and deploy the public output to a browser-accessible host before creating the review.
Site behind an application login or SSO
Use another workflow
Install the BugSmash Feedback Widget or share a static export. A pasted URL does not bypass application login or SSO.
Using the BugSmash Feedback Widget on a Hugo site
Add the BugSmash script to the rendered site when the review must stay inside an authenticated or otherwise stateful browser flow. Include it through the site's templates so it is present in the deployed HTML being reviewed.
The feedback workflow for teams using Hugo
From documentation and editorial sites to campaign launches, keep content, design, engineering and QA aligned on the same generated release.
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.
Hugo documents hugo server as a local development server that watches files and uses LiveReload. For external review, build the site and deploy the public output to a browser-accessible host.
Which Hugo folder should I deploy?
Hugo writes the built site to public by default. You can change the destination with the --destination flag or the publishDir configuration setting.
Does Hugo remove old files from public when it builds?
Not by default. Hugo overwrites existing files but does not delete stale files from public unless you clean the directory or enable the documented destination-cleaning option.
Will drafts appear in the review build?
Pages marked as drafts, pages dated or scheduled for the future, and expired pages are excluded by default unless their build options are enabled. Hugo can still publish descendants of draft, future and expired branch pages unless build options are applied through cascade.
Why do links or assets point to the wrong place?
Check baseURL. Hugo defines it as the absolute URL of the published site, including its protocol, host, path and trailing slash.
Does BugSmash require a specific Hugo host?
No. Hugo documents multiple hosting and deployment paths. BugSmash needs the resulting site to be reachable through a browser URL that the reviewer can access.
Can I review a Hugo site published under a subdirectory?
Yes. Use the full deployed path and configure Hugo's baseURL for that published location before building.
Do reviewers need access to the Hugo repository?
No. They review the hosted browser output rather than the source project, build environment or hosting dashboard.
Ship Hugo sites without chasing feedback
Paste an accessible Hugo deployment URL and send the first review link in under a minute.
BugSmash adds the review layer around the hosted site:
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