Site Keys

The playbook keys configured under site manage the site’s published identity and how it interacts with certain applications once it’s published.

When building the site, some of the attributes defined in the playbook can be overridden on the command line or with environment variables.

site key

Global generated site files, service accounts, and other common properties are defined under the site key in a playbook file. These settings are applied to the entire site when it’s generated.

site: (1)
  title: Docs Site (2)
  url: (3)
  start_page: component-b::index.adoc (4)
  robots: allow (5)
  keys: (6)
    google_analytics: XX-123456 (7)
1 Required site key
2 Required title key
3 Required url key
4 Optional start_page key
5 Optional robots key
6 Optional keys key
7 Example google_analytics key

The site, title, and url keys are required. The other keys are optional; Antora will use their default values if they’re not specified. Many of these keys can also be configured from the Antora CLI or with environment variables.

Alternatively, title, start_page, and keys can be assigned from the CLI. The url key can be assigned from the CLI or using an environment variable.

Available site keys

Site Keys Description Required


Account and API keys for reference by the UI templates or extensions. Accepts a map of name-value pairs that specify account identifiers for service integrations such as Google Analytics.



Specifies whether Antora generates a robots.txt file. Accepts the values allow, disallow, and a custom, multi-line string. Ignored if the sibling url key is not set.



Accepts a page ID that specifies the start page of a site.



Specifies the title of a site.



Specifies the base URL of a site.