> For the complete documentation index, see [llms.txt](https://docs.ultramarinastudios.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ultramarinastudios.com/guides/seo.md).

# SEO

### Why we use multiple H1 tags

Some SEO tools and scanners may occasionally flag that there are multiple `<h1>` tags in Primavera. This is based on outdated guidelines, as modern search engines are equipped to handle multiple  `<h1>` tags on a single page.

Primavera uses multiple `<h1>` tags by choice: the use of `<dialog>` for elements such as product descriptions with rich text content ensures the intended heading hierarchy is preserved. Otherwise, the modal content would have an incorrect heading hierarchy and further confuse the search engine crawlers and screen reader users.

In addition, we've exposed a [Set as page title](/common-settings.md#set-as-page-title) setting in dynamic sections that enable you to specify the heading as an `<h1>` , providing added flexibility and SEO benefits.

Therefore, if your SEO checker flags this, it's probably okay to ignore it. And if you have any questions, don't hesitate to [get in touch](https://ultramarinastudios.com/support/).


---

# 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://docs.ultramarinastudios.com/guides/seo.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.