Forum Moderators: open
The solution would be using asapi rewrite, or isapi rewrite, IIS rewrite....one of those rewriting solutions...
The thing is that I am not the one who programmed the site, this was done by another company. They have NO clue of how the rewrite is done, what is a SE friendly URL, etc...As I have some experience with mod-rewrite, I am trying to explain it to them.
But I have some questions too and I hope you can help me.
- I belive not every server comes with a rewrite solutions right? The programming company told me we don't have it on the server and would need to buy the solution. Is there any solution bundled on IIS server?
- Just using the rewrite to translate the URLs would be enough right? We actually need to make changes to our code in a way to get ride of the SE unfriendly marks. Right?
- The company came with a solution that looks like completely spamming. Tell me what you think. They want to hide an image link on the home page, linking to a page that would have links to every product of the website, those links would be dynamic but have only one parameter on the query.
I said this is problably SE spamming and we could get banned.
My boss wants me to find a solution for all that, wether is instructing the programming company to do the rewrite, or convinving them to outsource the service, or finding if there are services that would crawl our dynamic site and include it on the search engines.
I appreciate a lot your time and consideration. And we might hire you to do the job is they can't do it.
Thanks a lot
I belive not every server comes with a rewrite solutions right?
Correct, particularly Windows Servers. :(
The programming company told me we don't have it on the server and would need to buy the solution. Is there any solution bundled on IIS server?
I do believe there is a basic ISAPI filter in IIS 6 that can be utilized for rewriting. You will need more than the basics.
Just using the rewrite to translate the URLs would be enough right?
No.
We actually need to make changes to our code in a way to get rid of the SE unfriendly marks. Right?
Yes.
The company came with a solution that looks like complete spamming. Tell me what you think. They want to hide an image link on the home page, linking to a page that would have links to every product of the website, those links would be dynamic but have only one parameter on the query. I said this is problably SE spamming and we could get banned.
I doubt the above would be classifed as spam. The hidden link isn't necessary. You just need to build a site map and provide a visible link to the site map from every page of the site.
My boss wants me to find a solution for all that, whether it is instructing the programming company to do the rewrite, or convincing them to outsource the service, or finding if there are services that would crawl our dynamic site and include it on the search engines.
My recommendation is ISAPI Rewrite. I've been using it for a couple of years and it performs without fail. You need to understand Regular Expressions.
In reference to services who crawl dynamic content, there are different ways to go about this. If you choose PPC/CPC, the dynamic URIs are not a concern. If you choose PFI, they may not be a concern, depends on their structure.
The best thing to do is a complete rewrite. You are going to need to implement various 301s to capture any existing traffic from old pages that may be indexed.
You also need to walk backwards through the URI paths when performing a rewrite. You want to make sure that the URIs act just if they would had they not been rewritten. For example...
www.example.com/category/product/00/
www.example.com/category/product/00
www.example.com/category/product/0
www.example.com/category/product/
www.example.com/category/product
www.example.com/category/produc
www.example.com/category/
www.example.com/category
www.example.com/categor
www.example.com/
www.example.com
You need to verify that the proper server header status is being returned at each part of the URI. Any path leading to a sub-directory with an index page should resolve with a trailing forward slash.
Any path leading to a sub-directory without an index page should return a 404. And so on, and so forth.
[edited by: pageoneresults at 12:49 am (utc) on Feb. 19, 2004]