> For the complete documentation index, see [llms.txt](https://software-help-docs.gitbook.io/knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://software-help-docs.gitbook.io/knowledge-base/software-guide/reputation-management-and-reviews/how-to-use-yext.md).

# How to Use Yext

Yext is a service that allows you to quickly and easily list your business on 150+ portals and websites. **our software** may include special pricing for Yext. This feature helps to boost your online presence and SEO rapidly. Check out these quick steps to get started:

**Step 1: Creating a Yext Account.**

* Navigate to Online Listing from your Dashboard.
* Click “Get Started” in the popup.
* Fill out your payment information and email address.
* Click Confirm.
* Your Yext account is now created.

**Step 2: Viewing Your Yext Data**

* On your Online Listings page, you’ll see a graph and icons, which give you an overview of how Yext is working to boost your online presence.
* It can take about 48 hours for the information to be live, so at first the graph may look like this, with most information “Processing” or “Unavailable”:
* Once Yext processes the information, you’ll see a majority of it is “Live”.
* Scroll down to view the individual networks and statuses to see how Yext is working for you.


---

# 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://software-help-docs.gitbook.io/knowledge-base/software-guide/reputation-management-and-reviews/how-to-use-yext.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.