Website Hierarchy Question / Discussion
-
Hey all,
I am looking to get the opinions off the community to help settle a discussion / debate.
We are looking at how a site is laid out and which is the preferred method. There are two options:
- www.site.com --> /category-page --> /product-page (With this option, you always have the domain name and then page, no matter where in the site you actually are, and how many clicks it took you to get there). Your URL to the end page here would be www.site.com/product-page
- www.site.com --> /category-page --> /category-page/product-page --> (With this option, you into a defined structure). Your URL to the end page here would be www.site.com/category-page/product-page
If you have a moment, I would be interested to know your views on which you would consider to be your preferred method and why.
Thanks,
Andy
-
Thanks David & Dana,
So far, this appears to be erring towards the simple URL's.
To address your comment about moving Dana, this is only quite a small site, but I can see the benefits of looking at it in this way.
-Andy
-
I agree with David. There are really arguments for going either way. I would give one edge to this method:
www.site.com/category-page/product-page
The advantage to using this instead of the super simple URLs is when you have a really large complex site and you need to move it to another platform. From an organizational standpoint, and just knowing from looking at your URLs what "lives" where, it's much easier if your URLs echo the structure of your site. Still, there are probably some ways to cope with that too, so depending on your CMS, this might not really be a problem.
-
www.site.com/category-page/product-page
I would prefer this method, because that is what a user would expect, although it can go either way.
Using the bolded method above is better for navigation, as a user and search engine can see how the product relates to the category it placed in. Generally, URL structures like this also include breadcrumbs, allowing for a user to quickly go back to the main category page and begin a new search, if desired. Having simple navagation can increase onsite time, since it's easy to view content and products.
I can also vouch for the other method for a few reasons. Using a shortened URL is more direct, and IMO better for seo. This allows you to set up the top level or category page with anchor text links directed at the subpages or products. When one of those is clicked, the page the user lands on will be the shorter, more direct version, with a clean URL. I think Google likes this method better, as the end URL is more directly related to the product being referenced, without any pollution. (unless you are using markup for breadcrumbs).
Got a burning SEO question?
Subscribe to Moz Pro to gain full access to Q&A, answer questions, and ask your own.
Browse Questions
Explore more categories
-
Moz Tools
Chat with the community about the Moz tools.
-
SEO Tactics
Discuss the SEO process with fellow marketers
-
Community
Discuss industry events, jobs, and news!
-
Digital Marketing
Chat about tactics outside of SEO
-
Research & Trends
Dive into research and trends in the search industry.
-
Support
Connect on product support and feature requests.
Related Questions
-
301 Redirect Timing Questions
Hey all, Quick question on 301 redirects and the timing of creating them when transitioning from an old site to a new site. Does the timing matter? Can redirects interfere with DNS propigation (which seemed to happen to us when we did redirects minutes after redirecting someone's DNS A record to now point to the new site) And lastly, how long AFTER a new site launch can one still submit redirects and not lose the google juice? All the best,
Technical SEO | | WorldWideWebLabs0 -
Duplicate Content Question
I have a client that operates a local service-based business. They are thinking of expanding that business to another geographic area (a drive several hours away in an affluent summer vacation area). The name of the existing business contains the name of the city, so it would not be well-suited to market 'City X' business in 'City Y'. My initial thought was to (for the most part) 'duplicate' the existing site onto a new site (brand new root domain). Much of the content would be the exact same. We could re-word some things so there aren't entire lengthy paragraphs of identical info, but it seems pointless to completely reinvent the wheel. We'll get as creative as possible, but certain things just wouldn't change. This seems like the most pragmatic thing to do given their goals, but I'm worried about duplicate content. It doesn't feel as though this is spammy though, so I'm not sure if there's cause for concern.
Technical SEO | | stevefidelity0 -
Is this normal on my website speed tool
Hi, i would like to know if this is normal as i have never come across it before. i have just checked my speed which needs a lot of improving. I use joomla 3.0 and recently had a developer upgrade it from 1.5, but now i am seeing under the speed test my website showing twice which looks like it is causing a time delay. the tool is http://tools.pingdom.com/fpt/#!/dTjwDM/www.in2town.co.uk can someone please look and let me know if this is normal. my site www.in2town.co.uk is coming up twice which seems to be slowing the site down and i have checked this tool with other sites and they are fine many thanks
Technical SEO | | ClaireH-1848860 -
Indexation question
Hi Guys, i have a small problem with our development website. Our development website is website.dev.website.nl This page shouldn't be indexed bij Google but unfortunately it is. What can i do to deindex it and ask google not to index this website. In the robots.txt or are there better ways to do this? Kind regards Ruud
Technical SEO | | RuudHeijnen0 -
Website Redirects
Background information: We have a website (devicelock.com) which is currently our corporate website. The company use to operate under (ntutility.com) which is now being redirected to devicelock.com via a DNS Forward - 302 Redirect. The IT admin (a founder of the company) is reluctant to change it to a 301. The current flow is ntutility.com redirects to protect-me.com then redirects again to devicelock.com. When i search up Devicelock on google, it shows up as ntutlity.com. There is no devicelock.com homepage on google search. Question: Are there any negative implications about this? Is this hurting our SEO in any way? When i do link building, will this have any negative affects? Will my links for devicelock be attributed to devicelock.com?
Technical SEO | | Devicelock0 -
301 Redirect Questions
I have a site I built on a wisiwig editing platform that will not allow a 301 redirect. The site has already been remade and I need to point it to another domain. To do the redirect, can I change it to another domain host that will allow a 301 or will that make me loose the authority of the site? I may not be able to move the content of the site. Please help.
Technical SEO | | photoseo10 -
403 forbidden error website
Hi Mozzers, I got a question about new website from a new costumer http://www.eindexamensite.nl/. There is a 403 forbidden error on it, and I can't find what the problem is. I have checked on: http://gsitecrawler.com/tools/Server-Status.aspx
Technical SEO | | MaartenvandenBos
result:
URL=http://www.eindexamensite.nl/ **Result code: 403 (Forbidden / Forbidden)** When I delete the .htaccess from the server there is a 200 OK :-). So it is in the .htaccess. .htaccess code: ErrorDocument 404 /error.html RewriteEngine On
RewriteRule ^home$ / [L]
RewriteRule ^typo3$ - [L]
RewriteRule ^typo3/.$ - [L]
RewriteRule ^uploads/.$ - [L]
RewriteRule ^fileadmin/.$ - [L]
RewriteRule ^typo3conf/.$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_FILENAME} !-l
RewriteRule .* index.php Start rewrites for Static file caching RewriteRule ^(typo3|typo3temp|typo3conf|t3lib|tslib|fileadmin|uploads|screens|showpic.php)/ - [L]
RewriteRule ^home$ / [L] Don't pull *.xml, *.css etc. from the cache RewriteCond %{REQUEST_FILENAME} !^..xml$
RewriteCond %{REQUEST_FILENAME} !^..css$
RewriteCond %{REQUEST_FILENAME} !^.*.php$ Check for Ctrl Shift reload RewriteCond %{HTTP:Pragma} !no-cache
RewriteCond %{HTTP:Cache-Control} !no-cache NO backend user is logged in. RewriteCond %{HTTP_COOKIE} !be_typo_user [NC] NO frontend user is logged in. RewriteCond %{HTTP_COOKIE} !nc_staticfilecache [NC] We only redirect GET requests RewriteCond %{REQUEST_METHOD} GET We only redirect URI's without query strings RewriteCond %{QUERY_STRING} ^$ We only redirect if a cache file actually exists RewriteCond %{DOCUMENT_ROOT}/typo3temp/tx_ncstaticfilecache/%{HTTP_HOST}/%{REQUEST_URI}/index.html -f
RewriteRule .* typo3temp/tx_ncstaticfilecache/%{HTTP_HOST}/%{REQUEST_URI}/index.html [L] End static file caching DirectoryIndex index.html CMS is typo3. any ideas? Thanks!
Maarten0