Enhance VitePress docs with SEO metadata for better discoverability

[waynesun09]

Summary

The VitePress documentation site at https://fullsend.sh/docs would benefit from additional SEO metadata to improve search engine indexing, social media sharing, and content discoverability.

Enhancement Opportunities

Social Sharing

• Open Graph tags - Add og:title, og:description, og:image, og:url for rich previews on LinkedIn, Facebook, Slack
• Twitter Cards - Add twitter:card, twitter:title, twitter:description, twitter:image for better Twitter/X sharing

Search Engine Optimization

• Canonical URLs - Add <link rel="canonical"> tags to establish preferred URLs
• Sitemap.xml - Generate proper XML sitemap for efficient crawling (currently returns HTML)
• Structured data - Add JSON-LD schema markup for documentation, breadcrumbs, and software application metadata
• Per-page descriptions - Use unique meta descriptions instead of the same "Autonomous SDLC agents for your codebase" across all pages

Nice-to-Have

• Explicit robots meta tags for per-page crawl control
• Rich snippets support via schema.org markup

Current State ✅

The docs already have good foundations:

• Basic meta descriptions
• Page-specific title tags
• Proper robots.txt with search signals (search=yes)
• Strong internal linking (203 links)
• Clean URL structure
• Search indexing enabled

Implementation

VitePress has built-in SEO support. Example website/.vitepress/config.ts:

export default defineConfig({
  // Global head tags
  head: [
    ['meta', { property: 'og:type', content: 'website' }],
    ['meta', { property: 'og:site_name', content: 'Fullsend' }],
    ['meta', { name: 'twitter:card', content: 'summary_large_image' }],
  ],
  
  // Sitemap generation
  sitemap: {
    hostname: 'https://fullsend.sh'
  },
  
  // Per-page canonical and OG tags
  transformHead({ pageData }) {
    const url = `https://fullsend.sh${pageData.relativePath.replace(/\.md$/, '.html')}`
    return [
      ['link', { rel: 'canonical', href: url }],
      ['meta', { property: 'og:url', content: url }],
      ['meta', { property: 'og:title', content: pageData.title }],
      ['meta', { property: 'og:description', content: pageData.description }],
    ]
  }
})

Add unique descriptions via frontmatter:

---
title: Getting Started
description: Install and configure Fullsend autonomous agents for your repository
---

Testing Tools

• https://cards-dev.twitter.com/validator
• https://www.opengraph.xyz/
• https://search.google.com/test/rich-results

References

• VitePress Sitemap Guide
• Open Graph Protocol

[fullsend-ai-triage]

🤖 Finished Triage · ✅ Success · Started 3:17 PM UTC · Completed 3:20 PM UTC
Commit: 0a95cac · View workflow run →

[fullsend-ai-triage]

Triage Summary

This is a well-defined feature request to add SEO metadata to the VitePress documentation site.

Problem: The docs site lacks Open Graph tags, Twitter Cards, canonical URLs, an XML sitemap, and per-page meta descriptions — reducing search engine discoverability and social sharing quality.

Current state: The VitePress config (website/.vitepress/config.ts) has a static global description and no sitemap or transformHead configuration. The foundations are solid (good internal linking, clean URLs, local search), but these SEO additions would meaningfully improve external discoverability.

Recommended implementation:

1. Add sitemap: { hostname: 'https://fullsend.sh' } to the VitePress config
2. Add global og:type, og:site_name, and twitter:card meta tags to the head array
3. Add a transformHead hook to generate per-page canonical, og:url, og:title, and og:description tags from pageData
4. Add description frontmatter to key documentation pages for unique per-page descriptions

Proposed test case:

After building the VitePress site:
1. Parse generated HTML for multiple pages and assert og:title, og:description,
   og:url, and twitter:card meta tags are present with page-specific values
2. Assert each page has a <link rel="canonical"> with the correct full URL
3. Assert sitemap.xml exists in the build output and contains valid XML
   with entries for all documentation pages
4. Assert pages with frontmatter descriptions use those values
   instead of the global default

The issue provides a ready-to-use implementation template. This is a good first issue with clear scope.

---

Labels: Docs-site SEO feature request — adding component/docs and type/feature for structured labeling, priority/low for non-urgent enhancement, and removing redundant legacy labels.