Auto Clean URL for SEO removes STOP WORDS from the WordPress Slugs (URLs) in ENGLISH, SPANISH, GERMAN and FRENCH.

apasionados

netconsulting

<p>This plugin removes STOP WORDS from the WordPress Slugs in ENGLISH, SPANISH, GERMAN and FRENCH.</p>
<p>For all languages it removes HTML entities and anything that is not a letter, digit, space or apostrophe.</p>
<p>Please note that the plugin should not be used together with QTRANSLATE, WPML or POLYLANG. In case you have a multi-language blog, this plugin doesn’t work correctly.</p>
<p><strong>Yoast WordPress SEO has added a similar functionality to the one of this plugin in version 1.4.16</strong> (“Add option to enable slug stop word cleaning”) which is on by default but removed it in version 7.0.0 (Release Date: March 6th, 2018). If you use our plugin together with Yoast WordPress SEO in versions older than 7.0.0, please turn the WordPress SEO functionality off (find it under SEO -> Permalinks).</p>
<blockquote>
<p><strong>Yoast WordPress SEO</strong> acts on the WordPress filter “name_save_pre” which means that the Slug is modified when saved as draft the first time or when published (only if it hasn’t been saved as draft before). This means that when the slug is first created from the Title of the post the Stop words and HTML entities are not removed at this moment.</p>
<p><strong>Our plugin</strong> acts on the WordPress filter “name_save_pre” and on the AJAX action “wp_ajax_sample-permalink” which fires when the Slug is created for the first time. <strong>This means that with our plugin the slug is created without stop words in real time</strong>. After that you can edit the slug and it will not be modified again by the plugin after it has been edited.</p>
</blockquote>
<h4>What can I do with this plugin?</h4>
<p>This plugin automatically removes STOP WORDS from the WordPress Slugs in ENGLISH, SPANISH, GERMAN and FRENCH to enforce your SEO efforts.</p>
<h4>Where did you get the STOP WORD list from?</h4>
<p>The stop words were taken from the great resource of <a href="http://www.ranks.nl/stopwords/" title="Ranks.nl/StopWords" rel="nofollow ugc">Ranks.nl/StopWords</a>.</p>
<h4>Auto Clean URL for SEO Plugin in your Language!</h4>
<p>This first release is avaliable in English and Spanish. In the languages folder we have included the necessarry files to translate this plugin.</p>
<p>If you would like the plugin in your language and you’re good at translating, please drop us a line at <a href="http://apasionados.es/contacto/index.php?desde=wordpress-org-autocleanseo-home" rel="nofollow ugc">Contact us</a>.</p>
<ul>
<li>Translation to Serbo-Croatian language sr_RS by <a href="http://www.webhostinghub.com" rel="nofollow ugc">Borisa Djuraskovic</a>.</li>
</ul>
<h4>Further Reading</h4>
<p>You can access the description of the plugin in Spanish at: <a href="http://apasionados.es/blog/optimizar-urls-wordpress-seo-plugin-wordpress-1925/" rel="nofollow ugc">Auto Clean URL SEO en castellano</a>.</p>
<h3>Contact</h3>
<p>For further information please send us an <a href="http://apasionados.es/contacto/index.php?desde=wordpress-org-autocleanseo-contact" rel="nofollow ugc">email</a>.</p>
<h3>Translating WordPress Plugins</h3>
<p>The steps involved in translating a plugin are:</p>
<ol>
<li>Run a tool over the code to produce a POT file (Portable Object Template), simply a list of all localizable text. Our plugins allready havae this POT file in the /languages/ folder.</li>
<li>Use a plain text editor or a special localization tool to generate a translation for each piece of text. This produces a PO file (Portable Object). The only difference between a POT and PO file is that the PO file contains translations.</li>
<li>Compile the PO file to produce a MO file (Machine Object), which can then be used in the theme or plugin.</li>
</ol>
<p>In order to translate a plugin you will need a special software tool like <a href="http://www.poedit.net/" rel="nofollow ugc">poEdit</a>, which is a cross-platform graphical tool that is available for Windows, Linux, and Mac OS X.</p>
<p>The naming of your PO and MO files is very important and must match the desired locale. The naming convention is: <code>language_COUNTRY.po</code> and plugins have an additional naming convention whereby the plugin name is added to the filename: <code>pluginname-fr_FR.po</code></p>
<p>That is, the plugin name name must be the language code followed by an underscore, followed by a code for the country (in uppercase). If the encoding of the file is not UTF-8 then the encoding must be specified.</p>
<p>For example:</p>
<ul>
<li>en_US for US English</li>
<li>en_UK for UK English</li>
<li>es_ES for Spanish from Spain</li>
<li>fr_FR for French from France</li>
<li>zh_CN for Simplified Chinese</li>
</ul>
<p>A list of language codes can be found <a href="http://en.wikipedia.org/wiki/ISO_639" rel="nofollow ugc">here</a>, and country codes can be found <a href="http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2" rel="nofollow ugc">here</a>. A full list of encoding names can also be found at <a href="http://www.iana.org/assignments/character-sets" rel="nofollow ugc">IANA</a>.</p>


Alternatives to Auto Clean URL for SEO

Top alternatives