Find hidden metadata issues with Meta Checker
Meta Checker is a Chrome extension for inspecting webpage metadata in one focused view. It compares the browser's live DOM with the original HTML response, revealing metadata that was added, changed, or removed after the page loaded.
What is Meta Checker?
When search titles or social preview images differ from expectations, finding individual tags in developer tools is slow. Meta Checker brings essential tags, Open Graph data, HTTP response details, language signals, robots directives, and JSON-LD summaries into one interface.
It is especially useful when metadata changes during JavaScript rendering. Separating server values from client-added, modified, or removed values gives you a clearer basis for diagnosing what search engines and AI crawlers may encounter.
What you can inspect
Original HTML vs live DOM
See whether metadata is unchanged, newly added, modified, or removed.
SEO and social metadata
Review essential metadata and Open Graph values used by search and sharing surfaces.
Robots, language, and structured data
Inspect robots directives, language signals, JSON-LD summaries, and HTTP response information together.
Practical use cases
Pre-release SEO QA
Check title, description, canonical, robots, and language settings across templates to catch omissions before release.
Diagnose social preview issues
Verify Open Graph titles, descriptions, and image URLs to narrow down the cause of broken share cards.
Compare SPA and SSR metadata
Compare server responses and rendered DOM output in frameworks such as Next.js to identify client-dependent metadata.
Review foundational GEO signals
Check that language, robots, structured data, and page descriptions are consistent, giving AI search systems clearer signals about the content.
How to use it
- 1
Install the extension
Open the link and add Meta Checker to your browser from the Chrome Web Store.
- 2
Open the page to inspect
Navigate to a public page or an accessible development URL, then launch the extension.
- 3
Review differences and omissions
Compare original HTML and live DOM states, then focus the visible fields on potential SEO and GEO conflicts.
Metadata audit checklist
- Confirm every page has a unique title and description that accurately summarize its content.
- Check that canonical, hreflang, and HTML lang values follow the same locale and URL strategy.
- Review robots and X-Robots-Tag directives for unintended restrictions on search or AI crawlers.
- Ensure JSON-LD names, URLs, and descriptions agree with the visible content and metadata.
- If essential metadata appears only after JavaScript rendering, consider crawler differences and review server output as well.
Frequently asked questions
Why compare the live DOM with the original HTML?
JavaScript can add or change metadata after load. Comparing both states reveals differences between server output and the final browser DOM, making potential crawling and indexing risks easier to assess.
Can Meta Checker predict search rankings?
No. It is a diagnostic tool for technical metadata and related signals. Search performance also depends on content quality, site structure, links, performance, crawlability, and many other factors.
Does detected JSON-LD mean the structured data is valid?
Presence and validity are different. Use the summary for a quick review, then validate syntax and eligibility with the relevant search engine's official structured-data testing tools.
What should I check first for GEO?
Start by confirming that the topic and publisher are clear and that visible content, descriptions, language signals, and structured data agree. GEO is not a single tag; it involves clarity, trust, and accessibility together.
Inspect the page immediately after deployment
What matters is not just metadata in source code, but what the server and rendered page actually expose. Open the production page with Meta Checker and inspect both the original HTML and live DOM.
Add Meta Checker to Chrome