Forum Moderators: open
Whatever you do to generate pages dynamically, you can turn it into a WSH program (with some small adjustments to accomplish SSI includes by some other means). The result is a program that spits out static HTML on some schedule (or whenever you click an icon).
But anyway to be safe I agree with geebee2 on changing from "?productid=" to "?product".
Google is quite able to index these urls and does so. The way to check is to do a site:www.mydomain.com command and see what Google returns. Usually the dynamic pages show up (unless there are other problems beside dynamic urls).
The issue that I am experiencing is that the dynamic pages are definitely in the index but are ranking poorly. A check using the Google toolbar says that these pages are "not ranked", which I take to mean that Google is not passing ANY Page Rank to them.
A quick whip around the internet checking out other dynamic pages with a "?" in the url show the same symptoms. While Google refuses to pass page rank, these pages will continue to underperform in the rankings.
It doesn't seem to matter what follows the? it can be id= category= or even?opendocument (for Lotus Notes sites), none of them have Page Rank.
I am attempting to solve this problem using the server.transfer method but have run into some problems with passing the parameters. You can see my recent post here [webmasterworld.com...]
Is there a cheaper alternative to IISRewrite?
You may want to look at ISAPI_Rewrite. Less expensive and more robust based on our testing of multiple ISAPI filters.
Eliminate all characters from the URI. If you are going to rewrite, you would be defeating its purpose if you are leaving anything in that URI but alpha/numerical characters and separators like slashes, hyphens and underscores.
google will pick up my pages that contain id=xyz in the querystring but the page rank on those has gone to zero in the last year
I completely agree with that, when i do a site search it returns 195 pages from my site BUT they are they tagged "Supplemental Result", they dont pass PR and worst of all they dont produce any backward links! (although they are cross referenced)
I think its kinda mixed belssing that i rank better on Inktomi.
Helicontech's software that you're suggesting?
Yes. What's nice about the ISAPI_Rewrite filter is that you can install the global .ini at the server root and then drop the local .ini at each virtual root. So in essence, you have the ability to perform rewrites for each virtual domain. Open the .ini in NotePad, add your rules, save and its done. No IIS restart. There is also a log file produced at the root that will record any errors in the expressions. Really neat stuff.
1. /myBrand/myCat/
2. /myBrand/myCat/index.htm
3. /myBrand/myCat/index.aspx
Out of the three, Option 1 would be the preferred method. There is no need to utilize a full URI to a root level page.
/brand/cat/
/brand/cat/product-1.asp
/brand/cat/product-2.asp When using an ISAPI filter, we've found that using absolute URIs is mandatory.