Deploy Hugo Profile to Netlify

Netlify is the easiest way to deploy Hugo Profile — you get automatic builds, HTTPS, and a global CDN for free. Every push to your connected repository triggers a fresh build, so your live site stays in sync with your content without any manual steps.

Deployment paths

Use This Template (fastest)
From Quick Start setup

The quickest route to a live site is to start directly from the Hugo Profile repository using GitHub’s template feature. Netlify will detect the included netlify.toml automatically — no manual build configuration required.

Create your repository

Open https://github.com/gurusabarish/hugo-profile and click Use this template, then Create a new repository. Give your repository a name and choose a visibility setting.

Add the site to Netlify

Go to https://app.netlify.com, click Add new site, then select Import an existing project.

Connect your GitHub repository

Authorize Netlify to access GitHub if prompted, then select the repository you just created.

Review build settings

Netlify automatically detects the netlify.toml in the repository root and pre-fills the build command and publish directory. No changes are needed.

Deploy

Click Deploy site. Netlify builds the site and gives you a live URL within a minute or two.

Any changes you push to files inside the exampleSite/ folder will automatically trigger a redeployment on Netlify.

If you followed the Quick Start guide to scaffold a new Hugo site locally, you can still connect it to Netlify with a small amount of additional configuration.

Push your site to a remote repository

Initialize a Git repository inside your site’s root directory (if you haven’t already) and push it to a new repository on GitHub or GitLab.

git init
git add .
git commit -m "Initial commit"
git remote add origin https://github.com/your-username/your-site.git
git push -u origin main

Add the site to Netlify

In the Netlify dashboard, click Add new site > Import an existing project, then connect your GitHub or GitLab account and select your repository.

Configure build settings

Set the following values in the build settings form:

Setting	Value
Build command	`hugo`
Publish directory	`public`

Then add an environment variable to pin the Hugo version:

Key	Value
`HUGO_VERSION`	`0.143.0`

Deploy

Click Deploy site. Netlify runs hugo, places output into public/, and serves it on your Netlify subdomain.

netlify.toml reference

The repository ships with a netlify.toml that drives automated deployments for the template flow. Here is the complete file:

[build]
  publish = "exampleSite/public"
  command = 'cd exampleSite && echo -e "\ngoogleAnalytics: $GOOGLE_ANALYTICS \ndisqusShortname: $DISQUS_SHORTNAME \n" >> config.yaml && hugo --gc --minify --themesDir ../..'

[context.production.environment]
  HUGO_VERSION = "0.143.0"
  HUGO_ENV = "production"
  HUGO_ENABLEGITINFO = "true"
  HUGO_THEME = "repo"

[context.split1]
  command = "cd exampleSite && hugo --gc --minify --enableGitInfo --themesDir ../.."

[context.split1.environment]
  HUGO_VERSION = "0.143.0"
  HUGO_ENV = "production"
  HUGO_THEME = "repo"

[context.deploy-preview]
  command = "cd exampleSite && hugo --gc --minify --buildFuture --themesDir ../.. -b $DEPLOY_PRIME_URL"

[context.deploy-preview.environment]
  HUGO_VERSION = "0.143.0"
  HUGO_THEME = "repo"

[context.branch-deploy]
  command = "cd exampleSite && hugo --gc --minify --themesDir ../.. -b $DEPLOY_PRIME_URL"

[context.branch-deploy.environment]
  HUGO_VERSION = "0.143.0"

[context.next.environment]
  HUGO_ENABLEGITINFO = "true"

If you scaffolded your own site with the Quick Start guide, your build command is simply hugo and your publish directory is public — the exampleSite/ paths in the default netlify.toml only apply to the template repository layout.

Custom domain

You can point your own domain to your Netlify site at any time:

In the Netlify dashboard, open your site and go to Domain settings > Add a domain.
Enter your domain name and follow the DNS instructions Netlify provides.
Netlify automatically provisions a TLS certificate via Let’s Encrypt — HTTPS is enabled without any extra steps.

Before going live on a custom domain, update baseURL in your hugo.yaml to match the production domain exactly. Mismatched baseURL values cause broken asset paths and incorrect canonical links.

baseURL: "https://www.yourdomain.com"

Getting Started

Configuration

Sections

Content & Features

Deployment

Deploy Hugo Profile to Netlify

Deployment paths

netlify.toml reference

Custom domain

Further reading

Build docs developers (and LLMs) love

Getting Started

Configuration

Sections

Content & Features

Deployment

Documentation Index

​Deployment paths

​netlify.toml reference

​Custom domain

​Further reading

Build docs developers (and LLMs) love

Deployment paths

netlify.toml reference

Custom domain

Further reading