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.
ECommerce Product Meta Descriptions vs. Product Descriptions
-
Wondering if using on-page product descriptions as the individual product meta descriptions is a best practice for an eCommerce site?
Instead of writing two product descriptions (one regular and one meta), I am thinking if the product copy is SEO rich, we'd be good to use just the one for both purposes.
Thoughts? Ideas? Suggestions?
Seems that many companies follow this practice. Thanks!
-
Hi. I know I'm a bit late to the question, but Google favours unique content. Google will issue warnings in GWT if you have just copied and pasted from the page content. You should be looking to write a compelling message that informs viewers of the content of the page and urges them to click through to read more.
I found this [relatively] recent article useful. I just so happen to be looking for more examples when I came here.
http://econsultancy.com/uk/blog/62553-33-examples-of-great-meta-descriptions-for-search
-
You're welcome Gretchen - would love to hear how it turns out in the end...
-
Thanks Alan!
Per your response, I will look closely at the product descriptions already written and either pull out copy that can have keywords added intelligently or simply write a whole separate meta description.
Want to be sure this is time well spent. Approaching this project partially utilizing what is already done could be my best bet.
Thanks again!
-
Are your product descriptions well written? Do they accommodate "cut and paste" use within Meta Description fields? Remember there's a character limit to Meta Descriptions - too short and searchers may not be enticed to click. Too long and you leave it to Google to decide where to cut off...
Otherwise, the concept is a sound one, since the idea is you've said "product copy is SEO rich".
Then again what does THAT mean? A description that is too "spammy" looking may be a deterrent to a click.
Best course of action is to have human review on that whole policy.
And if you want to automate as much as possible, have the first portion of the product description the exact content you want in the meta description field. Standardize it. Make it a policy that writers need to keep that concept in mind.
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
-
Page Title (Meta descriptions) length... how strict are you?
I have just had a conversation with a client... the gist was this... Is it more important to stay under the 55-60 characters OR go over a bit and have the page title make sense and include the clients company name. The same argument for meta description. I have a client insisting on 55-60 length but the keywords are long and if we use the primary keyword phrase the length is 44 if we use the keyword phrase and add the company name it becomes 64. This is with us trimming it a bit. Anyone else discussed this before?
On-Page Optimization | | JohnW-UK1 -
Meta description for Privacy Policy?
Hello guys, Quick question about optimizing other pages on my woocommerce e-commerce store. Do I need to optimize pages like the cart page, checkout page, privacy policy, return policy, shipping policy, etc? Strictly talking about on page SEO for these pages, like meta titles, description. Thanks!
On-Page Optimization | | The_Kiwi_Man0 -
Tags vs. Categories? What should I use?
I'm starting with a blog (self-hosted wordpress) and I'm thinking of the following content structure so that the readers are easily able to locate relevant content: Background: It's a blog which gives people relevant info about government jobs. To start with we will just be publishing information about these jobs but over a period of time also intend to post content that helps readers prepare for these jobs. In other words, right now it's just about detailed job notifications but in the coming months, we shall also post about preparation-related information. Typically, each of the job notifications can be bifurcated like: Jobs basis industry Banking Railways Clinical, etc. Jobs basis company ABC co. DEF co. XYZ co. etc. Jobs basis State / City City 1 City 2, etc. Jobs basis educational qualification Graduation Post-Graduation, etc. Now, I'm seriously confused how should I structure this data from the perspective of Categories & Tags such that it's reader as well as SEO-friendly. Do note that each of the government jobs post ideally falls in a couple of above mentioned categories. Thanks..
On-Page Optimization | | Shalin.TJ0 -
Add content as blog post or to product pages?
Hi, We have around 40 products which we can produce plenty of in-depth and detailed "how to"-type pieces of content for. Our current plan is to produce a "How to make" style post for each as a long blog post, then link that to the product page. There's probably half a dozen or more of these kind of blog posts that we could do for each product. The reason why we planned on doing it like this is that it would give us plenty of extra pages (blog posts) on their own URL which can be indexed and rank for long tail keywords, but also that we can mention these posts in our newsletter. It'd give people a new page full of specific content that they can read instead of us having to say "Hey! We've updated our product page for X!", which seems a little pointless. Most of the products we sell don't get very many searches themselves; Most get a couple dozen and the odd few get 100-300 each, while one gets more than 2,000 per month. The products don't get many searches as it's a relatively unknown niche when it comes to details, but searches for the "categories" these products are in are very well known (Some broad terms that cover the niche get more than 30,000+ searches a month in the UK and 100,000+ world wide) [Exact].
On-Page Optimization | | azu25
Regarding the one product with more than 2,000 searches; This keyword is both the name of the product and also a name for the category page. Many of our competitors have just one of these products, whereas we're one of the first to have more than 6 variations of this product, thus the category page is acting like our other product pages and the information you would usually find on our product pages, is on the category page for just this product. I'm still leaning towards creating each piece of content as it's own blog post which links to the product pages, while the product pages link to the relevant blog posts, but i'm starting to think that it may be be better to put all the content on the product pages themselves). The only problem with this is that it cuts out on more than 200 very indepth and long blog posts (which due to the amount of content, videos and potentially dozens of high resolution images may slow down the loading of the product pages). From what I can see, here are the pros and cons: Pro (For blog posts):
1. More than 200 blog posts (potentially 1000+ words each with dozens of photos and potentially a video)..
2. More pages to crawl, index and rank..
3. More pages to post on social media..
4. Able to comment about the posts in the newsletter - Sounds more unique than "We've just updated this product page"..
5. Commenting is available on blog posts, whereas it is not on product pages..
6. So much information could slow down the loading of product pages significantly..
7. Some products are very similar (ie, the same product but "better quality" - Difficult to explain without giving the niche away, which i'd prefer not to do ATM) and this would mean the same content isn't on multiple pages.
8. By my understanding, this would be better for Google Authorship/Publishership.. Con (Against blog posts. For extended product pages):
1. Customers have all information in one place and don't have to click on a "Related Blog posts" tab..
2. More content means better ability to rank for product related keywords (All but a few receive very few searches per month, but the niche is exploding at an amazing rate at the moment)..
3. Very little chance of a blog post out-ranking the related product page for keywords.. I've run out of ideas for the 'Con' side of things, but that's why I'd like opinions from someone here if possible. I'd really appreciate any and all input, Thanks! [EDIT]:
I should add that there will be a small "How to make" style section on product pages anyway, which covers the most common step by step instructions. In the content we planned for blog posts, we'd explore the regular method in greater detail and several other methods in good detail. Our products can be "made" in several different ways which each result in a unique end result (some people may prefer it one way than another, so we want to cover every possible method), effectively meaning that there's an almost unlimited amount of content we could write.
In fact, you could probably think of the blog posts as more of "an ultimate guide to X" instead of simply "How to X"...0 -
Pagination for product page reviews
Hi, I am looking to add pagination on product pages (they have lots of reviews on the page). I am considering using rel="next/prev, to connect the series of review pages to the main product page. I unfortunately don't have a view-all page for these reviews or the option to get one - the reviews refresh on the same product page (by clicking whatever number page of reviews). This means each page has the exact same description content and everything else, but with different reviews. In this case is rel=next a good option? The format currently would be: On example.com/product link rel="next" href="http://example.com/product?review-p2" On example.com/product?review-p2 link rel="prev" href="http://example.com/product, link rel="next" href="http://example.com/product?review-p3 etc. Would this be a good format for product page reviews? I see rel=nextprev commonly used on ecommerce category/list pages but not really on the paginated reviews on product pages, so I thought I would see if anyone has advice on how best to solve this. I'm also wondering if it would be best to not combine this with a canonical tag on all the different review pages pointing to the product page, seeing as the reviews are actually different (despite the rest of the content being identical). I am hoping to pick up longer tail traffic from this, I figure by connecting the pages and not using canonicals that this way I could get more traffic from the phrases used in the reviews. By leaving out the canonicals, is it possible a user searching for phrases that might be deeper in the series, to land on, say, ?review-p4? Any thoughts if this would drive more traffic? Thanks!.
On-Page Optimization | | pikka0 -
Can I use the same text in my meta description as I put in my post excerpt?
Hi, I'm just trying to understand the right way to optimise my blog posts and this is likely a dumb question... but to what extent should the text in my meta description differ from the text in my post excerpts? cheers, Andrew
On-Page Optimization | | seowhiskey0 -
Internal Linking - in content vs navigation menu
Would like to get some thoughts on whether navigation menus or in-content links are best for internal linking, from an SEO standpoint. A few thoughts to get started with: For sites with a lot of content, you can have a navigation menu linking to your higher-level pages, then in-content links to deeper pages on your site. For smaller sites, this is not an option, as the navigation menu will probably link to all your important pages. You could add in-content links, but Google only counts the first link on the page, so the in-content links would be ignored if you'd already linked yp the page in your top nav menu. I can think of several possible reasons navigation menu links could be less desirable than in content links from a Google perspective. (They are sitewide boilerplate content without context.) If you setup your navigation structure based on what is best for the user, small sites don't have much wiggle room to optimize internal link structure, as all their money pages will be linked to from the top nav menu. Do you think Google prefers in content links to navigation menu links? If so, how do you get around the fact that for many sites, all their money pages are being linked to from their main navigation menu?
On-Page Optimization | | AdamThompson0 -
.us VS .com
In general from what I have experienced a location specific extension such as .co.uk geo-targeted to the same location gives the best results when ranking BUT when I look at results from the US, page after page shows results of .com, surely if my above statement is true then a .us domain extension should rank better then a .com.
On-Page Optimization | | activitysuper0