SEO features for Shopware 6
require in composer.json
composer require teu/seo
Versions the maintainer declares support for in
composer.json, not versions extdir has tested. A dashed chip
marked ˚ means the constraint is open-ended, like
^6.5.
| Version | Declared constraint | Read from | Confidence | Released | Download |
|---|---|---|---|---|---|
| 2.0.0 | >=6.7.0 |
core | wildcard | 2025-12-18 | source |
| 1.3.0 | >=6.6.10 |
core | wildcard | 2025-06-05 | source |
| 1.2.1 | >=6.5 <6.6.10 |
core | explicit | 2025-06-05 | source |
| 1.2.0 | ~6.5 |
core | caret | 2025-06-02 | source |
| 1.1.0 | ~6.5 |
core | caret | 2024-12-02 | source |
| 1.0.1 | ~6.5 |
core | caret | 2024-11-08 | source |
| 1.0.0 | ~6.5 |
core | caret | 2024-11-08 | source |
The constraint column is the maintainer's own text, verbatim.
Available on Packagist:
composer require teu/seo
Then activate it:
bin/console plugin:refresh bin/console plugin:install --activate TeuSeo
From extra.shopware-plugin-class, so this is the name to
type.
same category · covers the same Shopware versions · actively maintained
same category · covers the same Shopware versions · actively maintained
same category · covers the same Shopware versions · actively maintained
same category · covers the same Shopware versions
same category · overlapping Shopware versions · actively maintained
same category
same category · covers the same Shopware versions
same category · overlapping Shopware versions
same category · overlapping Shopware versions · actively maintained
same category · overlapping Shopware versions · actively maintained
Not on GitHub, so write access cannot be checked through an API. Publish a small file in the repository instead.
You will be asked to sign in, so the verification belongs to an account.
Not the maintainer? Report a wrong category, an outdated description or a rights complaint here. No account needed, and the takedown policy covers what happens next.
Markdown:
[](https://extdir.com/extension/teu-seo)
Updates when the declared compatibility changes.