Moz Q&A is closed.
After more than 13 years, and tens of thousands of questions, Moz Q&A closed on 12th December 2024. Whilst we’re not completely removing the content - many posts will still be possible to view - we have locked both new posts and new replies. More details here.
Best URL-structure for ecommerce store?
-
What structure will recommend to the product pages?
Lets make an example with the keyword "Luxim FZ200"
With category in url:
www.myelectronicshop.com/digital-cameras/luxim-FZ200.htmlWith /product prefix:
www.myelectronicshop.com/product/luxim-FZ200.htmlWithout category in url:
www.myelectronicshop.com/luxim-FZ200.htmlI have read in a blog post that Paddy Moogan recommend /lluxim-FZ200.html - i think i prefer this version too.
But I can see that many of the bigger ecommerce stores are using a /product prefix before the product name. What is the reason for this? and what is best practice?
-
I Have an ecommerce site hosted on volusion and they make the structure /category/product (Specifically www.example.com/shortnameurl/productcode"). I figure with 10000+ sites they have found that this structure is best. They want the best results for their clients so they retain & gain new busines.
I recently tried to duplicate(ish) the product name like /black-luxium-camera/luxiumfz200 ... and google killed me.
My suggestion, stick with /categoryORbrand/product, NOT .com/product/ as there is more opportunity to stand out when people search.
-
I guess if you could host all your products at root level then this would be better....it just may be difficult to manage house keeping wise.
-
Why would you go for example.com/product/luxim-FZ200.html instead of example.com/luxim-FZ200.html ?
-
Duplicate content is not at problem - there will of course always be a default category.
-
To avoid duplicate content I would specify that you don't have the same product page sitting in different categories.
Instead the product page should be the same URL even if it lives in multiple categories.e.g. www.example/product/luxim-FZ200.html
So if you click on the product link in Panasonic you go to the product page. You then go to the same page if you click on the product page from the "digital camera" category. The page is then unique and doesn't live in any category in particular.
You can then set the canonical link at product page level.
-
Hey Jesper,
The decision of URL structure can be affected by multiple stuff, that your Content Management System supports or not.
I prefer the 3rd version (the one without category in the link) to avoid duplicate content coming from different URL patterns to the same page (now I know you could place canonical links, but what happens when you have 50000 products and at least 10000 categories and child categories?).
If you do not have too many categories and subcategories, and you are able to insert canonical links into your system, then I would go for URL structure with category name included (it is more descriptive).
Just an example for your case:
A. Website with a lot of categories and subcategories
www.example.com/panasonic/lumix/lumix-FZ200.html
www.example.com/digital-cameras/panasonic/lumx-FZ200.html
www.example/product/luxim-FZ200.html
and so on...
Could leave to duplicate content if you cannot point out which version of the URL is the "Real" version.
B. Website would have the same product under the same categories, but then the product URL would look like:
www.example/luxim-FZ200.html
I hope that helps you take a decision.
Gr.,
Istvan
-
I believe the reason many ecommerce stores use a /product prefix in the URL is because their ecommerce provider / program does it by default.
I'd typically go with the first (with category, but without product) as you have a sort of breadcrumbing in your URL structure, which can also be applied on page.However, I don't usually have products in more than one category - if you do then Paddy's suggestion is the way to go, because, as he says, if you have the category in the URL in that scenario it can lead to duplicate content issues.
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
-
Correct use of schema for online store and physical stores
I have been getting conflicting advice on the best way to implement schema for the following scenario. There is a central e-commerce store that is registered to it's own unique address which is "head office". There are a few physical shops each of which has their own location and address. Each shop has its own landing page within /our-stores/. So each page on the website has the Organisation schema for the central 'organisation', something like: Then on each physical store landing page is something like the following as well as the Organisation schema: Is this correct? If it is should I extend LocalBusiness with store URL and sameAs for GMB listing and maybe Companies House registration? It's also been suggested that we should use LocalBusiness for the head office of the company, then Departmentwith the typeStore. But i'm not sure on that?
Technical SEO | | MickEdwards0 -
Vanity URLs are being indexed in Google
We are currently using vanity URLs to track offline marketing, the vanity URL is structured as www.clientdomain.com/publication, this URL then is 302 redirected to the actual URL on the website not a custom landing page. The resulting redirected URL looks like: www.clientdomain.com/xyzpage?utm_source=print&utm_medium=print&utm_campaign=printcampaign. We have started to notice that some of the vanity URLs are being indexed in Google search. To prevent this from happening should we be using a 301 redirect instead of a 302 and will the Google index ignore the utm parameters in the URL that is being 301 redirect to? If not, any suggestions on how to handle? Thanks,
Technical SEO | | seogirl221 -
Approved Word Separators in URLs
Hi There, We are in the process of revamping our URL structure and my devs tell me they have a technical problem using a hyphen as a word separator. There's a whole lot of competing recommendations out there and at this point I'm just confused. Does anyone have any idea what character would be next-best to the hyphen for separating words in a URL? Any reason to prefer one over another? Some links I've found discussing the topic: This page says that "__Google has confirmed that the point (.), the comma (,) and the hyphen (-) are valid word separators in URL’s.": http://www.internetofficer.com/seo/google-word-separator/ This page suggests the plus (+) symbol would be best: http://labs.phurix.net/posts/word-separators-in-urls This guy says he's tested and there's a whole bunch of symbols that will work as word separators: http://www.webproguide.com/articles/Symbols-as-word-separators-a-look-inside-the-search-engine-logic/ I'm leaning towards the tilde (~) or the plus (+) sign. Usage would be like so: http://www.domain.com/shop/sterling~silver OR /shop/sterling+silver etc... Thanks in advance for your help!
Technical SEO | | Richline_Digital1 -
Landing Page URL Structure
We are finally setting up landing pages to support our PPC campaigns. There has been some debate internally about the URL structure. Originally we were planning on URL's like: domain.com /california /florida /ny I would prefer to have the URL's for each state inside a "state" folder like: domain.com /state /california /florida /ny I like having the folders and pages for each state under a parent folder to keep the root folder as clean as possible. Having a folder or file for each state in the root will be very messy. Before you scream URL rewriting :-). Our current site is still running under Classic ASP which doesn't support URL rewriting. We have tried to use HeliconTech's ISAPI rewrite module for IIS but had to remove it because of too many configuration issues. Next year when our coding to MVC is complete we will use URL rewriting. So the question for now: Is there any advantage or disadvantage to one URL structure over the other?
Technical SEO | | briankb0 -
ECommerce: Best Practice for expired product pages
I'm optimizing a pet supplies site (http://www.qualipet.ch/) and have a question about the best practice for expired product pages. We have thousands of products and hundreds of our offers just exist for a few months. Currently, when a product is no longer available, the site just returns a 404. Now I'm wondering what a better solution could be: 1. When a product disappears, a 301 redirect is established to the category page it in (i.e. leash would redirect to dog accessories). 2. After a product disappers, a customized 404 page appears, listing similar products (but the server returns a 404) I prefer solution 1, but am afraid that having hundreds of new redirects each month might look strange. But then again, returning lots of 404s to search engines is also not the best option. Do you know the best practice for large ecommerce sites where they have hundreds or even thousands of products that appear/disappear on a frequent basis? What should be done with those obsolete URLs?
Technical SEO | | zeepartner1 -
Optimal Structure for Forum Thread URL
For getting forum threads ranked, which is best and why? site.com**/topic/**thread-title-goes-here site.com**/t/**thread-title-goes-here site.com**/**thread-title-goes-here I'd take comfort in knowing that SEOmoz uses the middle version, except that "q" is more meaningful to a human than "t". The last option seems like the best bet overall, except that users could potentially steal urls that I may want to use in the future. My old structure was site.com/forum/topic/TOPIC_ID-thread-title-goes-here so obviously any of those would be a vast improvement, but I might as well make the best choice now so I only have to change once.
Technical SEO | | PatrickGriffith0 -
Drupal URL Aliases vs 301 Redirects + Do URL Aliases create duplicates?
Hi all! I have just begun work on a Drupal site which heavily uses the URL Aliases feature. I fear that it is creating duplicate links. For example:: we have http://www.URL.com/index.php and http://www.URL.com/ In addition we are about to switch a lot of links and want to keep the search engine benefit. Am I right in thinking URL aliases change the URL, while leaving the old URL live and without creating search engine friendly redirects such as 301s? Thanks for any help! Christian
Technical SEO | | ChristianMKTG0 -
Someone is redirecting their url to mine
Hello, I have just discovered that a company in Poland www.realpilot.pl is directing their domain to ours www.transair.co.uk. We have not authorised this, neither do we want this. I have contacted the company and the webmaster to get it removed. If you search for the domain name www.realpilot.pl we (www.transair.co.uk) come up top. My biggest worry is that we will get penalised by Google for this re-direct as it appears to be done using some kind of frame. Does anyone know anything about this kind of thing? Many Thanks Rob Martin
Technical SEO | | brightonseorob0