Download the PHP package noeldemartin/laravel-semantic-seo without Composer

Laravel Semantic SEO

Use this package to define Semantic SEO information through meta tags and structure data types.

Installation

Install using composer:

Usage

This package helps to scaffold Semantic HTML for a website defining two things:

• Meta tags: The most common approach to define semantic information in a website is to include meta tags with specific information of the current page. This is how most social networks create a preview when sharing links, for example Twitter Cards or Facebook Open Graph. Search engines also use some of these tags to format how a link appears on the search results.

• Types: In order to provide richer semantics, types can be defined for specific use cases such as Blog Posts, Persons, Web Applications, etc. The type system used in this package provides schema.org schemas that are a common way of defined Structured Data. One advantage of defining this richer data, is that meta tags can be inferred from this types and information doesn't need to be repeated.

The markup generated with this package should be placed on the head element. A Blade directive named semanticSEO is included with this package:

In order to define Types and Meta tags, use the SemanticSEO facade.

Using Types

Not all types are available with this package, but most common are. For example, you could define the information for a WebSite schema in your page as such:

You can place this code wherever you want, for example on the Controller handler methods.

Types automatically add meta tags that make sense, for example the code above would generate the following markup:

Other than the available types, any new types can be used with the method is like so:

To see more examples of what's available and how to use existing types, take a look to the tests in TypesTests.php file under /tests/Unit.

Using Meta tags

Some times it is necessary to define meta tags explicitly. It's also possible that for some reason you don't want to use types, in which case meta tags can be defined one by one:

Keep in mind that this package is aware of some special meta tags, for example using the "title" meta tag will actually render as a <title> tag and not <meta>. Multiple meta tags can also be defined at once (for example, if you keep the content of this tags in translation files):

To see more examples of what's available and how to use existing meta tags, take a look to the tests in MetaTagsTests.php file under /tests/Unit.

Some other special meta tags are the following:

Robots

To hide one page from crawlers, call SemanticSEO::hide() which will generate:

A middleware has also been registered in case this wants to be called from the routes file (for example, when using the view short-hand to define routes):

Sitemap and RSS

To define sitemap or rss xml locations (this could be placed in a Service Provider to prevent calling this in every controller):

Which will generate:

Canonical url

The canonical location of the page is automatically generated for every page, this can be disabled setting it as false (as well as any meta overriding by Types):

Social networks

Some short-hands are also defined for twitter and open graph, which will automatically include twitter: and og: prefixes:

Which will generate:

Extending

The basic functionallity for this package is completed, but it's lacking some type definitions. They are, however, very easy to add. In order to create a new type (or extend an existing one) three things need to be done:

• Extend one existing type under NoelDeMartin\SemanticSEO\Types namespace. If none appropiate exists, use Thing.
• If the name of your class is not the name of the type (for example, if you are defining a class to reuse the arguments), override getType method and return the appropriate name.
• If you want to automatically add meta tags when using a type, override the beforeRender method.
• If you want to add extra field attributes, override the getAttributeDefinitions method.

Examples on how to do this can be found under the /src/Types folder, since existing classes already use this approach. I encourage you to create PRs adding extensions that live within the schema.org specification. The hierarchy of types together with their fields can be found here.