> For the complete documentation index, see [llms.txt](https://doc.aissist.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.aissist.io/tutorial/turn-assets-into-ai/web-page.md).

# Web Page

*Last updated: May 12, 2026*

Use a web page asset to index one specific public URL.

This is useful when only a single page matters and you do not want to include the rest of the site.

### Add a web page asset

Go to **Workspace → Assets** and add a web page asset.

Provide one or more public page URLs.

Common examples:

* a status page
* a return or refund policy page
* a single FAQ or product page

<figure><img src="/files/iDL2QZidX2DZ30mxfeL0" alt=""><figcaption></figcaption></figure>

### Choose web page or domain

Use a **web page** asset when you want to index only the page you provide.

Use a **domain** asset when you want Aissist to search across a wider site.

See [Website Domain](/tutorial/turn-assets-into-ai/website-domain.md) for full-site setup.

<details>

<summary>Web page content updates</summary>

Web page assets are indexed and stored directly by Aissist.

Aissist checks for updates every 24 hours.

If you update the asset manually from the console, that also triggers a refresh.

</details>

### Best practice

Use web page assets for focused, high-value content.

If you need broader coverage across a site, use a domain asset instead.


---

# 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:

```
GET https://doc.aissist.io/tutorial/turn-assets-into-ai/web-page.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.