Re: [WSG] URL length best practices [SEC=UNCLASSIFIED]
yes, good point. I was making a subtle stab at the .htm versus .html discussion in here recently. but given my 'druthers, yes, I'd personally drop all file extensions in URLs completely if I could. Joe On 05/11/2008, at 4:04 PM, Hassan Schroeder wrote: Joe Ortenzi wrote: the long and friendly URL is really for the final page, which should not bury a full product list so deeply and should be titled / product_list.html anyway. Uh, how about more properly '/product_list' (or '/product-list') -- your customers don't care about the underlying '.xyz' technology, and `Cool URIs don't change` http://www.w3.org/Provider/Style/URI, or so I've heard. :-) -- Hassan Schroeder - [EMAIL PROTECTED] Webtuitive Design === (+1) 408-621-3445 === http://webtuitive.com dream. code. *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** Joseph Ortenzi [EMAIL PROTECTED] +61 (0)434 047 804 http://www.typingthevoid.com http://twitter.com/wheelyweb http://www.linkedin.com/in/jortenzi Skype:wheelyweb http://au.movember.com/mospace/1714401 *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] URL length best practices
Todd Budnikas wrote: Wondering if people have insights into the length of a url for an article, and whether or not it is recommended to complete the name of an article in the url. For instance: http://egovau.blogspot.com/2008/10/do-collaborative-online-groups-need-to.html The name of this article is Do collaborative online groups need to be successful. The url above strips out be-successful. This may be the part of Blogger, or the author, but I've seen it in other instances with different Content Management systems as well. I personally would have added the additional words. Thoughts? I've always disliked short url's. Often they get cut off in silly and nonsensical places. There also may be a 'little seo' involved. Mostly personal preference methinks. The main issue is planning article titles to be as short as possible to begin with as the menu's have to be there as well. eg: Online Groups Success? And for menus we want short titles as much as possible... But personal preferences always rule, much like underscores or dashes, or the forbidden, Which CMS? Ford or Chev? lol Bruce bkdesign solutions *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] URL length best practices
..and if you are truncating url paths based on a page title at a certain point, you'll end up with some odd urls sooner or later.. e.g example.com/blog/why-xyz-browser-sucks.html when your title is: Why XYZ browser sucks less than ABC browser RFC 2616 (HTTP/1.1) doesn't set a maximum length on a url but I think our friend IE limits it to about 2048 characters (see google). Either way, there is no good reason I can see to limit a url path to a certain number of characters. HTH J On Wednesday 05 November 2008 04:22:12 Todd Budnikas wrote: Wondering if people have insights into the length of a url for an article, and whether or not it is recommended to complete the name of an article in the url. For instance: http://egovau.blogspot.com/2008/10/do-collaborative-online-groups-need-to.h tml The name of this article is Do collaborative online groups need to be successful. The url above strips out be-successful. This may be the part of Blogger, or the author, but I've seen it in other instances with different Content Management systems as well. I personally would have added the additional words. Thoughts? *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] URL length best practices
other than making sense and having a strong connection with the page the content is on, there is no direct reason, other than being a bit sensible about it, I wouldn't advise testing out the 2048 characters. On 05/11/2008, at 9:32 AM, James Ellis wrote: RFC 2616 (HTTP/1.1) doesn't set a maximum length on a url but I think our friend IE limits it to about 2048 characters (see google). Either way, there is no good reason I can see to limit a url path to a certain number of characters. Joseph Ortenzi [EMAIL PROTECTED] +61 (0)434 047 804 http://www.typingthevoid.com http://twitter.com/wheelyweb http://www.linkedin.com/in/jortenzi Skype:wheelyweb http://au.movember.com/mospace/1714401 *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] URL length best practices
On Wed, Nov 5, 2008 at 11:21 AM, Joe Ortenzi [EMAIL PROTECTED] wrote: other than making sense and having a strong connection with the page the content is on, there is no direct reason, other than being a bit sensible about it, I wouldn't advise testing out the 2048 characters. of course there is a good reason: so it's typable. not every url should required to be clicked to be gotten to. -- noon silky http://skillsforvilla.tumblr.com/ http://www.themonkeynet.com/armada/ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
RE: [WSG] URL length best practices [SEC=UNCLASSIFIED]
More reasons to keep 'em short: 1. Makes it easy to quote URL (maybe over the phone) 2. I've seen a few email or publication programs break URLs where there's a line return, so breaks the hyperlink 3. Makes layout difficult for desktop publishers and marketing ie. www.chrisandhispetstore.com/what_i_keep_in_stock/supplies_for_birds/cages_and_ornaments/full_product_list.htm 4. If it's longer than the width of the address bar then the whole URL is not visible. Accessibility isn't just about clean code and text to speech readers. It's about good IA and making everything generally better to get at. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of silky Sent: Wednesday, 5 November 2008 11:28 AM To: wsg@webstandardsgroup.org Subject: Re: [WSG] URL length best practices On Wed, Nov 5, 2008 at 11:21 AM, Joe Ortenzi [EMAIL PROTECTED] wrote: other than making sense and having a strong connection with the page the content is on, there is no direct reason, other than being a bit sensible about it, I wouldn't advise testing out the 2048 characters. of course there is a good reason: so it's typable. not every url should required to be clicked to be gotten to. -- noon silky http://skillsforvilla.tumblr.com/ http://www.themonkeynet.com/armada/ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** *** WARNING: The information contained in this email may be confidential. If you are not the intended recipient, any use or copying of any part of this information is unauthorised. If you have received this email in error, we apologise for any inconvenience and request that you notify the sender immediately and delete all copies of this email, together with any attachments. *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
RE: [WSG] URL length best practices [SEC=UNCLASSIFIED]
May also be worth considering the use of an alias URL that redirects the user to the desired location on the page. They're good for referencing URLs in non-electronic media as they're more descriptive, easier to remember, and easier for the user to correctly type into their browser's address bar. For example, http://ato.gov.au/ActivityStatements as opposed to http://ato.gov.au/businesses/pathway.asp?pc=001/003/001. Both URLs take you to the same location. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chris Vickery Sent: Wednesday, 5 November 2008 12:41 To: wsg@webstandardsgroup.org Subject: RE: [WSG] URL length best practices [SEC=UNCLASSIFIED] More reasons to keep 'em short: 1. Makes it easy to quote URL (maybe over the phone) 2. I've seen a few email or publication programs break URLs where there's a line return, so breaks the hyperlink 3. Makes layout difficult for desktop publishers and marketing ie. www.chrisandhispetstore.com/what_i_keep_in_stock/supplies_for_birds/cage s_and_ornaments/full_product_list.htm 4. If it's longer than the width of the address bar then the whole URL is not visible. Accessibility isn't just about clean code and text to speech readers. It's about good IA and making everything generally better to get at. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of silky Sent: Wednesday, 5 November 2008 11:28 AM To: wsg@webstandardsgroup.org Subject: Re: [WSG] URL length best practices On Wed, Nov 5, 2008 at 11:21 AM, Joe Ortenzi [EMAIL PROTECTED] wrote: other than making sense and having a strong connection with the page the content is on, there is no direct reason, other than being a bit sensible about it, I wouldn't advise testing out the 2048 characters. of course there is a good reason: so it's typable. not every url should required to be clicked to be gotten to. -- noon silky http://skillsforvilla.tumblr.com/ http://www.themonkeynet.com/armada/ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** *** WARNING: The information contained in this email may be confidential. If you are not the intended recipient, any use or copying of any part of this information is unauthorised. If you have received this email in error, we apologise for any inconvenience and request that you notify the sender immediately and delete all copies of this email, together with any attachments. *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** IMPORTANT The information transmitted is for the use of the intended recipient only and may contain confidential and/or legally privileged material. Any review, re-transmission, disclosure dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited and may result in severe penalties. If you have received this e-mail in error please notify the Privacy Hotline of the Australian Taxation Office, telephone 13 28 69 and delete all copies of this transmission together with any attachments. *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] URL length best practices [SEC=UNCLASSIFIED]
i completely agree with Justin, and all points from just about everyone who responded, so thanks. A follow-up question is then do you paraphrase an article title into a url, or just chop it? /music/a-fresh-and-powerful-new-cd-from-the-most-influential/ or /music/influential-musician-new-cd/ where article title is: A fresh and powerful new CD from the most influential musician of our generation On Nov 4, 2008, at 8:54 PM, Bucci, Justin wrote: May also be worth considering the use of an alias URL that redirects the user to the desired location on the page. They're good for referencing URLs in non-electronic media as they're more descriptive, easier to remember, and easier for the user to correctly type into their browser's address bar. For example, http://ato.gov.au/ActivityStatements as opposed to http://ato.gov.au/businesses/pathway.asp?pc=001/003/001. Both URLs take you to the same location. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chris Vickery Sent: Wednesday, 5 November 2008 12:41 To: wsg@webstandardsgroup.org Subject: RE: [WSG] URL length best practices [SEC=UNCLASSIFIED] More reasons to keep 'em short: 1. Makes it easy to quote URL (maybe over the phone) 2. I've seen a few email or publication programs break URLs where there's a line return, so breaks the hyperlink 3. Makes layout difficult for desktop publishers and marketing ie. www.chrisandhispetstore.com/what_i_keep_in_stock/supplies_for_birds/cage s_and_ornaments/full_product_list.htm 4. If it's longer than the width of the address bar then the whole URL is not visible. *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] URL length best practices [SEC=UNCLASSIFIED]
From: silky [EMAIL PROTECTED] To: wsg@webstandardsgroup.org Sent: Tuesday, November 04, 2008 9:27 PM Subject: Re: [WSG] URL length best practices [SEC=UNCLASSIFIED] On Wed, Nov 5, 2008 at 1:06 PM, Todd Budnikas [EMAIL PROTECTED] wrote: i completely agree with Justin, and all points from just about everyone who responded, so thanks. A follow-up question is then do you paraphrase an article title into a url, or just chop it? /music/a-fresh-and-powerful-new-cd-from-the-most-influential/ or /music/influential-musician-new-cd/ where article title is: A fresh and powerful new CD from the most influential musician of our generation Thats a sentence, not a title ;) Powerful New CD would suffice. But changing a lot of existing titles would be a pain with all the redirects needed... Bruce bkdesign solutions *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
RE: [WSG] URL length best practices
Just a quick note that if you're going to shorten Do collaborative online groups need to be successful to make a URL, it would be better, from the SEO viewpoint, to cut out the common words, do, need, to etc. So, your URL would be collaborative-online-groups-successful.html not do-collaborative-online-groups-need-to.html the former one would get you better weighting with Google, etc. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Todd Budnikas Sent: Wednesday, 5 November 2008 4:22 AM To: wsg@webstandardsgroup.org Subject: [WSG] URL length best practices Wondering if people have insights into the length of a url for an article, and whether or not it is recommended to complete the name of an article in the url. For instance: http://egovau.blogspot.com/2008/10/do-collaborative-online-groups-need-t o.html The name of this article is Do collaborative online groups need to be successful. The url above strips out be-successful. This may be the part of Blogger, or the author, but I've seen it in other instances with different Content Management systems as well. I personally would have added the additional words. Thoughts? *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** Please consider the environment before printing this e-mail. The information contained in this email and any attachment is confidential and may contain legally privileged or copyright material. It is intended only for the use of the addressee(s). If you are not the intended recipient of this email, you are not permitted to disseminate, distribute or copy this email or any attachments. If you have received this message in error, please notify the sender immediately and delete this email from your system. The ABC does not represent or warrant that this transmission is secure or virus free. Before opening any attachment you should check for viruses. The ABC's liability is limited to resupplying any email and attachments. *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] URL length best practices
I said no direct reason, but you point is a good reason to consider short URLs but this is not always possible, but yes, typablity is a good thing too. On 05/11/2008, at 11:27 AM, silky wrote: On Wed, Nov 5, 2008 at 11:21 AM, Joe Ortenzi [EMAIL PROTECTED] wrote: other than making sense and having a strong connection with the page the content is on, there is no direct reason, other than being a bit sensible about it, I wouldn't advise testing out the 2048 characters. of course there is a good reason: so it's typable. not every url should required to be clicked to be gotten to. -- noon silky http://skillsforvilla.tumblr.com/ http://www.themonkeynet.com/armada/ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** Joseph Ortenzi [EMAIL PROTECTED] +61 (0)434 047 804 http://www.typingthevoid.com http://twitter.com/wheelyweb http://www.linkedin.com/in/jortenzi Skype:wheelyweb http://au.movember.com/mospace/1714401 *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] URL length best practices [SEC=UNCLASSIFIED]
Sorry for being a bit off topic but. I think you missed a point about friendly URLs For each of these examples you state, you really don't want to burden your marketing team with urls like your example: www.chrisandhispetstore.com/what_i_keep_in_stock/supplies_for_birds/cages_and_ornaments/full_product_list.htm when any sensible marketer will tell you: www.chrisandhispetstore.com/products is where you should point them, and then let them find cages in one click on that page., maybe even at www.chrisandhispetstore.com/products/cages the long and friendly URL is really for the final page, which should not bury a full product list so deeply and should be titled / product_list.html anyway. BAD IA IMHO Joe OK, in marketing terms you can easily create your own TinyURL by redirecting vimportant traffic through a rewrite. On 05/11/2008, at 12:40 PM, Chris Vickery wrote: More reasons to keep 'em short: 1. Makes it easy to quote URL (maybe over the phone) 2. I've seen a few email or publication programs break URLs where there's a line return, so breaks the hyperlink 3. Makes layout difficult for desktop publishers and marketing ie. www.chrisandhispetstore.com/what_i_keep_in_stock/supplies_for_birds/cages_and_ornaments/full_product_list.htm 4. If it's longer than the width of the address bar then the whole URL is not visible. Accessibility isn't just about clean code and text to speech readers. It's about good IA and making everything generally better to get at. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of silky Sent: Wednesday, 5 November 2008 11:28 AM To: wsg@webstandardsgroup.org Subject: Re: [WSG] URL length best practices On Wed, Nov 5, 2008 at 11:21 AM, Joe Ortenzi [EMAIL PROTECTED] wrote: other than making sense and having a strong connection with the page the content is on, there is no direct reason, other than being a bit sensible about it, I wouldn't advise testing out the 2048 characters. of course there is a good reason: so it's typable. not every url should required to be clicked to be gotten to. -- noon silky http://skillsforvilla.tumblr.com/ http://www.themonkeynet.com/armada/ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** *** WARNING: The information contained in this email may be confidential. If you are not the intended recipient, any use or copying of any part of this information is unauthorised. If you have received this email in error, we apologise for any inconvenience and request that you notify the sender immediately and delete all copies of this email, together with any attachments. *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** Joseph Ortenzi [EMAIL PROTECTED] +61 (0)434 047 804 http://www.typingthevoid.com http://twitter.com/wheelyweb http://www.linkedin.com/in/jortenzi Skype:wheelyweb http://au.movember.com/mospace/1714401 *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] URL length best practices
Wait so would it make more sense to include keywords in your link for you main navigation? so instead of about I would make it about-andrew-brown? On 4-Nov-08, at 11:21 PM, Joe Ortenzi wrote: I said no direct reason, but you point is a good reason to consider short URLs but this is not always possible, but yes, typablity is a good thing too. On 05/11/2008, at 11:27 AM, silky wrote: On Wed, Nov 5, 2008 at 11:21 AM, Joe Ortenzi [EMAIL PROTECTED] wrote: other than making sense and having a strong connection with the page the content is on, there is no direct reason, other than being a bit sensible about it, I wouldn't advise testing out the 2048 characters. of course there is a good reason: so it's typable. not every url should required to be clicked to be gotten to. -- noon silky http://skillsforvilla.tumblr.com/ http://www.themonkeynet.com/armada/ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** Joseph Ortenzi [EMAIL PROTECTED] +61 (0)434 047 804 http://www.typingthevoid.com http://twitter.com/wheelyweb http://www.linkedin.com/in/jortenzi Skype:wheelyweb http://au.movember.com/mospace/1714401 *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
RE: [WSG] URL length best practices [SEC=UNCLASSIFIED]
Please stop emailing me! -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Joe Ortenzi Sent: Wednesday, 5 November 2008 3:30 PM To: wsg@webstandardsgroup.org Subject: Re: [WSG] URL length best practices [SEC=UNCLASSIFIED] Sorry for being a bit off topic but. I think you missed a point about friendly URLs For each of these examples you state, you really don't want to burden your marketing team with urls like your example: www.chrisandhispetstore.com/what_i_keep_in_stock/supplies_for_birds/cages_an d_ornaments/full_product_list.htm when any sensible marketer will tell you: www.chrisandhispetstore.com/products is where you should point them, and then let them find cages in one click on that page., maybe even at www.chrisandhispetstore.com/products/cages the long and friendly URL is really for the final page, which should not bury a full product list so deeply and should be titled / product_list.html anyway. BAD IA IMHO Joe OK, in marketing terms you can easily create your own TinyURL by redirecting vimportant traffic through a rewrite. On 05/11/2008, at 12:40 PM, Chris Vickery wrote: More reasons to keep 'em short: 1. Makes it easy to quote URL (maybe over the phone) 2. I've seen a few email or publication programs break URLs where there's a line return, so breaks the hyperlink 3. Makes layout difficult for desktop publishers and marketing ie. www.chrisandhispetstore.com/what_i_keep_in_stock/supplies_for_birds/cages_an d_ornaments/full_product_list.htm 4. If it's longer than the width of the address bar then the whole URL is not visible. Accessibility isn't just about clean code and text to speech readers. It's about good IA and making everything generally better to get at. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of silky Sent: Wednesday, 5 November 2008 11:28 AM To: wsg@webstandardsgroup.org Subject: Re: [WSG] URL length best practices On Wed, Nov 5, 2008 at 11:21 AM, Joe Ortenzi [EMAIL PROTECTED] wrote: other than making sense and having a strong connection with the page the content is on, there is no direct reason, other than being a bit sensible about it, I wouldn't advise testing out the 2048 characters. of course there is a good reason: so it's typable. not every url should required to be clicked to be gotten to. -- noon silky http://skillsforvilla.tumblr.com/ http://www.themonkeynet.com/armada/ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** *** WARNING: The information contained in this email may be confidential. If you are not the intended recipient, any use or copying of any part of this information is unauthorised. If you have received this email in error, we apologise for any inconvenience and request that you notify the sender immediately and delete all copies of this email, together with any attachments. *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** Joseph Ortenzi [EMAIL PROTECTED] +61 (0)434 047 804 http://www.typingthevoid.com http://twitter.com/wheelyweb http://www.linkedin.com/in/jortenzi Skype:wheelyweb http://au.movember.com/mospace/1714401 *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** -- Message protected by MailGuard: e-mail anti-virus, anti-spam and content filtering. http://www.mailguard.com.au/mg Click here to report this message as spam: https://login.mailguard.com.au/report/1wc50HObVz/4A8jXjLDyusxDyPnihvJDC/0 *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] URL length best practices [SEC=UNCLASSIFIED]
What? On Tue, Nov 4, 2008 at 11:39 PM, Ashley Butler [EMAIL PROTECTED] wrote: Please stop emailing me! -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Joe Ortenzi Sent: Wednesday, 5 November 2008 3:30 PM To: wsg@webstandardsgroup.org Subject: Re: [WSG] URL length best practices [SEC=UNCLASSIFIED] Sorry for being a bit off topic but. I think you missed a point about friendly URLs For each of these examples you state, you really don't want to burden your marketing team with urls like your example: www.chrisandhispetstore.com/what_i_keep_in_stock/supplies_for_birds/cages_an d_ornaments/full_product_list.htmhttp://www.chrisandhispetstore.com/what_i_keep_in_stock/supplies_for_birds/cages_and_ornaments/full_product_list.htm when any sensible marketer will tell you: www.chrisandhispetstore.com/products is where you should point them, and then let them find cages in one click on that page., maybe even at www.chrisandhispetstore.com/products/cages the long and friendly URL is really for the final page, which should not bury a full product list so deeply and should be titled / product_list.html anyway. BAD IA IMHO Joe OK, in marketing terms you can easily create your own TinyURL by redirecting vimportant traffic through a rewrite. On 05/11/2008, at 12:40 PM, Chris Vickery wrote: More reasons to keep 'em short: 1. Makes it easy to quote URL (maybe over the phone) 2. I've seen a few email or publication programs break URLs where there's a line return, so breaks the hyperlink 3. Makes layout difficult for desktop publishers and marketing ie. www.chrisandhispetstore.com/what_i_keep_in_stock/supplies_for_birds/cages_an d_ornaments/full_product_list.htmhttp://www.chrisandhispetstore.com/what_i_keep_in_stock/supplies_for_birds/cages_and_ornaments/full_product_list.htm 4. If it's longer than the width of the address bar then the whole URL is not visible. Accessibility isn't just about clean code and text to speech readers. It's about good IA and making everything generally better to get at. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of silky Sent: Wednesday, 5 November 2008 11:28 AM To: wsg@webstandardsgroup.org Subject: Re: [WSG] URL length best practices On Wed, Nov 5, 2008 at 11:21 AM, Joe Ortenzi [EMAIL PROTECTED] wrote: other than making sense and having a strong connection with the page the content is on, there is no direct reason, other than being a bit sensible about it, I wouldn't advise testing out the 2048 characters. of course there is a good reason: so it's typable. not every url should required to be clicked to be gotten to. -- noon silky http://skillsforvilla.tumblr.com/ http://www.themonkeynet.com/armada/ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** *** WARNING: The information contained in this email may be confidential. If you are not the intended recipient, any use or copying of any part of this information is unauthorised. If you have received this email in error, we apologise for any inconvenience and request that you notify the sender immediately and delete all copies of this email, together with any attachments. *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** Joseph Ortenzi [EMAIL PROTECTED] +61 (0)434 047 804 http://www.typingthevoid.com http://twitter.com/wheelyweb http://www.linkedin.com/in/jortenzi Skype:wheelyweb http://au.movember.com/mospace/1714401 *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** -- Message protected by MailGuard: e-mail anti-virus, anti-spam and content filtering. http://www.mailguard.com.au/mg Click here to report this message as spam: https://login.mailguard.com.au/report/1wc50HObVz/4A8jXjLDyusxDyPnihvJDC/0 *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help
RE: [WSG] URL length best practices [SEC=UNCLASSIFIED]
Yes o.O ...aren't we saying the same thing? Keep the url short and to the point. Sorry... I exaggerated the example URL to illustrate the point. Ashley try the unsubscribe if you don't want to get emails... http://webstandardsgroup.org/join/unsubscribe.cfm -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Joe Ortenzi Sent: Wednesday, 5 November 2008 3:30 PM To: wsg@webstandardsgroup.org Subject: Re: [WSG] URL length best practices [SEC=UNCLASSIFIED] Sorry for being a bit off topic but. I think you missed a point about friendly URLs For each of these examples you state, you really don't want to burden your marketing team with urls like your example: www.chrisandhispetstore.com/what_i_keep_in_stock/supplies_for_birds/cages_and_ornaments/full_product_list.htm when any sensible marketer will tell you: www.chrisandhispetstore.com/products is where you should point them, and then let them find cages in one click on that page., maybe even at www.chrisandhispetstore.com/products/cages the long and friendly URL is really for the final page, which should not bury a full product list so deeply and should be titled / product_list.html anyway. BAD IA IMHO Joe OK, in marketing terms you can easily create your own TinyURL by redirecting vimportant traffic through a rewrite. On 05/11/2008, at 12:40 PM, Chris Vickery wrote: More reasons to keep 'em short: 1. Makes it easy to quote URL (maybe over the phone) 2. I've seen a few email or publication programs break URLs where there's a line return, so breaks the hyperlink 3. Makes layout difficult for desktop publishers and marketing ie. www.chrisandhispetstore.com/what_i_keep_in_stock/supplies_for_birds/cages_and_ornaments/full_product_list.htm 4. If it's longer than the width of the address bar then the whole URL is not visible. Accessibility isn't just about clean code and text to speech readers. It's about good IA and making everything generally better to get at. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of silky Sent: Wednesday, 5 November 2008 11:28 AM To: wsg@webstandardsgroup.org Subject: Re: [WSG] URL length best practices On Wed, Nov 5, 2008 at 11:21 AM, Joe Ortenzi [EMAIL PROTECTED] wrote: other than making sense and having a strong connection with the page the content is on, there is no direct reason, other than being a bit sensible about it, I wouldn't advise testing out the 2048 characters. of course there is a good reason: so it's typable. not every url should required to be clicked to be gotten to. -- noon silky http://skillsforvilla.tumblr.com/ http://www.themonkeynet.com/armada/ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** *** WARNING: The information contained in this email may be confidential. If you are not the intended recipient, any use or copying of any part of this information is unauthorised. If you have received this email in error, we apologise for any inconvenience and request that you notify the sender immediately and delete all copies of this email, together with any attachments. *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** Joseph Ortenzi [EMAIL PROTECTED] +61 (0)434 047 804 http://www.typingthevoid.com http://twitter.com/wheelyweb http://www.linkedin.com/in/jortenzi Skype:wheelyweb http://au.movember.com/mospace/1714401 *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** *** WARNING: The information contained in this email may be confidential. If you are not the intended recipient, any use or copying of any part of this information is unauthorised. If you have received this email in error, we apologise for any inconvenience and request that you notify the sender immediately and delete all copies of this email, together with any attachments. *** *** List Guidelines: http
Re: [WSG] URL length best practices [SEC=UNCLASSIFIED]
Joe Ortenzi wrote: the long and friendly URL is really for the final page, which should not bury a full product list so deeply and should be titled /product_list.html anyway. Uh, how about more properly '/product_list' (or '/product-list') -- your customers don't care about the underlying '.xyz' technology, and `Cool URIs don't change` http://www.w3.org/Provider/Style/URI, or so I've heard. :-) -- Hassan Schroeder - [EMAIL PROTECTED] Webtuitive Design === (+1) 408-621-3445 === http://webtuitive.com dream. code. *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***