ποΈ Weekly SEO Audit
Analyzed 92 of 92 built HTML pages (mode: full).
Audits: 0 broken internal link(s), 0 redirect chain(s).
π Score summary
| Metric |
Value |
| Overall score |
π’ 100 / 100 β¬ 0 |
| Pages analyzed |
92 |
| Title issues (missing or >70 chars) |
β
0 β¬ 0 |
| Description issues (length out of 70β160) |
β
0 β² -2 |
| Canonical missing |
β
0 β¬ 0 |
| H1 issues (0 or >1) |
β
0 β¬ 0 |
| Noindex on built pages |
β
0 β¬ 0 |
| og:image missing |
β
0 β¬ 0 |
| JSON-LD invalid |
β
0 β¬ 0 |
| Pages with missing alt text |
β
0 β¬ 0 |
| Broken internal links |
β
0 β¬ 0 |
| Redirect chains |
β
0 β¬ 0 |
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
| Issue |
Count |
Template Fix |
| Description at exactly 160 chars (at the byte limit, likely to truncate) |
3 pages |
In the content frontmatter or CMS field for each, trim to β€155 chars. No layout change needed. |
| Description <120 chars (thin for search snippets) |
3 pages |
Expand to 130β155 chars in page frontmatter. |
| Title β€30 chars (too short; wastes keyword real estate) |
4 pages |
Expand titles in page frontmatter to 50β60 chars including brand + primary keyword. |
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."
ποΈ 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.src/layouts/(likelyBaseLayout.astro,HandbookLayout.astro, or equivalent), defaultog:titleto the page<title>andog:descriptionto 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+WebSitetypes. Product, handbook, event, legal, and blog pages would benefit from richer types (WebPage,Article,Event,FAQPage).schemaTypeprop toBaseLayout.astro; emitBreadcrumbListon all handbook/brand sub-pages,Eventon/events/*, andArticleon/changelogentries.og:imagefalls back todefault.Dhe8XgQ0.pngon 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.events.png,legal.png,pricing.png) and assign them in each section's layout or frontmatter, similar to how/brand,/handbook,/contact, and/productalready 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"."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."Datum Careers β Join the Team Building Open Network Cloud"./handbook/about/model β Title is 35 chars (
"Our Business Model - Datum Handbook")."Datum Business Model: Consumption-Based Network Cloud Revenue"(trim to fit β€60)./handbook/build/oncall β Title is 34 chars (
"On-Call Rotations - Datum Handbook")."On-Call Rotations & Engineer Well-Being Policy β Datum Handbook"(trim to β€60)./handbook/eos/quarterly-rocks β Title is 32 chars (
"Quarterly Rocks - Datum Handbook")."Quarterly Rocks: Q1 & Q2 2026 Priorities β Datum Handbook"./handbook/teams/finance β Title is 29 chars (
"Finance Team - Datum Handbook")."Datum Finance Team: Payroll, Contracts & Governance β Handbook"(trim to β€60)./handbook/teams/leadership β Title is 32 chars (
"Leadership Team - Datum Handbook")."Datum Leadership Team: Founders, Roles & Accountability"./handbook/teams/biz-dev β Title is 37 chars (
"Business Development - Datum Handbook")."Business Development Team: Partnerships & Ecosystem β Datum"./handbook/pay-perks/career-progression β Title is 35 chars (
"Career Progression - Datum Handbook")."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)."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")."Async Status Updates: How Datum Keeps Teams Aligned β Handbook"(trim to β€60)./handbook/build/oncall β Description is 110 chars, below comfortable threshold.
/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."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")./handbook/pay-perks/time-off β og:description is 28 chars (
"How time off works at Datum."), far too short for social cards."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.
/pricing β Description is exactly 160 chars (at the hard limit; risk of truncation).
"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).
/handbook/product/milo β Description is 157 chars (near limit).
/legal/terms β Description is 157 chars (near limit).
/handbook/operate/using-github β Description is 158 chars (near limit).
/handbook/policy/vendors β Description is 159 chars (near limit).
/brand/logos β Description is exactly 160 chars (at the limit).