> 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/seo-meta.md).

# SEO titles & meta descriptions

TMN writes an **SEO title** and **meta description** for every article it generates — the text search engines show in results. It works with your existing SEO plugin, and stands in for one if you don't have it.

## Turn it on (it's on by default)

Meta generation is controlled by your **Generation Preset**, under **SEO automation**:

* **Generate meta title**
* **Generate meta description**

Both are **on by default**, so you usually don't have to do anything. The same SEO-automation group also generates **tags** and **schema**. Switch any of them off in the preset if you'd rather handle them yourself — see [Use presets](/building-a-site/presets.md).

## Works with your SEO plugin

When a post is generated, TMN detects your active SEO plugin and writes the title and description straight into **its** fields — so they appear in that plugin's editor and on your live pages, exactly as if you'd typed them in. Supported plugins:

* **Yoast SEO**
* **Rank Math**
* **All in One SEO**
* **SEOPress**
* **The SEO Framework**

Detection is automatic — there's nothing to configure. If you switch SEO plugins later, newly generated posts write to the new plugin's fields.

{% hint style="info" %}
TMN **also** keeps its own copy of every title and description, alongside the SEO plugin's. So nothing is lost if you change or remove your SEO plugin.
{% endhint %}

## No SEO plugin? TMN handles it

If none of the supported plugins is active, TMN serves the meta itself:

* It outputs the **page title** and the **`<meta name="description">`** tag on each article, so search engines still get the right values.
* It adds a lightweight **"SEO Meta (TMN)"** box on the post editor where you can read and edit the meta title and description by hand.

That box only appears when no supported SEO plugin is active — when one is, you edit the meta in that plugin instead.

## Editing after generation

You're always free to tweak what TMN generated — your edits win.

* **With an SEO plugin** — edit the title and description in that plugin's panel on the post, as usual.
* **Without one** — edit them in the **SEO Meta (TMN)** box on the post editor.

## Where it's stored

TMN writes the title and description to two custom fields on every post:

* **Meta title** — `_tmn_meta_title`
* **Meta description** — `_tmn_meta_description`

It writes the active SEO plugin's own keys too, so both stay in sync. Developers can change or extend the destination keys with the `tmn_seo_meta_keys` filter.

## Next

* [**Use presets**](/building-a-site/presets.md) — where the SEO-automation toggles live.
* [**Generate & publish articles**](/building-a-site/generate-articles.md) — meta is written as each post is created.


---

# 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/seo-meta.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.