title: Is including <meta name="fragment" content="!"> harmful for pages with hashbang?
body: <p>Google says about this meta tag:</p>
  
  <blockquote>
    <p>The following important restrictions apply:</p>
    
    <ol>
    <li>The meta tag may only appear in pages without hash fragments.</li>
    <li>Only "!" may appear in the content field.</li>
    <li>The meta tag must appear in the head of the document.</li>
    </ol>
  </blockquote>
  
  <p>Source: <a href="https://developers.google.com/webmasters/ajax-crawling/docs/specification?hl=fr-FR">https://developers.google.com/webmasters/ajax-crawling/docs/specification?hl=fr-FR</a></p>
  
  <p>I'm aware that it is only needed for pages that do <strong>not</strong> contain a hashbang but still should be served with a snapshot. But that is usually just the home page.</p>
  
  <p>Let's say we have:</p>
  
  <p><em>www.foo.com</em></p>
  
  <p><em>www.foo.com/#!/jobs</em></p>
  
  <p>The second one will be fetched as:</p>
  
  <p>www.foo.com?_escaped_fragment_=/jobs</p>
  
  <p>just because of the hashbang.</p>
  
  <p>But the root page has no hashbang so it needs to have this special meta tag in the head.</p>
  
  <pre><code>&lt;meta name="fragment" content="!"&gt;
  </code></pre>
  
  <p>But since all my single page application uses the same <code>&lt;head&gt;</code> so far I wonder if it's actually harmful to keep the meta tag in for all the other pages that <strong>do</strong> contain a hashbang.</p>
  
  <p>What will actually happen?</p>