> For the complete documentation index, see [llms.txt](https://docs.airops.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.airops.com/actions/playbooks/tools/seo-research.md).

# SEO Research

Use SEO research tools to gather keyword, domain, backlink, and search performance data

SEO Research Tools help Playbooks gather search data before planning, refreshing, or publishing content. Use them when the Playbook needs keyword volume, ranking data, domain metrics, backlink context, or Google Search Console performance.

## Tools

### DataForSEO

Retrieve SEO data and keyword research, including keyword metrics, ranked keywords, related keywords, search intent, domain competitors, domain intersections, relevant pages, and organic SERP results.

Use **DataForSEO** when a Playbook needs broad keyword and SERP data. It can support:

* Keyword overview, search volume, CPC, competition, search intent, and monthly trends.
* Organic SERP results for a keyword.
* Ranked keywords for a domain or URL.
* Competitor domains, keyword gaps, relevant pages, related keywords, keyword suggestions, and bulk keyword difficulty.

### Moz

Retrieve SEO and domain analysis, including authority metrics, link metrics, keyword metrics, and related keyword ideas.

Use **Moz** when a Playbook needs domain authority, page authority, spam score, linking domain data, or keyword suggestions from Moz.

### Google Search Console

Read Google Search Console data for connected sites. Use it to inspect clicks, impressions, CTR, average position, pages, queries, and performance trends.

Use **Google Search Console** when a Playbook needs first-party performance data for owned pages. The Playbook can list available sites, then query search analytics by page, query, country, device, or date.

## How to Configure

1. Open the Playbook editor.
2. Type `/` in the Section where search data should be gathered.
3. Select the SEO Research Tool.
4. For **Google Search Console**, connect a Google Search Console authentication if prompted.
5. Tell the Playbook which site, page, query, competitor, region, language, and date range to use.

## Parameters

| Tool                      | Required context                        | Optional guidance                                                              |
| ------------------------- | --------------------------------------- | ------------------------------------------------------------------------------ |
| **DataForSEO**            | Keyword, URL, domain, or competitor set | Add location, language, search intent, limits, and comparison rules            |
| **Moz**                   | Keyword, URL, or domain                 | Add metric type, locale, scope, and result limit                               |
| **Google Search Console** | Connected site and date range           | Add dimensions, filters, query text, page URL, country, device, or search type |

## Examples

```markdown
Use **Google Search Console** to find queries where `target_url` has impressions but weak CTR over the last 30 days.
```

```markdown
Use **DataForSEO** to compare our domain against the listed competitors and return keyword gaps with search intent.
```


---

# 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.airops.com/actions/playbooks/tools/seo-research.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.