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.
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
-
Best way to handle URLs of the to-be-translated pages on a multilingual site
Dear Moz community, I have a multilingual site and there are pages with content that is supposed to be translated but for now is English only. The structure of the site is such that different languages have their virtual subdirs: domain.com/en/page1.html for English, domain.com/fr/page1.html for French and so on. Obviously, if the page1.html is not translated, the URLs point to the same content and I get warnings about duplicate content. I see two ways to handle this situation: Break the naming scheme and link to original English pages, i.e. instead of domain.com/fr/index.html linking to domain.com/fr/page1.html link to domain.com/en/page.html Leave the naming scheme intact and set up a 301 redirect so that /fr/page1.html redirects to /en/page1.html Is there any difference for the two methods from the SEO standpoint? Thanks.
Technical SEO | | Lomar0 -
Removed URLs
Hi all, We have recently removed 200+ articles from our blog. However, those links are still being shown on Google weeks after their removal. In there a way to speed up the process? What effect will this have on our SEO ranking?
Technical SEO | | businessowner0 -
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 -
Backslash in URL
my main URL is www.americanmusical.com, SEOMOZ shows I have a duplicate page title on www.americanmusical.com/. I have the think the backslash is causing other issues. I noticed when I first go to my site it is without the /, but if I navigate to the home page, the URL has the / in it. Any ideas on if this is a problem or how to handle it?
Technical SEO | | dianeb1520 -
301 redirects and Dynamic URLs
I just ran my first diagnostic and one of my primary immediate problems are duplicate titles and duplicate content. My guess it that because the root URL http://sitename.com (which has not yet been redirected to www...) has generated an entire tree of content which is identical to the tree rooted at http://www.sitename.com. QUESTION: Do I need to do a redirect simply for the root url (sitename.com -> www.sitename.com) or do I now need to develop specific 301 redirects for each of the sub-nodes/pages? ie sitename.com/?q=about-us -> www.sitename.com/?q=about-us sitename.com/?q=our-team -> www.sitename.com/?q=our-team etc.
Technical SEO | | Barrycliff680 -
Best Personna Strategy
I'm building a site for a manufacturer where all products will be entered as blog posts. Then I have to build some awareness for the site. What personna am I best off doing this with? Company Name, My Name, A ficticious name that works for the company, or some other? Any Mozzers want to share thoughts or past strategies that have been successful?
Technical SEO | | waynekolenchuk0