November 9, 20269 min read

Meta Tags Checker: Title, Description, Robots & Social

Check titles, meta descriptions, robots directives, canonicals, Open Graph, and Twitter Cards with this practical pre-publish workflow.

A meta tags checker should do more than confirm that a title and description exist. A page can contain both tags and still send weak or conflicting signals because the title is generic, the description describes a different offer, the robots directive blocks indexing, or the social preview uses stale copy.

The useful question is not “Does this page have metadata?” It is “Does every important metadata signal describe the same page, support the same intent, and allow the page to appear where we expect?”

Use this checklist before publishing a new page, after changing a template, during a migration, or whenever a search or social preview looks wrong.

Start with the rendered page

Check the URL that users and crawlers can actually open. CMS fields and template settings are useful, but they are not proof of the final HTML. A plugin may override a title, a staging directive may survive deployment, or client-side rendering may produce a different result from the editor preview.

Record the final URL and the page’s primary purpose before reviewing individual tags. Without that context, it is easy to approve metadata that is technically present but strategically wrong.

Title tag checklist

The title tag should identify the page clearly and distinguish it from neighboring pages. It does not need to contain every keyword variation, product feature, or audience segment.

  • Confirm that exactly one effective title is rendered.
  • Put the page’s main topic or task near the beginning when natural.
  • Make sure the title is specific enough to be unique within the site.
  • Check that the brand is included only when it adds useful context.
  • Remove repeated words and near-identical keyword variants.
  • Compare the title with the visible H1 and page content.
  • Review how the title reads in a SERP-style preview rather than relying only on character count.

Pixel width, device, query, and Google’s rewriting decisions all affect the displayed title. Treat length rules as review hints, not guarantees.

Meta description checklist

A meta description is a concise promise about what the visitor will find. Search engines may choose another passage, but a clear description still improves the page’s default preview, editorial quality, and handoff documentation.

  • Describe the page users will actually see.
  • Include the main task, benefit, or answer in plain language.
  • Avoid lists of disconnected keywords.
  • Do not reuse the same description across many important pages.
  • Make sure the copy does not promise data or functionality the page lacks.
  • Check that the description complements the title instead of repeating it word for word.
  • End with a useful reason to visit when the page has a commercial or action-oriented purpose.

If a description is missing, do not automatically write a generic sentence. First decide what makes this page different from other pages competing for the same user need.

Robots meta and X-Robots-Tag

Metadata review must include indexability. A perfect title cannot compensate for an accidental noindex directive.

Review both the HTML robots meta tag and any X-Robots-Tag response header. The effective directive may come from either location.

  • Check for noindex, nofollow, nosnippet, noarchive, or restrictive preview directives.
  • Look for Googlebot-specific directives that differ from the general robots rule.
  • Confirm that staging and preview rules were removed from production.
  • Treat robots.txt separately: it controls crawling, while noindex is an indexing directive.
  • Escalate conflicting directives instead of assuming the most convenient interpretation.

Canonical and language signals

The canonical link is not a meta tag, but it belongs in the same page-signal review because it tells search systems which URL should represent the content.

  • Confirm that the canonical is present when the site strategy expects one.
  • Verify that it points to the preferred, indexable URL.
  • Remove tracking parameters, preview paths, and staging hosts from the canonical target.
  • Check that canonical and robots directives do not contradict each other.
  • If the page uses hreflang, confirm that localized URLs and canonical targets align.

A page that declares another URL as canonical may be working as intended, but that decision should never be accidental.

Open Graph and Twitter Card checklist

Social metadata controls the default presentation when a page is shared in messaging tools and social platforms. It also exposes content drift quickly: old titles, descriptions, and images often survive here after the visible page changes.

  • Check og:title, og:description, og:url, og:type, and og:image.
  • Confirm that Twitter Card metadata provides a usable fallback.
  • Open the image URL directly and verify that it is publicly accessible.
  • Make sure the image represents the current page, not an old campaign or generic placeholder.
  • Check that the social URL agrees with the preferred canonical URL.
  • Compare social copy with the current title, description, and visible H1.

Look for conflicts, not only missing tags

The highest-risk metadata problems are often contradictions:

  • the title targets one topic while the H1 targets another;
  • the canonical points to a different page;
  • robots meta allows indexing but an HTTP header says noindex;
  • og:url contains a tracking URL;
  • the description promises a feature that is not visible;
  • schema names a different product, article, or organization.

A good audit groups these signals around the page’s intended identity. Reviewing every value in isolation can miss the larger problem.

Practical meta tags review order

  1. Confirm the final URL and page purpose.
  2. Review title, H1, and visible introduction together.
  3. Check the meta description against the actual page promise.
  4. Verify robots meta and X-Robots-Tag directives.
  5. Check the canonical target and URL consistency.
  6. Review Open Graph and Twitter Card values.
  7. Inspect social images and important page images.
  8. Compare metadata with structured data and visible content.
  9. Record the issue, evidence, priority, and owner.

How Crowra supports the workflow

Crowra reviews the active page’s title, meta description, headings, canonical, robots directives, Open Graph, Twitter Card, SERP-style preview, social preview, images, and related schema signals in one Chrome side panel.

Use the page overlay when a finding depends on visible content, then move the issue into the Fix Plan or export it for the person who owns the template. Crowra can surface the live-page evidence, but the final title and description still require human judgment about audience, accuracy, and intent.