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
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
-
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 -
NOINDEX, FOLLOW on product page - how about images indexing?
Hi, Since we have a lot of similar products with duplicate descriptions, I decided to NOINDEX, FOLLOW most of these different variants which have duplicate content. However, I guess it would be useful in marketing terms if Google image search still listed the images of the products in image search. How does the image search of Google actually work - does it read the NOINDEX on the product page and therefore skip the image also or is the image search completely dependent on the ALT tag of any image found on our site? Thanks!
On-Page Optimization | | speedbird12290 -
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 -
How will it effect SEO to have multiple h1 tags on a page?
I have a client who recieved this advice from his marketing consultant: "If there are multiple h1 tags on a page, this can confuse Google and it may have a negative impact on the keyword rankings. If you could ask your web developer to go in and remove the h1 tags on the header images that would be helpful. This way it will be easier for Google to index your site and will help your keyword rankings." How will it effect SEO to have multiple h1 tags on a page?
On-Page Optimization | | GRIP-SEO0 -
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 -
Is it ok to use the H1 tag for bullet points?
Our search results page doesn't have a typical H1 tag because adding a true header would take up space unnecessarily. Therefore, we've assigned the h1 tag to be the breadcrumb. As filters are applied, the breadcrumb grows to include these filters. This breadcrumb is coded as bullet points, even though they're not the typical style of bullet points. Here's a screenshot: http://screencast.com/t/AjGC9iAYR3 For example, the breadcrumb: Home >> NYC Social Media Classes >> Adult >> Manhattan is currently coded as: | |
On-Page Optimization | | mevseo
| | * class="first"><a <span="">href</a><a <span="">="</a>/">Home |
| | * <a <span="">href</a><a <span="">="</a>/nyc/classes/social-media/age-adults/neighborhood-manhattan" class="Selected">Search results |
| | |
| | |
| | id="cat_social-media" type="checkbox" checked onclick="setCategory('social-media')" /> |
| | # style="font-size: 12px; display: inline;">NYC Social Media Classes |
| | <label <span="">for</label>="cat_social-media"> |
| | |
| | |
| | |
| | <nobr>id="age_adults" type="checkbox" checked onclick="setAge('adults')" /><label <span="">for</label>="age_adults">Adults</nobr> |
| | |
| | |
| | <nobr>id="nbhd_manhattan" type="checkbox" checked onclick="setNeighborhood('manhattan')" /><label <span="">for</label>="nbhd_manhattan">Manhattan</nobr> |
| | |
| | | Right now that H1 tag just relates to 'NYC Social media classes', but we'd like to expand it to include both 'Manhattan' & 'Adults' - would that be ok? And if so, would it be better to put the tag before and after the tag?0 -
Tag clouds: good for internal linking and increase of keyword relevant pages?
As Matt Cutts explained, tag clouds are OK if you're not engaged in keyword stuffing (http://www.youtube.com/watch?v=bYPX_ZmhLqg) - i.e. if you're not putting in 500 tags. I'm currently creating tags for an online-bookseller; just like Amazon this e-commerce-site has potentially a couple of million books. Tag clouds will be added to each book detail page in order to enrich each of these pages with relevant keywords both for search engines and users (get a quick overview over the main topics of the book; navigate the site and find other books associated with each tag). Each of these book-specific tag clouds will hold up to 50 tags max, typically rather in the range of up to 10-20. From an SEO perspective, my question is twofold: 1. Does the site benefit from these tag clouds by improving the internal linking structure? 2. Does the site benefit from creating lots of additional tag-specific-pages (up to 200k different tags) or can these pages become a problem, as they don't contain a lot of rich content as such but rather lists of books associated with each tag? Thanks in advance!
On-Page Optimization | | semantopic0 -
E-Commerce product pages that have multiple skus with unique pages.
Hey Guys, With the recent farm/panda update from google i'm at a cross roads as to how I should optimize product pages for a project i'm working on for a client. My client sells tires and one particular tire brand can have up to 15 models and each model can have up to 30 sizes. IE: 'Michelin Pilot Sport Cup' comes in 15 different sizes. Each size will have it's unique product page and description bringing me to my question. Should I use the same description on every size? I do plan on writting unique content for each tire model however i'm not sure if I should do it for every size. After all the tire model description is the same for every size, each size doesn't carry any unique characteristics that I can describe. Thanks in advance!
On-Page Optimization | | MikeDelaCruz770