> For the complete documentation index, see [llms.txt](https://seyarat.gitbook.io/seyarat-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://seyarat.gitbook.io/seyarat-docs/configuration/page-title-builder.md).
# Page Title Builder
The Page Title area appears below the Header and introduces the current page. It can show the page title, breadcrumb navigation, a background, and supporting text.
{% hint style="info" %}
A breadcrumb shows the visitor's location, for example Home → Listings → Vehicle. Keep the title area clear and readable.
{% endhint %}
#### Create and design
1. Open **N3Theme** → **Page Title** and click **Add New**.
2. Enter a clear **title**, then click **Publish** and **Edit with Elementor.**
3. Add the dynamic **Page Title**, **breadcrumb**, and a **readable background.**
4. Check **Desktop**, **Tablet**, and **Mobile**; adjust type, padding, and wrapping.
5. Click Update.
#### Assign globally
1. Open **N3Theme** → **Theme Options** → **Builder Option** → **Page Title**.
2. Select the template in **Page Title Type**.
3. To use the built-in version, select **Default**.
4. For **Default**, configure breadcrumb, desktop/mobile padding, and background.
5. Click **Save Changes**.
#### Override and test
1. Edit the **page** and open **Page Options** → **Page Title Option**.
2. Choose **Default**, a **Page Title** template, or **None**.
3. When using **Default**, optionally set the local **Page Title background**.
4. Click **Update**, then test logged out and on mobile.
5. If stale, clear **Elementor**, site, server, and browser caches.
---
# 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://seyarat.gitbook.io/seyarat-docs/configuration/page-title-builder.md?ask=&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.
