User Tools

Site Tools


admin_menu:addons:seo:general_settings:start

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
admin_menu:addons:seo:general_settings:start [2009/06/26 21:14]
james
admin_menu:addons:seo:general_settings:start [2014/09/25 16:55] (current)
Line 16: Line 16:
 === Updates requiring .htaccess Changes === === Updates requiring .htaccess Changes ===
  
-So far, there are updates that require changes to the .htaccess file in order to take advantage of new features.+So far, there are updates that require changes to the .htaccess file in order to take advantage of new features.
  
-== SEO 1.0.> 2.0.==+<tip c n>**Note:**  We now recommend that you re-generate the .htaccess file any time the SEO addon needs to be updated The versions listed below are the "main" versions that changes to the .htaccess file were required, but it does not list every single version that requires the .htaccess to be updated.  Also if any other addons "use" SEO URL's, such as the Storefront addon, the .htaccess may need to be updated for changes from those addons.  The best practice is any time the SEO addon is updated, go ahead and re-generate the .htaccess contents.</tip> 
 + 
 +== SEO 2.0.==
  
 When you update from SEO 1.0.0 (used for Geo 3.1.9 and earlier versions) to SEO 2.0.0 or higher:  The first time you attempt to access the SEO settings, it will inform you that proceeding will require changes to your .htaccess and will make it start using the newer format for URL's.  Before that, it will still re-write URL's in the same way that was done in SEO 1.0 so that your existing URL's will not suddenly "break" when you update. When you update from SEO 1.0.0 (used for Geo 3.1.9 and earlier versions) to SEO 2.0.0 or higher:  The first time you attempt to access the SEO settings, it will inform you that proceeding will require changes to your .htaccess and will make it start using the newer format for URL's.  Before that, it will still re-write URL's in the same way that was done in SEO 1.0 so that your existing URL's will not suddenly "break" when you update.
  
-== SEO 2.0.* > 2.1.==+== SEO 2.1.==
  
 In SEO version 2.0.*, the titles that are used in the URL (such as the Category title or listing title) used underscores "_" for the word separator.  Starting in SEO 2.1.0 and up, it now uses dashes "-" to separate words, since this is [[http://www.google.com/support/webmasters/bin/answer.py?hl=en&answer=76329|Google's recommended word separator]]((And who are we to argue with Google?)). In SEO version 2.0.*, the titles that are used in the URL (such as the Category title or listing title) used underscores "_" for the word separator.  Starting in SEO 2.1.0 and up, it now uses dashes "-" to separate words, since this is [[http://www.google.com/support/webmasters/bin/answer.py?hl=en&answer=76329|Google's recommended word separator]]((And who are we to argue with Google?)).
Line 32: Line 34:
   "-" instead.    "-" instead. 
  
 +== SEO 2.3.0 ==
 +
 +The title in the URL can now have more than just alpha-numeric characters, such as punctuation and similar.  The change was actually done to allow it to work with languages that use non-Latin characters, such as Arabic.  These changes however, require that the .htaccess file is re-generated.
 ==== Re-Write URLs ==== ==== Re-Write URLs ====
  
Line 59: Line 64:
  
 Note: Changing any settings in this section **does not** require re-generating the .htaccess file. Note: Changing any settings in this section **does not** require re-generating the .htaccess file.
 +
  
 ==== Convert Accents ==== ==== Convert Accents ====
Line 69: Line 75:
  
 **Setting Enabled:**\\ **Setting Enabled:**\\
-<nowiki>www.example.com</nowiki>/categorias/83/cuestiones-importantes/anuncios/423/D**o**nde-est**a**-el-ba**n**o.html+<nowiki>www.example.com</nowiki>/categorias/83/cuestiones-importantes/anuncios/423/¿D**o**nde-est**a**-el-ba**n**o.html
  
 **Setting Disabled:**\\ **Setting Disabled:**\\
-<nowiki>www.example.com/categorias/83/cuestiones-importantes/anuncios/423/Dnde-est-el-bao.html</nowiki>+<nowiki>www.example.com</nowiki>/categorias/83/cuestiones-importantes/anuncios/423/¿D**ó**nde-est**á**-el-ba**ñ**o.html
  
 <tip c w>Only turn this setting on if you need it!  It will cause the software to have to do a lot of extra work if you turn this on when it is not needed.</tip> <tip c w>Only turn this setting on if you need it!  It will cause the software to have to do a lot of extra work if you turn this on when it is not needed.</tip>
Line 168: Line 174:
   * If your server //improperly// reports the **REQUEST_URI** of the page, it can cause "endless redirects".   * If your server //improperly// reports the **REQUEST_URI** of the page, it can cause "endless redirects".
   * If your server //does not// report the **REQUEST_URI** at all, the force SEO URL feature will simply have no effect when turned on.   * If your server //does not// report the **REQUEST_URI** at all, the force SEO URL feature will simply have no effect when turned on.
 +
 +===== Extra Page Urls =====
 +
 +This support wiki article has been [[startup_tutorial_and_checklist:usability_configuration:seo:seo_rewrite_extra_pages|moved here]]
admin_menu/addons/seo/general_settings/start.1246050866.txt.gz · Last modified: 2014/09/25 16:55 (external edit)