This plugin was created to facilitate SEO work by automating most of the manual labor
This plugin was created to facilitate SEO work. It adds functionality in 3
- In the CMS by adding extra functionality to the Site Tree object
- In the Controller to alter the final html output during rendering
- As a standalone testing tool to perform various checks on the site
composer require dylangrech92/seotoolbox framework/sake dev/build
Manually adding and updating thousands of links every time you do a small url change or wanting to target a new keyword is just insanity.
This tool allows you to simply specify a keyword you want to target and where it should point to amongst a few other options. Once that is saved, the tool will automatically link the keyword specified to the page specified.
A report called Automated Links Report is automatically added to you reports section that will list all the pages that were affected by the Automated Links and how these were affected.
# Once this config is activated the report will stop running in realtime and start # looking for the AutomatedLinkPageResult object. # # To populate this object add this to your crontab: # framework/sake AutomatedLinkReportTask AutomatedLinkReport: run_in_realtime: false
- Test for various seo issues such as h1, meta titles, orphan pages, etc..
- Find more pages such as paginated pages
A full list of tests performed can be found here
Apart from the crawler this plugin also adds a small report to every page edit form. This idea was taken from Live SEO for Silverstripe. However turned it into a much smaller but greatly more reliable report. Instead of just 1 report for the whole page, this report is split into 2 tabs: Desktop & Mobile and in here only the most important data is shown + a google preview snippet and a keyword analysis tool.
This functionality can be re-used in other parts of the CMS by using the SEOToolboxAnalyzerField
Note: A curl is made to the page that is being tested on every page load in the CMS.
When you're reporting an issue try to include as much information as you can so that the mantainers of this module can try to closely replicate the issue.
Useful Information to send in
- Full stack trace
- PHP version
- Silverstripe version
- A simplistic overview of your setup example: Apache 2.4, admin and front-end are on seperate domains
- Module name that might be conflicting with this one
All contributions are welcome however before starting any work please do drop me a message on firstname.lastname@example.org so that we can coordinate what will be done and making sure all guidelines are followed so to avoid duplicate work.