> 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/workflow-concepts/workflow-steps/seo-research.md).

# SEO Research

SEO Research Steps provide comprehensive search intelligence tools to power your content strategy and organic growth initiatives. These steps connect directly to leading SEO platforms, giving you access to valuable keyword, competitor, and performance data within your workflows.

The SEO Research Steps include:

1. [**Moz**](/actions/workflow-concepts/workflow-steps/seo-research/moz.md) -- access domain authority and link metrics
2. [**DataForSEO Steps**](/actions/workflow-concepts/workflow-steps/seo-research/content-+-seo.md)
   1. **Keyword Ideas from Domain** -- discover potential keywords that a domain could target
   2. **Keyword Ranked For** -- identify keywords a domain currently ranks for and their metrics
   3. **News Research** -- find keyword mentions in recent news articles
   4. **Related Keyword Finder** -- uncover semantically related keywords
   5. **Related Searches Finder** -- access Google's related search suggestions
   6. **Web Research** -- retrieve keyword-relevant content snippets from the web
   7. **On-Page SEO Analysis** -- analyze a URL's SEO structure and content
3. [**Google Search Console**](/actions/workflow-concepts/workflow-steps/seo-research/google-search-console.md) -- retrieve search performance data and indexing status

These steps can be combined with other AirOps capabilities to automate SEO research, build data-driven content strategies, identify competitive gaps, and optimize existing content for better search performance.


---

# 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/workflow-concepts/workflow-steps/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.