You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, social share previews on Twitter/X, Discord, and LinkedIn point to the SVG icon terminal-demo.svg. We need a dedicated 1200x630 JPEG/WebP graphic that displays clearly in social cards, search engines, and rich link embeds.
📋 Scope of Work
Create a high-contrast 1200x630 OpenGraph banner (docs/og-image.jpg or docs/og-image.webp).
Incorporate AgentShield branding, tagline ("Zero-Leak Secret Defense & Sandbox for AI Agents"), and terminal snippet.
Update <meta property="og:image" content="https://agentshield.ritualdev.in/og-image.jpg"> and Twitter card metadata in docs/index.html.
Quick check before you ship the new banner: X, LinkedIn, Discord, and Slack generally do not render SVG og:image / twitter:image (a lot of validators will look fine in-browser while the crawlers still show nothing). A 1200×630 JPEG/PNG/WebP at an absolute https://… URL is the reliable path, with og:image:width / og:image:height set and twitter:card=summary_large_image.
Also watch for relative image URLs and a CDN/host that 403s crawler user-agents — the page can 200 in Chrome while facebookexternalhit / Twitterbot get blocked.
After deploy, re-scrape in each platform’s debugger (they cache hard).
Disclosure: I maintain a free MIT Open Graph / Twitter card linter that flags SVG/relative/og:image reachability issues in one pass — https://dimonch-byte.github.io/og-lint/ — if that’s useful while you verify.
New docs/og-image.jpg — high-contrast 1200×630 raster built from the site tokens (shield mark, tagline, agent shield check redaction demo), which X/LinkedIn/Discord/Slack will actually render (SVG is not supported by those scrapers).
og:image + twitter:image now point at the raster, with width/height/type added.
docs/ is deployed verbatim by the Pages workflow, so the URL resolves once merged.
Activity
dimonch-byte commentedon Oct 12, 2026
Quick check before you ship the new banner: X, LinkedIn, Discord, and Slack generally do not render SVG
og:image/twitter:image(a lot of validators will look fine in-browser while the crawlers still show nothing). A 1200×630 JPEG/PNG/WebP at an absolutehttps://…URL is the reliable path, withog:image:width/og:image:heightset andtwitter:card=summary_large_image.Also watch for relative image URLs and a CDN/host that 403s crawler user-agents — the page can 200 in Chrome while
facebookexternalhit/ Twitterbot get blocked.After deploy, re-scrape in each platform’s debugger (they cache hard).
Disclosure: I maintain a free MIT Open Graph / Twitter card linter that flags SVG/relative/
og:imagereachability issues in one pass — https://dimonch-byte.github.io/og-lint/ — if that’s useful while you verify.adamshatzkamer commentedon Oct 14, 2026
PR ready: #7
Implements the Open Graph banner task:
docs/og-image.jpg— high-contrast 1200×630 raster built from the site tokens (shield mark, tagline,agent shield checkredaction demo), which X/LinkedIn/Discord/Slack will actually render (SVG is not supported by those scrapers).og:image+twitter:imagenow point at the raster, with width/height/type added.docs/is deployed verbatim by the Pages workflow, so the URL resolves once merged.feat(seo): add 1200x630 raster OG banner (docs/og-image.jpg)