Re: WebCat and search engines

This WebDNA talk-list message is from

1998


It keeps the original formatting.
numero = 21907
interpreted = N
texte = >Is there anyway to use urls that look like standard urls but really are >database calls? > >In other words, change: >http://www.server.com/product.tpl?id=12345 > >to: >http://www.server.com/12345/product.tpl > >or something like this to allow the search engines to traverse the >individual product pages? Or is there another solution?No, it's not possible exactly as you asked, but there's another solution that's probably even better:Make webcat write a unique '[sku].html' file for each and every item in your db. Name these pages [sku].html -- not [sku].tpl -- because these pages should be static pages *not* served via webcat.Make sure to create *another* static page, call it Links.html for example, and make sure it has links to every single detail page and that it is also linked to your home page directly. Also, be sure to place a link back to your home page on every detail page, so no matter which detail page a visitor comes in on, they can go directly to your 'home' page to see the rest of your site.Use webcat's [writefile] context and the triggers.db to do these tasks automatically, once a day, so your pages will always be up-to-date. Or else create an admin form that lets you update them whenever you want simply by clicking the 'Update' button ...:)Sincerely, Ken Grome 808-737-6499 WebDNA Solutions mailto:ken@webdna.net http://www.webdna.net Associated Messages, from the most recent to the oldest:

    
  1. Re: WebCat and search engines (Kenneth Grome 1998)
  2. WebCat and search engines (Sam Lewis 1998)
>Is there anyway to use urls that look like standard urls but really are >database calls? > >In other words, change: >http://www.server.com/product.tpl?id=12345 > >to: >http://www.server.com/12345/product.tpl > >or something like this to allow the search engines to traverse the >individual product pages? Or is there another solution?No, it's not possible exactly as you asked, but there's another solution that's probably even better:Make webcat write a unique '[sku].html' file for each and every item in your db. Name these pages [sku].html -- not [sku].tpl -- because these pages should be static pages *not* served via webcat.Make sure to create *another* static page, call it Links.html for example, and make sure it has links to every single detail page and that it is also linked to your home page directly. Also, be sure to place a link back to your home page on every detail page, so no matter which detail page a visitor comes in on, they can go directly to your 'home' page to see the rest of your site.Use webcat's [writefile] context and the triggers.db to do these tasks automatically, once a day, so your pages will always be up-to-date. Or else create an admin form that lets you update them whenever you want simply by clicking the 'Update' button ...:)Sincerely, Ken Grome 808-737-6499 WebDNA Solutions mailto:ken@webdna.net http://www.webdna.net Kenneth Grome

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

[WebDNA] Conditional search (2009) Problems appending to database (1997) emailer on Windows Beta 18 (1997) File upload woes (1998) WebCatalog Hosting (1996) Duplicate Hell (1999) Generating Report Totals (1997) Credit Card processing (1998) Search design (1997) [WebDNA] fastcgi 7+ & [cart]? (2010) suffix mapping, use of cache, etc. (1997) [dos] command and [math] (1998) Showif date range comparison (1999) [WebDNA] How to stop cutting a word (2008) WebCat2b12--[searchstring] bug (1997) Mac 2.1b2 speed (1997) WebCatalog Plug-in for Webstar. (1997) Shipcost update problem (1997) [sendmail] questions... (1997) Using Cookie for client specific info? (1997)