flower
/
1
All briefs
idea draft review_synthesis vodmanager
epic · VOD Manager — post-review roadmap (ambassador launch...

Public SEO / social-share / LLM-discoverability — per-page OG images are the top lever

Dispatch

canonical · plan

Spec

markdown

hand-off · dispatch

Dispatch

Auto-dispatch

when it reaches planned

Design-loop

design pass before build

Direct dispatch — no refine required. The packet tells the agent to ask questions only if the request is blocked by ambiguity.

kind

No dispatch requests yet — dispatch above to generate a copy-paste packet.

provenance · append-only

Trace

live
or paste a screenshot uploading…
  1. parent set 11h ago

    Grouped under epic #272.

    agent · claude-code
  2. note added 2d ago

    SEO/share-card/LLM review of all guest pages (home, /guides index + 21 guides, FAQ, privacy, terms, referral landing, overlays). Posture is STRONG: every public page emits a full card tag-set (og:title/description/image + width/height/type/url/site_name, twitter:card=summary_large_image + title/description/image), unique hand-authored titles/descriptions, well-formed JSON-LD on home/FAQ/20-of-21 guides, clean canonicals (url()->current()), complete favicon/manifest, and fully server-rendered HTML (the #1 LLM-ingestion asset — no screenshots-as-content, no JS-gated text). "Raise the ceiling," not "fix the floor." == HIGHEST-IMPACT, ORDERED == 1. Per-page / per-category OG images — the single biggest share-link win. TODAY every page renders the identical 1200×630 /images/og-image.png; card TEXT differs, VISUAL never does. Worst for the 7 provider guides (interchangeable) and the referral landing (personalized title/desc but generic art — its whole job is sharing). - Cheapest: 4 guides already ship real screenshots in public/images/marketing/ (chat-sidecar, encoding-settings, highlights-index, replay-player) — crop/resize to 1200×630 and wire as og:image. - Templated: 2–3 branded 1200×630 category templates ("bucket setup" S3/R2/B2/Wasabi; "OAuth connect" Drive/Dropbox/OneDrive; "reference/decision"). - Referral landing (highest ROI single page): generate a per-ambassador card server-side (/referrals/{code}/og-image.png rendering ambassador name + Twitch handle over a branded template; cache indefinitely). Interim: composite the ambassador's Twitch avatar (already on the linked TwitchAccount, not currently passed to the view) onto a static template. - Cache-bust on any swap: Discord/Slack cache OG images per-URL forever — change the filename or ?v=2. 2. Extract a shared <head> meta partial (resources/views/partials/seo-head.blade.php). ROOT CAUSE of drift: welcome.blade.php and components/marketing-page.blade.php duplicate the whole <head> and have ALREADY diverged (theme-color variants). One partial taking title/description/canonical/ogImage/ogImageAlt/noindex → both shells collapse to one @include; lands og:image:alt + og:locale everywhere; enables Fix 1's per-page images. Also fixes the homepage <title>-hardcoded-literal vs $seo_title desync. Do this FIRST (substrate for Fix 1). 3. Trim ~8 over-length meta descriptions (feed meta/og/twitter simultaneously; target ≤155–160, front-load): choosing-your-storage 309 (worst, top-of-funnel), wrapped-reports 221, why-archive 212, how-long-vods-stay 203, chat-replay 200, stream-analytics 196, cloudflare-r2 196; homepage 164 light trim. 4. Two zero-risk freebies: (a) robots.txt → add "Sitemap: https://vod-manager.com/sitemap.xml"; (b) privacy/terms pass bare titles ("Privacy Policy") breaking the "<Page> — VOD Manager" convention → weak cards; add the suffix. 5. Sitemap parity Pest test — the sitemap is a hand-maintained array in routes/web.php with no parity check; add a test asserting every /guides/* route appears in the array (durable fix vs one-time reconcile). Also reconcile dateModified(JSON-LD) vs lastmod(sitemap) drift on smart-features + watching-stream-replays. 6. twitter:site/creator — one line in the partial once an X handle exists (referral landing + homepage are the share surfaces). == STRUCTURED DATA (answer-engine wins; note Google restricted FAQ/HowTo rich results in 2023, so value is LLM/AI-overview ingestion) == - Homepage: enrich the thin SoftwareApplication (add url, image, applicationCategory, offers price 0, featureList naming S3/R2/B2/Wasabi/Drive/Dropbox/OneDrive + chat replay + transcripts + highlights). - /guides index: NO JSON-LD today → add ItemList of the guide catalog. - twitch-vod-vs-clip-vs-highlight + how-long-twitch-vods-stay: Q-shaped H2s but plain Article → upgrade to FAQPage (exactly what Perplexity/AI Overviews extract; these are the highest-value LLM target queries). - enabling-vod-storage-on-twitch: HowTo done right → add HowToStep.image. - privacy/terms: add lightweight WebPage + dateModified (AI assistants check policy freshness before citing). - Optional BreadcrumbList on the storage sub-hubs. == LLM notes == Fundamentals already ahead of most sites because content is honest server-rendered HTML with descriptive link text (FAQ uses native <details> so answers are in source even collapsed). Remaining work = make the STRUCTURED layer as good as the RENDERED layer so answer engines cite VOD Manager precisely. Overlays (referrals/overlay*) correctly out of scope: noindex,nofollow, no OG (bearer-token URLs must not unfurl). Full per-page gaps table exists in the review.

    agent · claude-code
  3. participant joined 2d ago
    system · claude-code

epic · dependencies

Relationships

depends on

No dependencies — dispatchable once planned.

agents · waves

Participants

  • claude-code participant · active

trace · graph

Links

No links yet — they accrue as agents work the brief.

scope

Projects

  • vodmanager · primary

dogfood · read-only

Agent’s-eye view

The literal recall_brief payload an agent gets — same service path as the MCP tool.