Best SEO iTranslator for WordPress

This is normal. This plugin relies on an external website (Google Translate) and the loading time of your translated posts mainly depends on how fast Google will translate your pages. If it takes more than 10 seconds, there must be something wrong with your server. In this case check your host's error log to see whether everything is OK with your hosting. "Please return to this page in some minutes." message There has been something wrong with the translation process, or Google temporarily banned your website for excessive queries. Don't worry! A 503 Service Temporarily Unavailable message is displayed to both human readers and search bots, informing them that the page is not available at the moment. The cache gets too large in size This is normal. Every page is stored in a cached file, so the next time a request is made for that page, it is quickly fetched from the cache, saving a lot of time and server resources. The cache can grow quickly in size, make sure you have the required space on your server, before activating the plugin. The translated page has a bad/broken layout Usually Google Translate will deliver translated pages in the original format, however it may happen sometimes to get a page with a broken layout. Unfortunately, it is almost impossible to regenerate such broken files automatically.

That box informs the readers that the page they are currently viewing is a translated version and the original source is to be found in a different place (link provided).

Cache Duration is the time a cached file can stay on your server before it can be removed with a new one (if obsolete). Best Cache Duration time to set in the plugins settings are higher than 86000 seconds (one day). If you notice that translated pages are displayed correctly and they don't need to be replaced, set the Cache Duration to 1 week or more (use the calculator to get the value in seconds: Xdays24hours60minutes*60seconds) Best SEO iTranslator for Wordpress plugin doesn't work First things to check is that the cache folder inside the plugin's directory exists and is chmoded to 0755. If that is not the problem you may write a comment message on my blog at , and I'll see what I can do to help you.