1. Nguồn
Phản hồi HTML trực tiếp. Kết quả xác định nguồn gốc của bằng chứng.
The Novaverb meta tag checker fetches one page's live HTML and reports its title, meta description, headings, canonical, robots directive, Open Graph and X card tags, and the JSON-LD schema types it declares.
Chạy một kiểm tra thực tế ở trên
Gửi một URL công khai, tên miền, hoặc từ khóa. Novaverb sẽ chỉ hiển thị bằng chứng mà công cụ này thực sự có thể lấy hoặc đo lường.
A meta tag checker is a tool that reads the tags a page declares about itself in its HTML. The Novaverb Meta Tag Checker requests one page's live initial HTML and reports the title tag, meta description, heading structure, canonical, robots directive, social tags and JSON-LD schema types found in that response.
The meta tag checker checks the title and its character count, the meta description and its length, every H1 with a count of H2 and H3 headings, the canonical URL, the meta robots value, the mobile viewport, the html lang attribute, Open Graph and X card tags, image alt attributes, internal and external links, and JSON-LD types.
The meta tag checker is for content editors confirming a page published with the title they wrote, SEO specialists reviewing a landing page before a campaign, developers checking that a template outputs a canonical and a viewport tag, and social media managers who need to know whether a shared link will carry Open Graph tags.
A meta tag checker catches tag problems that a rendered page hides. A missing title, an empty description, a second H1 added by a theme, a noindex value left over from staging or a JSON-LD block that never reached the HTML all look fine in a browser. One fetch shows them before a crawler reads the same response.
The meta tag checker works in a fixed sequence. The page address is normalized and fetched, and the title, meta description and heading hierarchy are read from the returned HTML. Length and presence are compared with common search-appearance guidance, which is guidance and not a hard rule. Declared JSON-LD type values are then detected and listed.
Enter one page address into the meta tag checker, not just a domain, because metadata is a per-page property and a homepage title says nothing about a product page. Scheme, www, path and query are normalized. Only publicly routable addresses are checked, and a page that does not return HTTP 200 is reported as unreadable instead of parsed.
yourdomain.com/a-real-pageBất kỳ hình thức địa chỉ nào cũng hoạt động - siêu dữ liệu được đọc từ đúng trang đó. http hoặc https, có hoặc không có www, chỉ tên miền hay một đường dẫn đầy đủ - chúng tôi chuẩn hóa cho bạn.https://www.yourdomain.com/blog/postMột URL đầy đủ với một đường dẫn là lý tưởng; chúng tôi đọc các thẻ của tài liệu đó.Expecting a site-wide audit from one URLChúng tôi đọc thẻ của một trang; kiểm tra thẻ toàn bộ trang web là một quá trình thu thập không gian làm việc kết nối, không phải lần lấy đơn này.A meta tag checker report contains the HTTP status, a search snippet preview built from the captured title and description, length bars for both, heading and word counts, image and link counts, the text of each H1, a table of technical and social tags, the detected schema types, and an analysis panel with findings and priority fixes.
Read a meta tag checker result from the snippet preview down. Length bars are green inside the suggested range, amber outside it and red when the tag is absent, a review cue and not a verdict. A warning beside the H1 count means none or several were found. A row reading missing names the tag to add.
Trình kiểm tra này lấy HTML của một trang và trích xuất các thẻ mà các công cụ tìm kiếm và nền tảng xã hội đọc: tiêu đề, mô tả meta, tiêu đề, chuẩn hóa, ngôn ngữ, chỉ thị robots, Open Graph và thẻ Twitter/X, và bất kỳ dữ liệu có cấu trúc schema.org nào. Nó báo cáo những gì có mặt và kích thước của nó, nhưng không đảm bảo xếp hạng hoặc cách Google sẽ hiển thị đoạn trích của bạn.
The meta tag checker gets its data from the live HTML response of the address you submit, fetched at the moment of the check. The status code, the tags and every count come from that one response. Nothing is read from a stored crawl or a search engine, and no other page of the site is requested.
The meta tag checker does not tell you how a search engine will display the page. Titles and descriptions can be rewritten to match a query, so a well-formed tag is what you control and the visible snippet is not. Metadata or schema injected only after JavaScript runs may not appear, and only the submitted page is read.
A meta tag checker result proves what a page declares about itself in its initial HTML: the title, the description, the heading hierarchy and the JSON-LD types present in the markup. That is proof of declaration, not of display. A tag reported as missing is also what a non-rendering crawler sees, even when a browser shows it.
Phản hồi HTML trực tiếp. Kết quả xác định nguồn gốc của bằng chứng.
Công cụ đọc phản hồi HTML ban đầu. Thẻ meta hay schema chỉ được chèn vào sau khi JavaScript chạy trên trình duyệt có thể sẽ không xuất hiện.
Sử dụng phát hiện để xác minh một vấn đề, sau đó kết nối một không gian làm việc khi bạn cần lịch sử, giám sát hoặc phân tích toàn bộ trang web.
The meta tag checker applies the WHATWG HTML Standard, which defines the title, meta description and heading elements it reads, and the schema.org vocabulary, which defines the JSON-LD types it detects. Length is reported as guidance because no specification fixes a title length. The width a search result allows is a rendering decision, not a rule.
Đọc thẻ title, meta description và các phần tử heading theo tiêu chuẩn HTML.
Đọc thông số kỹ thuậtPhát hiện các giá trị @type dữ liệu có cấu trúc được khai báo dưới dạng JSON-LD.
Đọc thông số kỹ thuậtVerify a meta tag checker result by opening the page source in a browser, not the element inspector, and searching for the title element, the description meta tag, the canonical link and each script of type application/ld+json. Page source shows the initial HTML the checker read, while the inspector shows the page after scripts have run.
A typical meta tag checker finding is a product page that returns HTTP 200 with a clear title, while the snippet preview shows no meta description and the H1 count carries a warning because a theme wrapped the logo in a second H1. The analysis panel lists both and adds a priority fix for the missing description.
The meta tag checker is free and runs without an account. Any public page can be checked from the form. A free Novaverb account is needed only for work the single fetch cannot do: auditing titles, descriptions, canonicals and schema across a whole site, saving the evidence and rechecking that a fix is live.
A Novaverb workspace adds a crawl of every page to the meta tag checker, so titles, descriptions, canonicals and schema are reviewed across the site in one place. Crawl Explorer is the product that continues the job: it inspects every URL captured in the project crawl and turns each supported technical finding into an action.
A free meta tag checker run is not enough when the question covers more than one page. Finding every page that shares a title, lacks a description or misses a canonical needs a crawl of the whole site. Confirming that a template change stayed in place after later releases needs the same measurement repeated over time.
After running the meta tag checker, deal with a noindex value or a missing title first, since both are listed as errors. Then write or tighten the meta description, settle on one clear H1, declare a canonical and add a viewport tag if absent. Publish, run the check again, and confirm the new tags appear in the response.
Other free tools pair with the meta tag checker once a gap is found. The Meta Tag Generator creates title, description, canonical, robots, Open Graph and X card tags. The Schema Markup Generator builds JSON-LD for types such as FAQ, Article and Product. The Website SEO Checker adds robots.txt and sitemap checks for the homepage.
People ask what the meta tag checker checks, what a meta description and JSON-LD are, what a good title length is, how to fix a missing H1, how many H1 tags to use, how a title tag differs from an H1, which HTTP status a page should return and why schema added by JavaScript does not show.
It requests your page's live initial HTML and reports the title tag, meta description, H1 headings, the HTTP status code, and any JSON-LD structured-data schema types it detects in that response.
A meta description is an HTML tag summarizing a page's content. Search engines may show it as the snippet under your title in results, so a clear, relevant one can improve click-through even though it is not a direct ranking factor.
There is no universal character limit because result titles are constrained by rendered width and may be rewritten. Use the measured count as a review cue, keep the identifying words early, and judge clarity in context.
Add a single, descriptive H1 heading that states the page's main topic. The checker lists detected H1s, so if none appear or several compete, you can consolidate to one clear heading.
The title tag is a strong on-page relevance signal and the clickable headline in results; the meta description shapes the snippet. Together they influence whether searchers understand and click your listing.
JSON-LD is a script format for embedding schema.org structured data in a page. It helps search engines understand entities like articles, products, or FAQs, and can enable rich results. The tool reports which schema types it detects.
It reads the initial HTML response only. If your title, description, or JSON-LD is injected after browser JavaScript runs, it may not appear here even though a full browser render would show it.
The title tag lives in the HTML head and appears in the browser tab and search results; the H1 is a visible on-page heading. They often align but serve different placements and audiences.
One clear main heading is a useful editorial convention, but HTML permits multiple H1 elements. The checker reports what the initial HTML contains; whether the hierarchy is clear still requires review.
A 200 OK confirms the page is live and its metadata applies. Redirect or error statuses like 301 or 404 mean crawlers may not see the content you expect, so investigate those first.