Trial
- Websites
- 1
- Pages
- 3
- Blocks
- 100
- Languages
- 2
- File storage
- 50 MB
- Auto-translation characters
- 10,000
- Content and live editing
- Auto-translation into other languages
- Dashboard, files, team members, activity log
Fetch content with one request, render it in your own components, and let editors click a heading on the live site to change it. No SDK, no schema files, no rebuild of your app.
We give you a REST content API, not a site builder. Your developer builds the site on any stack, and text, images and lists come from the CRM with a plain GET request. A page, a section or a single block arrives as JSON keyed by your own markers; blog posts come as a list.
Roasted fresh every morning
View menuA React app already has its components, its routing and its build. What it lacks is a place where non-developers change texts and images without a pull request. Most headless CMSs give you that place — as a separate admin panel full of forms that look nothing like the site.
Sitecog gives you the API and the place in one: content comes from a REST API as JSON, and the same content is edited right on top of your rendered React components.
Vite, Create React App, Remix or your own build: one request returns the whole page as JSON. No SDK to install and keep up to date.
Add data-crm-text or data-crm-image to the element that renders a block. Editors see your real UI, click and save.
A page is a set of sections, a section is a set of blocks: texts, images, videos, lists, objects. It maps naturally onto components.
Every text block holds its translations. Ask for ?lang=de,en and fall back when a translation is missing.
Responses carry Cache-Control and an ETag: unchanged content is answered with 304 and costs almost nothing.
The public key is read-only and works only for one site’s published content — fine to ship in a client bundle.
Add your site in the CRM and create a page with its sections and blocks.
One request with the public key in the x-crm-key header. Render the blocks with your own components.
Add the widget script once and data-crm-* attributes on the elements editors should change.
// Hero.jsx — a client component (Vite, CRA, anything)
import { useEffect, useState } from 'react';
const API = 'https://back.sitecog.com/content';
const KEY = import.meta.env.VITE_CRM_KEY; // public key, fine in the browser
export function Hero() {
const [hero, setHero] = useState(null);
useEffect(() => {
fetch(API + '/v1/pages/home?lang=en', { headers: { 'x-crm-key': KEY } })
.then((res) => res.json())
.then((page) => setHero(page.content.hero.content));
}, []);
if (!hero) return null;
return <h1 data-crm-text="hero_title">{hero.hero_title.content.en}</h1>;
}
// index.html — once, right before </body>
// <script src="https://widget.sitecog.com/widget.js" defer></script>Visual editing the way it should work: open your website in the CRM, click a heading, price or image and change it right on the page. No clunky admin forms: a developer connects the site once, and after that every edit is yours.
Made to order and delivered nationwide in 5 days. 10‑year warranty.

−20%


Pick a language from the list and the CRM translates the texts on your pages in the background with Google Translate. Your site stays live the whole time: until the translation is ready, the new language shows a copy of the original.
No, and you do not need one. It is a plain REST API that returns JSON: one fetch per page, the same in any framework.
Yes. It is an HTTP API: call it wherever you load data — in an effect, a loader or on the server. For Next.js there is a separate page with a Server Component example.
Every element that shows content from the API and carries a data-crm-text, data-crm-image or data-crm-array attribute. Hard-coded text stays code: the editor will not save it. The editor itself loads only when the site is opened inside the CRM — visitors never download it.
Yes. The pk_… key is public and read-only: it can fetch the published content of one site and nothing else. Send it in the x-crm-key header, never in the URL, so it does not end up in proxy logs and browser history.
Responses are cached for 60 seconds and carry an ETag, so unchanged content costs almost nothing. The limits are 300 requests a minute from one IP and 600 a minute per site key — with caching on your side, a normal site never gets close.
The responses are plain JSON with a documented shape: page → sections → blocks, each block with its type and content. Describe the parts you use with your own types.
Every account starts on the Trial: your website, on-page editing and auto-translation. Basic adds leads from forms, live chat, the blog and site traffic; Pro adds the rest of marketing.
| Plan | Trial | Basic | Pro |
|---|---|---|---|
| Limits | |||
| Websites | 1 | 3 | 10 |
| Pages | 3 | 20 | 200 |
| Page sections | 30 | 300 | 3,000 |
| Blocks | 100 | 1,000 | 20,000 |
| Languages | 2 | 5 | 20 |
| File storage | 50 MB | 2 GB | 20 GB |
| Auto-translation characters | 10,000 | 220,000 | 590,000 |
| Team members per website | 2 | 5 | 20 |
| Blog posts | Not included | 100 | 1,000 |
| Ad links | Not included | Not included | 500 |
| Forms and events | Not included | Not included | 100 |
| Features | |||
| Content editing | Included | Included | Included |
| Live editing on the page | Included | Included | Included |
| Auto-translation | Included | Included | Included |
| Leads from website forms | Not included | Included | Included |
| Live chat with visitors | Not included | Included | Included |
| Blog | Not included | Included | Included |
| Marketing analytics | Not included | Included | Included |
| Visitor accounts on your website | Not included | Not included | Soon |
Sign up and the Trial is yours: 7 days free. Connect your website — once it’s set up, edit it right on the page. Leads, live chat and analytics come with paid plans.
Have a question first? Talk to us