> For the complete documentation index, see [llms.txt](https://en-ascent.webvista.studio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://en-ascent.webvista.studio/others/version-upgrade-notes/v3.1.0-coming-soon.md).

# v3.1.0（Coming Soon）

This update focuses on **AI-ready storefront discovery**. As more shoppers use AI search tools and answer engines to compare products, explore brands, and find helpful content, Ascent now gives those systems clearer signals about your store.

#### Added

* Enhanced **AI readability** for key storefront pages, helping AI-powered search and discovery tools better understand products, collections, blog content, and brand information
* Added clearer page relationship signals, making it easier for AI tools to understand how pages connect across your store
* Improved blog listing signals so article collections can be interpreted more accurately by search engines and AI assistants

#### Changed

* Optimized article pages to rely on cleaner native article information
* Improved collection and collection list signals to better match the products and collections currently shown on the page
* Strengthened brand and social profile signals for a clearer connection between your store and official channels
* Improved Open Graph image consistency for cleaner sharing previews

#### Fixes and other improvements

* Reduced duplicate article signals that could make content harder for search and AI systems to interpret
* Refined how blog, collection, article, and content pages communicate their meaning to search and AI discovery tools
* General SEO, AI discovery, and content clarity improvements across the theme


---

# 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://en-ascent.webvista.studio/others/version-upgrade-notes/v3.1.0-coming-soon.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.