🗓️ Weekly SEO Audit
Analyzed 95 of 95 built HTML pages (mode: full).
Audits: 0 broken internal link(s), 0 redirect chain(s).
📊 Score summary
| Metric |
Value |
| Overall score |
🟢 99 / 100 ▼ -1 |
| Pages analyzed |
95 |
| Title issues (missing or >70 chars) |
✅ 0 ▬ 0 |
| Description issues (length out of 70–160) |
🔴 3 ▼ +3 |
| Canonical missing |
✅ 0 ▬ 0 |
| H1 issues (0 or >1) |
🟡 1 ▼ +1 |
| Noindex on built pages |
🟡 1 ▼ +1 |
| og:image missing |
🟡 1 ▼ +1 |
| 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-07-12): ▲ improved · ▼ worsened · ▬ unchanged.
SEO Review — datum.net (95 pages)
1. Summary
Overall SEO health is strong: canonicals, robots directives, hreflang, H1 structure, alt text, and JSON-LD are consistently implemented across all 95 pages. 5 critical issues were identified across 8 pages, concentrated in the platform sub-section and a redirect page.
2. Critical Issues
| Issue Type |
Affected Pages |
Count |
| Description too short (<70 chars) |
/platform/build, /platform/connect, /platform/deliver |
3 |
| Description too long (>160 chars) |
/pricing, /open-source, /events/community-huddles, /events |
4 |
| Missing description entirely |
/platform (redirect) |
1 |
| Title is sentence/H1 copy, not keyword-optimised |
/platform/deliver |
1 |
noindex redirect page with bare-minimum metadata |
/platform |
1 |
Template-level fix (platform feature pages): The three /platform/* feature pages appear to share a layout (likely src/layouts/PlatformFeature.astro or equivalent). The description field is being populated with a single-line UI tagline rather than a full meta description. Add a dedicated description frontmatter field to each content file and wire it to <meta name="description"> in the layout, enforcing a 120–155 char minimum at build time (e.g. via a remark/rehype plugin or Zod schema validation).
Template-level fix (/platform redirect): The redirect page at /platform emits noindex and no OG/meta data — this is acceptable behaviour for a redirect if it resolves immediately, but the crawlable title "Redirecting to: /platform/deliver" suggests a client-side or slow redirect. Prefer an HTTP 301 at the CDN/server level so the page is never indexed and never crawled as content.
3. Improvements
| Theme |
Affected Pages |
Count |
| JSON-LD schema depth |
All 95 pages emit only Organization + WebSite |
95 |
og:title / og:description diverge significantly from <title> / <meta description> |
Several handbook and brand pages |
~15 |
JSON-LD coverage: Every page uses the same two-type schema (Organization, WebSite). Add page-type-specific schemas in the relevant Astro layouts: BreadcrumbList for handbook/policy/brand sub-pages (in src/layouts/Handbook.astro), Event for /events/* pages, JobPosting for /careers, and FAQPage or WebPage for key marketing pages (/pricing, /essentials).
OG consistency: Several pages have og:title values that are significantly shorter or more casual than the <title> tag (e.g. /brand has title "Datum Brand Assets: Logos, Guidelines & Identity" but og:title "Our visual identity"). While intentional tone-of-voice differentiation is fine, pages where og:description is substantially shorter than <meta description> lose social-share keyword coverage. Audit the OG fields in the shared layout and content frontmatter to ensure the primary keyword appears in both.
4. Per-page Notes
-
/platform/build — Title is only 22 chars ("Build – Datum Features"); description is only 54 chars ("Millisecond cold-start compute and related primitives.") — both well below recommended minimums.
- 💡 Fix: Expand title to ~55 chars, e.g.
"Datum Build — Edge Compute & Networking Primitives". Rewrite description to 130–155 chars, e.g. "Deploy millisecond cold-start compute at the network edge. Datum's Build primitives give AI-native applications the performance layer they need to scale globally." Update the content frontmatter for this page.
-
/platform/connect — Title is only 24 chars ("Connect – Datum Features"); description is only 60 chars ("Land diverse connections on your own virtual \"meet me room\".") — both below recommended minimums.
- 💡 Fix: Expand title to ~55 chars, e.g.
"Datum Connect — Private Networking & Virtual Interconnect". Rewrite description to 130–155 chars covering keywords like 'private connectivity', 'virtual meet-me room', 'cross-connect'. Update the content frontmatter.
-
/platform/deliver — Title ("Protect, manage, and route traffic.", 35 chars) is a sentence fragment matching the H1, not a keyword-rich page title; description is 117 chars (borderline short) and matches og:description verbatim with no keyword differentiation.
- 💡 Fix: Replace title with
"Datum Deliver — CDN, WAF & AI Inference Proxy" (~47 chars). Expand description to 135–155 chars incorporating 'CDN', 'WAF', 'traffic routing', and 'edge proxy'. Update frontmatter.
-
/platform — Page is noindex, has title "Redirecting to: /platform/deliver", no description, no OG tags, no JSON-LD, no H1, no lang attribute — all expected for a redirect, but the page is being rendered and crawled as HTML.
- 💡 Fix: Replace the client-side/meta-refresh redirect with an HTTP 301 at the CDN level (e.g. Netlify
_redirects: /platform /platform/deliver 301). This eliminates the crawlable HTML stub entirely.
-
/pricing — Description is 159 chars, exceeding the 155-char safe threshold (will be truncated in SERPs).
- 💡 Fix: Trim to ≤155 chars; suggested:
"A low-friction plan for builders, developers, and agents — enterprise-grade network primitives free. Production tier from $20/month. Start building today." (154 chars).
-
/open-source — Description is 154 chars — right at the limit but the text includes a long comma-separated list that Google may truncate mid-phrase.
- 💡 Fix: Trim to ≤150 chars and restructure:
"Datum is an open source company leading Milo and the Envoy AI Gateway, and building on Crossplane, SRv6, and HickoryDNS. See our open source commitment." (152 chars → trim one word).
-
/events/community-huddles — Description is 154 chars, at the edge of truncation; og:description mirrors it exactly, so both will be truncated consistently but sub-optimally.
- 💡 Fix: Shorten to ~145 chars:
"Join Datum's monthly community huddle — an informal session for live demos, open Q&A, and the latest Datum product and ecosystem updates. All welcome." and update og:description to match.
-
/events — Description is 154 chars, same truncation risk as above.
- 💡 Fix: Shorten to ~145 chars:
"Discover upcoming Datum events, conferences, and community meetups. Connect with AI-native builders, developers, and alt-cloud providers around the world." (153 chars → remove one word to reach ≤150).
🗓️ Weekly SEO Audit
Analyzed 95 of 95 built HTML pages (mode:
full).Audits: 0 broken internal link(s), 0 redirect chain(s).
📊 Score summary
Trend vs previous audit (2026-07-12): ▲ improved · ▼ worsened · ▬ unchanged.
SEO Review — datum.net (95 pages)
1. Summary
Overall SEO health is strong: canonicals, robots directives, hreflang, H1 structure, alt text, and JSON-LD are consistently implemented across all 95 pages. 5 critical issues were identified across 8 pages, concentrated in the platform sub-section and a redirect page.
2. Critical Issues
/platform/build,/platform/connect,/platform/deliver/pricing,/open-source,/events/community-huddles,/events/platform(redirect)/platform/delivernoindexredirect page with bare-minimum metadata/platformTemplate-level fix (platform feature pages): The three
/platform/*feature pages appear to share a layout (likelysrc/layouts/PlatformFeature.astroor equivalent). Thedescriptionfield is being populated with a single-line UI tagline rather than a full meta description. Add a dedicateddescriptionfrontmatter field to each content file and wire it to<meta name="description">in the layout, enforcing a 120–155 char minimum at build time (e.g. via a remark/rehype plugin or Zod schema validation).Template-level fix (
/platformredirect): The redirect page at/platformemitsnoindexand no OG/meta data — this is acceptable behaviour for a redirect if it resolves immediately, but the crawlable title"Redirecting to: /platform/deliver"suggests a client-side or slow redirect. Prefer an HTTP 301 at the CDN/server level so the page is never indexed and never crawled as content.3. Improvements
Organization+WebSiteog:title/og:descriptiondiverge significantly from<title>/<meta description>JSON-LD coverage: Every page uses the same two-type schema (
Organization,WebSite). Add page-type-specific schemas in the relevant Astro layouts:BreadcrumbListfor handbook/policy/brand sub-pages (insrc/layouts/Handbook.astro),Eventfor/events/*pages,JobPostingfor/careers, andFAQPageorWebPagefor key marketing pages (/pricing,/essentials).OG consistency: Several pages have
og:titlevalues that are significantly shorter or more casual than the<title>tag (e.g./brandhas title"Datum Brand Assets: Logos, Guidelines & Identity"butog:title"Our visual identity"). While intentional tone-of-voice differentiation is fine, pages whereog:descriptionis substantially shorter than<meta description>lose social-share keyword coverage. Audit the OG fields in the shared layout and content frontmatter to ensure the primary keyword appears in both.4. Per-page Notes
/platform/build — Title is only 22 chars (
"Build – Datum Features"); description is only 54 chars ("Millisecond cold-start compute and related primitives.") — both well below recommended minimums."Datum Build — Edge Compute & Networking Primitives". Rewrite description to 130–155 chars, e.g."Deploy millisecond cold-start compute at the network edge. Datum's Build primitives give AI-native applications the performance layer they need to scale globally."Update the content frontmatter for this page./platform/connect — Title is only 24 chars (
"Connect – Datum Features"); description is only 60 chars ("Land diverse connections on your own virtual \"meet me room\".") — both below recommended minimums."Datum Connect — Private Networking & Virtual Interconnect". Rewrite description to 130–155 chars covering keywords like 'private connectivity', 'virtual meet-me room', 'cross-connect'. Update the content frontmatter./platform/deliver — Title (
"Protect, manage, and route traffic.", 35 chars) is a sentence fragment matching the H1, not a keyword-rich page title; description is 117 chars (borderline short) and matchesog:descriptionverbatim with no keyword differentiation."Datum Deliver — CDN, WAF & AI Inference Proxy"(~47 chars). Expand description to 135–155 chars incorporating 'CDN', 'WAF', 'traffic routing', and 'edge proxy'. Update frontmatter./platform — Page is
noindex, has title"Redirecting to: /platform/deliver", no description, no OG tags, no JSON-LD, no H1, no lang attribute — all expected for a redirect, but the page is being rendered and crawled as HTML._redirects:/platform /platform/deliver 301). This eliminates the crawlable HTML stub entirely./pricing — Description is 159 chars, exceeding the 155-char safe threshold (will be truncated in SERPs).
"A low-friction plan for builders, developers, and agents — enterprise-grade network primitives free. Production tier from $20/month. Start building today."(154 chars)./open-source — Description is 154 chars — right at the limit but the text includes a long comma-separated list that Google may truncate mid-phrase.
"Datum is an open source company leading Milo and the Envoy AI Gateway, and building on Crossplane, SRv6, and HickoryDNS. See our open source commitment."(152 chars → trim one word)./events/community-huddles — Description is 154 chars, at the edge of truncation;
og:descriptionmirrors it exactly, so both will be truncated consistently but sub-optimally."Join Datum's monthly community huddle — an informal session for live demos, open Q&A, and the latest Datum product and ecosystem updates. All welcome."and updateog:descriptionto match./events — Description is 154 chars, same truncation risk as above.
"Discover upcoming Datum events, conferences, and community meetups. Connect with AI-native builders, developers, and alt-cloud providers around the world."(153 chars → remove one word to reach ≤150).