Has Meta X Domain checks whether the document head declares the legacy twitter:domain meta tag, returning 1 when a matching tag is found and 0 when it is absent. It is a pure presence test — it does not confirm the value is correct, matches the analyzed host, or that X reads the property today.
| Factor ID | RG-SOC-015 |
|---|---|
| Family | Social signals |
| Measurement | Boolean presence (0 / 1) |
| Measured zone | Rendered, script-free document head |
What it measures
Has Meta X Domain indicates whether RankGear recognizes the legacy twitter:domain meta name and its accompanying content structure in the page head. It is a social-card lineage marker rather than a quality judgment — a page either carries this specific legacy tag or it does not.
How RankGear measures it
RankGear searches the lowercased head for name="twitter:domain" followed by a quoted content attribute. A tag that matches the pattern scores 1; anything else scores 0. The check is structural only: it does not validate that the content value matches the analyzed host, nor that X actually uses the property.
What RankGear looks for
<meta name="twitter:domain" content="example.com">| Value | Meaning |
|---|---|
| 1 | A twitter:domain meta tag with a quoted content attribute was found in the head. |
| 0 | No matching tag was found in the head. |
How to optimize it
Treat this as an observation, not a target to chase. Follow current card documentation for the platform: if the property is genuinely supported and useful, supply the correct canonical domain in the content attribute. Otherwise, rely on the metadata that current cards actually require rather than retaining or adding an obsolete field just to move this score. A page can be fully valid and modern while returning 0 here.
Important considerations
- Presence does not prove correctness or platform use — a matching tag can still hold a wrong or stale domain.
- Empty content can still trigger the detector, because the check is structural rather than value-aware.
- Attribute order matters to this pattern: the
contentattribute is expected to follow thenameattribute. - Do not treat legacy metadata as a universal requirement; this is a lineage marker, not a mandate.
- This factor correlates with, and never causes, ranking position — it is one prioritization signal measured within a result set, not a lever that makes a page rank.
Related factors
Part of the Factors reference · how RankGear measures · glossary.