Question: In RTF if I add meta tag as `<meta name="description" content="Products" />` then if I view in source tab of RTF it displays below HTML for single line of meta tag.

```
<pre id="line1">
 <span>&lt;<span class="start-tag">meta</span> <span class="attribute-name">name</span>="<a class="attribute-value">description</a>" <span class="attribute-name">content</span>="<a class="attribute-value">Products</a>" <span>/</span>&gt;</span> 
</pre>

```

How we can restrict to not add extra tags for meta tag.

Answer: 
Meta tag is meant for the head element. It's not something you normally let editors mess with in free form like RTF.

Typically you render each field individually in you page template. By putting it in an RTF you are creating an invalid markup scenario because RTF is meant for content inside the body element. Hence, tridion tries to fix it by converting it into the best markup it can figure out (it's not that smart in this case).

In summary, your approach here is a bit funky, and rethinking the content model of how you specify page meta is probably something to consider.
Many standard WYSIWYG editors will not respond well to HTML elements that are reserved for the `<head>`. Tridion is no different

In both Tridion 2011, and Tridion 2013, a `<meta>` tag added to the **source** of an RTF field will get stripped out. The same will be true if you add a `<link>` or a `<title>`

For RTF fields both in and out of Tridion, it's best to stick with block, or inline-level elements that are meant for content and/or allowed by the W3C to be in the `<body>`