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.
Using a non-visible H1
-
I have a developer that wants to use style="text-indent:-9999px" to make the H1 non-visible to the user. Being the conservative person I am, I've never tried this before and worry that Search Engines may think this is a form of cloaking. Am I worrying about nothing? And apologies if it's already been covered here. I couldn't find it. Thanks in advance!!!!
-
From Whiteboard Friday - The Biggest SEO Mistakes SEOmoz Has Ever Made
http://www.seomoz.org/blog/whiteboard-friday-the-biggest-seo-mistakes-seomoz-has-ever-made
"3. Recommending People Use H1 Tags with Keywords
This mistake is a little bit more subtle. For years, SEOmoz recommended including keywords in the H1 of pages. After we started doing formal machine learning correlation tests we found out that this tactic didn't actually help very much at all (including the keywords in normal text in bigger fonts worked essentially the same). This was a shame because it meant we wasted time and energy convincing our clients to update their H1s."
-
Using that CSS wouldn't Hide it from the spiders view, it will simply "move" the H1 off the screen.
It is a pretty old "trick".
Lets not forget Heading tags are useful to site visitors to so shouldn't necessarily be hidden to them.
Users will use the headings whilst they Scan read your pages, if they can't quickly identify what the page content is about there is a danger they could simply bounce off... and you will lose them.
As for Search engines penalising you for it, I'm not too sure, is there any research which anybody can point us towards? I dont think they are reading CSS attributes just yet right?
Andy
-
You came to the right place for the validity you seek
I frequently vet things here in the forum and it has proven very helpful in convincing other members of my team to go one way or the other. Also, I completely agree with George's suggestion to use the "alt" attribute if it is indeed an image we are talking about, but it appears we are really talking about a bonafidetag for text with keywords in it.
That being the case. Stick to your guns and insist on it being visible. If you really feel that it disrupts the design...it would be better to leave it out than to make it invisible.
Good luck!
Dana
-
Thanks All! So here's more detail. The home page design was completed. I still think H1 has some reasonable value and it didn't have one so I told him to put a keyword rich H1 in. He felt it disrupted the existing design and executed it as above. So....I thought I would seek "convergent validity" on the subject as a next step.
-
I concur with Dana,
Hiding your H1 tag will not necessarily cause a penalty. However, if you do so you are at risk for a penalty. If a particular savvy competitor comes along and notices you are obfuscating your H1 tags and reports it, then you may get dinged. I doubt that alone would cause a problem, but if that sort of tactic is par for the course for this web developer you may be in trouble.
-
Read up on this Webmaster Tools guideline: http://support.google.com/webmasters/bin/answer.py?hl=en&answer=66353
Note the following from the guideline if there is a very important reason for why your developer wants to use CSS to move the text off the page:
"However, not all hidden text is considered deceptive. For example, if your site includes technologies that search engines have difficulty accessing, like JavaScript, images, or Flash files, using descriptive text for these items can improve the accessibility of your site."
If there is not a very important reason, and even if there is, suggest they populate the ALT attribute of the image with the text instead.
Hope this helps!
-
The general SEO community consensus is that you should:
A. be doing what is best for the user (so not concealing the H1 tag)
B. not doing anything that could make Matt Cutts and the Google team upset
They have advised against attempting to conceal content for SEO gain so I would strongly recommend avoiding it. They have been dealing with these issues now for a LONG time, so presumably their bots can easily pick up on those tricks.
The Google bots can now "see" what is visible on the page. They discount things that are not in the visible content area so the benefit to an offset H1 would likely be none. Also: They're watching you.
-
Personally, I wouldn't do it. Does it work? Maybe. Or, maybe it works for a while and then Googlebot wises up and deindexes you. Is all the work you will have to go through for reconsideration going to justify hiding that tag? I'd say, definitely not.
It's just an
tag...leave it on the page and visible. Listen to your conservative gut and do what you know is the right thing. That's my two cents
-
I have personally created an H1 tag in an image, I didn't see no negative effects. H1 tags are not as important but should be implemented, so even if it had any impact maybe it was minuscule.
H1 tags don't generally have to be visible like in my case, it was an H1 tag for the logo. I'm not sure where you are putting the H1 tag but if its an image I say why not, but if it is a regular text, why not just keep it as an H1 without hiding?
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
-
Same H1 & H2 Tags
Is it bad to have the same H1 & H2 tag on one page? I found a similar question here on the moz forum but it didn't exactly answer my question. And will adding "about" on the H2 help, or should we avoid duplicate tags completely? Here is a link to the page in question (which will repeat throughout this site.) Thanks in advance!
Technical SEO | | Mike.Bean0 -
Brand name as H1 on every page
Hi, Along with the title of each page, a Wordpress client has their brand name as a H1 on every single page. This is situated in the footer and just sits within the company info/address. Should these tags be removed, leaving just the page titles as H1s? Cheers, Lewis
Technical SEO | | PeaSoupDigital0 -
Duplicate Content Issue WWW and Non WWW
One of my sites got hit with duplicate content a while ago because Google seemed to be considering hhtp, https, www, and non ww versions of the site all different sites. We thought we fixed it, but for some reason https://www and just https:// are giving us duplicate content again. I can't seem to figure out why it keeps doing this. The url is https://bandsonabudget.com if any of you want to see if you can figure out why I am still having this issue.
Technical SEO | | Michael4g1 -
Can I use a 410'd page again at a later time?
I have old pages on my site that I want to 410 so they are totally removed, but later down the road if I want to utilize that URL again, can I just remove the 410 error code and put new content on that page and have it indexed again?
Technical SEO | | WebServiceConsulting.com0 -
302 redirect used, submit old sitemap?
The website of a partner of mine was recently migrated to a new platform. Even though the content on the pages mostly stayed the same, both the HTML source (divs, meta data, headers, etc.) and URLs (removed index.php, removed capitalization, etc) changed heavily. Unfortunately, the URLs of ALL forum posts (150K+) were redirected using a 302 redirect, which was only recently discovered and swiftly changed to a 301 after the discovery. Several other important content pages (150+) weren't redirected at all at first, but most now have a 301 redirect as well. The 302 redirects and 404 content pages had been live for over 2 weeks at that point, and judging by the consistent day/day drop in organic traffic, I'm guessing Google didn't like the way this migration went. My best guess would be that Google is currently treating all these content pages as 'new' (after all, the source code changed 50%+, most of the meta data changed, the URL changed, and a 302 redirect was used). On top of that, the large number of 404's they've encountered (40K+) probably also fueled their belief of a now non-worthy-of-traffic website. Given that some of these pages had been online for almost a decade, I would love Google to see that these pages are actually new versions of the old page, and therefore pass on any link juice & authority. I had the idea of submitting a sitemap containing the most important URLs of the old website (as harvested from the Top Visited Pages from Google Analytics, because no old sitemap was ever generated...), thereby re-pointing Google to all these old pages, but presenting them with a nice 301 redirect this time instead, hopefully causing them to regain their rankings. To your best knowledge, would that help the problems I've outlined above? Could it hurt? Any other tips are welcome as well.
Technical SEO | | Theo-NL0 -
Hreflang on non-canonical pages
Hi! I've been trying to figure out what is the best way to solve this dilemma with duplicate content and multiple languages across domains. 1 product info page 2 same product but GREEN
Technical SEO | | LarsEriksson
3 same product but RED
4 same product but YELLOW **Question: ** Since pages 2,3,4 just varies slightly I use the canonical tag to indicate they are duplicates of page 1. Now I also want to indicate there are other language versions with the_ rel="alternate" hreflang="x" _element. Should I place the _rel="alternate" hreflang="x" _on the canonical page only pointing to the canonical page with "x" language. Should I place the _rel="alternate" hreflang="x" _on all pages pointing to the canonical page with the "x" language? Should I place the _rel="alternate" hreflang="x" _on all pages and then point it to the translated page (even if it is not a canonical page) ? /Lars0 -
404 errors on non-existent URLs
Hey guys and gals, First Moz Q&A for me and really looking forward to being part of the community. I hope as my first question this isn't a stupid one but I was just struggling to find any resource that dealt with the issue and am just looking for some general advice. Basically a client has raised a problem with 404 error pages - or the lack thereof- on non-existent URLs on their site; let's say for example: 'greatbeachtowels.com/beach-towels/asdfas' Obviously content never existed on this page so its not like you're saying 'hey, sorry this isn't here anymore'; its more like- 'there was never anything here in the first place'. Currently in this fictitious example typing in 'greatbeachtowels.com/beach-towels/asdfas**'** returns the same content as the 'greatbeachtowels.com/beach-towels' page which I appreciate isn't ideal. What I was wondering is how far do you take this issue- I've seen examples here on the seomoz site where you can edit the URI in a similar manner and it returns the same content as the parent page but with the alternate address. Should 404's be added across all folders on a site in a similar way? How often would this scenario be and issue particularly for internal pages two or three clicks down? I suppose unless someone linked to a page with a misspelled URL... Also would it be worth placing 301 redirects on a small number of common mis-spellings or typos e.g. 'greatbeachtowels.com/beach-towles' to the correct URLs as opposed to just 404s? Many thanks in advance.
Technical SEO | | AJ2340 -
Using a third party server to host site elements
Hi guys - I have a client who are recently experiencing a great deal of more traffic to their site. As a result, their web development agency have given them a server upgrade to cope with the new demand. One thing they have also done is put all website scripts, CSS files, images, downloadable content (such as PDFs) - onto a 3rd party server (Amazon S3). Apparently this was done so that my clients server just handles the page requests now - and all other elements are then grabbed from the Amazon s3 server. So basically, this means any HTML content and web pages are still hosted through my clients domain - but all other content is accessible through an Amazon s3 server URL. I'm wondering what SEO implications this will have for my clients domain? While all pages and HTML content is still accessible thorugh their domain name, each page is of course now making many server calls to the Amazon s3 server through external URLs (s3.amazonaws.com). I imagine this will mean any elements sitting on the Amazon S3 server can no longer contribute value to the clients SEO profile - because that actual content is not physically part of their domain anymore. However what I am more concerned about is whether all of these external server calls are going to have a negative effect on the web pages value overall. Should I be advising my client to ensure all site elements are hosted on their own server, and therefore all elements are accessible through their domain? Hope this makes sense (I'm not the best at explaining things!)
Technical SEO | | zealmedia0
