> For the complete documentation index, see [llms.txt](https://docs.peakcommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peakcommerce.com/product/journeys-and-pages/journey-settings/seo-and-metadata.md).

# SEO & metadata

The **SEO & metadata** settings control how a journey's public page appears in browser tabs, search results, and social-link previews. Set them on the journey's **Settings** tab — the same fields also appear when you first create a journey.

| Field                 | Controls                                                          |
| --------------------- | ----------------------------------------------------------------- |
| **Browser tab title** | The title shown in the browser tab. Defaults to the journey name. |
| **Meta description**  | The short description search engines display.                     |
| **OG title**          | The title shown when the journey link is shared on social media.  |
| **OG description**    | The description shown on social shares.                           |
| **OG image URL**      | The preview image on social shares (recommended 1200×630px).      |

Because journeys are public pages that search engines and AI agents crawl, filling these in helps your flows surface accurately in search results and link previews.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.peakcommerce.com/product/journeys-and-pages/journey-settings/seo-and-metadata.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
