Does the engine fix this itself?

Yes. The corrected artefact is generated and queued for your approval, then pushed and re-fetched to confirm it went live.

Check library · Experience and conversion

Page is not mobile friendly

highmobile_unfriendlyfix written automatically

Why it matters

Indexing is mobile-first, and most traffic is mobile.

What to do about it

Fix the viewport, tap targets and horizontal overflow.

The engine generates this fix itself using the add_viewport strategy. It arrives in your queue as a complete artefact, because an incomplete fix never reaches the queue, and once you approve it the change is pushed and the page re-fetched to confirm it is live.

How it is weighted

These are the values the scoring actually uses, not a description of them. Priority is derived from all three rather than chosen, which is why a high-impact, low-effort finding surfaces above a severe one that would take a quarter to fix.

Severity: high
Impact: 70% of the weight this category can carry
Effort: 50%, where 100% is a project rather than a change
Confidence: 80% that a hit is a real problem rather than a pattern we misread
Area: Experience and conversion

Other checks in Experience and conversion

highPage format does not match search intentintent_mismatchneeds a decision mediumNo clear call to actionno_clear_ctaneeds a decision lowNo Open Graph or Twitter cardno_social_previewfix written

Check your own site for this

The whole catalogue over a real crawl, in about four minutes, in your browser. No account and no card.

See what we would fix this week Back to the library