> ## Documentation Index
> Fetch the complete documentation index at: https://docs.blode.md/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Custom domains

Use your own domain for your documentation site.

Every project deployed with blode.md gets a subdomain at `your-slug.blode.md` automatically. You can also point your own domain to your docs site for a fully branded experience.

## Default subdomain

When you run `blodemd push`, your docs are published to `{slug}.blode.md`, where `slug` is the project slug resolved from `--project`, `BLODEMD_PROJECT`, or docs.json `slug`. No per-project DNS setup is required because the platform wildcard handles `*.blode.md`.

## Add a custom domain

  1. **Choose your domain**

Decide whether to use a subdomain (e.g., `docs.example.com`) or an apex domain (e.g., `example.com`).

    > [!TIP]
> Subdomains are recommended. They are simpler to configure and do not interfere with your root domain's other records.
  1. **Configure DNS**

Add a CNAME record pointing your domain to `cname.vercel-dns.com`.

    | Type  | Name   | Value                  |
    | ----- | ------ | ---------------------- |
    | CNAME | `docs` | `cname.vercel-dns.com` |

    For apex domains, some DNS providers require an `A` record instead of a CNAME. Check your provider's documentation for CNAME flattening or ALIAS record support.
  1. **Verify ownership**

If prompted, add the TXT verification record provided in your project dashboard:

    | Type | Name                       | Value                          |
    | ---- | -------------------------- | ------------------------------ |
    | TXT  | `_vercel.docs.example.com` | `vc-domain-verify=...` |
  1. **Add the domain in your project settings**

Configure the custom domain through Blode.md's custom-domain workflow after
    your project has been deployed. That control plane provisions the domain on
    Vercel and returns any verification records you need.

## Apex vs subdomain

## Path prefix

If you want your docs mounted at a subpath rather than the domain root, set the
path prefix when configuring the custom domain in the control plane.

Your documentation will then be accessible at `docs.example.com/docs` instead
of `docs.example.com`.

> [!NOTE]
> The path prefix is applied to all routes, including search, sitemaps, and API
>   reference pages.