WP-AvoideR

Description

When optimizing a website, Google´┐Ż Page Speed Insights or GTMetrix.com can display a poor ranking if there are too many redirects for a URL to the landing page.

If a visitor enters http://domainname.com in the browser, the visitor is redirected to httpS://domainname.com and finally lands on httpS://www.domainname.com. This double redirection is punished by numerous search engines.

This plugin examines the redirects and then issues a suggestion for a solution. By simply clicking on it, the plugin makes the necessary settings in the .htaccess file – including backup of the existing file.

The plugin itself is only 4kb in size.

Screenshots

  • This screen shot shows the demo-webite on https://varvy.com/tools/redirects/ BEFORE installation of WP-AVOIDER
  • WP-AVOIDER investigated the 2 redirects and finally...
  • https://varvy.com/tools/redirects/ shows that everything is fine now.

Installation

  1. Upload the plugin files to the /wp-content/plugins/plugin-name directory, or install the plugin through the WordPress plugins screen directly.
  2. Activate the plugin through the ‘Plugins’ screen in WordPress
  3. Use the Settings->avoid landing pages redirect screen to configure the plugin

FAQ

Does this Plugin any filechanges?

Yes. It changes the .htaccess-file but before doing this it makes a backup.

Reviews

19 May 2020
I cannot believe so few people have downloaded this great plugin. Using GTMetrix, It has taken my Page from a B rating 84% to an A rating 96% and my Yslow form B 86% to an A 92%. This will no doubt also help improve SEO ranking with Google. I am so impressed with this little plugin I am going to make a donation and buy the people who made it a beer. The Plugin is simple to use and easy to understand. Many thanks for work and efforts guys.
Read all 1 review

Contributors & Developers

“WP-AvoideR” is open source software. The following people have contributed to this plugin.

Contributors

Translate “WP-AvoideR” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Change log

1.0

  • Initial release (October 2019)