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
-
Logo Image H1 Tag SquareSpace
We have a site hosted on SquareSpace: Roomhance.com Going through the on-page optimizaton tool, we noticed that the H1 tags weren't fully optimized. If you click on view source on the page, it shows 2 H1 tags on the home page: id="logoImage"><a <span="" class="html-attribute-name">href</a><a <span="" class="html-attribute-name">="</a>/">src="//static1.squarespace.com/static/5bcca055ab1a62465f5b9ee7/t/5c18feb270a6adf771765799/1588613682225/?format=1500w" alt="Virtual Staging For Real Estate | Roomhance" /> style="text-align:center;white-space:pre-wrap;">Virtual Staging The 2nd one shown above it the H1 tag we want. I'm wondering if the H1 tag in the logo image is hurting us for SEO? Can't figure out how to modify it in SquareSpace.
On-Page Optimization | | vikasnwu0 -
Multiple H1 tags on Squarespace blog page?
Hi All, I use Squarespace and while running my site (https://www.growmassagebusiness.com) through programs am seeing that my blog posts are being seen as one page with multiple H1 tags. I read through the SS help desk and found back in 2015 someone wrote that it's not a bit deal b/c of HTML5 and that the search engines will read each blog post as a sub-page. I'm not so sure about that and wondering what the experts think? If that is screwy then I'm considering possibly making each blog post it's own page rather than using their blog posting format.
On-Page Optimization | | rajam0 -
Will it upset Google if I aggregate product page reviews up into a product category page?
We have reviews on our product pages and we are considering averaging those reviews out and putting them on specific category pages in order for the average product ratings to be displayed in search results. Each averaged category review would be only for the products within it's category, and all reviews are from users of the site, no 3rd party reviews. For example, averaging the reviews from all of our boxes products pages, and listing that average review on the boxes category page. My question is, will this be doing anything wrong in the eyes of Google, and if so how so? -Derick
On-Page Optimization | | Deluxe0 -
Duplicate page titles and hreflang tags
Moz is flagging a lot of pages on our site which have duplicate page titles. 99% of these are international pages which hreflang tags in the sitemap. Do I need to worry about this? I assumed that it wasn't an issue given the use of hreflang. And if that's the case, why is Moz flagging them as an issue? Thanks.
On-Page Optimization | | ahyde0 -
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 -
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!
On-Page Optimization | | kennyrowe1 -
How to handle Meta Tags on Pagination... page 2,3,4....
Seems that SEOMoz reports are considering my paginated pages as duplicate Meta Tags. For example, I have a product catalog with 5 paginated pages. Obviously the content on each page is unique and the URL ends in =4, =5 for the page number, but the Title and Description are the same for all the pages. Any suggestions on how to handle this? The pages other than page 1 are not indexed, so it should not be a big deal. But wondering if I should programatically ad the page number to the additional pages to show a difference?
On-Page Optimization | | paddlej0 -
Would it be bad to change the canonical URL to the most recent page that has duplicate content, or should we just 301 redirect to the new page?
Is it bad to change the canonical URL in the tag, meaning does it lose it's stats? If we add a new page that may have duplicate content, but we want that page to be indexed over the older pages, should we just change the canonical page or redirect from the original canonical page? Thanks so much! -Amy
On-Page Optimization | | MeghanPrudencio0