What you can customize
Make the site work the way you need, from its address to its error page.
In the site’s settings
| What | How | Read more |
|---|---|---|
| Name | Change it any time. It does not affect the address. | Your address |
| Address | Pick any free name.lovelyco.de; the old one stops working at once. | Your address |
| Custom domain | Point a domain you own at the site, with HTTPS handled for you. Paid plan. | Custom domains |
| Online or offline | Pause visitor access while keeping your files in place. | Getting started |
| Passwords | Up to ten, each covering the whole site or one folder, each with its own sign-in duration. | Password |
| Files source | Drag and drop, a GitHub repository and branch, or a deploy key for your CI. | Publishing |
| Environment variables | Public values and secrets, with the hosts each secret may be sent to. | Environment variables |
| Delete | Permanently remove the site and release its address. | Getting started |
With a file in your site
| What | How | Read more |
|---|---|---|
| Your own 404 page | Add 404.html. It is served with a real 404 status. | Paths and routing |
| Single-page app routing | Add 200.html. Unknown addresses are answered with it, status 200. | Paths and routing |
| Redirects | Add _redirects, Netlify format, one rule per line. | Redirects |
| Response headers | Add _headers: security policies, CORS, content disposition, anything starting with X-. | Headers |
| Browser caching | Set Cache-Control in _headers for files with fingerprinted names. | Caching |
| Search engine preference | A <link rel="canonical"> in each page chooses which address is indexed. | Custom domains |
HTTPS and hosting on Cloudflare’s global network are handled for you.