Meta Tag Extractor

The Meta Tag Extractor reads the head of an HTML document and lists every meta tag as a tidy table of name or property paired with its content value. In one pass you can see the page description, keywords, viewport, robots directives, character set, and the full set of Open Graph and Twitter Card tags that control how a link looks when shared.

It is built for SEO specialists, social media managers, and developers who need to verify that a page exposes the right metadata before it ships. Missing or duplicated description tags, an absent og:image, or a wrong twitter:card value can quietly ruin search snippets and social previews, and this tool makes those problems obvious at a glance rather than hidden in the markup.

All parsing happens locally in your browser with JavaScript, so there is no upload and no waiting on a server. Paste the page source or upload an HTML file, optionally filter to only social sharing tags, and the table appears instantly. Because your markup never leaves your device, you can audit private staging pages and confidential templates with confidence.

Features

• Extracts every meta tag and pairs each with its name, property, http-equiv, or charset key for clarity.
• Recognises Open Graph tags such as og:title, og:description, and og:image that drive rich link previews.
• Recognises Twitter Card tags such as twitter:card and twitter:image used by social sharing platforms.
• Offers a social-only filter that hides ordinary meta tags and shows just the sharing-related entries.
• Decodes common HTML entities in content values so ampersands and quotes read naturally in the table.
• Reports counts for total meta tags, Open Graph tags, and Twitter Card tags as quick summary statistics.
• Exports the results to CSV or XLSX, or copies the table to your clipboard for an SEO audit report.

How to use Meta Tag Extractor

1. Paste the full HTML source of the page into the input box, or upload an .html or .htm file.
2. Leave the social-only filter off to see all meta tags, or turn it on to focus on sharing tags.
3. Read the table to confirm the description, viewport, robots, Open Graph, and Twitter Card values.
4. Check the stats panel for the total meta count and how many social tags the page exposes.
5. Fix any missing or incorrect tags in your source, then paste it again to re-verify the output.
6. Export the table to CSV or XLSX, or copy it to share the metadata audit with your team.

Benefits

• SEO specialists confirm that title, description, and robots directives are present and correctly worded.
• Social managers verify that Open Graph and Twitter Card tags will render the intended share preview.
• Developers catch duplicated or empty meta tags before a page reaches production and search engines.
• Agencies produce clear metadata audits for clients using an exportable, easy-to-read table.
• Content teams check that the viewport and charset tags exist so pages render correctly on mobile.
• Anyone debugging a broken link card can see exactly which sharing tag is missing or malformed.

Rich link previews depend on a small but strict set of tags. Open Graph expects og:title, og:description, og:image, and og:url at a minimum, while X and other platforms read twitter:card, twitter:title, twitter:description, and twitter:image. When a shared link shows no image or a plain text card, the cause is almost always one of these tags missing or pointing at a broken URL, and the extractor surfaces the exact values so you can fix them fast.

The social-only filter is handy when a page has a long head full of analytics, verification, and framework meta tags that you do not care about during a sharing audit. Toggle it on to strip everything down to just the og: and twitter: entries. When auditing general SEO, leave it off so you can also confirm the description length, robots policy, and canonical-adjacent directives in one view.

Because the tool relies on regular-expression parsing rather than a live browser, it reads exactly what is in the source you paste, including tags injected server-side. It does not execute JavaScript, so meta tags added dynamically at runtime by a client framework will only appear if they are present in the rendered HTML you supply. Everything is processed locally, keeping private and pre-launch pages secure.