oixan/laravel-prerender
Composer 安装命令：
composer require oixan/laravel-prerender
包简介
Laravel middleware for prerendering javascript-rendered pages on the fly for SEO
关键字：
README 文档
README
For Laravel 4, use the 1.0 branch
Laravel Prerender 
Google, Facebook, Twitter, Yahoo, and Bing are constantly trying to view your website... but they don't execute javascript. That's why Prerender was built. Prerender is perfect for AngularJS SEO, BackboneJS SEO, EmberJS SEO, and any other javascript framework.
This middleware intercepts requests to your Laravel website or application from crawlers, and then makes a call to the (external) Prerender Service to get the static HTML instead of the javascript for that page.
Prerender adheres to google's _escaped_fragment_ proposal, which we recommend you use. It's easy:
- Just add
<meta name="fragment" content="!">to the<head>of all of your pages - If you use hash urls (#), change them to the hash-bang (#!), but you can also use HTML5's push-state
- That's it! Perfect SEO on javascript pages.
Installation
Require this package run: composer require nutsweb/laravel-prerender
After installing, add the ServiceProvider to the providers array in config/app.php.
'Oixan\LaravelPrerender\LaravelPrerenderServiceProvider',
If you want to make use of the prerender.io service, add the following to your .env file:
PRERENDER_TOKEN=yoursecrettoken
If you are using a self-hosted service, add the server address in the .env file.
PRERENDER_URL=http://example.com
You can disable the service by adding the following to your .env file:
PRERENDER_ENABLE=false
This may be useful for your local development environment.
How it works
- The middleware checks to make sure we should show a prerendered page
- The middleware checks if the request is from a crawler (
_escaped_fragment_or agent string) - The middleware checks to make sure we aren't requesting a resource (js, css, etc...)
- (optional) The middleware checks to make sure the url is in the whitelist
- (optional) The middleware checks to make sure the url isn't in the blacklist
- The middleware checks if the request is from a crawler (
- The middleware makes a
GETrequest to the prerender service (phantomjs server) for the page's prerendered HTML - Return that HTML to the crawler
Customization
To customize the whitelist and the blacklist, you first have to publish the configuration file:
$ php artisan vendor:publish
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.
// prerender.php: 'whitelist' => [ '/frontend/*' // only prerender pages starting with '/frontend/' ],
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 extentions 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.
// prerender.php: 'blacklist' => [ '/api/*' // do not prerender pages starting with '/api/' ],
Contributing
I love any contributions! Feel free to create issues or pull requests.
License
The MIT License (MIT)
Copyright (c) 2014 Jeroen Noten
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
oixan/laravel-prerender 适用场景与选型建议
oixan/laravel-prerender 是一款 基于 PHP 开发的 Composer 扩展包，目前已累计 141 次下载、GitHub Stars 达 0， 最近一次更新时间为 2019 年 09 月 30 日， 在 PHP 生态内属于活跃度较高的组件。
它主要适用于以下技术方向： 「laravel」 「prerender」 等业务场景。在实际项目中，围绕这些方向常见需要落地的问题包括：接口对接、性能调优、并发安全、与既有框架（Laravel / ThinkPHP / Yii / Webman 等）的兼容适配，以及生产环境的日志埋点与稳定性保障。
我们在过去多个企业项目中使用过 oixan/laravel-prerender 或与其功能相近的方案，如果你在选型或落地过程中遇到问题，例如 版本兼容、二次改造、私有化封装、与内部系统对接、生产 BUG 排查，欢迎联系我们协助评估。
基于 oixan/laravel-prerender 在你已有业务上做功能扩展、字段裁剪、UI 适配、与内部账号 / 权限 / 日志系统的深度对接。
线上偶发问题、内存泄漏、慢查询、并发异常等排查修复；针对高流量场景做缓存、队列、索引层面的调优。
承接完整的项目从需求 → 设计 → 开发 → 上线 → 长期运维；也可按月提供技术保姆服务。
与 oixan/laravel-prerender 相关的其它包
同方向 / 同关键字的高下载量 PHP Composer 包推荐，方便对比选型：
Laravel middleware for prerendering javascript-rendered pages on the fly for SEO
Laravel middleware for prerendering javascript-rendered pages on the fly for SEO
Crawl your own website with various clients for SEO and indexing purposes.
Alfabank REST API integration
Laravel middleware for prerendering javascript-rendered pages on the fly for SEO
Prerender
统计信息
- 总下载量： 141
- 月度下载量： 0
- 日度下载量： 0
- 收藏数： 0
- 点击次数： 1
- 依赖项目数： 0
- 推荐数： 0
其他信息
- 授权协议： MIT
- 更新时间： 2019-09-30