LLMention
← All 40 checksDelivery & Mobile

Viewport meta tag is present

One of 40 checks the scanner runs. This one is worth 1 point inside the Delivery & Mobile dimension, which carries 2% of the total score.

Browse sections

What does this check look at?

A meta viewport tag is present.

This reads the declaration, not the value. A viewport tag with `content="width=10000"` passes exactly as `width=device-width, initial-scale=1` does, because deciding whether a viewport configuration is usable needs a rendering engine and this scanner deliberately does not run one.

How do I fix it?

  1. Add a viewport meta tag so the page renders on mobile.

Why is it worth 1 point?

Points are relative weights inside a dimension, and a dimension's weight decides how much of the total it can move. The reasoning for this dimension's weight is published rather than asserted:

DimensionDelivery & Mobile — 2% of the total score
Points for this check1 of 2 in this dimension
Worth at most1.0 of the 100 points

Lowest. The checks here are coarse on purpose; full Core Web Vitals need a real browser, which this scanner deliberately does not run.

Which dimension does this belong to?

Delivery & Mobile — 2% of the total score, decided by 2 published rules.

A slow or non-mobile-readable page is dropped before any content analysis happens.

None of the five guides covers this rule, which is why this page shows the fix in full rather than pointing at one.

What else is measured in this dimension?

How do I see my own result?

Run a scan on your own domain. The report lists every failed check with the evidence that produced it, so you can tell a real failure from a check that does not apply.

Run a free GEO audit on your own site →

The full method, including the dimensions that are deliberately weighted low and the parts of a picture a single-URL scan cannot see, is on the methodology page.

Questions about this rule

What does this check look at?

A meta viewport tag is present.

Why does this dimension carry 2% of the score?

The checks here are coarse on purpose; full Core Web Vitals need a real browser, which this scanner deliberately does not run.

Evidence and sources

GEO can boost visibility by up to 40% overall in generative engine responses, and in the paper's Table 1 the best of the tested methods improve on the no-optimization baseline by 41% and 28%. — Generative Engine Optimization, KDD 2024

This rule is applied by the scanner and published in the rule set it is read from, so the condition on this page is the condition the scan tests rather than a summary of it.

Primary sources