Look at FormURL2Attributes on Fusebox.org.  It will work with SES (search
engine safe) urls.

-----Original Message-----
From: Nelson, John [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 15, 2001 9:35 AM
To: CF-Community
Subject: Search Engine Optimization


I'm wondering how this could be done using NT/IIS and CF:

(reprinted from webmonkey:
http://hotwired.lycos.com/webmonkey/01/23/index1a_page3.html?tw=e-business)
Clean Up Your URLs
The problem with most e-commerce sites is that their product pages are
dynamically generated. While Google will crawl any URL that a browser can
read, most of the other search engines balk at links with "?" and "&"
characters that separate CGI variables (such as
"artloop.com/store?sku=123&uid=456"). As a result, many individual product
pages don't show up outside of Google.
One way to circumvent this difficulty is to create static versions of your
site's dynamic pages for search engines to crawl. Unfortunately, duplicating
your pages is a huge amount of extra work and a constant maintenance chore,
plus the resulting pages are never quite up-to-date -- all the headaches
dynamic pages were designed to eliminate.
A far better strategy is to follow the lead of Amazon and rewrite your
dynamic URLs in a syntax that search engines will gladly crawl. So URLs that
look like this:
amazon.com/store?shop=cd&sku=
B00004WFIZ&ref=p_ir_m&sessionID=
107-6571839-6268523
Become:
amazon.com/exec/obidos/ASIN/ref=
B00004WFIZ/ref=pd_ir_m/107-6571839-6268523
Amazon's application server knows the fields in the URL are actually CGI
parameters in a certain order, and processes them accordingly.
You don't necessarily need to modify the source code for your application
server to do this: As one of Artloop's Web programmers learned, you can
create Apache <http://httpd.apache.org/docs/mod/mod_rewrite.html>  rewrite
rules that tell Apache how to translate slash-separated URLs into a format
used by their  <http://www.creativescience.com/index.cgi?feed=netzyme>
Netzyme application server. On the back end, Netzyme is passed something
like this:
artloop.com/cgi-bin/CssP.exe?CsspApp=
ArtLoopClient1&CssServer=localhost%3A32401&CsspFn
=@/details/ArtistDetail.html:@:getForm&ObjectLocation
=ART&ArtistID=3918
But users and search engines see the tidier, Apache-served URLs, which look
something like this:
artloop.com/artists/profiles/3918.html
Not only are the rewritten URLs crawlable by all search engines, they're
also more human-friendly, making them easier to pass around the Net.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at 
http://www.fusionauthority.com/bkinfo.cfm
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at 
http://www.fusionauthority.com/bkinfo.cfm

Archives: http://www.mail-archive.com/cf-community@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists

Reply via email to