How can Twitter card metadata identify a creator and site account?

Definition: Twitter card account metadata associates a page with a site account and, when relevant, a content creator. The twitter:site:id and twitter:creator:id tags carry account identifiers, while twitter:creator carries the creator's @username in the documented Next.js output.

Key facts

• Next.js maps twitter.siteId to twitter:site:id in the generated HTML and shows 1467726470533754880 as its example value in the metadata API reference.
• Next.js maps twitter.creator to twitter:creator and twitter.creatorId to twitter:creator:id; its example uses @nextjs and 1467726470533754880 in the same reference.
• X's developer blog describes twitter:site as the publication account and twitter:creator as the account for the writer, artist, seller, contributor or media user.
• X's User Lookup documentation distinguishes lookup by unique user ID from lookup by @handle.
• The tags use the name and content attributes of HTML meta elements in Next.js's documented output.

What do the three tags identify?

twitter:site:id is the site-account field in this scope. twitter:creator is the public @username associated with the content creator, and twitter:creator:id is the creator-account identifier. Next.js exposes these as siteId, creator and creatorId under its twitter metadata object.

X's developer blog describes the pairing as two usernames: the main account for the publication and another for the person or other contributor associated with the media. The wording supports using a site account for the website and a creator account for the page's author or contributor.

X's current user documentation gives the corresponding account lookup distinction. It says that users can be looked up by a unique user ID or by an @handle, and its example response contains separate id and username fields. An ID field and a username field therefore represent two different ways to identify the same X user in the API documentation.

How does Next.js emit the metadata?

The Next.js reference describes the Twitter object as part of the metadata export. Its example is:

export const metadata = {
  twitter: {
    siteId: '1467726470533754880',
    creator: '@nextjs',
    creatorId: '1467726470533754880',
  },
}

The same reference shows this HTML output for the account fields:

<meta name="twitter:site:id" content="1467726470533754880" />
<meta name="twitter:creator" content="@nextjs" />
<meta name="twitter:creator:id" content="1467726470533754880" />

The HTML uses name for the Twitter field name and content for its value. The example also shows that these fields sit alongside the card, title, description and image metadata in the page head.

Which value should a website maintain?

Use siteId for the X account representing the publication or website, creator for the creator's @username, and creatorId for that creator's account identifier. If the site account and the creator are the same account, the documented fields can contain the same account values, as Next.js's example does for the two displayed IDs.

X's User Lookup page provides endpoints for both forms: /2/users/:id retrieves a user by ID, while /2/users/by/username/:username retrieves a user by username. That gives a direct way to check that the handle and identifier refer to the intended account before the metadata is rendered.

Related terms

• Which HTML metadata declares a Twitter card with a large image?
• Which Twitter card tag supplies image alternative text?
• Which metadata fields describe app links in a Twitter app card?
• How does og:site_name differ from og:title?

FAQ

Is twitter:creator the website account?

It identifies the content creator's @username. X's developer guidance assigns the publication account to twitter:site and the other account to twitter:creator.

What is the purpose of twitter:creator:id?

It carries the creator account identifier in the Next.js metadata mapping. X documents user lookup by unique ID and by @handle, so the identifier is the ID form of the creator account reference.

Can the site account use an ID without a username?

Next.js documents siteId and emits twitter:site:id in its example. The reference does not show a site property in that example, so the documented output supports the ID field without requiring a site username in the shown object.

Sources

1. Next.js, "generateMetadata", 19 August 2026
2. X, "User Lookup", 25 July 2026
3. Twitter Developer Platform Blog, "Tips and Tricks for better Twitter Cards", 4 November 2012

---

Check how a page reads to answer engines. Open the GEO score analyzer