[marceloprerender]

Summary

Fixes the long-standing customer-visible bug where the SEO score modal in the Prerender dashboard reports OG meta tags as missing when they are present in the cached HTML.

The current scorer only checks meta[property=\"og:...\"], but real-world pages use two other patterns it doesn't handle:

• mixed-case attribute values — e.g. <meta property=\"OG:Title\" ...>. CSS attribute selectors are case-sensitive on values by default.
• name attribute instead of property — used by some CMSes and SEO plugins, e.g. <meta name=\"og:title\" ...>.

This PR makes detection robust to both patterns by using CSS Level 4 case-insensitive value matching ([attr=\"value\" i], supported by cheerio) and adding a name attribute fallback.

Empirical reproducer

A real customer page (lululemon KSA) declares all 5 OG tags with name= instead of property=:

<meta name=\"og:title\" content=\"...\">
<meta name=\"og:type\" content=\"website\">
<meta name=\"og:image\" content=\"...\">
<meta name=\"og:url\" content=\"...\">
<meta name=\"og:description\" content=\"...\">

Version	Score	OG-tag false positives
1.5.1 (current production)	-15	All 5 reported missing
1.5.2 (this PR)	2	None

Changes

• `src/checks/og-tags.check.ts` — extracted `findOgContent($, tag)` helper that tries `meta[property="og:..." i]` first, falls back to `meta[name="og:..." i]`.
• `src/checks/og-tags.test.ts` — 4 new regression tests covering mixed-case values, `name`-attribute, mixed scenarios, and empty `content`.
• `package.json` — bumped to 1.5.2.

Test plan

• All 45 existing tests pass.
• 4 new tests added and pass.
• Verified against the real customer HTML — no false-positive OG recommendations.
• Once published, bump `prerender-seo-scorer` to ^1.5.2 in monostack `services/dashboard-api/package.json` (and optionally `prerender-custom/package.json`) — this is what makes the fix reach customers' modal.

Related

• Linear: PRE-2238
• Linear: PRE-2716 — broader scoring-architecture cleanup
• The monorepo's `@prerender/seo-scorer` package received a similar (but type-only) refactor in monostack PR #3122. That fix did not reach this package, and the customer-visible modal at `dashboard-api/v2/score` calls this package — so this PR is what actually closes PRE-2238 for customers.