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.
H1 Tags on Volusion Product Pages
-
So I'm working with a client who has no heading tags on his site and I'm wondering if there is an ideal method to implementing these on the product pages specifically, as the wording I ideally want to specify is is the product title, which i can't really code with an H1.
Has anyone run into this issue? If so, what was your solution?
Also, how vital are these heading tags on the product pages, anyways?
If the Volusion SEO expert could chime in, that would be much appreciated.
Thanks everyone!
-
Hi Nathan,
Has Volusion implemented this change yet? Will They?
-
Hi Jason, the
concern will be addressed with the release of Volusion's new theme engine. I expect this to be available this year, perhaps Q3. Along with this concern, the entire Volusion interface will be modernized and the new framework will enable unprecedented optimization options across categories and products. More information will be available soon.
As for your 300+ pages of duplicate content, it's very unlikely this is an
issue. Have you tried entering one of your URLs into a free service like copyscape.com ? This could help you identify what content is duplicate. Furthermore, If you'd like to provide your store, I'll take a look and get back to you ASAP with a recommendation.
Regards,
Nathan Joynt
-
I just wanted to check in with this question and see if the latest versions of volusion now incorporate h1 automatically, or if i still need to go into the html on each page and add my h1's manually? Moz says i have over 300 pages of duplicate content, I think because there are no h1 tags with my new volusion store?
-
Hi Paul, thank you for your patience. And thank you everyone else as well. I did get this entered into product for 2014. I do not know currently exact timing, although I will keep you posted.
-
Any update on fixing this in Volusion? It seems so simple just to wrap the page title in H1 rather than having users go through thousands of product pages and manually adding H1 titles to the descriptions.
-
Hi Igor, yes you will have to do it manually for now. I am working with V13 product team on this.
Regards,
Nathan
-
Hi Nathan
Is it now implemented? or I need to do it manually?
Kind regards Igor
-
Nathan,
Thanks for your response. The domain name is www.Oransi.com and I did use Tamara's advice, which worked for the most part. Certain variables came into play that I wasn't expecting, but overall that did fix my issue. However, if you could indeed suggest to the V13 product team about using product names as H1s, I believe your clientele would benefit indeed.
Thanks to everyone who helped here.
-
Hello,
Yes, Tamara is correct with her suggestion to include the
within the Description 'HTML Editor' area. I can talk with the V13 product team as well about the ability to treat the product name as the
. I like to use actual merchant examples in my product optimization requests. Would you mind telling me the domain so I can include it in the story?
Kind regards,
Nathan Joynt
-
Ah Volusion. Yes, we've run into this issue. Unfortunately, you can't add an
around the logical spot for the product name (at the top of the page below the crumb trail) So what we've done, and had very good results from in long tail / product-based search results, is to repeat the product name (sometimes with a bit of a keyword tweak) as the leading data in the product description area - where you do have control over the HTML.
Here's an example: https://www.diigo.com/item/image/3y63p/5pnd?size=o
The CSS which styles the H1's was edited to match the product name display at the top of the page, for consistency.
In order to quickly implement this run of site for all products, we used the CONCAT function in Excel to append the tags, and generally used the "productname" value to populate the heading text, then appended the closing tag + the actual description, and then just inserted back into the db.
CAVEAT: If you're pulling a product feed back out of Volusion, you'll want to strip the HTML out of that description, in order to not get wonky behavior in the CSE's (comparison shopping engines).
Hope that helps - if not, and there's anything else I can add - please let me know.
Cheers!
BMT
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
-
Issues with Multiple H1 tags on homepage?
Hi folks, My homepage has 3 identical H1 tags due to the fact that I have had to create individual hero images (with headings) for desktop, tablet and mobile. I couldn't get my theme to display the layout in exactly the way I wanted on each device without doing a specific hero image and tag for each device type. Does this have a major impact on my SEO? Thanks,
On-Page Optimization | | Veevlimike
Mike.0 -
Should we rename and update a page or create a new page entirely?
Hi Moz Peoples! We have a small site with a simple site navigation, with only a few links on the nav bar. We have been doing some work to create a new page, which will eventually replace one of the links on the nav bar. The question we are having is, is it better to rename the existing page and replace its content and then wait for the great indexer to do its thing, or perm delete the page and replace it with the new page and content? Or is this a case where it really makes no difference as long as the redirects are set up correctly?
On-Page Optimization | | Parker8180 -
Product content length & links within product description
Hello, I have questions regarding content length and links within descriptions. With our ecommerce site, we have thousands of products, each with a unique description. In the product description, I have links to the parent category and grandparent category (if it has one) in the main product text which is generally about 175 words. Then I have a last paragraph that's about 75 words that includes links to our main homepage and our main product catalogue page. Is the content length long enough? I used to use text that was 500 words, and shortening it I still rank when launching new products, so I don't think an increase in text length will have any additional benefit. I do see conflicting information when I do searches, with some people recommending a minimum of 300 words and some saying to try and go a 1000 for category pages. In regards to the links, I noticed a competitor has stopped following this format, so I'm unsure if I should keep going too. Is it too many links to have each of the products link back to the main catalogue and homepage? Is it good to have links with anchor text to the categories a product is in? There are breadcrumbs on the page with these links already. There are already have heaps of links on our pages (footer, and a right sidebar with image links to relevant categories), so my pages do get flagged for too many links. Thanks!
On-Page Optimization | | JustinBSLW0 -
Listing all services on one page vs separate pages per service
My company offers several generalized categories with more specific services underneath each category. Currently the way it's structured is if you click "Voice" you get a full description of each voice service we offer. I have a feeling this is shooting us in the foot. Would it be better to have a general overview of the services we offer on the "Voice" page that then links to the specified service? The blurb about the service on the overview page would be unique, not taken from the actual specific service's page.
On-Page Optimization | | AMATechTel0 -
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 -
Home page or landing page?
Hello, I want to ask a question related to that - Should we put keywords in the home page title if we wish to position another landing page better for particular keywords? I have read in one website about SEO that it's good the main keywords of your website to be positioned in homepage title also. f.e. Let's say we have website about web-design and our company is named Company Ltd. The title of the home page is "Company Ltd. - Web design, SEO, etc" We have also another inner page named "Web design | Company Ltd.". So should we leave the first page name only "Company Ltd." and the landing page's name "Web design | Company Ltd." . I don't know if they both have the same keyword in their title they won't compete with each other.
On-Page Optimization | | HrishikeshKarov0 -
Does it matter what text you wrap in an H1 tag?
Typically H1 tags are reserved for page headings, i.e. on a blog post the blog post title is very often the pages H1, or top-level heading as the W3C puts it. On the SEOmoz home page they currently have "SEO Software." as their H1 tag, which seems perfectly reasonable and to me fits the W3C criteria. However, what if the primary keyword for SEOmoz was "seo community" so they decided to wrap just those two words in the sentence that follows on their home page and maintain the existing style of the words "seo community" with CSS. (see attachment) Are there any arguments against doing that? Would Google be able to detect this? If so, would Google care? I do believe the overall importance of the H1 tag has lessened to a degree, however I still believe they are valuable to an extent and would love to hear anyone's thoughts. 7NZcD.png
On-Page Optimization | | TakeLessons1