Companies Using Hugo

With over a decade analyzing web technographic data and building crawling infrastructure, I've watched static site generators go from developer toys to the default way engineering teams publish documentation. This analysis draws on our crawl detecting Hugo on 28,690 active domains, of which 12,969 (a 45.2% match rate) we cross-referenced with LinkedIn company data. Data freshness: our August 2026 crawl.

One caveat frames everything below. Hugo is visible to us only when the pages it builds say so, in a single line of the page source. Strip that line, as a customized theme easily can, and the site drops out of our count entirely. So 28,690 is a floor, and for a tool whose users edit templates as a matter of course it is probably a generous distance below the real number. The compensation is precision: what we do see, we see cleanly. Only 27.9% of Hugo domains are one-off sightings, against 60.4% for Astro, and Hugo's detection and scan counts sit almost on top of each other. A static tag does not flicker. When we report Hugo on a domain, Hugo is on that domain.

1. Growth trajectory

Hugo first appears in our records in March 2015 on one domain. It crossed 1,000 active domains in November 2017, 5,263 by August 2020, 10,099 in September 2022, and reached 16,528 in March 2025, the end of that stretch of our records. Those readings are not plotted on the chart above, which shows the current crawl only: 22,846 in June 2026 and 28,690 in August 2026. Note what the curve never does: within any continuous stretch of our records, it does not turn down. The step between the two stretches reflects both of the things that move a number like this, a crawled domain set that turns over every month and detection coverage that has widened, so I would not read it as adoption accelerating.

"The honest headline for Hugo is not the count, it's the confidence interval. We are more certain about the 28,690 domains we report here than about almost any number on this site, and simultaneously more certain that the real total is meaningfully higher. Both follow from the same fact: Hugo shows itself in one place or nowhere." - Mehmet Suleyman, CEO at TechnologyChecker.io

Sales Signal: Do not size the Hugo market from our count alone. Size it from the shape of our count, which is remarkably consistent: a small-team, engineering-owned buyer in the US and Northern Europe. Vendors selling into that profile can trust the composition even where they should discount the total.

2. Customer profile

The customer base is overwhelmingly small. 77.39% of the Hugo companies we can size have 1-10 employees and 15.5% have 11-50, so 92.9% sit at fifty people or fewer. On founding dates, 45.68% were founded in the 2010s and 30.45% in the 2020s, so roughly three in four post-date 2010. The classic profile is a developer running a personal site, or a two-to-ten person team publishing docs for an open-source project.

The tail above that is small but instructive: 563 companies in the 51-200 band, 147 in 201-500, and 21 at 10,001 employees or more. At the large end, Hugo lives almost entirely on subdomains. Of the fifty companies listed on this page, 34 are detected on a subdomain rather than the apex, and 13 of those carry a docs, developer, support, learn, community, or tech prefix: docs.gitlab.com, docs.digitalocean.com, learn.arm.com, community.apache.org, developer.leaseweb.com, tech.kakaobank.com. The enterprise never bought Hugo. An engineering team inside it chose Hugo.

Sales Signal: For enterprise outbound, target the documentation-tooling buyer (technical writers, developer relations, docs engineering), not the marketing-website buyer. The Hugo enterprise persona has a documentation pain point first and a marketing pain point close to never.

3. Industry and geographic concentration

This is the cleanest buyer signal I have seen on any profile in this category. Software Development (14.48%) and IT Services and IT Consulting (14.11%) are almost exactly level and together make up 28.6% of the companies we can classify. Add Technology, Information and Internet (6.59%) and Information Technology and Services (3.58%) and the developer-facing share passes 38%. The fifth-placed vertical, Business Consulting and Services, is 2.75%. That is not a gentle skew, it is a cliff.

Geographically, the United States leads with 2,771 companies, but the story is Europe. The United Kingdom (1,375) and Germany (1,357) are effectively tied for second, and no other tool in this category puts Germany level with the UK. France (731), the Netherlands (519), Switzerland (271), Spain (213), Belgium (194), Italy (178), Poland (148), and Norway (145) fill out the European block, which comes to 5,131 companies in our top fifteen, close to double the US figure. A self-hosted, single-binary, no-vendor tool is an easy sell into markets with strong data sovereignty preferences, and the numbers behave accordingly.

Sales Signal: Tooling that speaks to German and Swiss data-residency and privacy requirements has a defensible niche in this base. Content marketing for Hugo-adjacent products should publish in German and French alongside English, because the long tail is genuinely there and not just an artifact of a few large accounts.

4. Migration patterns

We began recording generator switches in March 2026, so the window is five months and the numbers are correspondingly small. 138 domains moved from Hugo to Astro with 25 coming back, and 76 moved to Next.js with 24 back, for net losses of 113 and 52. In the other direction Hugo is net positive against the older generators: +16 from Jekyll, +6 from Gatsby, +5 from Hexo, with no recorded flow back to any of them.

The direction is the same one the whole category shows, where the newer JavaScript generators take domains from the older Go and Ruby ones. But the magnitude deserves honesty. A net loss of 165 domains across both corridors, on a base of 28,690, is a rounding error dressed up as a trend if you squint at it too hard. What it does establish is a direction, and Astro rather than Next.js is the one taking the traffic.

"Hugo's outflow is small enough that I would not build a strategy on it. The useful part is which way it points. Teams leaving Hugo are not leaving static publishing, they are leaving static-only publishing, and they overwhelmingly pick the tool that lets them keep the static default and add interactivity where they need it." - Mehmet Suleyman, CEO at TechnologyChecker.io

Sales Signal: Two-sided. Migration services can price the Hugo-to-Astro corridor at a premium because the pain is fresh, but should size it realistically. Vendors selling Hugo retention (themes, custom development, hosting bundles) should focus on the documentation vertical, where flat HTML output is a feature rather than a constraint.

5. Technology ecosystem

The co-occurrence data confirms the customer profile from a completely different angle. Google Analytics is on 42.05% of Hugo sites and Cloudflare on 39.39%, with Cloudflare Browser Insights at 17.7%. Script CDNs are heavily represented, cdnjs (18.22%), jsDelivr (16.17%), Fastly (12.26%), and Amazon CloudFront (9.38%), which is the signature of sites that ship plain HTML and fetch the two or three libraries they need at load time. Plausible (2.76%) and Matomo (1.87%) show a real but modest privacy-tooling preference.

The most revealing number is the absence. The largest JavaScript framework on Hugo sites is AMP at 2.59%, followed by Alpine.js (2.26%), Vue.js (2.02%), and React at 1.25%, about one site in eighty. WordPress appears on 1.55% and Shopify on 0.28%. Hugo sites are not quietly hybrid and they are not quietly ecommerce. They are static pages with, at most, a sprinkle of Alpine.js. That is precisely the gap Astro's island architecture targets, and it explains why Astro rather than Next.js is the corridor with movement in it.

Sales Signal: The stack has obvious holes. Headless CMS adoption is barely detectable in this base, and search, commenting, and form-handling services are all underrepresented. Any vendor in those categories is looking at greenfield rather than displacement, with the caveat that this buyer expects an open-source option and will build it themselves if the pricing offends them.

6. Community sentiment signals

Hugo's community lives on GitHub and its own forum, not on enterprise software review sites, which is itself consistent with everything above. The Hugo repository carries more than 89,500 stars and 8,300 forks, putting it in the top tier of Go open-source projects, and the project shipped v0.165.0 on 12 August 2026, six releases after v0.163.0 in early June. Whatever the migration numbers say, this is not a project running out of momentum.

The recurring complaints in community discussion are consistent and well known: the Go template syntax has a learning curve, and there is no native way to add interactivity without bolting on a separate JavaScript bundle. Our stack data corroborates the second one directly. React sits on 1.25% of Hugo sites, so almost nobody has bolted anything on, and our migration data shows Astro as the destination when teams decide they need it.

Sales Signal: Do not prospect this base on software review sites. The channels that work are the Hugo themes directory, the official Discourse forum, developer subreddits, and partnerships with the static hosting platforms where these customers already deploy.

Key takeaways

1. 28,690 is a floor, and an unusually trustworthy one. Hugo shows itself in one line of page source or not at all, so sites with customized themes are missing entirely, while the domains we do report are as clean a signal as we have.
2. The counts in this category are not directly comparable. Next.js at 731,970 leaves several fingerprints in a page and Hugo leaves one, so the ratio between them overstates the real difference in use.
3. The buyer signal is the sharpest in the category: Software Development 14.48% and IT Services 14.11%, together 28.6% of classified companies, and 77.39% of the companies we can size at ten employees or fewer.
4. Hugo is the most European tool here: the UK (1,375) and Germany (1,357) are level behind the US (2,771), and ten European markets in our top fifteen total 5,131 companies.
5. Migration is small and mildly negative: net -113 to Astro and -52 to Next.js over five months, offset by +16 from Jekyll, +6 from Gatsby, and +5 from Hexo.

Sales applications

Targeting strategy on TechnologyChecker.io: filter Hugo companies by Industry = Software Development, IT Services and IT Consulting, or Technology, Information and Internet. Those three alone cover 4,033 of the companies we matched. Layer Country = US, UK, Germany, France, Netherlands to reach the densest geographies, and Employee Range = 1-50 to match where 92.9% of this base actually sits.

Documentation-first angle: prospect the subdomain, not the brand. Where we detect Hugo on docs, developer, support, or community hosts, the decision maker is a docs or developer-experience owner with a real budget line and no interest in a website platform pitch.

Competitive angle: for Astro vendors, the interactivity gap is the wedge, because React sits on only 1.25% of Hugo sites and the teams that want components are already moving. For Hugo-defending vendors, the European block and the small-team profile are the durable ground.

Find more Hugo customers and competitors on TechnologyChecker.io

Explore the full list of 28,690 domains running Hugo with industry, country, and size filters. Compare adoption against Next.js, Astro, and Nuxt.js. Our database tracks 29.9M active domains across 40K+ technologies, with monthly refreshes and LinkedIn-enriched company data covering 12,969 Hugo deployments.