Download the PHP package codebar-ag/laravel-prerender without Composer

This package was developed to give you a quick start to integrate with the Prerender.io service in your Laravel application.

🙇 Credits

This package is a clone from jeroennoten/Laravel-Prerender with jeroennoten as the original author. CasperLaiTW provided Laravel 6,7 & 8 compatibility by an unmerged (14th September 2020) Pull-Request.

💡 What is Prerender.io?

The Prerender.io middleware will check each request to see if it's a from a crawler. If it is a request from a crawler, the middleware will send a request to Prerender.io for the static HTML of that page. If not, the request will continue on to your normal server routes. The crawler never knows that you are using Prerender.io since the response always goes through your server.

Google now recommends that you use Prerender.io in their Dynamic Rendering documentation!

🛠 Requirements

⚙️ Installation

You can install the package via composer:

If you want to make use of the Prerender.io service, add the following to your .env file:

Or if you are using a self-hosted service, add the server address in the .env file.

That's it. Every GET-Request from a crawler will be prerendered.

✋ Disable the service

You can disable the service by adding the following to your .env file:

This may be useful for your local development environment.

✏️ How it works

1. The middleware checks to make sure we should show a prerendered page
   1. The middleware checks if the request is from a crawler (agent string or _escaped_fragment_)
   2. The middleware checks to make sure we aren't requesting a resource (js, css, etc...)
   3. (optional) The middleware checks to make sure the url is in the whitelist
   4. (optional) The middleware checks to make sure the url isn't in the blacklist
2. The middleware makes a GET request to the prerender service (phantomjs server) for the page's prerendered HTML
3. Return the HTML to the crawler

🔧 Configuration file

You can publish the config file with:

Afterwards you can customize the Whitelist/Blacklist on your own.

This is the contents of the published config file:

🤍 Whitelist

Whitelist paths or patterns. You can use asterix syntax. If a whitelist is supplied, only url's containing a whitelist path will be prerendered. An empty array means that all URIs will pass this filter. Note that this is the full request URI, so including starting slash and query parameter string.

🖤 Blacklist

Blacklist paths to exclude. You can use asterix syntax. If a blacklist is supplied, all url's will be prerendered except ones containing a blacklist path. By default, a set of asset extensions are included (this is actually only necessary when you dynamically provide assets via routes). Note that this is the full request URI, so including starting slash and query parameter string.

🚧 Local testing

Based on the Getting started guide in the Prerender.io documentation.

1. Download and run the prerender Server locally

The default port is 3000. You can start the node server on a different port like this:

2. Set the prerender URL:

3. (Optional) Open your browser and visit the following URL. Make sure to change domain.test to your local domain:

4. Test your page as a crawler. Make sure to change domain.test to your local domain:

5. 🎉 That's it — you should see the prerendered html!

📝 Changelog

Please see CHANGELOG for more information on what has changed recently.

✏️ Contributing

Please see CONTRIBUTING for details.

🧑‍💻 Security Vulnerabilities

Please review our security policy on how to report security vulnerabilities.

🎭 License

The MIT License (MIT). Please see License File for more information.