What happens if the meta tags are present in the document body?

HtmlTemplatesAsp ClassicSeoMeta Tags

Html Problem Overview

I am working on a ASP application and the code, template and files are organized in a way that does not allow me to alter anything outside the body tag. So I am thinking about inserting the meta tags inside the body -- like this:

<!-- FEW ASP INCLUDES -->
<html>
    <head>
    <!-- FALLBACK TITLE AND DESCRIPTION -->
    <title>Default Title</title>
    <meta name="description" content="Default Description">
</head>
<body>
    <!-- SOME HTML MARKUP -->
    <div class="dynamic-content">
        <!-- InstanceBeginEditable name="dynamic-content" -->
        <!-- THIS IS WHERE I CAN WRITE ASP CODE -->
        <title><%= Page.Meta.GetTitle( yada, yada ) %></title>
        <meta name="description" content="<%= Page.Meta.GetDescription( yada, yada ) %>">
        <!-- InstanceEndEditable -->
    </div>
    <!-- SOME MORE HTML MARKUP -->
</body>
</html>

I am wondering how good it is to put meta tags inside the body of an HTML document. How does it affect:

  1. search engines
  2. browsers

Html Solutions

Solution 1 - Html

This is of course invalid as per HTML4.01. META tags are only allowed within HEAD (just like, say, TITLE) so by putting it into a BODY, you're essentially creating an invalid markup.

From the cursory tests, it seems that some browsers (e.g. Firefox 3.5 and Safari 4) actually put these elements into HEAD when creating a document tree. This is not very surprising: browsers are known to tolerate and try to interpret all kinds of broken markup.

Having invalid markup is rarely a good idea. Non-standard handling by browsers might lead to various hard-to-pin rendering (and behavioral) inconsistencies. Instead of relying on browser guessing, it's best to follow a standard.

I don't know how search engines react to such tag soup, but I wouldn't risk experimenting to find out :) Perhaps they only parse HEAD tag for certain information and will skip your BODY-contained tags altogether. Or maybe they consider these to be some malicious gambling attempts and black-list pages containing such markup. Who knows.

The bottom line — avoid this whenever possible.

Solution 2 - Html

The bottom line is to avoid this whenever possible when the DOCTYPE forbids it. I think this is definitely permitted in HTML5 and very useful in cases using microdata. Example: http://schema.org/Event

Solution 3 - Html

If your aim is search engine optimization, then it is probably a good idea to follow the standards and put all your meta tags in the <head>. However, as far as browser behavior goes, if you place <meta> tags into your <body> they will still function. I decided to test this using multiple <meta http-equiv="refresh"/> tags and <title> tags in an otherwise standards-compliant document.

The results of my tests:

Firefox 18, Firefox 3.6, Firefox Mobile, Chrome 24, Chrome for Mobile, Opera 12, IE6, IE8, IE10:

  • All <meta> tags in the body were processed.
  • The first <title> tag in the document was processed, even if it was in the body. Subsequent <title> tags were ignored.
  • The earliest meta refresh directive took effect, implying that both were processed.

IE9:

  • Same as above, except all <title> tags in the body were ignored.
  • IE10 in IE9 Standards mode also behaves like this.
  • IE9 in IE8 Standards mode behaved the same as IE8, allowing 1 <title> tag in the body.

So, what happens when you use meta tags in the body? By and large, they seem to work fine. The meta tags will probably be processed, so if you can't put them in the head then I wouldn't fret too much.

Solution 4 - Html

I wouldn't do it. That's not where those tags go, and the search engines might view it as spamming. If you can reorganize the master page you can always add a contentplaceholder up in the head section. I've done it trivially with:

<asp:ContentPlaceHolder ID="HeadTags" runat="server" />

This way you can add whatever content you like in the head section back on your page:

<asp:Content ID="Whatever" ContentPlaceHolderID="HeadTags" runat="server" >

    <meta ... >

</asp:Content>

Solution 5 - Html

meta tags can be added anywhere in the HTML.

The web crawlers can read them but the only issue is when you have to share your pages over some application like facebook messenger, whatsapp etc.

These applications only read meta tags present inside the head tag. So, the og:image, og:description properties of meta tag if placed inside body tag are not read and hence won't be displayed while sharing in such applications.

If its only for SEO purpose, you can add meta tag anywhere but it is recommended to add inside head tag only

Solution 6 - Html

I would say you to use it. I found meta tags inside body on various webpages, and they are on one of top 10 searches (on google). It shows, at least to me, that searh engines don't mind if you have used this approach.

You must go ahead if there's no other way around.

Solution 7 - Html

Some meta tags that are meant for search engines will not be honored by the search engines in the body section of the page.

For example Google says that it will not honor a rel=canonical in the body of the page, but only in the head of the page. Here is what Matt Cutts from Google says:

> We don’t allow rel=canonical in the BODY (because as I mentioned, people would spam that),

Solution 8 - Html

I have put some meta tags into the body, but that is because of the Microdata technology. When I do not have a regular element with the info, that I need to describe the object according to the schema.org vocabulary , I set a meta tag with this content. I prefer to do it that way instead, to set an element with display:none. The way with display:none may cause more google problems instead of this, as far as I know. I agree it is not the best practice, but when I validate my document (HTML5) I pass the validation with zero errors. Also I have done this trick for a several projects and none of them has problems with google or other search engine. Even microdata improve the search engine ranking. I don't know what exactly you want to do with this meta tags into the body, because I have not saw any microdata in your code. If you need it for this approach I think it is ok, but in other cases meta elements must be in head section!

Solution 9 - Html

Having the META Description tag in the websites is invalid markup, however is not a huge issue as search engines can regularly find the tag where ever it is. My website does this, have a look at my HTML

http://cameras.specced.co.uk/compare/268/Canon_EOS_200D

The META is in the website BODY however it has been indexed by google and the page meta description has been set as the click though text in google search results.

Categories
Recommended Html Solutions
Recommended Templates Solutions
Recommended Asp Classic Solutions
Recommended Seo Solutions
Recommended Meta Tags Solutions

Previous Solution:

How to import a .hs file in Haskell

HaskellSyntaxModule

Next Solution:

jQuery Datepicker localization

JavascriptJquery UiLocalizationInternationalizationJquery Ui-Datepicker

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionSalman AView Question on Stackoverflow
Solution 1 - HtmlkangaxView Answer on Stackoverflow
Solution 2 - HtmlMichael HView Answer on Stackoverflow
Solution 3 - HtmlnullabilityView Answer on Stackoverflow
Solution 4 - HtmlJohn LockwoodView Answer on Stackoverflow
Solution 5 - HtmlSitaramView Answer on Stackoverflow
Solution 6 - HtmlParvinder SinghView Answer on Stackoverflow
Solution 7 - HtmlStephen OstermillerView Answer on Stackoverflow
Solution 8 - HtmlKaloyan StamatovView Answer on Stackoverflow
Solution 9 - HtmlcousbradView Answer on Stackoverflow