Hi, I have a solution to the fusebox problem in regard to search engine spiders. I've built an application that dynamically creates several static version of a site. This will mean you can easily create HTML specific for each of the search engines and therefore get a high rating on ALL of the search engines. Not only that, only the spiders will see these pages so it doesn't matter what they look like. Normal Mozilla browsers (such as IE and Netscape) will see the main fusebox site as normal. Anyway, if anyone wants the source code for this, just send a direct email to me (NOT VIA THIS GROUP PLEASE) and I'll send you a zip. If you're wondering how this works, here is a brief overview: 1) A CFINCLUDE of a file called detectSpiderBrowser.cfm in the main index page (or mayber the app_global page, whatever you like) checks to see if the browser CGI.USER_AGENT is a Mozilla browser (that basically covers all the normal browsers out there) 2) If a normal browser is detected, it processes the main index page as normal. However, if something else is detected, Coldfusion queries a database for all the major spider cgi.user_agents and checks to see if it matches any. (it does this with REFindnocase so it's quite fast) 3) If it's not a mozilla browser and it turns out it's not a known spider too, coldfusion processes the index page as normal so if anyone out there is using some weird browser, they'll still see that main fusebox site. If on the other hand a spider USER_AGENT is found, another CFINCLUDE (depending on which spider it is) is displayed instead of the index page. This page then effectively becomes the home page for the spider. Each spider can have there own "Home Page" because different spiders like different things and having the facility to get spider specific with your HTML can be very handy. (NB. Because this is all done server side, the spider is unaware of all this checking and all the various CFINCLUDE files!) 4) Each of the spider home pages has links to other static pages that are only specific to that spider. So, if you have a fuseaction within your site that basically displays a page about selling shoes, you can setup my application to create a static "shoes" page just for Google .. The URL to this would be http://www.yourdomainname.com/P/shoes_5/shoes.cfm (I'll explain the "P" & 5 later.) Search engines like pages with the keywords in the URL so having the above URL for a page on shoes will be very helpful in your rankings. 5) When the search engine indexes the "Shoes" page and someone clicks on the link from the search engine, Coldfusion will do another check at the top of this static page to see if a mozilla browser is detected. If it is, they will be diverted via CFLOCATION to a page that you specify (remember, only the spiders will see the static pages) which in this case would probably be: index.cfm?fuseaction=shoes. 6) The way the static pages are created is via a few forms and a bit of CFFILE. Basically, you will create Home pages and normal static pages. The home pages will replace the Index.cfm file and the normal static pages will represent the various sections of your site. If at any point a Mozilla browser tries to view one of these pages, they will be redirected to a URL you specifiy (each page can have their own specific re-direction URL) Each page also has links to all the other pages specific to the spider. Oh, one other thing: to sort out the problem with conflicts in folder names, when creating these pages the folder name will have the SpiderID from the database appended to it and therefore guarantee no conflicts. (ie. The ID for google in the database is 5 and AltaVist is 4 therefore /p/shoes_5/shoes.cfm and /p/shoes_4/shoes.cfm represent Google and AltaVista respectfully. 7) The "P" mentioned earlier stands for Pages and is where all the static files are created in. (each static page will have it's own sub-file too, hence P/shoes_5/shoes.cfm. When you click the Publish button, coldfusion will automatically create the static pages and folders in the P folder. 8) There is also a folder called HomePages. Yes, that is where the home pages are published. 9) You should create the folders called P and Homepages and put them next to the your sites index page. If you want though, change my code and call them something else. I'll stop waffling on now because if you know fusebox, you'll figure out what is going on by looking at the code. I've only been working with coldfusion fusion for the last six months so for those of you out there with more experience who want to update/modify my code, please feel welcome to do so. Just send me the updates (with comments) back to me. Thanks, Andrew PS. I build this application a few weeks back for my company (who I resigned from yesterday because they've been F***ing around with the development team.Long story) and is why I'm giving away this code for free. I'll be taken a month or so off from commercial work to re-build my classical music site so please don't ask if I'm looking for more work (not yet anyway). Oh, one VERY last thing..I've called this application S.E.B.S. Can you guess what it stands for? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
