X Card Analyzer

X Card metadata helps control how a webpage is represented when its URL is shared on X. PKCapra’s X Card Analyzer lets you inspect the X/Twitter card metadata exposed by a public webpage, identify missing or duplicate card tags, review the detected sharing information, and check whether the page is providing the metadata needed for a more complete X preview.

What Is an X Card?

An X Card is metadata associated with a webpage that can provide information about that page when its URL is shared on X.

Instead of relying only on the ordinary HTML title or whatever text happens to be available on the page, social metadata gives a webpage additional information specifically intended for sharing.

Typical X Card properties include:

• twitter:card
• twitter:title
• twitter:description
• twitter:image
• twitter:image:alt
• twitter:site
• twitter:creator

You may notice that these properties still use the twitter: namespace even though the platform is now called X. That is important when troubleshooting: the name of the platform changed, but webpages can still contain these established metadata property names.

If you have ever opened a webpage and thought, “Why does the social preview look nothing like my actual page?”, checking the metadata is one of the first places to look.

Why X Card Metadata Deserves Its Own Check

One of the easiest mistakes in technical SEO is assuming that one piece of metadata does every job.

It doesn’t.

Your HTML title, meta description, canonical URL, Open Graph metadata, structured data, and X Card metadata all have different purposes.

A page can therefore pass one check and fail another.

For example, your normal HTML title might be excellent while the X Card title is missing. Your meta description might be beautifully written while the social description is absent. Your page may have a canonical URL but still contain an incorrect social image.

That is why a proper social-sharing audit should look at the page as a whole rather than treating one metadata field as a universal solution.

For the standard HTML title, you can use the Title Tag Analyzer.

For the standard meta description, the Meta Description Analyzer gives you a dedicated check.

And for a broader inspection of the page’s metadata, the Meta Tags Analyzer can help you see the bigger picture.

What Does the PKCapra X Card Analyzer Actually Check?

The tool is designed to answer a simple question:

What X Card information is this webpage actually exposing in its public HTML?

It checks the core properties first and then looks for useful supporting metadata.

twitter:card

This identifies the type of X Card being requested.

If this property is missing, the page is not explicitly providing the card type through this metadata.

twitter:title

This is the title associated with the social card.

It does not have to be identical to your normal SEO title. In many cases, a social title can be written with the social-sharing context in mind.

twitter:description

This provides a description associated with the shared page.

A good description should quickly explain what the visitor will find after opening the URL.

twitter:image

This identifies the image associated with the card.

For content-heavy websites, this is particularly important because an appropriate image can give the shared URL immediate visual context.

twitter:image:alt

This provides alternative text associated with the social image.

It is useful to check whether this field is present rather than assuming the image itself is enough.

twitter:site

This can identify the website or publisher account associated with the content.

twitter:creator

This can identify the creator associated with the content.

Advanced Player and App Metadata

The analyzer can also detect additional properties associated with player content and supported applications.

These include information such as:

• player URL
• player width
• player height
• player stream
• iPhone application metadata
• iPad application metadata
• Google Play application metadata

These fields are not mandatory for every webpage. They become relevant when your content actually uses these types of experiences.

The Most Important Part: Missing Metadata

A long list of detected tags is not particularly useful if you still don’t know what is wrong.

That is why PKCapra separates the important core fields from optional metadata.

If your page is missing one of the core X Card properties, you can immediately see that something deserves attention.

This is much more useful than simply dumping the source code on the screen and expecting you to figure it out yourself.

Missing twitter:title? Don’t Guess

If the analyzer reports that the X Card title is missing, first check how your website generates social metadata.

Don’t immediately assume that your HTML <title> is broken.

These are different things.

Use the Title Tag Analyzer to inspect the ordinary HTML title separately.

If the HTML title is present but the X Card title is missing, the problem is likely in your social metadata configuration rather than the page title itself.

Missing twitter:description?

The same principle applies to descriptions.

Your page can have a perfectly good standard meta description and still be missing a dedicated X Card description.

Use the Meta Description Analyzer to check the standard meta description separately.

Then compare the result with the X Card Analyzer.

That simple comparison can tell you whether you’re dealing with a general metadata problem or a social-specific configuration problem.

Missing twitter:image?

This is one of the issues worth investigating carefully.

First check whether your social image has actually been configured.

Then check whether the image URL is being exposed in the HTML.

Also make sure you’re not confusing the image shown inside the webpage with the image defined for social sharing.

A beautiful featured image on the page does not automatically prove that the correct social image metadata is present.

X Card vs Open Graph: Are They the Same Thing?

No.

They are related because both deal with how webpages can be represented when shared, but they are separate metadata systems.

Open Graph defines properties such as og:title, og:type, og:image, and og:url. The official Open Graph specification identifies those four as the basic required properties for an Open Graph object.

X Card metadata uses the twitter: namespace.

That means checking one does not automatically prove that the other is correctly implemented.

For a dedicated Open Graph inspection, use the Open Graph Analyzer.

Running both checks is particularly useful when you’re diagnosing inconsistent social previews.

Why Duplicate X Card Tags Matter

Here’s a problem that is easy to miss:

Your page can contain the correct metadata and still contain it more than once.

This often happens when several systems are responsible for SEO or social metadata.

For example, an SEO plugin might generate one twitter:title, while another social-sharing plugin generates a second one.

Now you have two competing declarations.

That doesn’t automatically mean the page will fail, but it creates unnecessary ambiguity and makes debugging harder.

The X Card Analyzer therefore checks for duplicate properties instead of simply saying “tag found.”

For a broader look at duplicate or unusual metadata, the Meta Tags Analyzer is useful as a second layer of inspection.

X Card Metadata and Your Canonical URL

Here’s another connection that is frequently overlooked.

Social metadata tells platforms what your page is about.

Your canonical URL tells search engines which URL represents the preferred version of that content.

Those signals don’t replace each other.

If your website has multiple URL variations, parameters, redirects, or duplicate versions of a page, check the canonical configuration as part of the same investigation.

The Canonical URL Checker can help you inspect that signal independently.

This is especially useful when you discover that one URL has the expected metadata but another version of the same content behaves differently.

Check the HTTP Response Before Blaming the Metadata

Sometimes the metadata isn’t the real problem.

Imagine that your URL returns a redirect, an access restriction, an error page, or an unexpected response.

A crawler cannot inspect the webpage you intended if it never receives that webpage.

That’s why HTTP status is worth checking when troubleshooting.

The HTTP Status Checker lets you inspect the HTTP response returned by a URL.

A normal 200 OK response tells you something very different from a 301, 302, 403, or 404.

Redirects Can Change the Page You’re Actually Analyzing

A URL can look correct in your browser while quietly redirecting somewhere else.

For example:

Old URL → redirect → new URL

If you’re troubleshooting social metadata on the old URL, you need to know where that request actually ends up.

The Redirect Checker helps you inspect the redirect path and identify unexpected redirect chains.

This is especially valuable after:

• website migrations
• domain changes
• URL restructuring
• HTTPS migrations
• WordPress permalink changes
• content consolidation

Don’t Confuse Social Metadata With Page Speed

A webpage can have excellent social metadata and still be technically slow.

It can also be extremely fast while having incomplete social metadata.

These are different parts of the technical picture.

Once you’ve finished checking the metadata, you can use the Page Speed Analyzer for a separate server-side technical snapshot covering response time, HTML size, resources, images, CSS, JavaScript, viewport information, HTTPS, and related signals.

Think of these tools as pieces of the same diagnostic process rather than competing tests.

What Does the X Card Health Score Mean?

The PKCapra score is deliberately a diagnostic score.

It looks at the presence of important X Card properties, missing core fields, useful supporting information, and duplicate metadata.

A high score means the detected implementation is relatively complete.

A lower score tells you that something deserves investigation.

But there is an important distinction:

The score is not a ranking score.

It does not predict your Google position.

It does not predict engagement on X.

It does not guarantee that a specific social preview will appear exactly as expected.

It simply gives you a practical way to assess the metadata that PKCapra found in the public HTML response.

A Better Way to Troubleshoot X Card Problems

Instead of randomly changing SEO settings, use a sequence.

Start with the webpage itself.

Then check:

1. Does the URL return the expected HTTP response?
2. Does it redirect somewhere else?
3. Does the final page have the correct canonical URL?
4. Does the HTML contain the expected title?
5. Does it contain the expected meta description?
6. Does it contain the required X Card metadata?
7. Does it contain duplicate social properties?
8. Does it have an appropriate social image?
9. Does Open Graph metadata also look correct?
10. Is the page technically healthy from a performance perspective?

This approach is much faster than changing five plugins at once and hoping the problem disappears.

Common X Card Problems

Your Page Has a Title but X Card Title Is Missing

The HTML title and X Card title are separate signals.

Check both independently.

Your Meta Description Exists but Social Description Is Missing

Again, these are different fields.

A standard meta description does not automatically prove that your X Card description is present.

Your Image Is on the Page but the Social Image Is Missing

The visible featured image and the image specified through social metadata are not necessarily the same thing.

Check the actual metadata.

The Same X Card Tag Appears Multiple Times

Look for multiple SEO or social plugins generating the same property.

The URL Redirects

Check the redirect chain and analyze the final destination.

The Page Returns an Error

Resolve the HTTP response problem before spending time troubleshooting social metadata.

The Score Is High but the Preview Still Looks Different

Remember that PKCapra is analyzing the public HTML response. Social platforms may cache content and apply their own processing and display behavior.

How to Use the X Card Analyzer

Using the tool is straightforward.

1. Enter a Public URL

Paste the complete URL of the webpage you want to inspect.

2. Start the Analysis

PKCapra retrieves the publicly accessible HTML and examines the supported X Card metadata.

3. Review the Core Fields

Look first at the card type, title, description, and image.

These are the fields most likely to matter for a basic implementation.

4. Look for Missing or Duplicate Properties

Don’t just look at the score.

Read the individual results.

A score tells you that something may be wrong. The individual fields tell you what to investigate.

5. Fix the Source

Make the necessary changes in your website, theme, SEO plugin, or social metadata configuration.

6. Test Again

Run the URL through the analyzer after the changes.

The goal isn’t simply to get a higher number.

The goal is to make the underlying HTML cleaner and more intentional.

Privacy and Processing

PKCapra’s X Card Analyzer works with publicly accessible webpages.

It does not require access to your WordPress dashboard, hosting account, or private website administration.

Do not submit private, authenticated, confidential, or sensitive URLs.

The analysis is based on the public HTML response retrieved by the tool.

That distinction matters because the tool is inspecting what a public request can receive — not what you may see after logging into your website’s administration area.

Is the X Card Analyzer a Ranking Tool?

No.

It is a technical inspection tool.

There is no legitimate analyzer that can look at a few social metadata fields and promise a Google ranking.

Good metadata can help machines understand and represent your content more clearly, but search visibility depends on a much larger collection of factors.

Use the X Card Analyzer to find and fix metadata problems — not to manufacture a fake “ranking score.”

Frequently Asked Questions

What is an X Card Analyzer?

An X Card Analyzer checks a webpage’s public HTML for X Card metadata and identifies important fields, missing properties, duplicates, and related information.

What are the most important X Card tags?

The core properties checked by PKCapra are twitter:card, twitter:title, twitter:description, and twitter:image.

Why do X Card tags still use twitter:?

The established metadata properties use the twitter: namespace. The platform’s name changed to X, but the metadata property names found in webpages can still use that namespace.

Is X Card metadata the same as Open Graph?

No. They are separate metadata systems. A webpage can have one implemented correctly while the other is incomplete.

Should I use both an X Card Analyzer and an Open Graph Analyzer?

For a complete social metadata review, yes. They inspect different metadata systems.

Can I analyze a private webpage?

No. The analyzer is designed for publicly accessible URLs.

Does PKCapra store the webpage I analyze?

The tool performs a server-side inspection of the public HTML needed for analysis. You should not submit private or sensitive URLs.

Does a perfect score guarantee my X preview?

No. The score reflects the metadata detected by PKCapra. Social platforms can cache webpages and apply their own processing and display rules.

Why does my webpage have a good SEO title but a missing X Card title?

Because the HTML title and X Card title are different metadata properties. Your SEO configuration can provide one without properly generating the other.

Why should I check redirects?

Because the URL you enter may not be the page that ultimately serves the content. A redirect can change which page a crawler receives.

Should I check my canonical URL too?

Yes, particularly if your website has duplicate URLs, URL parameters, migrations, or redirects. The canonical signal helps identify the preferred version of a page.

Final Word

The easiest way to think about X Card metadata is this:

Your webpage is built for people. Your metadata is also telling machines how to understand and represent that webpage.

When those two layers agree, everything becomes easier to maintain.

When they don’t, you can end up with a perfectly attractive webpage whose shared link has the wrong title, no image, an outdated description, or duplicate metadata.

The PKCapra X Card Analyzer gives you a direct way to see what your public HTML is actually saying.

Don’t guess.

Don’t rely only on what the page looks like in your browser.

Check the metadata, identify the problem, fix the source, and test it again.

And when you’re doing a deeper technical review, connect the dots: check your Open Graph metadata, HTML title, meta description, canonical URL, HTTP status, redirects, and page performance rather than treating any single SEO signal as the whole story.

That is how a simple social metadata check becomes a genuinely useful technical SEO workflow.