> For the complete documentation index, see [llms.txt](https://docs.premsoft.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.premsoft.de/en/plugins/seo-tools/management-dashboard/meta-data.md).

# Meta data

The meta title and meta description are the text Google shows in the search results. They co-decide whether someone clicks your result. This chapter bundles all the tools you use to optimise these texts – from a single product to bulk maintenance.

## SERP preview (Basic)

**What is it good for?** You immediately see how your product or category will look on Google – before the page even goes live. This avoids truncated titles or unsuitable descriptions.

**How to use it:** Open a product or category and switch to the **SEO** tab. Right above the meta fields, a true-to-life Google preview shows the title, URL and description. As you type, the preview updates live.

## Pixel and character counter (Basic)

**What is it good for?** Google truncates titles and descriptions that are too long. What matters is not the character count but the **pixel width**. The counter shows you both and warns before your text gets cut off.

**How to use it:** Below every meta title and meta description field (on products, categories and landing pages) you see a coloured bar: **green** = optimal length, **yellow** = borderline, **red** = will be truncated. Aim for the green range.

## Robots meta tag per page (Basic)

**What is it good for?** Some pages should not appear on Google – such as duplicates, internal landing pages or expiring campaigns. With the robots tag you control per page whether and how search engines treat it.

**How to use it:** In the SEO tab of a product, category or landing page you choose the desired value (e.g. *index,follow* or *noindex,follow*). The product listing additionally has an **SEO status column** where you see at a glance which products are set to "noindex".

## Open Graph & Twitter Cards (Premium)

**What is it good for?** When someone shares your shop link on Facebook, LinkedIn, WhatsApp or X (Twitter), the "social card" decides the title, description and image of the preview. Without your own details this often looks incomplete.

**How to use it:** In the SEO tab you find dedicated fields for the Open Graph and Twitter Card title, description, image and card type. A **live preview** shows you how the shared post looks in social networks. If you leave fields empty, the plugin uses sensible defaults from your product data.

## Bulk meta generator (Premium)

**What is it good for?** Writing meta texts for hundreds or thousands of products by hand is impossible. The generator creates them automatically from **templates with placeholders** – consistent and in minutes instead of weeks.

**How to use it:**

{% stepper %}
{% step %}

## Open the bulk generator

Open **SEO Tools → Bulk generator**.
{% endstep %}

{% step %}

## Create a template

Create a **template**, e.g. `Buy {product_name} | {manufacturer}` for the title and a matching description. The available placeholders (product name, manufacturer, category, price, etc.) are shown to you.
{% endstep %}

{% step %}

## Apply filters if needed

If needed, narrow it down with **filters** (only one category, only one manufacturer, or "only products without meta data").
{% endstep %}

{% step %}

## Choose the mode

Choose the mode: **Fill empty** (existing texts are kept) or **Overwrite**.
{% endstep %}

{% step %}

## Preview the results

**Preview (dry run)** opens a window with the first 20 results – nothing is saved yet. If the result looks right, you start the generation straight from that window via **Execute**. Alternatively close the preview and use the **Execute** button on the page.
{% endstep %}

{% step %}

## Run generation for large catalogues

For large catalogues the execution runs in the background. A **progress bar** shows how many products have been processed; you can leave the page and come back later.
{% endstep %}
{% endstepper %}

## AI meta suggestions (Premium)

**What is it good for?** Templates are consistent but generic. For especially important products you want more individual, higher-converting texts. The AI writes meta titles and descriptions at the push of a button – tailored to the specific product.

**How to use it:**

{% stepper %}
{% step %}

## Configure AI integration

In the [Configuration](/en/plugins/seo-tools/configuration.md#ai-integration-premium) under **AI integration**, store your provider (Anthropic Claude, OpenAI or a custom endpoint), the API key and the model.
{% endstep %}

{% step %}

## Generate suggestions from the SEO tab

Open a product, **SEO** tab. In the **SEO score** card you find the buttons **Generate meta title** and **Generate meta description**.
{% endstep %}

{% step %}

## Apply, regenerate, or cancel

The AI produces a suggestion that you write into the field with **Apply**, discard with **Regenerate**, or ignore with **Cancel**.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
**Important:** **Apply** only writes the text into the form field – you still have to **save** the product afterwards.
{% endhint %}

Optionally you store **custom prompts** and an **output language** so the texts match your brand. A **monthly usage overview** shows how many AI requests have already been consumed.

### AI for many products at once

If you do not want to go product by product, you will find the **AI bulk generation** card under **SEO Tools → Bulk generator**:

{% stepper %}
{% step %}

## Choose the field

Choose the **field** (meta title or meta description).
{% endstep %}

{% step %}

## Choose the mode

Choose the **mode**: *fill empty fields only* or *overwrite*.
{% endstep %}

{% step %}

## Set the maximum number of products

Set **max. products** – the upper limit for this run (default 50, maximum 1000).
{% endstep %}

{% step %}

## Optionally narrow the selection

Optionally narrow it down with the **filters** of the card above (category, manufacturer, "only without meta data").
{% endstep %}

{% step %}

## Start AI generation

**Start AI generation** – the run is queued and processed in the background with a progress indicator. You can leave the page and come back later.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
**Cost warning:** Every product triggers **one paid request** at your AI provider. That is why each run is capped. Start with a small number, check the results and only then increase it.

If every request fails right at the start (e.g. a wrong API key), the run aborts immediately instead of sending more requests.
{% endhint %}

{% hint style="info" %}
**Note:** The AI feature incurs costs at the respective AI provider – not at PremSoft. You use your own API key.
{% 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, and the optional `goal` query parameter:

```
GET https://docs.premsoft.de/en/plugins/seo-tools/management-dashboard/meta-data.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.