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

No Open Graph or Twitter card

lowno_social_previewfix written automatically

Why it matters

Shared links render as a bare URL, which nobody clicks.

What to do about it

Add og:title, og:description, og:image and a summary_large_image card.

The engine generates this fix itself using the generate_og 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: low
Impact: 25% of the weight this category can carry
Effort: 10%, 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 highPage is not mobile friendlymobile_unfriendlyfix written mediumNo clear call to actionno_clear_ctaneeds a decision

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