Forum Moderators: open
I am struggling to get a senior project developer to seriously consider URL rewriting for a major .Net database project, for its SEO benefits. The complaint is a common one, I'm sure, namely the additioinal server load will be prohibitive.
I haven't often encountered .Net environments so do not have much experience of the reality of the counter arguements in the Microsoft environment.
Is there any light you can shed? Particularly in regards to other enterprise sites running ISAPI_Rewrite or equivalent tools, and the arguments for such products that a resistant developer may find more compelling than my rather soft marketing oriented ones.
Any help much appreciated, and if the brand name isn't sufficient to locate the site (without links of course) then please sticky me.
Thanks in advance,
Steve
But the SEO benefits and ease of use, I feel, outweigh the performance hit. I'd rather have the SEO'd URLS and add another server then to have /article.aspx?articleId=100&categoryId=20&page=4.....
Chip-