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.
How to handle dynamic product url that changes regularly
-
Hey Moz,
It's actually my first post - although I look at the Q&As on a daily basis!
I was hoping to get your opinions on how to handle dynamic product url that can change regularly.
Before we start, our product page urls get populated by the product titles.
So the situation is this.
- Let’s say we have a product url: /product/12345-abcde-fghj/
- Then the client decides to change the title a week later, so the url changes with it to): /listing/12345-klm-qjk
- Another week later, the agent changes to: /listing/12345-jkhfk-jhf-kjdhfkjdhf
So to note, the product ID will always remain the same.
Naturally, 301 redirecting every time would cause a bit of page authority to be lost every time 301ed. Also potentially creating new a few hundreds of 301 redirect daily sounds totally mental. (I have been informed by the dev we expect a few hundreds to change url daily) Although I understand there’s no limit on how many 301s you can have on a single domain, this would look completely unnatural - really not ideal.
So the potential solution we thought was:
we’ll keep the original url, and make sure that is the only url that will get indexed**/product/12345-abcde-fghj/**and put canonical tag on any of the new urls, directing to the original url. The problem we will have then is that the most current url may not exactly match the description of the product -wouldn’t be ideal for ux.
Has anyone had dealing with issues like this in the past? Would love to get your input!
Many Thanks
-
Thanks Everett! yes there's definitely seo benefit from having the title in the URL, and I think it's pretty significant - from what I have seen previously when we made a massive url changes for one of the websites I worked on - went from /{id}/ to {id}-{product-title}. Also there is a study shows that display url in search results is still a prominent element to influencing searchers' clicks. This is from 2012 but I think the same still applies today. http://research.microsoft.com/pubs/155941/domainbias.pdf so I'd prefer to have the titles included.
It is completely possible to make the very original static, and that would be my preferred option - but we need to assess whether the changes were made because they were "mildly" or "totally" incorrect in the first place, and also at the same time need to convince others - who feel keeping the original urls (when the product titles change) would worsen ux.
301 redirects would be totally mental - so this would not be an option. Also adding canonical tag to the "non-original" urls method - potentially ok in the short term.
I think using static (hardcoded) urls would be the only long-term solution.
-
Hi Patrick that's really helpful thanks,
Completely understand it's confusing, I was totally surprised myself to find out there were so many changes to the title on a daily basis.
I would personally have one static url (original url) so this page can carry on build authority. I'm going to find out what these changes that are being made may be.I mean if it's just the title changing and nothing else, the chances are that the original product title (& url) will still stay relevant - it may be that our clients are trying to optimise their title, or spelling error etc. - I'm not sure at this point but that will be my next job to find out!
I can't link to the site, as it is being worked for relaunch currently. Site relaunches are always terrifying
-
Hi there
This is very confusing haha. What I would suggest is, if the product itself stays the same while new items or features are added to it (the only reason I can think why URLs are changing - correct?), to create one static URL / page for the product and update the description as the product updates. I would also add Schema into the template of the product so that it dynamically pulls information from the description and let's crawlers know of the changes. You'll have to talk to your web development team to make sure this is possible.
This way, you have one static URL per product, with only descriptions / features changing. This will cut down on multiple URLs, redirects, canonicals, and overall, confusion. I would also take a look at this resource from inFlow; this is on duplicate content for eCommerce which it sounds like you might potentially run into.
Let me know if a. that I am on the right thought pattern here and b. that this helps. You may want to link to your site so that the community can get a more indepth look! Hope this helps - good luck!
Patrick
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
-
What's the best way to handle product filter URLs?
I've been researching and can't find a clear cut answer. Imagine you have a product category page e.g. domain/jeans You've a lot of options as to how to filter the results domain/jeans?=ladies,skinny,pink,10 or domain/jeans/ladies-skinny-pink-10 or domain/jeans/ladies/skinny?=pink,10 And in this how do you handle titles, breadcrumbs etc. Is the a way you prefer to handle filters and why do you do it that way? I'm trying to make my mind up as some very big names handle this differently e.g. http://www.next.co.uk/shop/gender-women-category-jeans/colour-pink-fit-skinny-size-10r VS https://www.matalan.co.uk/womens/shop-by-category/jeans?utf8=✓&[facet_filter][meta.tertiary_category][Skinny]=on&[facet_filter][variants.meta.size][Size+10]=on&[facet_filter][meta.master_colour][Midwash]=on&[facet_filter][min_current_price][gte]=6.0&[facet_filter][min_current_price][lte]=18.0&per=36&sort=
Technical SEO | | RodneyRiley0 -
Robots.txt Syntax for Dynamic URLs
I want to Disallow certain dynamic pages in robots.txt and am unsure of the proper syntax. The pages I want to disallow all include the string ?Page= Which is the proper syntax?
Technical SEO | | btreloar
Disallow: ?Page=
Disallow: ?Page=*
Disallow: ?Page=
Or something else?0 -
How do I deindex url parameters
Google indexed a bunch of our URL parameters. I'm worried about duplicate content. I used the URL parameter tool in webmaster to set it so future parameters don't get indexed. What can I do to remove the ones that have already been indexed? For example, Site.com/products and site.com/products?campaign=email have both been indexed as separate pages even though they are the same page. If I use a no index I'm worried about de indexing the product page. What can I do to just deindexed the URL parameter version? Thank you!
Technical SEO | | BT20090 -
Duplicate content on Product pages for different product variations.
I have multiple colors of the same product, but as a result I'm getting duplicate content warnings. I want to keep these all different products with their own pages, so that the color can be easily identified by browsing the category page. Any suggestions?
Technical SEO | | bobjohn10 -
Best way to noindex long dynamic urls?
I just got a Mozcrawl back and see lots of errors for overly dynamic urls. The site is a villa rental site that gives users the ability to search by bedroom, amenities, price, etc, so I'm wondering what the best way to keep these types of dynamically generated pages with urls like /property-search-page/?location=any&status=any&type=any&bedrooms=9&bathrooms=any&min-price=any&max-price=any from indexing. Any assistance will be greatly appreciated : )
Technical SEO | | wcbuckner0 -
Trailing Slashes In Url use Canonical Url or 301 Redirect?
I was thinking of using 301 redirects for trailing slahes to no trailing slashes for my urls. EG: www.url.com/page1/ 301 redirect to www.url.com/page1 Already got a redirect for non-www to www already. Just wondering in my case would it be best to continue using htacces for the trailing slash redirect or just go with Canonical URLs?
Technical SEO | | upick-1623910 -
Duplicate canonical URLs in WordPress
Hi everyone, I'm driving myself insane trying to figure this one out and am hoping someone has more technical chops than I do. Here's the situation... I'm getting duplicate canonical tags on my pages and posts, one is inside of the WordPress SEO (plugin) commented section, and the other is elsewhere in the header. I am running the latest version of WordPress 3.1.3 and the Genesis framework. After doing some testing and adding the following filters to my functions.php: <code>remove_action('wp_head', 'genesis_canonical'); remove_action('wp_head', 'rel_canonical');</code> ... what I get is this: With the plugin active + NO "remove action" - duplicate canonical tags
Technical SEO | | robertdempsey
With the plugin disabled + NO "remove action" - a single canonical tag
With the plugin disabled + A "remove action" - no canonical tag I have tried using only one of these remove_actions at a time, and then combining them both. Regardless, as long as I have the plugin active I get duplicate canonical tags. Is this a bug in the plugin, perhaps somehow enabling the canonical functionality of WordPress? Thanks for your help everyone. Robert Dempsey0