https://github.com/divineomega/seo-middleware

Middleware to redirect to HTTPS when in production, and remove www. from URLs
https://github.com/divineomega/seo-middleware

https-redirect laravel-5-package laravel-middleware middleware seo seo-middleware

Last synced: 11 days ago
JSON representation

Middleware to redirect to HTTPS when in production, and remove www. from URLs

• Host: GitHub
• URL: https://github.com/divineomega/seo-middleware
• Owner: DivineOmega
• License: lgpl-3.0
• Created: 2016-04-13T12:18:32.000Z (over 8 years ago)
• Default Branch: master
• Last Pushed: 2019-09-23T10:47:15.000Z (about 5 years ago)
• Last Synced: 2024-10-15T02:37:52.709Z (24 days ago)
• Topics: https-redirect, laravel-5-package, laravel-middleware, middleware, seo, seo-middleware
• Language: PHP
• Homepage:
• Size: 9.77 KB
• Stars: 7
• Watchers: 3
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# SEO Middleware

This package contains various middleware classes that can be uses with Laravel

5.1 and above to easily add various SEO benefits to your site / web application.

## Features

* Redirecting production HTTP requests to HTTPS

* Removal of `www.` from requests and redirecting

* Middleware classes can be applied global or to specific routes

## Quick Start

1. Run `composer require divineomega/seo-middleware`.

2. In the `$middleware` array in your `app/Http/Kernel.php` file:

  * For HTTP to HTTPS redirects, add `\DivineOmega\SeoMiddleware\Http\Middleware\HttpsOnly::class`.

  * For removal of `www.` from requests, add `\DivineOmega\SeoMiddleware\Http\Middleware\RemoveWww::class`.

3. Remember to set the `APP_ENV` variable to `prod` (in the project's `.env` file) when the application is running in production. Some middleware will only function when this is set to allow for easier local development.

## Available Middleware Classes

Any of these middleware classes can be used globally, by adding them to

the `$middleware` array in `apps/Http/Kernel.php` file. They can also be used

on a per route basis, by adding them to the `$routeMiddleware` array in the

same file and then associated them with a route in your `apps/Http/routes.php`

file.

### HttpsOnly Middleware

The `HttpsOnly` middleware will redirect any HTTP request to their HTTPS

equivalents. The security of websites is becoming an ever increasing ranking

signal for search engine rankings.

The HTTP to HTTPS redirect will only take place if the application environment

is set to `prod` (production), to aid with local development environments in

the setup of HTTPS can be difficult and in many cases unnecessary. Changing

this setting can be set in your project's `.env` file, as shown in the example

extracts below.

```

APP_ENV=local # Local development (redirect disabled)

```

```

APP_ENV=prod  # Production use (redirect enabled)

```

### RemoveWww Middleware

The `RemoveWww` middleware will check for `www.` within the URL of any requests

made to your web application and then redirect them to a version of the URL

without the `www.` removed. This can be beneficial for SEO purposes by the

potential for similar URLs to be indexed with the same content.

This redirect will occur regardless of the application environment (`APP_ENV`)

setting.