Kill, pimp or cut loose? Ideas for a legacy ECommerce blog
-
Hi,
I'm looking to revamp the fortunes of an ailing Fashion ECommerce blog, which once had an impact on SEO for the site which it linked to but now has fallen by the wayside.
Blog sits here: www.mydomain.com/blog and links to products and categories on the ECommerce site www.mydomain.com.
The blog has about 2000 posts on it written over the past 5 years, which are almost all rewritten content about existing stories, events or embedded youtube videos related to fashion on the Web. None of the blog topics are unique, but the posts have been rewritten well and in an entertaining way - i.e. it's not just a copy and paste.
The blog is written on an old, proprietary platform and only has basic Social sharing. You can't comment on posts, or see "most popular" posts or tag clouds etc. It is optimised for SEO though, with fashion category tags, date archives and friendly URLs.
The company badly needs a shot in the arm for its content marketing efforts - so we're looking into the creation of infographics and other types of high quality, sharable content with an outreach effort. Ideally I want this content to be hosted on the Ecommerce site, but am faced with a few options which I'd appreciate the community's view on:
How I should handle the mix of the legacy content on /blog and the addition of new, "high quality" content?
- (Pimp v1) Leave the /blog exactly as is and add the new, high quality content as new posts to it. Invest in pimping the /blog UI so that it has features such as commenting/tag clouds etc. They could migrate the blog to Wordpress, but leave it on the same URL.
- (Cut loose) Leave the /blog alone, and start afresh with a new Wordpress blog for the new, high quality content. e.g. /News or news.mydomain.com. The old blog posts probably aren't worth bothering about, but it might be risky to delete them as there are a lot and are better off with them than without.
- (Pimp v2) Set up a new Wordpress blog (e.g. /News or news.mydomain.com) for the new content and move the old /blog content to it. 301 the old /blog posts to the new location. The depth of old content that exists will add weight to the new content from a user's perspective, but will seem sparse if published on its own. Not sure why I would do this, but it's an option...
- (Kill) Kill the old /blog content, start a new one for the new, high quality content.
- Maybe there's another option I haven't considered.
Thanks in advance,
George
-
In the interests of closing off the question, I've decided to keep the existing content on the same URLs and refresh the UI so it provides a better platform for hosting the high quality content.
My rationale is that I did find backlinks pointing to some of the content which would be a shame to lose, and setting up so many 301s to a new location did not seem like a good use of time.
-
5) Maybe there's another option I haven't considered.
Here's how I determine the value of my blogs...
A) how many visitors do they pull in (these generate ad income)
B) how many of those visitors are bouncing
C) how many of those visitors buy something
D) how much social action and linklove is being generated
If you ask those questions about your existing blog you might have a better perspective on killing, pimping or cutting loose. You might also discover what is working on that blog and use that as guide to creating more of what has worked in the past. In addition, if you find dead wood on the blog you know what to cut loose and what to avoid doing going forward. The analytics of the old blog can inform your future path.
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
-
Rel=Canonical Vs. 301 for blog articles
Over the last few years, my company has acquired numerous different companies -- some of which were acquired before that. Some of the products acquired were living on their previous company's parent site vs. having their own site dedicated to the product. The decision has been made that each product will have their own site moving forward. Since the product pages, blog articles and resource center landing pages (ex. whitepapers LPs) were living on the parent site, I'm struggling with the decision to 301 vs. rel=canonical those pages (with the new site being self canonicaled). I'm leaning toward take-down and 301 since rel=canonicals are simply suggestions to Google and a new domain can get all the help it can to start ranking. Are there any cons to doing so?
Intermediate & Advanced SEO | | mfcb0 -
Long product urls ecommerce store
Hi we have a site in the mens fashion space who have long product urls which look like this: https://www.domain.com/catalog/product/view/id/13700/s/the-mate-tee-grey-marle-upm618g/category/120/ The site is on Magento. Are there any serious SEO negatives of having such a long product url and including irrelevant information in the url like product/view/id/13700/s/ & /category/120/ in the URL. Or are the benefits of changing them to more URL friendly product urls like: https://www.domain.com/the-mate-tee-grey-marle-upm/ Minimal? Cheers.
Intermediate & Advanced SEO | | wozniak650 -
Should I write a new page or a blog post?
I am trying to rank for a local SEO term on a website for a national company. Should I write an optimized blog post, or optimized site page? Does it make a difference? Thanks!
Intermediate & Advanced SEO | | aj6130 -
Ecommerce SEO: Shared content on product pages
Hi Guys, I am wondering what the best practices are for avoiding duplicate content on product pages that have shared content. For example, say I have a 3 different product pages for each of the following: Verizon IPhone 5 16GB, AT&T IPhone 5 16GB, AT&T IPhone 5 32GB. Obviously each product is for the most part the same (all are IPhone 5). The only differences lie in the carrier of the phone and the storage capacity. I want to write product descriptions for each page to target a variety of different keywords, but I don't want to get penalized for duplicate content. Does anybody have any experience in what the SEO best practices are for product pages that have shared content like this? Thank you!
Intermediate & Advanced SEO | | Cody_West0 -
Are all duplicate content issues bad? (Blog article Tags)
If so how bad? We use tags on our blog and this causes duplicate content issues. We don't use wordpress but with such a highly used cms having the same issue it seems quite plausible that Google would be smart enough to deal with duplicate content issues caused by blog article tags and not penalise at all. Here it has been discussed and I'm ready to remove tags from our blog articles or monitor them closely to see how it effects our rankings. Before I do, can you give me some advice around this? Thanks,
Intermediate & Advanced SEO | | Daniel_B
Daniel.0 -
Multi Langes Blog on Multi languages Website
Hello! I need your Idea. I have my website in 4 languages. for example: domain.com/en domain.com/fr etc.. up to 4 languages. And i run at the moment domain.com/blog but now, i like to invest on content on all languages. What is your idea ? domain.com/en/blog or domain.com/blog/en/ or blog.domain.com/en/ blog.domain.com/fr/ or to use another word instead "blog" for example to use domain.com/en/magazine or domain.com/en/now or another word? what do you prefer me?
Intermediate & Advanced SEO | | leadsprofi0 -
Dynamic pages - ecommerce product pages
Hi guys, Before I dive into my question, let me give you some background.. I manage an ecommerce site and we're got thousands of product pages. The pages contain dynamic blocks and information in these blocks are fed by another system. So in a nutshell, our product team enters the data in a software and boom, the information is generated in these page blocks. But that's not all, these pages then redirect to a duplicate version with a custom URL. This is cached and this is what the end user sees. This was done to speed up load, rather than the system generate a dynamic page on the fly, the cache page is loaded and the user sees it super fast. Another benefit happened as well, after going live with the cached pages, they started getting indexed and ranking in Google. The problem is that, the redirect to the duplicate cached page isn't a permanent one, it's a meta refresh, a 302 that happens in a second. So yeah, I've got 302s kicking about. The development team can set up 301 but then there won't be any caching, pages will just load dynamically. Google records pages that are cached but does it cache a dynamic page though? Without a cached page, I'm wondering if I would drop in traffic. The view source might just show a list of dynamic blocks, no content! How would you tackle this? I've already setup canonical tags on the cached pages but removing cache.. Thanks
Intermediate & Advanced SEO | | Bio-RadAbs0 -
When to put a blog post and when an article in the articles section?
Hi All, I was wondering when I should write something as a post in my blog and when I should simply add an article in my articles section? What are the advantages of each way? Thanks
Intermediate & Advanced SEO | | BeytzNet0