Has Meta Viewport is a boolean signal (0 or 1) meant to flag whether a page declares a viewport meta tag in its head. In the current compatibility build it does not measure viewport metadata at all: it returns 1 whenever the head contains any element with a double-quoted id attribute, so treat the score as non-actionable.
| Factor ID | RG-MET-007 |
|---|---|
| Family | Meta tags |
| Measurement | Boolean presence (0 / 1) |
| Measured zone | Rendered, script-free document head |
What it measures
The factor is intended to detect a viewport meta tag — the declaration that tells mobile browsers how to size and scale a page. In its current compatibility implementation, though, it instead returns 1 when the head contains any recognized element carrying a double-quoted id="..." attribute. The name states the goal; the behavior below is what the score actually reflects today.
How RankGear measures it
RankGear scans the rendered, script-free document head for an element with a double-quoted ID attribute. It does not look for name="viewport", and it does not inspect the viewport content string. If a matching ID attribute is present anywhere in the head the factor is 1; if none is found it is 0.
What RankGear looks for
<!-- Matched: any head element with a double-quoted id -->
<meta id="x" ...> scores 1
<!-- Not evaluated (the intended target) -->
<meta name="viewport" content="width=device-width, initial-scale=1">| Value | Meaning |
|---|---|
| 1 | The head contains at least one element with a double-quoted id attribute. This does not confirm a viewport tag is present. |
| 0 | No double-quoted id attribute was found in the head. This does not prove the viewport tag is absent. |
How to optimize it
Treat this as an observation, not a target. Do not add or alter id attributes to influence the score — that games a compatibility artifact without improving the page. Independently, ensure every responsive page carries a correct viewport declaration (commonly width=device-width, initial-scale=1) and test mobile rendering and zoom accessibility on real devices. Consider the factor non-actionable until its compatibility behavior changes to actually parse the viewport tag.
Important considerations
- The current score does not measure viewport metadata — it keys off a double-quoted ID attribute in the head.
- A 0 does not prove the viewport tag is absent.
- A stray or random head ID can produce a score of 1.
- Treat the factor as non-actionable until the compatibility behavior changes.
- Correlation is not causation: like every RankGear factor, this is a prioritization signal measured within a result set. It relates to position; it does not make a page rank or guarantee any placement.
Related factors
Part of the Factors reference · how RankGear measures · glossary.