🗓️ Weekly SEO Audit

Analyzed 92 of 92 built HTML pages (mode: full).
Audits: 0 broken internal link(s), 0 redirect chain(s).

📊 Score summary

Trend vs previous audit (2026-06-14): ▲ improved · ▼ worsened · ▬ unchanged.

SEO Review — datum.net (92 pages)

1. Summary

All 92 pages are indexable, carry canonical tags, unique titles, descriptions, a single H1, and JSON-LD — a strong baseline. The site has no critical blockers, but there are 14 pages with margeable or borderline description lengths, several short titles, and pervasive og:title/og:description misalignment with the <title>/<meta description> that risks weaker social sharing.

2. Critical Issues

No missing titles, missing descriptions, duplicate titles/descriptions, missing canonicals, noindex on live pages, titles >70 chars, or broken JSON-LD were found.

3. Improvements

og:title / og:description diverge significantly from <title> / <meta description> on most pages. This is a site-wide pattern (affects ~70+ pages). The og variants are often terse, conversational, or incomplete relative to the keyword-rich SEO title/description. While intentional brand voice is valid, several og:descriptions are under 60 chars, wasting social preview space.

• Template fix: In src/layouts/ (likely BaseLayout.astro, HandbookLayout.astro, or equivalent), default og:title to the page <title> and og:description to the <meta description> when no explicit override is set. Allow per-page overrides only where a distinct social hook is genuinely needed. This eliminates the risk of social cards showing weaker copy.

JSON-LD schema depth — All 92 pages emit only Organization + WebSite types. Product, handbook, event, legal, and blog pages would benefit from richer types (WebPage, Article, Event, FAQPage).

• Template fix: Add a schemaType prop to BaseLayout.astro; emit BreadcrumbList on all handbook/brand sub-pages, Event on /events/*, and Article on /changelog entries.

og:image falls back to default.Dhe8XgQ0.png on 17 pages (events, legal, careers, locations, open-source, essentials, pricing, changelog). These pages have distinct purposes and a generic OG image undersells them in link previews.

• Template fix: Create section-specific OG images (e.g. events.png, legal.png, pricing.png) and assign them in each section's layout or frontmatter, similar to how /brand, /handbook, /contact, and /product already have dedicated images.

4. Per-page notes

• /brand/templates — Title is 36 chars ("Brand Templates - Datum Brand Assets"); short and front-loads the generic word "Brand".

  • 💡 Fix: Expand to ~55 chars, e.g. "Datum Brand Templates: Presentations, Docs & Design Files".

• /careers — Title is 29 chars ("Work at Datum - Datum Careers"); "Datum" appears twice and the title is very short.

  • 💡 Fix: Rewrite to ~55 chars, e.g. "Datum Careers — Join the Team Building Open Network Cloud".

• /handbook/about/model — Title is 35 chars ("Our Business Model - Datum Handbook").

  • 💡 Fix: Expand to ~52 chars, e.g. "Datum Business Model: Consumption-Based Network Cloud Revenue" (trim to fit ≤60).

• /handbook/build/oncall — Title is 34 chars ("On-Call Rotations - Datum Handbook").

  • 💡 Fix: Expand to ~55 chars, e.g. "On-Call Rotations & Engineer Well-Being Policy — Datum Handbook" (trim to ≤60).

• /handbook/eos/quarterly-rocks — Title is 32 chars ("Quarterly Rocks - Datum Handbook").

  • 💡 Fix: Expand to ~52 chars, e.g. "Quarterly Rocks: Q1 & Q2 2026 Priorities — Datum Handbook".

• /handbook/teams/finance — Title is 29 chars ("Finance Team - Datum Handbook").

  • 💡 Fix: Expand to ~52 chars, e.g. "Datum Finance Team: Payroll, Contracts & Governance — Handbook" (trim to ≤60).

• /handbook/teams/leadership — Title is 32 chars ("Leadership Team - Datum Handbook").

  • 💡 Fix: Expand to ~52 chars, e.g. "Datum Leadership Team: Founders, Roles & Accountability".

• /handbook/teams/biz-dev — Title is 37 chars ("Business Development - Datum Handbook").

  • 💡 Fix: Expand to ~56 chars, e.g. "Business Development Team: Partnerships & Ecosystem — Datum".

• /handbook/pay-perks/career-progression — Title is 35 chars ("Career Progression - Datum Handbook").

  • 💡 Fix: Expand to ~55 chars, e.g. "Career Progression at Datum: Growth, Impact & Autonomy".

• /handbook/operate/project-management — Title is 35 chars ("Project Management - Datum Handbook"); description is 116 chars (below 120).

  • 💡 Fix: Expand title to ~55 chars, e.g. "Project Management at Datum: Goal-Setting & Done Criteria". Expand description to ~135 chars by adding context such as "…in an async-first, distributed team."

• /handbook/operate/status — Title is 31 chars ("Status Updates - Datum Handbook").

  • 💡 Fix: Expand to ~54 chars, e.g. "Async Status Updates: How Datum Keeps Teams Aligned — Handbook" (trim to ≤60).

• /handbook/build/oncall — Description is 110 chars, below comfortable threshold.

  • 💡 Fix: Expand to 130–150 chars, e.g. append "…We use PagerDuty rotations and blameless reviews to protect both service quality and engineer well-being."

• /events/community-huddles — Description is 90 chars ("Join Datum's open and informal huddle for demos, discussions and the latest Datum updates."), well under the 120-char floor.

  • 💡 Fix: Expand to 130–150 chars, e.g. "Join Datum's monthly open community huddle — an informal session for live demos, open discussion, Q&A, and the latest Datum product and ecosystem updates." (152 chars; trim slightly).

• /contact — Description is 119 chars; og:description is only 61 chars ("Connect with a founder for a coffee, questions or share ideas").

  • 💡 Fix: Expand meta description to 130–150 chars with a clear CTA keyword; update og:description to match or use the full meta description (see template fix in section 3).

• /handbook/pay-perks/time-off — og:description is 28 chars ("How time off works at Datum."), far too short for social cards.

  • 💡 Fix: Set og:description to match the meta description ("Datum's approach to unlimited time off, holidays, flexible working, sick leave, maternity leave, and other leave policies.") or apply the layout-level default described in section 3.

• /handbook/pay-perks — Description is 111 chars (below 120); og:description is 65 chars.

  • 💡 Fix: Expand meta description to ~140 chars, e.g. append "…including stock options, transparent pay levels, and global benefit programs." Update og:description to match.

• /pricing — Description is exactly 160 chars (at the hard limit; risk of truncation).

  • 💡 Fix: Trim to ≤155 chars; suggested: "A low-friction plan for builders, developers, and agents — enterprise-grade primitives free. Production tier from $20/month." (125 chars; add a keyword phrase to reach ~145).

• /handbook/about/purpose — Description is 157 chars (near limit, risk of truncation).

  • 💡 Fix: Trim to ≤155 chars; remove the em-dash clause or shorten "democratize access to internet superpowers" to stay within budget.

• /handbook/product/milo — Description is 157 chars (near limit).

  • 💡 Fix: Trim to ≤155 chars; e.g. shorten "unifying identity, metering, and policy management for modern service providers. Automate your operations." to "…for modern service providers — automate billing, identity, and policy." (~150 chars total).

• /legal/terms — Description is 157 chars (near limit).

  • 💡 Fix: Trim to ≤155 chars; remove "including account responsibilities and acceptable use" or shorten to "…covering account responsibilities and use terms."

• /handbook/operate/using-github — Description is 158 chars (near limit).

  • 💡 Fix: Trim to ≤155 chars; shorten "we organize our work in releases, enhancements and issues" to "…organized around releases, enhancements, and issues."

• /handbook/policy/vendors — Description is 159 chars (near limit).

  • 💡 Fix: Trim to ≤155 chars; remove "and privacy" from the last clause.

• /brand/logos — Description is exactly 160 chars (at the limit).

  • 💡 Fix: Trim to ≤155 chars; shorten "Download official brand assets and usage guidelines for digital and print projects" to "Download assets and guidelines for digital and print."