PHPackages tugrul/seo-bundle - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [Utility & Helpers](/categories/utility) 4. / 5. tugrul/seo-bundle ActiveLibrary[Utility & Helpers](/categories/utility) tugrul/seo-bundle ================= symfony seo bundle v1.0.17(2mo ago)0861proprietaryPHPPHP >=8.1CI passing Since Sep 26Pushed 2mo ago1 watchersCompare [ Source](https://github.com/tugrul/SeoBundle)[ Packagist](https://packagist.org/packages/tugrul/seo-bundle)[ RSS](/packages/tugrul-seo-bundle/feed)WikiDiscussions master Synced 1mo ago READMEChangelog (10)Dependencies (14)Versions (19)Used By (0) Tug SEO Bundle ============== [](#tug-seo-bundle) The Tug SEO Bundle is a Symfony bundle that provides a powerful and flexible solution for managing SEO metadata in your Symfony applications. With this bundle, you can easily define and manage SEO fields, their translations, and rendering options, helping you optimize your website's search engine visibility. Features -------- [](#features) - Define SEO fields for various parts of your application, such as titles, descriptions, keywords, and more. - Easily manage translations for SEO fields, allowing you to serve content in multiple languages. - Customize SEO metadata rendering options to suit your needs. - Integration with Symfony's Twig templating engine for easy rendering of SEO metadata in your templates. - Extensible architecture that allows you to add custom SEO fields and renderers. - Built-in support for common SEO standards, including Open Graph and Twitter Card. Installation ------------ [](#installation) You can install the Tug SEO Bundle using Composer: ``` composer require tugrul/seo-bundle ``` After installation, make sure to configure the bundle as needed for your project. Configuration ------------- [](#configuration) The Tug SEO Bundle provides a wide range of configuration options to tailor SEO metadata management to your requirements. You can configure SEO fields, renderers, translation settings, and more. Check the [Configuration](#configuration)section in the documentation for detailed information on available options. ### Basic Configuration [](#basic-configuration) Create a new `config\packages\tug_seo.yaml` file then put contents below. ``` tug_seo: hierarchy: index: - information - gallery information: - about_us - faq default: title: My Website description: If there is no description of the route name, this description will appear on every page routes: index: title: Index Page description: This is homepage of my website gallery: title: Gallery description: Photos of staff information: title: Information description: Some information about my business about_us: title: About Us description: We are responsible for special assignments faq: title: Frequently Asked Questions description: Here are our short answers to the most frequently asked questions ``` Usage ----- [](#usage) Using the Tug SEO Bundle in your Symfony application is straightforward. Here are the basic steps: 1. Define SEO fields: Use the provided services to define SEO fields for your application, such as titles, descriptions, and keywords. 2. Configure translations: If your application serves content in multiple languages, configure translations for SEO fields. 3. Render SEO metadata: In your templates, use the Twig extension to render SEO metadata for the current route. 4. Customize rendering: Customize the rendering of SEO metadata according to your needs, such as adding Open Graph tags or Twitter Card tags. 5. Extend functionality: If necessary, extend the bundle's functionality by adding custom SEO fields or renderers. Registering Services (Optional) ------------------------------- [](#registering-services-optional) While the Tug SEO Bundle provides a comprehensive set of services out of the box, you have the option to register only the services you need for your specific use case. Registering services is an opt-in feature for users who want to customize or use specific parts of the bundle code. See the [Registering Services](#registering-services-optional)section below for more details. ### Define your own field type [](#define-your-own-field-type) Write your definition code for custom field. ``` namespace App\MyProject\Field; use Tug\SeoBundle\Field\{FieldData, FieldInterface}; use Tug\SeoBundle\Model\Meta as MetaModel; class Robot implements FieldInterface { /** * @inheritDoc */ public function getNamespace(): array { return ['my', 'robot']; } public function buildModels(FieldData $fieldData): iterable { $meta = new MetaModel(); $meta->setName('robot'); $meta->setContent($fieldData->getContent()); yield $meta; } } ``` Enable it on service configuration for autowiring. ``` services: App\MyProject\Field\Robot: ~ ``` Configure it on your `tug_seo.yaml` file. ``` tug_seo: routes: my_special_route: my: robot: noindex, nofollow ``` You will see the code below on your generated html. ``` ``` License ------- [](#license) The Tug SEO Bundle is open-source software licensed under the [MIT License](LICENSE). Contributing ------------ [](#contributing) Contributions are welcome! If you have suggestions, bug reports, or would like to contribute to the development of this bundle, please follow our [Contribution Guidelines](CONTRIBUTING.md). Credits ------- [](#credits) The Tug SEO Bundle is developed and maintained by the Tuğrul. Special thanks to our contributors for their valuable input and contributions. Support ------- [](#support) If you encounter any issues or have questions about the Tug SEO Bundle, please [open an issue](https://github.com/tugrul/SeoBundle/issues) on GitHub, and we'll do our best to assist you. ### Health Score 44 — FairBetter than 92% of packages Maintenance88 Actively maintained with recent releases Popularity10 Limited adoption so far Community8 Small or concentrated contributor base Maturity60 Established project with proven stability Bus Factor1 Top contributor holds 100% of commits — single point of failure How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Every ~52 days Total 18 Last Release 61d ago ### Community Maintainers ![](https://www.gravatar.com/avatar/8203eaef0737a157a828b37dc85a63defa0d26e3f215135fe76cff6c67d2fa20?d=identicon)[tugrul](/maintainers/tugrul) --- Top Contributors [![tugrul](https://avatars.githubusercontent.com/u/163442?v=4)](https://github.com/tugrul "tugrul (25 commits)") ### Code Quality TestsPHPUnit ### Embed Badge ![Health badge](/badges/tugrul-seo-bundle/health.svg) ``` [![Health](https://phpackages.com/badges/tugrul-seo-bundle/health.svg)](https://phpackages.com/packages/tugrul-seo-bundle) ``` ### Alternatives [sylius/sylius E-Commerce platform for PHP, based on Symfony framework. 8.4k5.6M650](/packages/sylius-sylius)[shopware/platform The Shopware e-commerce core 3.3k1.5M3](/packages/shopware-platform)[sulu/sulu Core framework that implements the functionality of the Sulu content management system 1.3k1.3M152](/packages/sulu-sulu)[prestashop/prestashop PrestaShop is an Open Source e-commerce platform, committed to providing the best shopping cart experience for both merchants and customers. 9.0k15.4k](/packages/prestashop-prestashop)[shopware/core Shopware platform is the core for all Shopware ecommerce products. 595.2M386](/packages/shopware-core)[ec-cube/ec-cube EC-CUBE EC open platform. 78527.0k1](/packages/ec-cube-ec-cube) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)