[leoisadev1]

Summary

Adds /guides/social-media-apis, a guide to the three ways a developer can post to social networks from code: each platform's own API, a unified social media API, or an open-source library. It lists what each platform (X, Bluesky, Threads, Instagram, LinkedIn, TikTok, YouTube) requires before you can post and its main limit, names the unified providers and schedulers neutrally, and ends with a tested Social SDK sample. It targets "social media api" (260/mo, KD 17, SE Ranking via treg), plus "social media posting api" (40) and "social media scheduling api" (30). The current top 10 is vendor list posts that rank their own product first, with no native-API rules, sources or code.

It also adds a Guides link to the homepage footer. Search Console shows all five guides as "Discovered - currently not indexed" (inspected 2026-10-30), and the homepage, the only well-indexed page, didn't link to /guides.

Evidence

• Facts: the Instagram (100 API posts per 24 h, updated 20 Oct 2026), LinkedIn (w_member_social, w_organization_social with Page roles), TikTok (private until audit) and YouTube (100 videos.insert a day) rows were read from each platform's own docs on 30 October 2026. The X, Bluesky and Threads rows summarise our existing guides. Provider lines quote each provider's own home page. The page lists no prices or user counts.
• Sample: type-checks against @opencoredev/social-sdk 0.5.0 from npm (strict). With a stub fetch on Node 24, it made one POST https://api.x.com/2/tweets and one createRecord to bsky.social and printed x published and bluesky published.
• Wiring: first on /guides, in the sitemap (81 URLs, dated by this commit) and llms.txt, with one-line links from /docs/platforms and /docs/backends. The sitemap-dates test now covers the new guide.
• Checks: lint, format:check, check-types, docs test (12 pass), validate, build, audit (0 errors, 0 warnings), rebrand:check, and release:ci ("all deterministic release checks passed"). After the review fixes (copy only), lint, format, build and audit were rerun and passed.
• Render: opened from the built site with agent-browser at 1440 and 390 px. Tables fit on mobile, only code blocks scroll, and the footer shows Guides between Blog and Brand at both widths. The built HTML has the title (40 chars), description, canonical, TechArticle and BreadcrumbList JSON-LD.
• Review: GPT-6.1 Sol flagged two issues. First, the page said unified providers always own the platform apps, but some take customer apps for certain networks. Second, "swap a managed backend and the call stays the same" ignored provider account references and requirements. Both are fixed. It found no SEO, link or duplicate-content problems.

Evaluation: the new page on 2026-11-23 (24 days after deploy), and the footer link on 2026-11-16 (guide indexing).

Merge Danger

Door: two-way. Docs-site content and one footer link, and a revert removes both.

Blast radius: social-sdk.dev /guides, /guides/social-media-apis, the homepage footer, /docs/platforms, /docs/backends, the sitemap and llms.txt. No package, release or npm changes.

Fixes SOCM-13

Created with Claude Opus 5.5 in Claude Code (T3 Code).

🤖 Generated with Claude Code

---

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
docs	Ready	Preview	Oct 30, 2026 12:03pm UTC

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

[capy-ai]

Capy found no issues.

[greptile-apps]

Confidence Score: 5/5

[Low impact] The PR appears safe to merge.

Summary

Adds /guides/social-media-apis, comparing native APIs, unified providers, and libraries, with a TypeScript publishing example.

• Developers can compare three ways to post to social networks in one guide.
• Readers can find the guide from the homepage and related docs.

_{Reviews (1) · Last reviewed commit: "docs(seo): qualify provider app ownershi..." · Reviewed by Greptile}