Answers.Body: <p>I this for the Craft 2 version of SEOmatic, or the Craft 3 version of SEOmatic? The Craft 3 version does not have a <code>{% hook 'seomaticRender' %}</code> tag at all.</p>
  
  <p>Instead, the metadata is automatically added where it should go to various parts of the document. I wouldn't <em>recommend</em> changing where this is output without a good reason, but if you really want to:</p>
  
  <p><a href="https://nystudio107.com/docs/seomatic/Using.html" rel="nofollow noreferrer">https://nystudio107.com/docs/seomatic/Using.html</a></p>
  
  <p>Disable automatic rendering:</p>
  
  <pre><code>{% do seomatic.config.renderEnabled(false) %}
  
  </code></pre>
  
  <p>Then where you want each container's output, you'd need to manually do:</p>
  
  <pre><code>{{ seomatic.jsonLd.render() }}
  {{ seomatic.link.render() }}
  {{ seomatic.script.render() }}
  {{ seomatic.tag.render() }}
  {{ seomatic.title.render() }}
  </code></pre>
  
  <p>In the appropriate places in the DOM. The reason it's not recommended that you do this is that SEOmatic puts things where they should go already, and there's no real benefit in moving them around.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-05-28T14:06:44.133Z
Answers.Text: This is for C3, so I will remove the hook tag. I did notice that the SEO renders with or without the tag. Does it make any big-picture difference if the meta title (and everything else handled by Seomatic) is output after my CSS, favicon links, and manifest? I usually place all of that SEO data before.
Answers.UserDisplayName: Vaughn D. Taylor
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-05-27T13:49:15.357Z
Answers.LastActivityDate: 2020-05-27T13:49:15.357Z
Answers.UserDisplayName: andrew.welch
Body: <p>When I use the <code>{% hook 'seomaticRender' %}</code> tag in my template, I expected that it would output the data in the position where it's located. For example, I have the following in my template:</p>
  
  <pre><code>{% hook 'seomaticRender' %}
  &lt;meta name="msapplication-TileColor" content="#ffffff"&gt;
  </code></pre>
  
  <p>But when the template is rendered, the Seomatic data is output after the "msapplication-TileColor" meta tag. I don't suppose it matters much, but I like to keep a specific order for tags in my header.</p>
  
  <p>I'm quite sure the answer is somewhere in the documentation, but it would be great to have a comprehensive example template.</p>
  
Tags: <plugin-seomatic>
Title: How do I control order of output using Seomatic plugin
ThreadText: # How do I control order of output using Seomatic plugin
  
  (Asked by: username_0 on 2020-05-27)
  
  When I use the `{% hook 'seomaticRender' %}` tag in my template, I expected that it would output the data in the position where it's located. For example, I have the following in my template:
  
  ```
  {% hook 'seomaticRender' %}
  <meta name="msapplication-TileColor" content="#ffffff">
  
  ```
  
  But when the template is rendered, the Seomatic data is output after the "msapplication-TileColor" meta tag. I don't suppose it matters much, but I like to keep a specific order for tags in my header.
  
  I'm quite sure the answer is somewhere in the documentation, but it would be great to have a comprehensive example template.
  
  **Tags:** plugin-seomatic
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2020-05-27. Score: 3 | Accepted answer
  
  I this for the Craft 2 version of SEOmatic, or the Craft 3 version of SEOmatic? The Craft 3 version does not have a `{% hook 'seomaticRender' %}` tag at all.
  
  Instead, the metadata is automatically added where it should go to various parts of the document. I wouldn't *recommend* changing where this is output without a good reason, but if you really want to:
  
  <https://nystudio107.com/docs/seomatic/Using.html>
  
  Disable automatic rendering:
  
  ```
  {% do seomatic.config.renderEnabled(false) %}
  
  ```
  
  Then where you want each container's output, you'd need to manually do:
  
  ```
  {{ seomatic.jsonLd.render() }}
  {{ seomatic.link.render() }}
  {{ seomatic.script.render() }}
  {{ seomatic.tag.render() }}
  {{ seomatic.title.render() }}
  
  ```
  
  In the appropriate places in the DOM. The reason it's not recommended that you do this is that SEOmatic puts things where they should go already, and there's no real benefit in moving them around.
  
  > **Comments:**
  > **username_0**: This is for C3, so I will remove the hook tag. I did notice that the SEO renders with or without the tag. Does it make any big-picture difference if the meta title (and everything else handled by Seomatic) is output after my CSS, favicon links, and manifest? I usually place all of that SEO data before.  
  
  ---
  
  