> 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/verifytextexist-1.md).

# verifyTextExist

This is a pre-built Action located under the **@Browser Element**. The functionality of this Action in Avo Assure is to check whether the specified input text exists on the Application Under Test (AUT). The result of this Action is stored in a dynamic variable for further use during test execution.

### Syntax

**Input Value:** `<text>`

<table><thead><tr><th>Argument</th><th>Description</th><th data-hidden></th></tr></thead><tbody><tr><td>&#x3C;text><br>(Required)</td><td>Provide the input text to verify how many times it appears on the current page of the AUT.</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><p>&#x3C;Dynamic Variable></p><p>(Required)</p></td><td>This dynamic variable stores the count of times the given text appears on the page.</td><td></td></tr><tr><td><p>&#x3C;Dynamic Variable></p><p>(Optional)</p></td><td>The dynamic variable stores the status as <strong>True</strong> or <strong>False</strong>.</td><td></td></tr></tbody></table>

### **Example: Verifying the Presence of Specific Text on a Web Page**

In this example, we explain how to verify whether a specified text is present on the current web page using the **verifyTextExist** action.

* **Action:** verifyTextExist
* **Input Value:** Avo Bank
  * The input value (**Avo Bank**) specifies the text whose occurrences are counted on the web page.
* **Output Value**: {TextFound}
  * The text count of occurrences (e.g., No. of occurrences of the text Avo Bank is 1 time(s)) is stored in this **{TextFound}** dynamic variable.
  * If a second output variable is provided, the action returns the status as True/False:
    * **True**: If the specified text is found on the web page.
    * **False**: If the specified text is not found on the web page.
* **Logical Explanation**: The **verifyTextExist** action takes the value from the **Input Value** column ( **Avo Bank**) and searches for that text in the currently loaded web page. The count of occurrences is stored in the **{TextFound}** variable (e.g., No. of occurrences of the text Avo Bank is 1 time(s)).

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FWA3MveIAmJ1MwbuXSsMh%2Fimage.png?alt=media&amp;token=26d5c104-e6f8-40aa-9f22-c6978c96d71b" 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/verifytextexist-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.