About the Meta Tag Checker
The Meta Tag Checker reads the tags that decide how one page is shown in a search result, in a link preview and on a phone. It fetches the page exactly once with our crawler, EchoRankBot, follows redirects that stay on the same site, and parses the result. Nothing is stored beyond the request: the fetched HTML is discarded as soon as the report is rendered.
Each tag gets a pass, warn or fail chip from the rules the full audit uses. The title is judged with S1 (30 to 60 characters), the meta description with S2 (70 to 160 characters), the H1 count with S3 (exactly one), the canonical with S6 (present and pointing at the page itself) and the Open Graph pair with S13 (og:title and og:image). Robots meta, viewport and Twitter card tags are read as well: a noindex is flagged because it removes the page from search results, a missing viewport because the page will render at desktop width on phones.
The snippet preview shows the title and description at the lengths a search result usually displays, so you can see where a long title would be cut. It is an approximation: search engines rewrite titles and pick other text from the page when they judge it a better fit. To use the report, fix the fails first, then the warns, then re-run the check. When the page is the homepage of a business, the free score continues where this tool stops: it runs the website, DNS, PageSpeed and search checks together and shows the evidence behind each.
Questions
Which page should I check?
Start with the homepage, then the pages you send people to from ads, listings and social posts. Every page has its own title, description and canonical, so check each one you care about.
Why does the title check say warn when the title looks fine?
The tool judges length only, 30 to 60 characters. The audit's S1 rule also asks whether the title names the brand or a service, which needs the business context the full audit has and this tool does not.
Does the tool store the page or my URL?
No. The page body is parsed in memory and discarded when the response is sent. Requests are rate-limited per network address to keep the tool available.
The page redirects to another domain. Why is there no report?
The crawler follows redirects only within the same site. If the page sends visitors to a different domain, check that domain instead; the report tells you where the redirect points.