PHPackages                             in-square/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. in-square/seo-bundle

ActiveSymfony-bundle[Utility & Helpers](/categories/utility)

in-square/seo-bundle
====================

Fork of leogout/seo-bundle with Symfony 7 support and extensible SEO tag attributes.

v1.0.2(3mo ago)071MITPHPPHP ^8.3

Since Apr 12Pushed 3mo agoCompare

[ Source](https://github.com/in-square/seo-bundle)[ Packagist](https://packagist.org/packages/in-square/seo-bundle)[ RSS](/packages/in-square-seo-bundle/feed)WikiDiscussions main Synced 1w ago

READMEChangelog (3)Dependencies (4)Versions (4)Used By (1)

InsquareSeoBundle
=================

[](#insquareseobundle)

Maintained fork of [leogout/SeoBundle](https://github.com/leogout/SeoBundle), adapted for modern Symfony/PHP projects. This fork includes:

- Symfony `7.3` compatibility
- PHP `8.3` compatibility
- extensible custom attributes for `link`/`meta` tags (for example `hreflang`)

This bundle provides a simple and flexible API to manage *search engine optimization* (SEO) tags in your application. Its main goal is to make it simple for you to manage the most common **meta**, **open graph** and **twitter card** tags and to let you configure less common ones with ease.

Compatibility and Migration
---------------------------

[](#compatibility-and-migration)

- Supported stack: Symfony `7.3+`, PHP `8.3+`, Twig `3+`.
- Backward-compatibility Twig alias `leogout_seo()` is intentionally removed.
- Use `render_seo_tags()` and `render_seo_tags('alias')` only.
- Migration checklist: [`docs/migration-plan.md`](docs/migration-plan.md).

Installation
------------

[](#installation)

Install the bundle with the command:

`composer require in-square/seo-bundle`

Register the bundle in `config/bundles.php`:

```
return [
    // ...
    InSquare\SeoBundle\InsquareSeoBundle::class => ['all' => true],
];
```

Configuration
-------------

[](#configuration)

These configuration values are the defaults used to render your tags. See the next section to learn how to override them dynamically.

There are four sections in the config:

- `general`: The *global* configuration. Its values are shared among the other as defaults.
- `basic`: A set of the most common SEO tags.
- `og`: A set of *open graph* tags based on .
- `twitter`: A set of *twitter card* tags based on

See "Configuration reference" to get the whole configuration.

**In your `config/packages/in_square_seo.yaml`:**

```
in_square_seo:
    general:
        title: Default title
        description: Default description.
        image: http://images.com/poneys/12/large # This one is shared by open graph and twitter only
    basic:
        title: Awesome title
        keywords: default, keywords
    og:
        type: website
        url: http://test.com/articles
    twitter:
        card: summary
        site: '@leogoutt'
```

**In your view:**

```

    {{ render_seo_tags() }}

```

**NOTE:** *You can provide a generator name to the `render_seo_tags()` twig method to render it specifically. For example, to render the `basic` seo generator, you can use `render_seo_tags('basic')`.*

**The result:**

```

    Awesome title

```

**NOTE:** *By default, the SEO generators aren't loaded if you don't require them in the config. However, if you want to use the associated generators without configuring any default values (or configuring only the general ones), you can use this notation:*

```
in_square_seo:
   general:
       title: Default title
       description: Default description.
       image: http://images.com/poneys/12/large # This one is shared by open graph and twitter only
   basic: ~
   og: ~
   twitter: ~
```

Setting values dynamically
--------------------------

[](#setting-values-dynamically)

You can get the `'[basic|twitter|og]` as a service to set or override any values. Each configuration value can be overridden using a setter of the following form: `$this->get('in_square_seo.provider.generator')->get('` **\[basic|twitter|og\]** `')->set` **\[config field name\]** `(` **\[value\]** `)`

For example, if you want to change `title` and `robots` from `basic`, you can do this:

```
class DefaultController extends Controller
{
    public function indexAction()
    {
        $this->get('in_square_seo.provider.generator')->get('basic')
            ->setTitle('Title set in controller')
            ->setRobots(true, false); // they can be chained

        return $this->render('AppBundle:Default:index.html.twig');
    }
}
```

Setting values from a resource
------------------------------

[](#setting-values-from-a-resource)

You can configure your own model classes to let the seo generators do all the work thanks to the **fromResource()** method. Multiple interfaces are available to help the method guess which setters to call to fill the tags.

This is an example for the `basic` generator: **In your resource:**

```
use InSquare\SeoBundle\Seo\Basic\BasicSeoInterface;

class MyResource implements BasicSeoInterface
{
    protected $name;
    protected $description;
    protected $tags = [];

    // ...Your logic

    // These methods are from BasicSeoInterface and have to
    // return a string (or an object with a __toString() method).
    public function getSeoTitle()
    {
        return $this->name;
    }
    public function getSeoDescription()
    {
        return $this->description;
    }
    public function getSeoKeywords()
    {
        return implode(',', $this->tags);
    }
}
```

**In your controller:**

```
class MyController extends Controller
{
    public function indexAction(Request $request)
    {
        $myResource = new MyResource();
        $myResource
            ->setName('Cool resource')
            ->setDescription('Some description')
            ->addKeyword('hey')
            ->addKeyword('ho')
            ->addKeyword('let's go!');

        $this->get('in_square_seo.provider.generator')->get('basic')->fromResource($myResource);

        return $this->render('MyController:Default:index.html.twig');
    }
}
```

**In your view:**

```

    {{ render_seo_tags('basic') }}

```

**The result:**

```

    Cool resource

```

There are **three** main interfaces, one for each generator:

- `BasicSeoInterface` for `basic`
- `OgSeoInterface` for `og`
- `TwitterSeoInterface` for `twitter`

These interfaces extend *simpler interfaces* that you can implement instead, or additionally. For example, if you only have a meta description on your resource, you can implement `DescriptionSeoInterface` only to provide a description alone. This is the list of the different interfaces and what they extends:

TitleSeoInterfaceDescriptionSeoInterfaceKeywordsSeoInterfaceImageSeoInterfaceBasicSeoInterfaceXXXOgSeoInterfaceXXXTwitterSeoInterfaceXXXAdvanced usage
--------------

[](#advanced-usage)

If the built-in generators don't suit your needs, InsquareSeoBundle provides a way to create your own SEO generators. First, you have to create a class that extends the AbstractSeoGenerator class:

```
use InSquare\SeoBundle\Seo\AbstractSeoGenerator;

class MyTagsGenerator extends AbstractSeoGenerator
{
    public function setMyTag($content)
    {
        $this->tagBuilder->addMeta('myTag')
            ->setType(MetaTag::NAME_TYPE)
            ->setValue('myAwesomeTag')
            ->setContent((string) $content);

        return $this;
    }

    public function getMyTag()
    {
        return $this->tagBuilder->getMeta('myTag');
    }
}
```

Then, register it as a service and add it a `in_square_seo.generator` tag and a custom alias. Don't forget the `@in_square_seo.builder` dependency:

```
services:
    app.seo_generator.my_tags:
        class:     AppBundle\Generator\MyTagsGenerator
        arguments: [ '@in_square_seo.builder' ] # This is required
        tags: { name: in_square_seo.generator, alias: my_tags }
```

That's it, now you can use it alongside the others:

**In your controller:**

```
class MyController extends Controller
{
    public function indexAction(Request $request)
    {
        $this->get('in_square_seo.provider.generator')->get('my_tags')->setMyTag('cool');

        return $this->render('MyController:Default:index.html.twig');
    }
}
```

**In your view:**

```

    {{ render_seo_tags('my_tags') }}

```

**Result:**

```

```

Custom attributes (issue #30)
-----------------------------

[](#custom-attributes-issue-30)

You can pass custom attributes directly to `addLink()` or `addMeta()`. Tag content and attribute values are HTML-escaped by default for safer rendering. Example inside your own SEO generator (class extending `AbstractSeoGenerator`):

```
$this->tagBuilder->addLink(
    'alternate_pl',
    'https://site.com/page-pl',
    'alternate',
    null,
    null,
    ['hreflang' => 'pl']
);
```

This renders, for example:

```

```

Configuration reference
-----------------------

[](#configuration-reference)

```
in_square_seo:
    general:
        title: Default title
        description: Default description.
        image: http://images.com/poneys/12/large
    basic:
        title: Basic title
        description: Basic description.
        keywords: default, keywords
        canonical: http://test.com
        robots:
            index: false
            follow: false
    og:
        title: Open graph title
        description: Open graph description.
        image: http://images.com/poneys/12/large
        type: website # article, book, profile
        url: http://test.com/articles
    twitter:
        title: Twitter title
        description: Twitter description.
        image: http://images.com/poneys/12/thumbnail
        card: summary # summary_large_image
        site: '@leogoutt' # optional
```

Contributing
------------

[](#contributing)

If you want to contribute (thank you!) to this bundle, here are some guidelines:

- Please respect the [Symfony guidelines](http://symfony.com/doc/current/contributing/code/standards.html)
- Test everything! Please add tests cases to the tests/ directory when:
    - You fix a bug that wasn't covered before
    - You add a new feature
    - You see code that works but isn't covered by any tests (there is a special place in heaven for you)

Todo
----

[](#todo)

- Packagist

Thanks
------

[](#thanks)

Many thanks to the [ARCANEDEV/SEO-Helper](https://github.com/ARCANEDEV/SEO-Helper) who authorized me to take some ideas from their library and to [KnpMenuBundle](https://github.com/KnpLabs/KnpMenuBundle) which inspired me for the Providers APIs.

###  Health Score

38

—

LowBetter than 83% of packages

Maintenance81

Actively maintained with recent releases

Popularity4

Limited adoption so far

Community8

Small or concentrated contributor base

Maturity51

Maturing project, gaining track record

 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 ~2 days

Total

3

Last Release

98d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/ad729a699b734ec9098b169b396f7c686c5eb920bd04d20b29f346b592f59ee8?d=identicon)[kolarian](/maintainers/kolarian)

---

Top Contributors

[![twin-elements](https://avatars.githubusercontent.com/u/17727266?v=4)](https://github.com/twin-elements "twin-elements (4 commits)")

---

Tags

symfonyseoSymfony Bundle

###  Code Quality

TestsPHPUnit

### Embed Badge

![Health badge](/badges/in-square-seo-bundle/health.svg)

```
[![Health](https://phpackages.com/badges/in-square-seo-bundle/health.svg)](https://phpackages.com/packages/in-square-seo-bundle)
```

###  Alternatives

[easycorp/easyadmin-bundle

Admin generator for Symfony applications

4.3k17.9M400](/packages/easycorp-easyadmin-bundle)[rcsofttech/audit-trail-bundle

Enterprise-grade, high-performance Symfony audit trail bundle. Automatically track Doctrine entity changes with split-phase architecture, multiple transports (HTTP, Queue, Doctrine), and sensitive data masking.

1189.8k](/packages/rcsofttech-audit-trail-bundle)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)