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?
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
-
Is 301 redirect the only way when using Vanity URLs?
We have been using vanity urls for some of our pages. Mostly the pages that have a vanity URL have a long URL length. But now the problem is, the vanity URL is getting displayed on the search engine when the particular keyword related to the page is entered. I checked the google search console, the vanity URL is indexed and the original URL remains unindexed. What should I do? Is adding 301 redirect to the vanity URLs are solution? Since some of vanity URLs are not redirecting to the original. Some of the original pages are not getting traffic. Also, can using canonical tag help?
Technical SEO | | tejasbansode0 -
Using 410 To Remove URLs Starting With Same Word
We had a spam injection a few months ago. We successfully cleaned up the site and resubmitted to google. I recently received a notification showing a spike in 404 errors. All of the URLS have a common word at the beginning injected via the spam: sitename.com/mono
Technical SEO | | vikasnwu
sitename.com/mono.php?buy-good-essays
sitename.com/mono.php?professional-paper-writer There's about 100 total URLS with the same syntax with the word "mono" in them. Based on my research, it seems that it would be best to serve a 410. I wanted to know what the line of HTACCESS code would be to do that in bulk for any URL that has the word "mono" after the sitename.com/0 -
Hidden H1 Tag on Image
Hi, In the page I'm working on, I encountered an tag in an image, rather than in a text form. Do you think it's an issue when it comes to SEO?
Technical SEO | | nerdieb
What do you suggest I should do if there is an issue? Keen to hear from you!0 -
Hiding h1 tags in Magento
Hi Moz Community, I know that hiding h1 tags isn't a good practice for SEO and google, but we have banners that look much nicer than the stock text Magento uses for its titles. The banners have the same text and the h1 is in the source code, just not visible on front end. The option Magento gives is "hide title on the page." So I'm not sure if this is actually the bad way to hide it or if it's fine for search engines. Thanks,
Technical SEO | | IceIcebaby
-Reed0 -
Custom hreflang tags in WP & using with Yoast
Hi My clients dev has added custom fields for adding hreflang tags to head of pages such as: "Rel Type", "The URL", and "Language Code" Am i right in thinking that until a different language/country version of the site is created these can remain empty or should they still be populated once added say with some sort of global reference or best left blank since will leave the head content global by default ? Also how important is it to add charset to the language code ? since seems optional ? Also this set up is on WP multi-site with Yoast and devs asked me the below: _One thing to note is that Yoast generates its own "canonical" tags - so if _
Technical SEO | | Dan-Lawrence
_you are going to use hreflang tags and canonical tags then you don't need to _
_add a canonical using the custom fields I have set up - Yoast has that _
sorted. _But if you are going down the route of NOT having any canonical tags - and _
_using a x-defult for the hreflang tags, I will need to try and suppress the _
_Yoast canonical tag so you can do this. Much depends on your approach and _
what you think is best. So how do i know if using canonicals or x-default, i take it best simplest to leverage Yoast and hence not add canonicals to custom fields ? Isnt x-default just for indicating language selectors/redirector not specific to 1 region? So long as havnt got those then good to proceed with Yoasts generated canonicals ? Cheers dan0 -
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 -
Using hyphenated sub-domains or non-hyphenated sub-domains? What is the question! I Any takers?
For our corporate business level domain, we are exploring using a hyphenated sub-domain foir a project. Something like www.go-figure.extreme.com I thought from a user perspective it seems cluttered. The domain length might also be an issue with the new Algorithm big G has launched in recent past. I know with past experience, hyphenated domains usually take longer to index, as they are used by spammers more frequently and can take longer to get out of the supplementary index. Our company site has over 90 million viewers / year, so our brand is well established and traffic isn't an issue. This is for a corporate level project and I didn't have the answer! Will this work? anyone have any experience testing this. Any thoughts will help! Thanks, Rob
Technical SEO | | RobMay0 -
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
