Resolved bugs
| Release date: | Thursday, March 25, 2010 |
|---|---|
| C1 Version: | Composite C1 1.2 SP4 Patch 5 (1.2.3736.24833)... |
| Description | The way Composite C1 handles URL's and does front-page redirection is not optimal from a SEO perspective. The path to pages is case insensitive, meaning that "/C1/SEO/Perfect.aspx" and "/C1/SeO/perfect.aspx" yields the same page. Search Engines like Google will interpret this as two different pages, leading to content dilution and lower rankings. By default C1 will always ensure that internal page URL’s is in the correct casing, but external URL’s may have a ‘casing error’ and thus lead to this issue. Also Composite C1 does a front-page redirection from the “/” path to the path of the front page, like “/C1.apsx” – this is done using HTTP 302 and not HTTP 301 as prescribed by SEO experts. |
| Known work around: | Composite will release a patch for this issue. The patched version will do a HTTP 301 redirect on all URL's having wrong casing, redirecting to the URL casing specified by editors.. Also the front-page redirect will be changed to a HTTP 301. |