fix(seo): expand short titles and fix description lengths across 22 pages

[felixwidjaja]

Summary

Addresses all per-page issues from the weekly SEO audit (issue #1417):

• Expanded 11 meta titles from ≤37 chars to 51–59 chars (careers, finance, leadership, biz-dev, model, oncall, quarterly-rocks, career-progression, project-management, status, brand/templates)
• Expanded 3 descriptions below 120 chars to 140–153 chars (oncall: 110→143, community-huddles: 90→152, project-management: 116→153)
• Trimmed 7 descriptions at or near the 160-char limit to ≤155 chars (pricing, brand/logos, legal/terms, purpose, milo, using-github, vendors)
• Fixed og:description on 3 pages to match meta description (contact: 61→141, time-off: 28→120, pay-perks: 65→147)

Test plan

• Build the site and confirm no frontmatter parse errors
• Spot-check affected pages to confirm <title> and <meta name="description"> render correctly in browser DevTools
• Confirm og:description on contact, time-off, and pay-perks renders in social preview tools

Closes #1417

[github-actions]

🔎 SEO & Meta Review

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

📊 Score summary

Metric	Value
Overall score	🟢 100 / 100
Pages analyzed	19
Title issues (missing or >70 chars)	✅ 0
Description issues (length out of 70–160)	✅ 0
Canonical missing	✅ 0
H1 issues (0 or >1)	✅ 0
Noindex on built pages	✅ 0
og:image missing	✅ 0
JSON-LD invalid	✅ 0
Pages with missing alt text	✅ 0
Broken internal links	✅ 0
Redirect chains	✅ 0

No previous audit found — trend will appear next run.

---

SEO Review

All 19 pages are indexed, canonical-tagged, and carry valid og:image and twitter:card signals. The site is in good shape overall, but 5 pages have actionable issues across short descriptions, mismatched og:description vs meta description, and weak og:description copy.

---

2. Critical Issues

Short meta descriptions (<70 chars) — 0 pages. ✅
Titles >70 chars — 0 pages. ✅
Descriptions >160 chars — 0 pages. ✅
Missing/duplicate titles, canonicals, h1s, og:image, noindex — 0 pages. ✅

No critical issues found.

---

3. Improvements

og:description diverges from meta description (shorter/weaker copy) — 4 pages
/handbook/pay-perks/stock-options, /handbook/teams/biz-dev, /handbook/teams/finance, /handbook/teams/leadership
In each case the ogDescription is a throwaway stub ("Everything you need to know…", "How the Biz Dev team works…", etc.) while the meta description is well-written. These og:description values are what social cards display.

• 💡 Template fix: In src/layouts/Handbook.astro (or the frontmatter schema), default ogDescription to the page's description field if no override is set; or audit and update the four frontmatter ogDescription values directly.

JSON-LD types are site-wide Organization + WebSite only — 19 pages
Handbook articles and legal pages would benefit from Article or WebPage structured data to surface richer snippets.

• 💡 Template fix: In src/layouts/Handbook.astro, conditionally emit a WebPage or Article JSON-LD block alongside the existing schema, using the page title, description, datePublished, and canonical URL from frontmatter.

og:title diverges significantly from <title> tag — 5 pages
/handbook/about/model ("How we make money" vs. full title), /handbook/about/purpose, /handbook/build/oncall, /handbook/operate/status, /handbook/operate/using-github — all use terse, context-free og:titles that lose keyword value on social shares.

• 💡 Template fix: Unless intentionally overridden for social, default ogTitle to the page title in src/layouts/Handbook.astro; review the five listed pages and decide if the short labels are intentional.

---

4. Per-page notes

• /handbook/about/model — ogTitle is "How we make money" (18 chars) vs. page title "Datum's Business Model: Revenue Through Network Cloud Usage" — loses brand and keyword signal on social shares.

  • 💡 Fix: Update frontmatter ogTitle to match or approximate the page title, e.g. "Datum's Business Model: Revenue Through Network Cloud Usage".

• /handbook/about/purpose — ogTitle is "Datum's purpose" (16 chars) vs. page title "Datum's Purpose - Upgrading the Internet for AI" — social card loses the AI hook.

  • 💡 Fix: Set frontmatter ogTitle to "Datum's Purpose — Upgrading the Internet for AI".

• /handbook/build/oncall — ogTitle is "On-call" (7 chars) — no brand or context on social.

  • 💡 Fix: Set frontmatter ogTitle to "On-Call Rotations & Well-Being Policy — Datum" or match page title.

• /handbook/operate/status — ogTitle is "Status updates" (14 chars) — loses the async/team-alignment keywords on social.

  • 💡 Fix: Set frontmatter ogTitle to "Async Status Updates: How Datum Keeps Teams Aligned".

• /handbook/operate/using-github — ogTitle is "Using GitHub" (12 chars) — no brand signal on social card.

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

• /handbook/pay-perks/stock-options — ogDescription is "Everything you need to know about Datum's stock option program." (62 chars) — well below the ~130-char sweet spot and weaker than the meta description (descriptionLen: 129).

  • 💡 Fix: Replace frontmatter ogDescription with the existing 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 — ogDescription is "How the Biz Dev team works and what it's accountable for." (56 chars) vs. meta description of 137 chars with concrete keywords (partnerships, ecosystem, design wins).

  • 💡 Fix: Replace frontmatter ogDescription with the meta description: "Datum's Business Development team focuses on building an open, vendor-neutral ecosystem through partnerships, design wins, and community.".

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

  • 💡 Fix: Replace frontmatter ogDescription with the meta description: "The Finance team keeps Datum running cleanly so the rest of the company can move fast: payroll, contracts, vendors, governance, and reporting.".

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

  • 💡 Fix: Replace frontmatter ogDescription with the meta description: "The Datum leadership team charts the company's direction and is accountable to investors, the board, and the broader organization.".