Search Engine Friendly URLS

Hi everyone,

I know Search engine friendly urls are important, and know that this can be done easily with apache servers.

Just wondering if anyone have any idea this can be done with Windows IIS servers? Unfortunely I cannot install ISAPI filters but am allowed .dlls

Any advice will be great

Thanks

Dolphin

I'm not at all sure about IIS servers. However, if you don't get an answer, I think most search engines are quite accepting of url strings now so long as the variables are descriptive. For example, avoid using "id=" and other short little variables like that.

There were a number of pages in my site that I wasn't expecting would be crawled because of the url, but it found all 700+ of them!

Anyway, hopefully someone will have a proper answer for you! :)

Thanks for that chromate,

I wonder how many pages Google will go through before it has enough? 10,000-20,000 pages?

Thanks

Dolphin

http://www.jfonts.com/?page=search&o...Famous%20Fonts

http://www.jtemplates.com/?page=display&cat=business

Both of those seemed to get into Google allright....

There are ways to do this with IIS but you generally need admin access to the server or you need them to install special software on the server to make it happen.

And unfortunately I believe nearly every thing I've seen to accomplish this involves an ISAPI filter.

Do'h

thanks guys anyway

Dolphin

Quote:

---

Originally posted by Chris
There are ways to do this with IIS but you generally need admin access to the server or you need them to install special software on the server to make it happen.

And unfortunately I believe nearly every thing I've seen to accomplish this involves an ISAPI filter.

---

Ugggh.

On IIS, the typical way to do this is to create a custom 404 error page. So what happens is that the user requests a page that doesn't exist, it gets sent to the custom 404 page, and that's where you can parse the requested URL for parameters, do database lookups, etc.

For a little more information, go here:

http://www.aspfaq.com/show.asp?id=2162

Quote:

---

http://www.aspfaq.com/show.asp?id=2162

---

Ironic isn't it, considering the article's content vs. URL construction? :p