Can pretty urls use .php extension?
Permalink
I'm sure this has been asked here before, but I could not find anything ...
Is there a way to change how the pretty urls work in concrete?
For example, the internal page links created by concrete look like this:
domainname.com/page/
However, i'd rather have .php at the end of them, for example:
domainname.com/page.php
I'm first to say the concrete way is more elegant, but would rather have the .php extension mainly because its an established site with lots of external links which we don't want to loose.
I know we could use some rewrite rules so that the .php urls are maintained, however I believe this opens up other issues.
I'm concerned about are google punishing our site for having two urls with the same content - for example, if both urls ../page/ and ../page.php are active, then google treats this as two separate pages and since the content will be the same, google frowns upon the page and punishes this sort of thing.
So ideally if we stick with the .php links, then all the internal concrete links will need to use the .php links as well.
We cant have concrete use ../page/ for it's internal links, and have existing external links go to ../page.php because google will see them as two pages and punish our site.
So, if any one knows how to overcome this please let me know.
Thanks!
Is there a way to change how the pretty urls work in concrete?
For example, the internal page links created by concrete look like this:
domainname.com/page/
However, i'd rather have .php at the end of them, for example:
domainname.com/page.php
I'm first to say the concrete way is more elegant, but would rather have the .php extension mainly because its an established site with lots of external links which we don't want to loose.
I know we could use some rewrite rules so that the .php urls are maintained, however I believe this opens up other issues.
I'm concerned about are google punishing our site for having two urls with the same content - for example, if both urls ../page/ and ../page.php are active, then google treats this as two separate pages and since the content will be the same, google frowns upon the page and punishes this sort of thing.
So ideally if we stick with the .php links, then all the internal concrete links will need to use the .php links as well.
We cant have concrete use ../page/ for it's internal links, and have existing external links go to ../page.php because google will see them as two pages and punish our site.
So, if any one knows how to overcome this please let me know.
Thanks!
The penalty for duplicate content isn't that harsh and doesn't even happen if you use proper 301 redirects.
http://googlewebmastercentral.blogspot.com/2009/10/reunifying-dupli...
http://googlewebmastercentral.blogspot.com/2008/09/demystifying-dup...
Also I just posted my approach to generating canonical references (which I'm using to reduce my duplicates in Google's index):
http://www.concrete5.org/community/forums/customizing_c5/canonical_...