No twitter:site handle

The twitter:site meta tag specifies the X (Twitter) username of the website or brand. This links your web pages to your official X account when content is shared on the platform.

This issue checks whether your page has the twitter:site tag implemented. A passing implementation must include:

• twitter:site - The X handle of your website or brand (with or without @ symbol)

Example of passing implementation:

<meta name="twitter:site" content="@examplecompany" />

Or:

<meta name="twitter:site" content="examplecompany" />

The twitter:site tag is valuable for brand connection and social media integration:

• Brand linking: Connects shared content to your official X account
• Account attribution: X may display your account name alongside shared content
• Follow promotion: Makes it easier for users to find and follow your account
• Brand consistency: Maintains consistent branding across platforms
• Analytics: Helps track social sharing performance

Without the twitter:site tag:

• No connection between shared content and your X account
• Missed opportunity to promote your X presence
• Reduced brand visibility on X

Resolving this issue improves brand integration with X and contributes to a higher overall SEO health score by strengthening social media signals.

1. Add the twitter:site tag to your HTML <head> section:

   • Use your official X handle (e.g., "@examplecompany" or "examplecompany")
   • Include the @ symbol for clarity (optional but recommended)
   • Ensure the handle matches your actual X account

2. Verify your X account:

   • Double-check that the handle is correct and active
   • The account should represent your website or brand

3. Use consistently:

   • Add this tag to all pages across your website
   • Keep the same handle value site-wide

4. Test your implementation:

   • Use X Card Validator to verify the site handle is detected
   • Tweet your URL and check if your account is linked

Example 1: Missing Twitter Site Handle

Problematic state (what fails):

<meta name="twitter:card" content="summary_large_image" />
<!-- Missing twitter:site tag -->

Corrected state (what passes):

<meta name="twitter:card" content="summary_large_image" />
<meta name="twitter:site" content="@examplecompany" />

Example 2: Incorrect Twitter Handle

Problematic state (what fails):

<meta name="twitter:site" content="@nonexistent" />
<!-- Handle doesn't match actual account -->

Corrected state (what passes):

<meta name="twitter:site" content="@examplecompany" />
<!-- Handle matches actual X account -->

Example 3: Inconsistent Site Handle

Problematic state (what fails):

<!-- Page 1 -->
<meta name="twitter:site" content="@exampleco" />

<!-- Page 2 -->
<meta name="twitter:site" content="@example_company" />
<!-- Inconsistent handles across pages -->

Corrected state (what passes):

<!-- All pages use consistent handle -->
<meta name="twitter:site" content="@examplecompany" />

PixyScan checks for the twitter:site tag by:

1. Fetching the page HTML after following all redirects
2. Parsing the <head> section to extract the meta tag with name="twitter:site"
3. Validating presence: Checks that the twitter:site tag exists
4. Validating content: Ensures the tag has a non-empty value
5. Flagging the issue if the tag is missing or empty

The detection is performed on the raw HTML response without JavaScript execution, matching how X's crawler sees your pages.

Storage Level

Page Level

Database Table / Prisma Model

SocialOpenGraphData

Stored Fields

Detection Dependencies

• HTML Document
• Meta Tags (twitter:site)