t1gor / robots-txt-parser
PHP class to parse robots.txt rules according to Google, Yandex, W3C and The Web Robots Pages specifications.
Installs: 470 457
Dependents: 6
Suggesters: 0
Security: 0
Stars: 83
Watchers: 9
Forks: 31
Open Issues: 14
Requires
- php: >=5.5.0
- ext-mbstring: *
- vipnytt/useragentparser: ^1.0
Requires (Dev)
- codeclimate/php-test-reporter: >=0.2
- phpunit/phpunit: ~3.7
This package is auto-updated.
Last update: 2024-12-06 05:11:56 UTC
README
PHP class to parse robots.txt rules according to Google, Yandex, W3C and The Web Robots Pages specifications.
Full list of supported specifications (and what's not supported, yet) are available in our Wiki.
Supported directives:
- User-agent
- Allow
- Disallow
- Sitemap
- Host
- Cache-delay
- Clean-param
- Crawl-delay
- Request-rate (in progress)
- Visit-time (in progress)
Installation
The library is available for install via Composer package. To install via Composer, please add the requirement to your composer.json
file, like this:
composer require t1gor/robots-txt-parser
You can find out more about Composer here: https://getcomposer.org/
Usage example
Creating parser instance
use t1gor\RobotsTxtParser\RobotsTxtParser; # from string $parser = new RobotsTxtParser("User-agent: * \nDisallow: /"); # from local file $parser = new RobotsTxtParser(fopen('some/robots.txt')); # or a remote one (make sure it's allowed in your php.ini) # even FTP should work (but this is not confirmed) $parser = new RobotsTxtParser(fopen('http://example.com/robots.txt'));
Logging parsing process
We are implementing LoggerAwareInterface
from PSR
, so it should work out of the box with any logger supporting that standard. Please see below for Monolog example with Telegram bot:
use Monolog\Handler\TelegramBotHandler; use Monolog\Logger; use PHPUnit\Framework\TestCase; use Psr\Log\LogLevel; use t1gor\RobotsTxtParser\RobotsTxtParser; $monologLogger = new Logger('robot.txt-parser'); $monologLogger->setHandler(new TelegramBotHandler('api-key', 'channel')); $parser = new RobotsTxtParser(fopen('some/robots.txt')); $parser->setLogger($monologLogger);
Most log entries we have are of LogLevel::DEBUG
, but there might also be some LogLevel::WARNINGS
where it is appropriate.
Parsing non UTF-8 encoded files
use t1gor\RobotsTxtParser\RobotsTxtParser; /** @see EncodingTest for more details */ $parser = new RobotsTxtParser(fopen('market-yandex-Windows-1251.txt', 'r'), 'Windows-1251');
Public API
Even more code samples could be found in the tests folder.
Some useful links and materials:
- Google: Robots.txt Specifications
- Yandex: Using robots.txt
- The Web Robots Pages
- W3C Recommendation
- Some inspirational code, and some more
- Google Webmaster tools Robots.txt testing tool
Contributing
First of all - thank you for your interest and a desire to help! If you found an issue and know how to fix it, please submit a pull request to the dev branch. Please do not forget the following:
- Your fixed issue should be covered with tests (we are using phpUnit)
- Please mind the code climate recommendations. It some-how helps to keep things simpler, or at least seems to :)
- Following the coding standard would also be much appreciated (4 tabs as an indent, camelCase, etc.)
I would really appreciate if you could share the link to your project that is utilizing the lib.
License
The MIT License
Copyright (c) 2013 Igor Timoshenkov
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.