Summary

Optimize README for search engines (SEO), AI search engines (AEO/GEO), update outdated screenshots, promote Auto-Combo feature, and request docs publish to omniroute.online.

Motivation

• README lacks structured data for rich snippets
• Screenshots show old UI (v3.6-era), not current features
• Docs site doesn't reflect latest features (cloud-agent, Auto-Combo, RTK compression)
• Auto-Combo (6-factor scoring) is hidden, competitors like Routerly market similar features

Proposed Changes

1. SEO Optimization (HIGH PRIORITY)

1.1 Schema Markup

{
  "@context": "https://schema.org",
  "@type": "SoftwareApplication",
  "name": "OmniRoute",
  "applicationCategory": "DeveloperApplication",
  "operatingSystem": "Windows, macOS, Linux, Android",
  "offers": {
    "@type": "Offer",
    "price": "0",
    "priceCurrency": "USD"
  },
  "description": "Unified AI proxy/router with 160+ providers, RTK+Caveman compression (15-95% savings), auto-fallback to free AI models"
}

1.2 OpenGraph + Twitter Cards

• Add og:title, og:description, og:image, og:url
• Add twitter:card, twitter:image, twitter:title

1.3 FAQ Schema (Rich Results)

• Add FAQPage schema with Q&A about:
  • "What is OmniRoute?"
  • "How does prompt compression save tokens?"
  • "Which free providers are available?"
  • "How does Auto-Combo work?"

1.4 Keywords for AI Search

• Add meta keywords: AI gateway, LLM router, OpenAI proxy, Anthropic proxy, multi-provider AI, free AI API, prompt compression, token optimization

1.5 Competitor Comparison Sections

• Add "Alternatives to LiteLLM" section
• Add "Alternatives to Bifrost" section
• Include comparison table with features

2. Screenshot Refresh (MEDIUM PRIORITY)

2.1 Capture New Screenshots

Run npm run dev and capture:

2.2 Replace in README

• Update image paths
• Update alt text with descriptive labels
• Verify dimensions match (800px width)

3. Auto-Combo Marketing (MEDIUM PRIORITY)

3.1 Add to Hero Section

Change from:

### Never stop coding. Save 15-95% eligible tokens with RTK+Caveman compression + auto-fallback to FREE & low-cost AI models.

To:

### Never stop coding. Save 15-95% eligible tokens with RTK+Caveman compression + Auto-Combo intelligent routing to FREE & low-cost AI models.

Auto-Combo uses 6-factor scoring (task type, cost, latency, quota, capability, diversity) to automatically pick the best model for each request.

3.2 Add Auto-Combo Section

• Add subsection explaining Auto-Combo vs manual combos
• Add comparison: OmniRoute (6-factor scoring, self-healing) vs Routerly (simple LLM)
• Include mode packs explanation (coding, vision, analysis)

4. Docs Publish Request (HIGH PRIORITY)

4.1 Request to Owner

Contact maintainer to:

1. Build docs: npm run docs:build or similar
2. Deploy to omniroute.online
3. Ensure these are included:
   • Cloud Agent providers (new category)
   • Auto-Combo engine docs
   • RTK + Stacked compression modes
   • Updated screenshots

Action Checklist

SEO Team (or contributor)

• Add JSON-LD SoftwareApplication schema to README
• Add FAQPage schema with 5+ Q&A
• Add OpenGraph meta tags
• Add Twitter Card meta tags
• Add "Alternative to LiteLLM" comparison section
• Add "Alternative to Bifrost" comparison section
• Verify with Google Rich Results test

Screenshots Team

• Run npm run dev
• Navigate to each page in table above
• Screenshot with Shift+Cmd+4 (mac) or Win+Shift+S (Windows)
• Save to docs/screenshots/ with exact filenames
• Update README image references
• Compress images if >500KB

Marketing Team

• Rewrite hero tagline to include Auto-Combo
• Add "Why OmniRoute?" section
• Add feature comparison table
• Add performance benchmark placeholder (awaiting results)

Docs Team

• Create GitHub issue to owner: "Deploy latest docs to omniroute.online"
• Include checklist of new features to add
• Set reminder if not done within 7 days

Files to Modify

• README.md - Schema, screenshots, marketing copy
• docs/screenshots/*.png - New screenshots
• GitHub issue to owner for docs deployment

Testing

• Run npm run lint - no errors
• Google Rich Results Test - all schemas valid
• README renders correctly on GitHub web
• All screenshot paths valid (no 404)

Priority

P0: SEO schema, docs publish request
P1: Screenshot refresh
P2: Auto-Combo marketing

Labels

enhancement, documentation, seo, marketing