🔎 SEO & Meta Review

Analyzed 19 of 92 built HTML pages (mode: changed-only).

📊 Score summary

No previous audit found — trend will appear next run.

SEO Review — Datum Handbook (19 pages)

Overall verdict: The site is in good shape structurally — all 19 pages have canonical tags, index, follow, a single H1, no missing og:image, and valid JSON-LD. Four pages have minor but fixable issues: two og:description mismatches (short/generic fallbacks), two description-length edge cases, and one title just at the boundary. No critical blockers.

Worst issues: 3 critical (og:description mismatches / short descriptions), 1 borderline improvement.

2. Critical Issues

og:description does not match meta description (short/generic fallback) — 3 pages

/handbook/pay-perks/stock-options, /handbook/teams/biz-dev, /handbook/teams/finance all have a full meta description but a short, generic og:description (e.g. "Everything you need to know about Datum's stock option program." / "How the Biz Dev team works…" / "How the Finance team works…").

• 💡 Template fix: In src/layouts/Handbook.astro (or wherever <meta property="og:description"> is set), default ogDescription to the page's description frontmatter value when no explicit override is provided, rather than accepting a short fallback.

og:description does not match meta description — 1 additional page

/handbook/teams/leadership — same pattern; og:description is "Who leads Datum and what each leader is accountable for." vs. the fuller meta description.

• 💡 Template fix: Same as above — unify via layout default.

3. Improvements

Meta description at or near lower boundary (≤130 chars) — 2 pages

/handbook/about/model (130 chars) and /handbook/eos/quarterly-rocks (128 chars) are at the lower bound. Descriptions below ~130 chars leave ranking signal on the table.

• 💡 Fix: Expand both to 140–155 chars by adding a concrete keyword or benefit phrase (e.g. for model: append "…aligned incentives that scale with your network usage.").

JSON-LD schema type is Organization + WebSite on every page — 19 pages

All handbook and legal pages emit only Organization + WebSite JSON-LD. Article/handbook pages would benefit from Article or TechArticle schema with datePublished, author, and breadcrumb.

• 💡 Template fix: In src/layouts/Handbook.astro, add a conditional Article or TechArticle block using the page's frontmatter (title, description, publishDate). For /legal/terms, a WebPage type with dateModified would be more semantically accurate.

og:title diverges significantly from <title> — 4 pages

Short og:title values like "On-call", "Status updates", "Using GitHub", "Quarterly Rocks" strip important brand/keyword context for social shares.

• 💡 Template fix: In the Handbook layout, default og:title to the full page <title> when no short override is intentionally set — or ensure the short forms include at least "— Datum".

4. Per-page notes

• /handbook/pay-perks/stock-options — og:description is "Everything you need to know about Datum's stock option program." (62 chars), far shorter and less informative than the meta description (129 chars).

  • 💡 Fix: Remove the explicit ogDescription frontmatter override and let the layout fall back to the meta description: "How Datum's stock option program works, including vesting, exercise windows, tax considerations, and what happens when you leave."

• /handbook/teams/biz-dev — og:description is "How the Biz Dev team works and what it's accountable for." (57 chars) vs. meta description of 137 chars.

  • 💡 Fix: Remove the short ogDescription override; use the meta description as the default in the layout. Alternatively, expand the override to ≥100 chars to include keywords like "partnerships", "ecosystem", and "design wins".

• /handbook/teams/finance — og:description is "How the Finance team works and what it's accountable for." (57 chars) vs. meta description of 142 chars.

  • 💡 Fix: Same as /teams/biz-dev — remove or expand the ogDescription frontmatter override; default to the meta description in the layout.

• /handbook/teams/leadership — og:description is "Who leads Datum and what each leader is accountable for." (56 chars) vs. meta description of 130 chars.

  • 💡 Fix: Remove the short ogDescription override; let the layout use the meta description: "The Datum leadership team charts the company's direction and is accountable to investors, the board, and the broader organization."

• /handbook/about/model — meta description is exactly 130 chars, at the lower recommended boundary; risks truncation and weak keyword coverage.

  • 💡 Fix: Expand to ~145 chars, e.g. "Datum's economic model uses consumption-based usage of our network cloud infrastructure — designed to align incentives with customer success and scale."

• /handbook/eos/quarterly-rocks — meta description is 128 chars (below 130-char floor) and ends without a terminal period, which some parsers flag.

  • 💡 Fix: Append a period and a clause: "…our public acknowledgement of our Q1 and Q2 2026 commitments to the team and our customers." (≈155 chars).

• /handbook/build/oncall — og:title is "On-call" (7 chars), stripping all brand and keyword context for social/Slack unfurls.

  • 💡 Fix: Update frontmatter ogTitle to "On-Call Rotations & Well-Being — Datum" or simply remove the override to inherit the full <title>.

• /handbook/operate/status — og:title is "Status updates" (14 chars); similarly stripped.

  • 💡 Fix: Set ogTitle to "Async Status Updates — Datum Handbook" or remove override to inherit <title>.

• /handbook/operate/using-github — og:title is "Using GitHub" (12 chars); loses "Engineering Workflows" keyword for social.

  • 💡 Fix: Set ogTitle to "Using GitHub for Engineering Workflows — Datum" or remove override.

• /handbook/eos/quarterly-rocks — og:title is "Quarterly Rocks" (15 chars); loses "Q1 & Q2 2026 Priorities" context.

  • 💡 Fix: Set ogTitle to "Quarterly Rocks: Q1 & Q2 2026 Priorities — Datum" or remove override.