> For the complete documentation index, see [llms.txt](https://salsa-digital.gitbook.io/govcms-content-administration/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://salsa-digital.gitbook.io/govcms-content-administration/unit-8-meta-tags-and-seo/tokens-and-default-meta-tags.md).

# Tokens and default meta tags

## What is a token

A *token* is a formatted chunks of text that serves as a placeholder for a dynamically generated value. For example \[site:name] serves as a placeholder for a site's name.

## How tokens are used to populate default meta tags

![Image of search results](/files/AGcyMzxFwttJ1z0FlElh)

The search result screenshot above outlines “tokens” that are automatically replaced by GovCMS when content is created or updated. The tokens in use are:

1. \[node:title] - title of the page, taken from the page's *Title* field.
2. \[site:name] - the name of the site (GovCMS in this case).
3. \[node:summary] - an automatically generated summary of the page contents.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://salsa-digital.gitbook.io/govcms-content-administration/unit-8-meta-tags-and-seo/tokens-and-default-meta-tags.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.