A meta element supplies document metadata that is not represented by another dedicated element. Title is a separate HTML element, not a kind of meta tag. Most meta uses belong in head and have no visible body result.
Inspect a complete document head
The example plugin supplies charset, viewport, and title in every copied document. This additional description is metadata, while the body explanation remains visible. Inspect the head in developer tools to see the declarations.
HTML and CSS
HTML
<h1>Metadata practice</h1>
<p>
The title appears in the browser tab; the description belongs in the head.
</p>CSS
Edit HTML or CSS to update the preview as you type. Copy code snippet copies the selected tab. Preview spacing and font defaults are not included.
Match the attribute to the purpose
Charset declares encoding and should appear early in the document. Name/content pairs describe metadata such as description or viewport. Http-equiv uses a different mechanism for supported pragma directives; it is not a way to simulate arbitrary server response headers. Do not combine unrelated forms of metadata in one element.
A width=device-width viewport helps mobile layout and should not disable user zoom. A description can inform a search snippet, but Google can choose other page text. A robots noindex rule asks compliant crawlers not to index a page; the crawler must be able to discover/process it, and it is not privacy protection.
Avoid stale search advice
Google Search does not use meta keywords for ranking. Adding more metadata does not guarantee indexing, traffic, or a rich result. Social platforms use their own supported metadata conventions, such as Open Graph, independently of ordinary img alt.
Write a truthful description of the visible lesson and keep title, headings, and content consistent. Learn meta, title, and head.
Sources
Reference 1 Reference 2 Reference 3 provide the technical details and current compatibility information.