Invision Community 4: SEO, prepare for v5 and dormant account notifications Matt November 11, 2024Nov 11
Posted December 18, 201113 yr I noticed that with the following ACP SEO settings Redirect to new friendly URL format - Yes URL type - Path Info Use .htaccess mod_rewrite - Yes many pages are accessible with both a trailing slash and no trailing slash. For example, the gallery can be accessed via {website}/gallery or {website}/gallery/. Could this result in duplicate content issues or other [SEO] issues? Would an htaccess 301 redirect scheme (from trailing-slash forms to non-trailing-slash forms, or vice versa) be recommended for this software?
December 21, 201113 yr Author It seems that a fair number of sources support the notion that a trailing-slash URL and a corresponding non-trailing-slash URL are treated as addresses to different pages by search engines and that thereby enabling both URLs without implementing proper redirects might cause duplicate content issues if both URLs direct to the same content. http://lmgtfy.com/?q=trailing+slash+seo
December 21, 201113 yr It seems that a fair number of sources support the notion that a trailing-slash URL and a corresponding non-trailing-slash URL are treated as addresses to different pages by search engines and that thereby enabling both URLs without implementing proper redirects might cause duplicate content issues if both URLs direct to the same content.http://lmgtfy.com/?q...iling+slash+seo so change it? 'act=idx' => array( 'app' => 'forums', 'allowRedirect' => 0, 'out' => array( '#act=idx(&|$)#i', 'index/$1' ), 'in' => array( 'regex' => '#^/index/(/|$|?)#i', 'matches' => array( array( 'act', 'idx' ) ) ) ), add the trailing slash in your furlTemplates
December 21, 201113 yr been looking at furl templates myself, just unsure if I should mess with them as updates would overwrite each time
December 21, 201113 yr Author What about just using an htaccess 301 redirect from non-trailing-slash to trailing-slash forms, or vice versa? e.g.: RewriteBase / RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_URI} !(.*)/$ RewriteRule ^(.*)$ http://%{HTTP_HOST}/$1/ [L,R=301] In this case, you wouldn't need to edit any furlTemplates. You would have to ensure that all pages remain accessible with this, however, which is one reason I am inquiring about this here.
Archived
This topic is now archived and is closed to further replies.