Website Meta Tags Checker

SEO Signals You’ll See After Entering a URL

Paste https://www.example.com/page into the field above. The report separates the Title, Meta Description, and Meta Keywords found in the server-rendered HTML, counts their characters, and generates a simplified search snippet preview. It also shows the HTTP status, redirect count, canonical URL, robots directives, first H1 and total H1 count, viewport settings, HTML language, character encoding, response time, Open Graph data, Twitter Card data, and hreflang annotations.

The “Passed,” “Review,” and “Fix” labels at the top provide a quick page-level assessment—not a search engine score. Use them for pre-launch checks, competitor page comparisons, and troubleshooting. Start with issues that could block crawling or indexing, then review metadata that affects search snippets and how search engines understand the page.

How to Run a Complete Check

Enter the exact page URL: You can enter a complete HTTP or HTTPS URL or just a domain, in which case the tool adds HTTPS automatically. To check an article or product page, paste its full path instead of checking only the homepage.
Click “Run Check”: The server requests the target page, follows up to five common HTTP redirects, and records the final URL, status code, and response time.
Review red issues first: Prioritize non-2xx HTTP responses, missing or invalid titles, page-level noindex directives, and similar problems.
Then review yellow recommendations: Assess title and description length, canonicals, H1 headings, and social sharing metadata in the context of the page’s purpose. Do not make changes solely to turn every item green.
Verify the extracted values: Each metadata card shows the exact value found. Copy it and compare it with your CMS, page source, or deployment configuration.

What TDK Means

Title comes from the HTML <title> element. It is one of the main sources search engines use to understand a page and generate its title link. Every indexable page should have an accurate, specific, and ideally unique title, although search engines may rewrite the displayed title based on the query and page content.

Description comes from <meta name="description"> and may be used as the search snippet. It should clearly summarize what the page offers or helps users accomplish, rather than repeat a list of keywords. Search engines may instead show a more relevant excerpt from the page content.

Keywords refers to the legacy Meta Keywords field. Google and other major search engines generally do not use it as a web ranking signal, so this tool does not treat a missing value as an error. It is mainly useful when auditing legacy sites, migrating metadata, or reviewing internal keyword lists that some sites still maintain.

The suggested ranges of 20–60 characters for titles and 50–160 characters for descriptions are common display guidelines—not ranking rules or guarantees of pixel-perfect truncation. Character width, device type, search queries, language, and search engine rewrites can all affect how a result appears in the SERP.

Check Indexing Signals Before Refining the Copy

Even a page with an excellent title may not be indexed if it returns a 404 or includes a noindex directive in its response headers or Meta Robots tag. Review the report in this order:

HTTP status and final URL: Confirm that the status is 2xx and that redirects lead to the intended page. Make sure you are not analyzing an old URL, login page, or error page.
Robots directives: The tool checks Meta Robots, Googlebot directives, and X-Robots-Tag headers together, including noindex and nofollow. If noindex was accidentally left enabled in production, fix it first.
Canonical URL: Confirm that the page declares one canonical URL and that it points to the version you want indexed. A missing canonical does not necessarily prevent indexing, but an incorrect cross-page canonical can consolidate signals with the wrong URL.
Title, description, and H1: These elements do not need to match word for word, but they should support the same page intent. Multiple H1 headings are not automatically invalid; what matters is a clear document hierarchy. The report therefore flags them for review rather than telling you to remove them automatically.

Pre-launch troubleshooting example

Suppose a new product page returns HTTP 200 and has a 68-character title, no description, a canonical pointing to a staging domain, one H1, and no noindex directive. The title length is not the most serious issue. The incorrect canonical could send consolidation signals to the staging site. First, update it to the production page URL. Then write a description aligned with the page’s search intent, and finally shorten the title by removing repeated brand and category terms.

Run the check again after deploying the changes. If the final URL, canonical, and page language are correct but the title remains slightly long, review actual search appearance and click data before removing useful information just to meet a fixed character count. As another example, a campaign page may intentionally use noindex. If the page is not meant to appear in search results, the red warning reflects the intended configuration and does not need to be “fixed.”

How to Review Multilingual and Social Sharing Metadata

The tool extracts the lang attribute from the root HTML element and lists up to 20 rel="alternate" hreflang="..." links. Use these values to confirm that the page references itself and its alternate language versions, uses the expected language and region codes, and links to the correct localized URLs. Because this check reads only the current document, it cannot verify return links from alternate pages or confirm that sitemap hreflang annotations match the HTML.

The Open Graph section shows values such as og:title, og:description, and og:image, while the Twitter section reads fields such as twitter:card. These fields control link previews on social platforms and are separate from Google’s title links and snippets. If the OG image is missing, shared links may not display a suitable thumbnail. Even when every field is present, use the relevant platform debugger to verify cached data and image accessibility.

What This Check Does Not Cover

JavaScript is not executed: The tool analyzes the static HTML returned directly by the server. Titles, descriptions, JSON-LD, or hreflang annotations injected only after JavaScript runs in the browser may not be detected.
Sitewide files are not checked: The tool does not crawl robots.txt, XML sitemaps, internal link graphs, pagination, duplicate content, or canonical relationships across every page.
Actual indexing is not verified: “Page-level signals allow indexing” only means that the current HTTP response and directives such as noindex show no obvious blockers. It does not mean that Google, Bing, or another search engine has indexed the page.
Structured data is not validated: The report does not currently validate JSON-LD, Microdata, or rich result eligibility. Use an official search engine testing tool for those checks.
Ranking potential is not evaluated: Backlinks, content quality, topical authority, Core Web Vitals, user intent alignment, and competition are outside the scope of this summary.
Crawling restrictions apply: The target must be a publicly accessible HTTP or HTTPS page. Localhost, private network, and private IP addresses are rejected. Checks may also fail if the response exceeds 2 MB, times out, is not HTML, or blocks this crawler.

Common Misconceptions

Assuming green checks guarantee rankings: Correct technical tags are only a starting point. They cannot replace useful content, strong internal linking, site authority, or genuine search demand.

Treating character ranges as strict limits: Title and description recommendations help identify obvious issues quickly. Final decisions should also consider pixel width, essential branding, query terms, and Search Console data.

Repeating keywords to increase keyword density: Titles, H1 headings, and descriptions should describe the current page naturally. Repeating synonyms can reduce readability and cannot fix a mismatch between the content and search intent.

Adding a keyword list because Meta Keywords is empty: Meta Keywords generally has no direct effect on rankings in major search engines. Spend that time improving the title, snippet, core content, and internal links instead.

Checking only the homepage: Search traffic often lands on articles, product pages, category pages, and individual tool pages. After changing a template, sample several page types rather than treating the homepage as representative of the entire site.

Frequently Asked Questions

Why can I see the title in my browser when the tool says it is missing?
The title may be injected client-side by JavaScript, or the site may serve different content to different User-Agents. Inspect the raw server response and confirm that essential SEO metadata is available in HTML that search engines can crawl.

Why are today’s results different from yesterday’s?
Site deployments, CDN caching, A/B tests, regional routing, and redirects can all change the response. This report is a snapshot of the current request, so interpret it alongside the check time and final URL.

Are multiple H1 headings always a problem?
No. HTML can contain headings for multiple sections, but the page’s primary hierarchy should remain clear. The warning is designed to help you spot duplicate template output—not to enforce exactly one H1 on every page.

Why can’t I find the page in search results when the report says “Indexing allowed”?
Indexing can also be affected by robots.txt, crawl discovery, sitemaps, canonical clusters, content quality, duplicate pages, and search engine processing status. Check Search Console or Bing Webmaster Tools for detailed indexing and coverage information.

Can I use this tool to audit an entire website?
The tool currently checks one public web page at a time, making it best suited to quick diagnostics and sample validation. For a sitewide audit, combine it with a crawler, server logs, sitemaps, and webmaster platform data.

Turn the Report Into an Action Plan

First, fix HTTP errors, redirect problems, noindex directives, and incorrect canonicals that could block access or indexing. Next, optimize the title, description, H1, and language annotations. Finally, review social previews and actual SERP performance. Google Search Central documentation on title links, snippets, robots meta tags, and multilingual sites can help you verify implementation rules, while actual indexing status should be confirmed in webmaster tools.

Start by checking a specific landing page that already receives organic search traffic and save its current values. After making and deploying changes, run the check again and compare the final URL, status code, and metadata to confirm that the updates are live.