> For the complete documentation index, see [llms.txt](https://tmniche-docs.keywordrush.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tmniche-docs.keywordrush.com/building-a-site/edit-topic-map.md).

# Edit your Topic Map

Your Topic Map is a proposal — shape it before you generate anything. This page covers the edits you'll actually use: changing an article's details, setting a hub's category, adding your own articles, and skipping the ones you don't want.

{% hint style="info" %}
Attaching products and adjusting internal links happen here too, but they have their own pages: [Curate products](/building-a-site/curate-products.md) and [Interlinking](/core-concepts/interlinking.md).
{% endhint %}

## Open an article

Click any article row — in the plan or in the **Content Queue** — to open the **node drawer** on the right. It opens read-only (**Node details**); click **Edit** to change fields, then **Save**.

![Clicking an article row opens the node drawer on the right](/files/EdeLMvgkd3jAq85RAdD2)

## Edit an article's details

In **Edit** mode you can change:

* **Working title** — the article's recommended title, and a starting point: TMN may polish it during generation to match the finished article and real product data.
* **Primary keyword** / **Secondary keywords** — what it targets.
* **Format** — the kind of article (review, how-to, comparison, …).
* **Intent** — **Money**, **Info**, or **Mixed**. Some formats (reviews, roundups, comparisons) must be Money or Mixed; the drawer won't let you set Info for those.
* **Target Publish date** — where the article sits on your calendar. **If the date is in the future, the generated post is created as *****Scheduled***** for that date.** Otherwise the post uses the status (draft, pending, or publish) from your Generation Preset.
* **Writing preset** — override the plan's preset for just this article. Defaults to **Inherit from plan**.
* **Instructions for AI** — free-text notes that steer how this one article is written.

Click **Save** when you're done.

{% hint style="warning" %}
**Leave a pillar's format alone.** TMN gives each pillar a broad format (a beginner guide or buying guide) on purpose: a pillar has to stay a wide overview so it naturally hosts links to every article in its hub. Switching it to a narrow format breaks that role.
{% endhint %}

## Set a hub's category

Every article in a hub is published into one WordPress category. Next to each hub you'll see its category — TMN's suggested name, or **Set category** if none is chosen yet. Click it to:

* **search and pick an existing** category, or
* **type a new name** and choose **Use new category: "…"**.

![The hub category picker (search or type a category)](/files/TC60ww2AuOXV78zN1VoN)

## Add your own article

Need a topic TMN didn't include? On the hub where it belongs, click **+ Add article**. In the **New node** drawer, fill the required fields — **Working title**, **Primary keyword**, **Format**, **Intent**, and **Target Publish date** — then click **Create node**. Your article joins the plan and generates like any other.

![The + Add article button on a hub and the New node drawer](/files/4FLt7BmlnLFTTeIoTm9m)

## Skip or delete

* **Skip** hides an article's **Generate** button without removing it — handy for topics you might want later, or ones you'd rather not generate. **Unskip** any time. This is how you set aside AI-planned articles you don't want.
* **Delete node** is only available for articles **you added yourself**. AI-planned articles can't be deleted — skip them instead.

## Next

* [**Generate & publish articles**](/building-a-site/generate-articles.md) — turn your plan into posts.
* [**Curate products**](/building-a-site/curate-products.md) — attach specific products to an article.
* [**Interlinking**](/core-concepts/interlinking.md) — how internal links work and how to adjust them.


---

# 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, and the optional `goal` query parameter:

```
GET https://tmniche-docs.keywordrush.com/building-a-site/edit-topic-map.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.