> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/actions/web/browser/get-page-title-1.md).

# Get Page Title

This is a pre-built Action located under the **@Browser Element**. The functionality of this Action in Avo Assure is to retrieve the title of the current web page. The result of this Action is stored in a dynamic variable for further use during test execution.

## **Syntax**

**Input Value:** `N/A`

<table><thead><tr><th>Argument</th><th>Description</th><th data-hidden></th></tr></thead><tbody><tr><td>N/A</td><td>Not Applicable</td><td></td></tr></tbody></table>

**Output Value:** `<Dynamic Variable>;<Dynamic Variable>(Optional)`

<table><thead><tr><th>Argument</th><th>Description</th><th data-hidden></th></tr></thead><tbody><tr><td>&#x3C;Dynamic Variable><br>(Required)</td><td>This dynamic variable stores the current browser's page title.</td><td></td></tr><tr><td>&#x3C;Dynamic Variable><br>(Optional)</td><td>The dynamic variable stores the status as <strong>True</strong> or <strong>False</strong>.</td><td></td></tr></tbody></table>

### **Example: Fetching the Title of the Currently Opened Web Page**

In this example, we explain how to retrieve the title of the currently opened web page using the **Get Page Title** action.

* **Action**: Get Page Title
* **Input Value**: N/A
  * This action does not require any input value. It retrieves the title of the active web page displayed in the browser (e.g., Home).
* **Output Value**: {PageTitle}
  * The retrieved current page title (e.g., Home) is stored in this **{PageTitle}** dynamic variable.
  * If a second output variable is provided, the action returns the status as True/False:
    * **True**: If the page title fetched successfully.
    * **False**: If the page title is not fetched successfully.
* **Logical Explanation:** The **Get Page Title** action executes without requiring any input value and fetches the title of the currently displayed web page in the browser window. The retrieved title is stored in the **{PageTitle}** variable (e.g., Home).

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FRbhGrTKEQYPcJhpwXJYT%2Fimage.png?alt=media&amp;token=43f4605b-db1a-4e82-908e-bdf973a8f387" alt=""><figcaption></figcaption></figure>


---

# 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.avoautomation.com/avo-assure/actions/web/browser/get-page-title-1.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.