> 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/link/verifylinktext.md).

# verifyLinkText

This is a pre-built Action located under the captured link element. The functionality of this Action in Avo Assure is to verify whether the text of the specified link element matches the provided input value. The result is stored in a dynamic variable for further use during test execution.

## **Syntax**

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

| Argument                           | Description                                                       |
| ---------------------------------- | ----------------------------------------------------------------- |
| <p>\<Input text><br>(Required)</p> | Provide the text value you want to verify with the captured link. |

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

| Argument                                                    | Description                                                       |
| ----------------------------------------------------------- | ----------------------------------------------------------------- |
| \<Dynamic Variable>(Optional);\<Dynamic Variable>(Optional) | Both dynamic variable stores the status as **True** or **False**. |

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

In this example, we explain how to use the **verifyLinkText** action to check whether a specified link text is present on the web page.

* **Action:** verifyLinkText
* **Input Value:** Don’t have an account? Create new account
  * The value (**Don’t have an account? Create new account)** specifies the link text to be verified on the page. The action checks whether the hyperlink with the provided text exists within the current page content.
* **Output Value:** {Status}
  * The result of the verification is stored in this **{Status}** dynamic variable with the following possible values:
    * **True**: If the specified link text is found successfully.
    * **False**: If the specified link text is not found.
* **Logical Explanation:** The **verifyLinkText** action takes the value from the **Input Value** column (**Don’t have an account? Create new account**) and checks whether it exists on the web page. The result of this verification (**True**) is stored in the **{Status}** variable.

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FUwPEVoTi3fUE4PbpxMou%2Fimage.png?alt=media&amp;token=71401ff1-55bf-4346-91a2-c9dd99ad4a20" 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/link/verifylinktext.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.