Conversations
Manage multiple chat threads per project to keep different SEO workflows organized with isolated context.
What Are Conversations
A conversation is a named chat thread scoped to a single project. Each thread has its own message history, agent context, and title. There is no limit on the number of threads per project, and the agent inside each thread only sees messages from that thread — context from one task never pollutes another.
Conversations are ordered by last updated time. Titles default to a timestamp but can be renamed to anything descriptive.
Use Cases
Keeping every SEO task in a single thread fills the memory window with unrelated context. Separate threads keep each workflow focused.
| Workflow | Why a separate thread helps |
|---|---|
| Content planning | The agent accumulates context about covered topics and remaining gaps. |
| Technical SEO | Crawl analysis and redirect audits stay isolated from editorial work. |
| Monthly reporting | GSC trend pulls build a running log you can revisit each month. |
| Article drafts | Brief, outline decisions, and revisions stay together per article. |
Technical crawl questions, content ideas, and GSC trends share one thread. The 20-message window fills with unrelated context and earlier decisions get pushed out.
Each thread stays on topic. The agent's memory window remains filled with relevant context for that specific task.
Creating, Switching, and Renaming
The conversation list appears in the left sidebar. From there you can create, switch, rename, or delete threads.
- Create — click “New Conversation” at the top of the sidebar.
- Switch — click any thread to load its message history.
- Rename — click the thread title to edit inline. Use descriptive names like “Q2 content calendar”.
- Delete — use the delete option in the thread menu. This is permanent.
“Let's start a new conversation focused on content planning for Q2”
A clear opening message sets the thread's purpose. The agent anchors its behavior to this framing.
Conversation Memory
Within a thread, the agent maintains context of keywords evaluated, content decisions made, crawl results, and any instructions about tone or structure. You do not need to re-explain prior decisions on follow-up questions.
The 20-Message Window
The agent uses the most recent 20 messages as its active context. Older messages remain in the database and chat UI but are no longer in the agent's working memory.
If the agent seems to forget earlier decisions, start a fresh thread and summarize the key conclusions from the previous thread in your opening message.
Tips for keeping threads effective:
- One workflow per thread. Narrower scope means more useful accumulated context.
- Name threads early. A descriptive title makes the list navigable as it grows.
- Open with context. Start with one or two sentences describing the goal.
- Start fresh when done. Leave completed threads as records and open new ones for the next phase.
Project-Scoped Threads
Conversations belong to the currently selected project. Switch projects and you get a completely different set of threads. The agent's context in each thread is implicitly scoped to that project's GSC properties, crawled content, and writing style profile.
If you manage multiple sites, use the project switcher to move between them. Each project maintains independent conversation history.
Try these prompts
© 2026 Agentic SEO. All rights reserved.