Talk:URL Schema
From ExtractValue Wiki
Contents |
Routing
Austinguu 19:00, 28 September 2008 (UTC) says: Start the user at "johnsmith" and subsequent names get a number Starting at 1 (johnsmith1, johnsmith2, etc.) Later, we will allow this name to be changed.
Dashboards
| Hierarchy | Routing Schema | Example |
| All users | ../people | ../people |
| All groups | ../groups | ../groups |
| Groups by group type | ../groups/<group-type> | ../groups/investment-advisors |
| All products | ../products | ../products |
| Products by product type | ../products/<product-type> | ../products/managed-accounts |
| All orders | ../orders | ../orders |
| Orders by product type | ../orders/<product-type> | ../orders/managed-accounts |
| All portfolios | ../portfolios | ../portfolios |
| All blogs | ../blogs | ../blogs |
| Blogs by tag | ../blogs/<tag> | ../blogs/mutual-funds |
| All news | ../news | ../news |
| News by tag | ../news/<tag> | ../news/press-release |
| Files | ../files | ../files |
| Files by tag | ../files/<tag> | ../files/account-application |
Search
| Hierarchy | Routing Schema | Example |
| Search | ../search | ../search |
| Search people | ../search/people | ../search/people |
| Search groups | ../search/groups | ../search/groups |
| Search products | ../search/products | ../search/products |
| Search orders | ../search/orders | ../search/orders |
| Search portfolios | ../search/portfolios | ../search/portfolios |
Users
| Hierarchy | Routing Schema | Example |
| View user profile | ../profile/<user-name><URI name>/
<URI name> is only necessary if there are duplicate names. | ../profile/johnsmith5/ |
| View user's orders | ../profile/<user-name><URI name>/orders
<URI name> is only necessary if there are duplicate names. | ../profile/johnsmith5/orders |
| View user's portfolios | ../profile/<user-name><URI name>/
<URI name> is only necessary if there are duplicate names. | ../profile/johnsmith5/portfolios |
Groups
| Hierarchy | Routing Schema | Example |
| Groups | ../group/<short-group-name> | ../group/charles-schwab |
Products
| Hierarchy | Routing Schema | Example |
| Products dashboard for a group | ../group/<short-group-name>/products | ../group/charles-schwab/products |
| Products | ../group/<short-group-name>/<product-name> | ../group/charles-schwab/schwab-fund-a |
Orders
| Hierarchy | Routing Schema | Example |
| Orders | ../orders/<product-type>/<transaction-type>-<product-name>-<URI> | ../orders/futures/buy-light-sweet-crude-oil-123456789 |
Portfolios
| Hierarchy | Routing Schema | Example |
| Portfolios | ../portfolio/<portfolio-name> | ../portfolio/account-statement-123/ |
User Blogs
| Hierarchy | Routing Schema | Example |
| Blogs list for a user | ../blog/<user-name><URI>/<userid>
<URI> is only necessary if there are duplicate names. | ..blog/johnsmith5/ |
| User Blog | ../blog/<user-name><URI>/<article-title>/
<URI> is only necessary if there are duplicate names. | ../blog/johnsmith5/all-about-stocks/ |
Group News
| Hierarchy | Routing Schema | Example |
| News dashboard for a group | ../news/<short-group-name> | ../news/charles-schwab |
| Group News | ../news/<short-group-name>/<article-title>/ | ../news/charles-schwab/all-about-stocks/ |
Wiki
| Hierarchy | Routing Schema | Example |
| Wiki (anything) | ../wiki/<article_title> | ../wiki/foreign_exchange |
| Wiki (products | ../wiki/<short_group_name>:<product_name> | ../wiki/charles_schwab:schwab_fund_a |
Files
| Hierarchy | Routing Schema | Example |
| User files | ../file/<user><#>_filename<(#)>.ext
<URI> is only necessary if there are duplicate names. | ../file/johnsmith5_biography.pdf |
| Group files | ../file/<short-group-name>_filename<(#)>.ext
<URI> is only necessary if there are duplicate file names. | ../file/charles-schwab_account-application(1).pdf |
URL Best Practices
Taken from SEOMOZ
Eleven Guidelines to Successful URLs
1. Describe Your Content An obvious URL is a great URL. If a user can look at the Address bar (or a pasted link) and make an accurate guess about the content of the page before ever reaching it, you've done your job. These URLs get pasted, shared, emailed, written down, and yes, even recognized by the engines. 2. Keep it Short Remember always; brevity is a virtue. The shorter the URL, the easier to copy & paste, read over the phone, write on a business card, or use in a hundred other unorthodox fashions, all of which spell better usability & increased branding. 3. Static is the Way & the Light Not to bring religion into this, but I can tell you with certainty that some of the engines absolutely DO treat static URLs differently than dynamic ones. And no human likes a URL where the big players are "?," "&," and "=." 4. Descriptives are Better than Numbers If you're thinking of using 114/cat223/, go with /brand/adidas/ instead. Even if the descriptive isn't a keyword or particularly informative to an uninitiated user, it's far better to use words when possible. If nothing else, your team members will thank you for making it that much easier to ID problems in development and testing. 5. Keywords Never Hurt If you know that you're going to be targeting a lot of competitive keyword phrases on your website for search traffic, you'll want every advantage you can get. Keywords are certainly one element of that strategy, so take the list from marketing, map it to the proper pages, and get to work. For dynamically created pages through a CMS, create the option of including keywords in the URL. 6. Subdomains Aren't the Answer First off, never use multiple subdomains (e.g., siteexplorer.search.yahoo.com) - it's unnecessarily complex and lengthy. Secondly, consider that subdomains have the potential to be treated separately from the primary domain when it comes to passing link and trust value. In most cases where just a few subdomains are used and there's good interlinking, it won't hurt, but I wouldn't take the chance. To me, the benefits derived from reputation management (by flooding the SERPs with your subdomains) are minimal compared to the potential loss of link/trust juice. I also think that subdomain takeovers of SERPs is not something the search engines see as beneficial to their users and may shut down at any point. Luckily, if you're doing it now, you can always 301 to the main domain. 7. Fewer Folders A URL should contain no unnecessary folders (or words or characters for that matter), for the same reason that a man's pants should contain no unnecessary pleats. The extra fabric is useless and will reduce his likelihood of impressing potential mates. 8. Hyphens Separate Best When creating URLs with multiple words in the format of a phrase, hyphens are best to separate the terms (e.g. /brands/dolce-and-gabbana/), followed (in order) by, underscores (_), pluses (+) and nothing. 9. Stick with Conventions If your site uses a single format throughout, don't consider making one section unique. Stick to your URL guidelines once established, so users (and future developers) will have a clear idea of how content is organized into folders and pages. This can apply globally as well for sites that share platforms, brands, etc. Re-inventing the wheel in situations where reliance on convention makes everyone's tasks easier is folly. 10. Don't be Case Sensitive Since URLs can accept both uppercase and lowercase characters, don't ever, ever allow any uppercase letters in your structure. If you have them now, 301 them to all-lowercase versions to help avoid confusion. If you have a lot of type-in traffic, you might even consider a 301 rule that sends any incorrect capitalization permutation to its rightful home. 11. Don't Append Extraneous Data There's no point to having a URL exist in which removing characters generates the same content. You can be virtually assured that people on the web will figure it out, link to you in different fashions, confuse themselves, their readers and the search engines (with duplicate content issues), and then complain about it.
Example Time The following are some grievously heinous violators of the guidelines above:
_encoding=UTF8&frombrowse=1&asin=B000FN0KWA Target (who's powered by Amazon) doesn't describe their content, use keywords, or keep it short. That and the horrifyingly useless data that can be removed from the URL without changing the content make this URL downright ugly.
Despite being one of my favorite sites, Etsy's URLs provide no descriptive information, use multiple dynamic parameters and separate breaks with underscores.
&om=1&iwloc=A Google should be ashamed - their guidelines for URLs practically set the town for the recommendations, but their maps feature is almost unusable due to inefficient, bloated URLs (when they must know that millions want to copy those URLs into emails)
These few below are doing a considerably better job, but could still go the extra mile:
It's almost there, and one could almost argue that the subdomain use here is justified for branding purposes. It is too bad they gave us so much data, but then cut out keywords and descriptives right at the end
Nasa has uselessly appended dynamic parameters onto the page, and added /home/index.html for no logical reason
- http://www.newyorkmetro.com/fashion/fashionshows/2007/spring/ main/newyork/womenrunway/marcjacobs/
They're trying to be descriptive, which is great, but not separating words and going 7 folders deep is really pushing it.
These last examples have done nearly everything right:
Brilliant - it's short, descriptive, static and obvious.
Despite the subdomain, everything else is near perfect.
I'm letting the White House off the hook for not using "john-kennedy" as the page title, because they've wisely also provided his number (the US' 35th President).
