> 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/blog/seo-rss-and-rich-snippets.md).

# SEO, RSS and Rich Snippets

PremsBlog is built for maximum discoverability. You don't have to configure anything — most SEO measures are active out of the box once the plugin is enabled in the sales channel.

## Speaking URLs

SEO URLs are created for every blog page automatically:

| Page              | Example URL            |
| ----------------- | ---------------------- |
| Magazine overview | `/magazine`            |
| Article detail    | `/magazine/my-article` |
| Authors overview  | `/authors`             |
| Author detail     | `/authors/max-doe`     |

URL paths follow the article title or the author's name. They automatically nest below the magazine / author category you chose in the [Plugin configuration](/en/plugins/blog/create-and-edit-blog-posts/configuration.md). The result: speaking paths that visitors and Google understand instantly.

If you prefer your own SEO URL templates, you can override them just like for any other Shopware route under **Settings → Shop → SEO URLs**.

## Meta tags

Every article detail page automatically sets:

* **Browser tab title** — uses the article meta title; falls back to the article title when empty.
* **Description** for Google search results — uses the meta description; falls back to the short description when empty.
* **Canonical URL** pointing to the speaking address of the current article — prevents duplicate content issues.
* **Open Graph and Twitter Card tags** for nice previews when shared on social networks.

Author and listing pages receive their matching meta information.

## Structured data (rich snippets)

Every article detail page emits **structured data markup** of type "blog article" for Google. With it Google can render in the search results:

* The **title** and a short description excerpt
* The **preview image**
* The **author**
* The **publish date** and last-modified date
* **Stars** and the review count (as soon as approved reviews exist — *premium*)

The result: your articles stand out in Google's search results much more than plain text matches.

## RSS feed

At `/blog/feed` the plugin exposes a complete RSS 2.0 feed. Per item it carries the title, speaking URL, publish date, short description, the full article body, the author name and the assigned categories.

Useful for…

* **Newsletter marketing** — RSS campaigns in Mailchimp or Sendinblue read the feed directly and send out a new issue automatically for every new article.
* **Feed readers** like Feedly, NewsBlur or Inoreader.
* **Third-party systems** that regularly import or sync your new articles.

The number of items in the feed (default 20) and the optional feed description live in the [Plugin configuration](/en/plugins/blog/create-and-edit-blog-posts/configuration.md).

## Sitemap

Articles and author pages land in your shop's XML sitemap automatically as soon as they are active. You don't have to do anything — the sitemap cache is refreshed via the regular Shopware mechanism.

## Inactive articles

Articles with status *Draft*, *In review* or *Disabled*, as well as articles outside their visibility window, return **HTTP 404** in the shop. They can be prepared safely without search engines or visitors seeing them too early.


---

# 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/blog/seo-rss-and-rich-snippets.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.