About this meta tags checker
Meta tags are the hidden lines in a page that search engines and social networks read. The title and meta description often become the headline and snippet in search results, the canonical link tells Google which address is the main one, the robots tag controls indexing, the viewport tag makes a page work on phones, and the Open Graph and Twitter tags decide how a shared link looks in a chat or a feed.
This checker fetches the page from our server, parses the HTML and extracts those tags, then adds short checks: a title between 30 and 60 characters and a description between 70 and 160 usually display well, and missing items are flagged. It also reads the H1, language, charset, theme colour, favicon and hreflang links used for translated versions of a page.
Only the HTML sent by the server is read, so tags that a script adds in the browser are not seen. That is also what many crawlers see first. The address you enter is sent to our API at /api/meta-tags-checker.php; private addresses are refused, redirects are checked at each step, and the app stores no history of searches.
Which controls should I check first?
The Meta Tags Checker form labels its controls as Page address. Use those labels to keep the source and settings separate. A sample argument that selects a mode is not additional source text. Choose the setting matching your intended operation before copying a result, and change it explicitly when comparing another mode. The labels describe what this form accepts; the worked examples below demonstrate only the stated supplied values.
How should I interpret this specific operation?
The checker reads metadata from the response available to its server request. Client-side JavaScript can later change a browser document, so that server view can differ from a rendered inspection. Distinguish an absent tag from a blank tag value. A title or description in the response is not proof of what a search service has indexed or will display. Compare the queried route with the actual intended page before replacing metadata based on this observation.
Worked helper values
These values come from the reproducible calculation examples supplied with this tool. Each row identifies the complete supplied arguments and the returned value. A visible ↵ denotes a line break and ⇥ denotes a tab in text examples. Settings appear alongside source data so that a different mode is not mistaken for an identical input. These are helper calculations, not observations of a live device, fetched target, image decoder, browser preview or downloaded file. Use the stated method above to relate the returned fields to the actual operation.
| Supplied values | Calculated return value |
|---|---|
| meta-tags-checker; a b.com | /api/meta-tags-checker.php?q=a%20b.com |
| example.com ; x | example.com |
Whose network view does this result represent?
A server-side check observes the target from the checking service's network location. Your browser, a mobile connection and another resolver can see different answers because of caching, geolocation, routing, filtering or load balancing. Keep the exact queried target and the time of your check when comparing observations. A timeout means this attempt did not obtain a result within its limit; it does not prove the target is unavailable everywhere. To investigate a discrepancy, compare the same target and protocol from the relevant client environment as a separate step.
How should I prepare a target?
Use a public target whose spelling and scope you can explain. A hostname, an IP address and a complete URL carry different information. A URL includes a scheme, path and possibly a query string, while a hostname identifies a host without those request details. Follow this page's stated input convention and omit credentials or confidential query values from demonstration targets. Correct an invalid-target message before retrying. The address is sent to the checking service for processing, so this workflow is different from a local parser that merely splits the supplied text into components.
What can I infer from missing fields?
A missing field can reflect the target, the available response or the check's scope. It should not be replaced with a guessed value. Read any status or explanation beside the output and distinguish an empty answer from an error. Compare the same type of evidence across repeated checks rather than treating every field as an independent verdict. A registration record, resolver result and HTTP response describe different layers and can disagree without any of them being fabricated. Follow a discrepancy to the layer it concerns before changing DNS, application settings or certificate configuration.
How can I document a reproducible observation?
Record the exact input, result fields that matter, and any timeout or error text. If the target is a URL, preserve the path and protocol because checking the homepage can differ from checking a specific resource. When a value appears to change, repeat a narrowly scoped check and compare the complete response, including intermediate context if the tool exposes it. Avoid attributing a difference to a named provider or person based only on one field. These outputs are observations from a limited check, not a record of ownership or an exhaustive audit of every configuration on the target.
What is the best length for a title and a description?
About 30 to 60 characters for the title and 70 to 160 for the description. These are guides, since search engines cut by pixel width.
Why are tags missing that I can see in the browser?
They may be added by JavaScript after the page loads. This tool reads the raw HTML like a simple crawler.
What are Open Graph tags?
Tags such as og:title and og:image that tell Facebook, LinkedIn, Slack and other apps how to show a preview of the link.
Can it check pages that block bots?
Not always. Some sites refuse requests from data centers, and then the tool reports the answer it got.