Blog is outranking ecommerce store
-
My client has a blog that posts information about products to support its ecommerce store.
The blog's main purpose is to support the products listed on the main website, but it has become so strong that its posts sometimes rank in the SERPS in place of the website product page, which is undesirable.
The blog posts always link to the product that they are supporting. Are there any other methods, other than doing a 301, that could help the product page to rank instead of the blog post?
-
Thanks Doug,
I will perhaps try having the links removed from the product page and see if that helps.
-
Without taking a look at the site and the content you've got it's hard to talk specifics, but you might want to test removing the links from the product pages to the blog. After all, you want people to add the products to their cart - not drift off into the blog.
(Of course. Depends on how well the blog supports people purchasing decisions, and promotes your offerings etc,)
In one of your response to Greg you say: "if there are not many reviews available for a product but my client has reviewed the product and posted it to their blog, Google will prefer that to the product page itself."
This makes me suspect that it's just the weight of relevant copy on the page that's causing Google to view the blog page as more authoritative. I'd also guess (gut feeling) that having links from your product pages to your blog is also going to make is less clear to Google which should be the authoritative page.
-
It's possible that we could add the content to the product pages. Perhaps it could be added to the product page first and then posted to the blog with the website being specified as the canonical link.
-
Thanks for the suggestions about analysing the different traffic once it lands on the product pages, I hadn't thought of that.
The setup is that content is added to the blog and linked back to the relevant product page. The blog content is tagged with the name of the product and then any content with the specified tag appears on the product page via an rss feed for that tag.
You're right about different stages of the buying cycle and this is why the supporting content is posted. We have tested some CTA banners with reasonable success but need to find a successful way to implement this feature in wordpress without adding an image file each time.
-
Nope content is written afresh and not copied at all from manufacturers.
There is the option for customers to leave reviews, although currently no scheme.org markup to add it to the metadata.
What makes you think that a 301 to the product pages will stop them from being indexed. I have 301'd other pages in the past without it casing problems?
-
I'm not sure what's causing the blog posts to outrank - in most cases it is the other way around. I think Google just prefers certain type of content in some instances - e.g if there are not many reviews available for a product but my client has reviewed the product and posted it to their blog, Google will prefer that to the product page itself.
-
This is a nice problem to have.
Think of the blog page as a landing page and as Robert suggested, link to the product so they can buy.
I'm curious how the keywords differ for each page. Whatever is being done on the blog pages successfully - can you do similar things to product pages that are not being blogged?
-
One solution would be to put this supporting information onto the product pages (and 301) but...
This might be more of an opportunity than a problem!
Not everyone searching for a product is actually looking to buy now. Recognising that different people will be in different stages of the buying cycle and creating content to support and more these people towards your sales pages.
Make sure that your blog posts also sell - both the products and also your offering/usp.
As well as just having a link - make sure it's an obvious call to action with a clear proposition too. if they want to go ahead any buy the product - give them a reason why they should buy from you.
Your blog posts might provide you with a great opportunity to communicate the added value, authority and trust in your brand to your prospective customer.
As well as having a link at the bottom - make sure that you've also got a clear and obvious "looking to buy now?" CTA above the fold for those competitive/impulsive people who do want to buy now!
What's happening when people arrive on your blog pages, how long so they spend on them, are they moving on to your product pages?
Is there a difference in the conversion rate for people entering via the blog and going on to your product page vs those that arrive directly on your product pages?
-
If the product descriptions are more or less copied from the manufacturer, then you may need to rewrite them and find ways to add user-generated content there, e.g. ratings and reviews, etc.
If you 301 the blog pages, then there won't be a blog to read and Google won't index the product pages.
-
What's causing the blog posts to rank above the product pages? Better information? More in-depth photos? Reviews? More content in general? If it's any of these, then think about you can apply these positives to the product pages so people start sharing and linking to those more.
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
-
Ecommerce Category Pages
First, let's define the terminology for the various types of ecommerce pages. The terminology differs from organization to organization: Product Description Pages (PDPs): These pages have a single product, pricing, an "add to cart" button, reviews, and a product description. Product Listing Pages (PLPs): These are product category/subcategory pages that have product image links and text links to Product Description Pages (PDPs). Category Pages: These pages have subcategory image and text links to subcategory pages. No product images are displayed Hybrid Category Pages: these pages combine sub-Category Images and text at the top of the page and product listings below. Our CMS currently does not allow us to create hybrids. This conversation revolves primarily around mobile. Our ecommerce team is having discussions around the appropriate use of PLPs vs Category pages. After doing a quick audit of the mobile sites of some top ecommerce players, there is definitely a trend to use Category Pages at the top of the category and sub-category hierarchy and use PLPs at the very bottom. The logic from a usability perspective is to allow visitors to navigate a site without ever using the hamburger navigation. ex: Baby (Category Page) => Car Seats (Category Page) => Convertible Car Seats (PLP) The sites I audited all had hamburger menus. A visitor would navigate from a home page image for "Baby," an image on the "Baby" page to "Car Seats", and an image on the "Car Seats" page to the Convertible Car Seats page. At that point, they would be able to shop for "Convertible Car Seats" on a PLP. This appears to be excellent UX and easy to use navigation. Theoretically, good for SEO as well. In short, category and subcategory pages are being used as navigation to allow visitors to easily navigate to the bottom of the hierarchy and shop on the most narrow page in the hierarchy. Much easier to use than a hamburger menu, but it does entail more clicks. The discussion revolves around allowing users to shop for product at a higher level in the taxonomy. For example, what if a visitor wants to shop all Car Seats? In the above taxonomy, we are precluding users from shopping in this manner. There is no "Car Seats" PLP. Our CMS has the ability to create both a Category Page and a PLP for "Car Seats". We could theoretically place an image on the "Car Seats" category page for "View All Car Seats", and allow users to click to a "Car Seats" PLP. None of the major ecommerce players I've audited are adding a PLP option higher up in the hierarchy. That doesn't mean that it's not good UX. Problems: From an SEO perspective, having a Category Page and a PLP for "Car Seats" would cause cannibalization - they would be competing for the same keywords. I am skeptical that canonicals would work. The pages are not near duplicate content. One page has category images, the other has product images. We could place content blocks on the page to make them more similar. We could noindex the PLP, but that's a waste of internal link juice. Need advice: Will canonicals work in this situation? Should we trash this idea entirely? Does adding a PLP add value or confusion? Is noindex a good idea? Is there an option to target keyword variations with the PLP? Is there another solution?
Web Design | | Satans_Apprentice0 -
Best practices for ecommerce product categories?
I'm trying to optimise my ecommerce site's category/navigation structure so that it is: Intuitive for human users Keyword optimised, and Minimises duplicate content penalties Here is my dilemma. Let's say my site sells widgets. Some people search for widgets according to size (big widgets, medium widgets) while others search according to colour (green widgets, blue widgets). My keyword research suggests that I should target some keywords that relate to size, others that relate to colour, yet others relating to material, etc. I figured that I'd use one of these taxonomies as a category system, then set the others as filter elements. So my site's main navigation would say "Big Widgets | Medium Widgets | Small Widgets". If you click on any of them, or if you click on the "Widgets" supercategory, you'd reach a filter function allowing you to see only green widgets, or only plastic widgets, etc. So far so good - from a user perspective. The problem with this method is that Google isn't going to index my filter results. So someone Googling "green widgets" or "plastic widgets" is unlikely to find my site, even though I have plenty of green/plastic widgets that they could have filtered for. My next thought was to add some of these filter urls to my main navigation so they will be crawled. My filter mod generates urls for each filter (eg mysite.com/category?filter=k39;w24). So now I have a flashier navigation menu where clicking "Widgets" will pop out a panel allowing you to browse by size or by colour. I don't know whether users will find this helpful or redundant/confusing, but at least Google can see my filter urls. But I've run into two more problems. My filter results aren't really pages, so I can't set things like H1s, meta descriptions and so on. There's very little I can do to keyword optimise them. Further, I now have duplicate content, because the same widget can show up under multiple filter urls. And so I'm stuck here. I've thought about creating custom pages for each target keyword and manually listing products that pertain to each keyword. This will allow me to optimise the pages, but it's a lot of ongoing work (I have to update them whenever I get new stock), and I'm not sure my visitors will appreciate this - I suspect they would rather just browse/filter/search through my site than have to click through pages of manual curated content. I'd appreciate any thoughts or advice on figuring out my category and navigation system!
Web Design | | peekpeeka0 -
Help with Schema.org on Ecommerce Products
I’m looking for ways of using schema.org with products that have pricing options. There appear to be two main problems 1) Whilst colour, width, height and depth are all catered for, size appears to be missing – how can we mark up products that are available in sizes that aren’t necessarily covered by width/height/depth (e.g. shoe size). Also, what if the product is available in different finishes – technically, these could not properly be described as colours so how could we mark them up? 2) There doesn’t seem to be any particularly good way of marking up pricing options that are displayed on the same product detail page. For e.g. if a pricing option table is used like this: | ID | Colour | Price 001-red | Red | £3.99 001-green | Green | £4.49 001-blue | Blue | £4.99 | I can mark up each row as an offer, and give each offer a price and sku or mpn, but then I can’t use itemprop=”color” to describe exactly what the option is. Would I just use itemprop=”name” in this case and abandon color altogether (even though it’s technically supposed to be describing the colour of the product and not the name of the offer)? I suppose another way I could approach it would be to mark up each row as an individual product, and assign each one an offer with the details as described above but then the containing page would effectively look like a separate product – which it isn’t. Any help or advice on this would be very much appreciated
Web Design | | paulbaguley0 -
Metro style design for a new eCommerce Platform: will it survive?
Hello, While developing eCommerce solution for building webstores in WordPress, our team decided to use metro style design for our dashboard. Could you check the Dashboard screenshot please and discuss several questions with me: How do you think, is it a good idea to use this kind of style? Do you think if there are many people who hate it?:) Should we offer more dashboard designs that can be changed through admin area (may be to offer a standard WP design) or this style will be enough for the start? Thank you very much! Yaros, GosuSell 001_dashboard.jpg
Web Design | | GosuSell0 -
Many errors from previous ecommerce site. Domain is now just a localized wordpress site.
Many errors from previous ecommerce site. Do I need to redirect every single page that no longer exists at this domain? loveyourcabinets.com used to be loveyourkitchenandbath.com but we have since changed course. We want loveyourkitchenandbath.com to be our local site on Long Island and NYC. Loveyourcabinets.com will be an ecommerce project that I'll be revamping in the coming months. I think Moz as well as Google still has all of the old ecommerce pages indexed. And of course, Moz is shooting me a bunch of error all regarding pages from the ecommerce site that used to be on loveyourkitchenandbath.com. Any thoughts? Commentary? Thx
Web Design | | loveyourkitchen0 -
Blog.yoursite.com or yoursite.com/blog/?
Rand made the following post in 2009. In July of 2013 I question whether this is still best practice. Obviously, much has changed in our industry in four-and-a-half years! "...if you're seeking to maximize your ranking ability for a given piece of content, it's my personal belief that you should, most of the time, keep it on 1 subdomain under 1 root domain (but feel free to use subfolders as it makes sense). Starting a blog? I almost always recommend yoursite.com/blog over blog.yoursite.com. Want to launch a new section of content? Use yoursite.com/newstuff rather than newstuff.yoursite.com." Source: http://moz.com/blog/understanding-root-domains-subdomains-vs-subfolders-microsites
Web Design | | JorgeUmana0 -
Infinite Scrolling vs. Pagination on an eCommerce Site
My company is looking at replacing our ecommerce site's paginated browsing with a Javascript infinite scroll function for when customers view internal search results--and possibly when they browse product categories also. Because our internal linking structure isn't very robust, I'm concerned that removing the pagination will make it harder to get the individual product pages to rank in the SERPs. We have over 5,000 products, and most of them are internally linked to from the browsing results pages in the category structure: e.g. Blue Widgets, Widgets Under $250, etc. I'm not too worried about removing pagination from the internal search results pages, but I'm concerned that doing the same for these category pages will result in de-linking the thousands of product pages that show up later in the browsing results and therefore won't be crawlable as internal links by the Googlebot. Does anyone have any ideas on what to do here? I'm already arguing against the infinite scroll, but we're a fairly design-driven company and any ammunition or alternatives would really help. For example, would serving a different page to the Googlebot in this case be a dangerous form of cloaking? (If the only difference is the presence of the pagination links.) Or is there any way to make rel=next and rel=prev tags work with infinite scrolling?
Web Design | | DownPour0 -
Is it OK to 301 Redirect http://homepage.com to http://blog.homepage.com?
I don't have a homepage built yet, and I suspect that my blog will be my primary SEO draw in the long term, so I'd like to do a 301 redirect (for the techies, I'm doing it in Django with http.HttpResponsePermanentRedirect ) I just wanted to confirm that this wouldn't cause any problems as Google gets used to my page (it's only been up for a few days) Thanks! -matt
Web Design | | 49wetnoodles0