> For the complete documentation index, see [llms.txt](https://learning.seoki.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learning.seoki.com/english/working-with-seoki/working-with-seoki.md).

# Working with SEOKI

In just a few steps, you can significantly improve your visibility with SEOKI. How does it work?

### KEYWORD RESEARCH

What keywords are your customers searching for? What are the questions that concern them? The right keywords form the basis of your successful content. That's why thorough keyword research is essential for sustainable visibility.

### WORDPRESS INTEGRATION

To make everything automated, your WordPress site is connected to SEOKI: This way, your new content can perform live right away.

### CREATE PROJECT

For each domain, you create your own project. Here, you upload new keywords and generate new content at the push of a button.

### LET THE MAGIC HAPPEN

Upload keywords, generate batches, enjoy content!

### FINISHING TOUCHES

The foundation is laid! Now you can refine by manually editing your new articles.

{% hint style="info" %}
You need help? [Contact us](https://seoki.com/kontakt).
{% endhint %}


---

# 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://learning.seoki.com/english/working-with-seoki/working-with-seoki.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.