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.
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:
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.
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.
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.
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:How it works
Three steps to a reviewed Hugo site
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.
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.
Content and documentation teams
Review navigation, copy and generated pages on the hosted build without giving reviewers repository access.
See how
Design and frontend teams
Collect visual reports with the exact page, selected element, browser, device and screenshot attached.
See how
QA and release teams
Validate base paths, publication settings and cleaned build output on the environment intended for release.
See howMore platforms
Explore more website feedback workflows
Read the published workflow guide for another website builder, CMS, framework or AI site platform.
- Webflow website feedback guide
- Framer website feedback guide
- WordPress website feedback guide
- Shopify website feedback guide
- Squarespace website feedback guide
- Wix website feedback guide
- Bubble website feedback guide
- Replit website feedback guide
- Lovable website feedback guide
- Claude Artifacts website feedback guide
- Next.js website feedback guide
- React website feedback guide
Turn Hugo site feedback into work
A comment on the published site becomes a task with the page, selected element, screenshot, browser and device context already attached.
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
WebhooksThe Hugo site is one deliverable. Review the rest of the launch with it.
Keep the site, documentation PDF, walkthrough video, campaign images, launch email and presentation in one review project with one approval trail.
Website HTML Widget Video Audio Image PDF PPT Doc Email 3D Model CAD Mobile App - Canvas
Hugo site feedback, answered
Should I share hugo server with a client?
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?
Does Hugo remove old files from public when it builds?
Will drafts appear in the review build?
Why do links or assets point to the wrong place?
Does BugSmash require a specific Hugo host?
Can I review a Hugo site published under a subdirectory?
Do reviewers need access to the Hugo repository?
Ship Hugo sites without chasing feedback
Paste an accessible Hugo deployment URL and send the first review link in under a minute.
