# Opinly Docs


- **Overview**
- [Opinly Docs](/docs): Publish your Opinly content in your own app, and measure what it earns.
- [Core concepts](/docs/concepts): How content flows from Opinly to your app: resolve, render, and SEO — and which package does what.

- **MCP connector**
- [MCP connector](/docs/mcp/overview): Connect Opinly to Claude and other MCP clients — a remote MCP server for SEO, content, and LLM-visibility workflows.
- [Tool reference](/docs/mcp/tools): Every tool exposed by the Opinly MCP connector, grouped by area, with its read/write behaviour.

- **Get started**
- [Sign up & get your API key](/docs/get-started/sign-up): Create an Opinly account and grab the API key + CDN namespace the SDK needs.
- [Quickstart](/docs/get-started/quickstart): Fetch a post and render it in under five minutes — the smallest possible integration.

- **Analytics**
- [Analytics](/docs/analytics): First-party visitor analytics — see which campaigns bring visitors, and which visitors turn into revenue.
- [Install the pixel](/docs/analytics/install): Add the Opinly pixel to your site — script tag or framework package — and confirm it's reporting.
- [What gets captured](/docs/analytics/what-gets-captured): Everything the pixel records on its own, what you have to send yourself, and where each event ends up.
- [Identify visitors](/docs/analytics/identify): Turn an anonymous ID into a known person, and carry that identity through to your backend.
- [Linking server events to browser visitors](/docs/analytics/server-events): How an order recorded on your server finds the anonymous browser visit that earned it.
- [Conversion goals & revenue](/docs/analytics/conversion-goals): Choose what counts as a conversion, and how revenue is attributed back to a campaign.
- [WordPress & WooCommerce](/docs/analytics/wordpress): Connect WordPress from the dashboard — the pixel and revenue tracking install themselves.
- [Pixel reference](/docs/analytics/reference): The window.opinly API, script tag attributes, package exports, and browser storage.

- **Frameworks**
- [Next.js](/docs/frameworks/nextjs): Add an Opinly blog to a Next.js App Router project — fetching, rendering, metadata, JSON-LD, sitemap and RSS.
- [Nuxt](/docs/frameworks/nuxt): Render your Opinly blog in Nuxt 3 — server-side fetch with useAsyncData, Vue rendering, and SEO via useHead.
- [SvelteKit](/docs/frameworks/sveltekit): Render your Opinly blog in SvelteKit — server load functions, Svelte rendering, and SEO via the OpinlySeo component.
- [React](/docs/frameworks/react): Use the Opinly SDK in any React app (Vite, CRA, Remix, Astro islands) — no Next.js required.
- [Vue](/docs/frameworks/vue): Use the Opinly SDK in any Vue 3 app — no Nuxt required.

- **Reference**
- [REST API (/v1)](/docs/reference/rest-api): The versioned HTTP contract behind @opinly/backend — endpoints, auth, pagination, and error shapes.
- [@opinly/backend](/docs/reference/backend-client): The typed data client — createOpinlyClient and every method it returns.
- [Events & tracking](/docs/reference/events): Send events with track(): standard events, custom events, and revenue.
- [Rendering content](/docs/reference/rendering): @opinly/shared's renderer — renderToHtml, createRenderer, the node/mark coverage, and customizing output.
- [SEO & structured data](/docs/reference/seo): Generate metadata and schema.org JSON-LD from resolved content, and feed it into your framework's head.

- **Operations**
- [Webhooks](/docs/webhooks): How to setup Opinly webhooks
- [Blog & image credits](/docs/billing): How Opinly credits work, why they're non-refundable, and how to manage your usage.