> For the complete documentation index, see [llms.txt](https://ai-seo-copilot.gitbook.io/ai-seo-copilot/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ai-seo-copilot.gitbook.io/ai-seo-copilot/getting-started/advanced-analysis/secondary-keywords.md).

# Secondary keywords

{% embed url="<https://youtu.be/4a-l9pwk51I>" %}

They usually include:

1. Synonyms and variations

   Words or phrases with the same or very similar meaning.

   * Primary keyword: *running shoes*
   * Secondary keywords: *jogging sneakers*, *trainers for running*
2. Close semantic variations

   Terms that aren’t strict synonyms but are relevant in the same context.

   * Primary keyword: *digital marketing*
   * Secondary keywords: *online advertising*, *internet marketing*, *SEO marketing*
3. Long-tail versions

   Extended, more specific phrases that include your main keyword.

   * Primary keyword: *web design*
   * Secondary keywords: *affordable web design services*, *modern responsive web design*

Why they matter?

* They help you capture a wider range of search queries without stuffing the same term repeatedly.
* They make your content sound natural and avoid over-optimization penalties.
* They improve topical relevance in Google’s eyes because search engines understand that related terms contribute to covering a topic comprehensively.<br>

How to use them?

* Place them naturally in headings, paragraphs, image alt text, and meta descriptions.
* Use them to answer slightly different search intents around your primary topic.
* Spread them across the page rather than clustering them together.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://ai-seo-copilot.gitbook.io/ai-seo-copilot/getting-started/advanced-analysis/secondary-keywords.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
