EVE Dynamic Prerender

Prerender Meta Tag allows webmasters to pre-load, in background, a second page in the browser. Until now you have to place a specific prerender by hand in your code, for each page. Otherwise you have to query Google Analytics API.

The plugin knows the next page users will visit and enables a very fast navigation experience. This plugin is based on users navigation paths and it can really guess the next page that the user will visit.

This WordPress plugin creates and injects into the head section of the HTML document a real dynamic Prerender Meta Tag. Each page with a perfect and dedicated prerender link!

The system stores users navigational paths inside a database table called “your-db-prefix_PRERENDER”. Than the plugin retrieves the most common next visited page and uses it as prerender meta tag.

If the plugin doesn’t hava any data for the next probable visited page, it will show a prerender to the homepage.

The database table WILL BE REMOVED automatically when the plugin is uninstalled. Do not uninstall the plugin if you want to keep historical data. Uninstall the plugin if you change permalink structure or if you are moving to version 3.5 of this plugin from a previous version – this way will purge the database table.

For info please visit: EVE Milano

Help Keep This Plugin Free

If you find this plugin useful to you, please consider making a donation to help contribute to my time invested and to further development. Thanks for your kind support! – Giovanni Sacheli

1. Install automatically through the Plugins, Add New menu in WordPress, or upload the eve-dynamic-prerender folder to the /wp-content/plugins/ directory.

2. Activate the plugin through the Plugins menu in WordPress. There is no option page for the moment.

See the official FAQ at evemilano.com

4.0.0

• code migrated to AJAX. Now the plugin works also with caching systems.

3.5.5

• code cleared

3.5.5

• removed meta name referrer

3.5.4

• plugin moved from managing full URL paths to post-id for more compatibility with different permalink structures.

3.4

• Versions 3.4 some new tweaks on the variable filtering.

3.3

• Versions 3.3 removed parameters from URL, so the plugin is not suitable for URL structure like /?p=123.

3.2

• undefined canonical variable will be ignored.

3.1

• To save space into the database, URLs stored are now relative instead of absolute.

3.0

• Drop table moved from disable plugin to uninstall plugin.