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
Load a page with useFetch in Nuxt or fetch in plain Vue, render it in your own components, and let editors change texts and images on the live site. No module to install, no schema to sync.
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 Nuxt or Vue site has its own components, layouts and routing. A CMS should add content to it, not a second framework: a module, generated types, a build step of its own.
With Sitecog the content arrives as JSON from a REST API, and editing happens on top of your rendered templates — the same site visitors see.
In Nuxt — useFetch with the key from runtime config, rendered on the server. In plain Vue — fetch in onMounted. No module needed.
data-crm-text and data-crm-image on the elements that show blocks. Editors click them on the live site and save.
Pass the current locale: ?lang=de,en returns the language and its fallback in one response.
Page → section → block: texts, images, videos, lists and objects map onto components one to one.
Cache-Control and an ETag on every response — Nuxt’s own caching and the API’s work together.
Safe in public runtime config: it reads one site’s published content and nothing else.
NUXT_PUBLIC_CRM_KEY in Nuxt, or a VITE_ variable in a plain Vue app.
One request with the key in the x-crm-key header. Render the blocks in your components.
The widget script once, data-crm-* attributes on editable elements and a frame-ancestors header for Live mode.
<!-- pages/index.vue (Nuxt) -->
<script setup lang="ts">
const config = useRuntimeConfig(); // NUXT_PUBLIC_CRM_KEY → config.public.crmKey
const { data: page } = await useFetch('https://back.sitecog.com/content/v1/pages/home', {
query: { lang: 'en' },
headers: { 'x-crm-key': config.public.crmKey },
});
const hero = computed(() => page.value?.content.hero.content);
</script>
<template>
<h1 data-crm-text="hero_title">{{ hero?.hero_title.content.en }}</h1>
</template>
<!-- plain Vue: the same request with fetch() in onMounted.
Once per page, 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 it is not needed: useFetch already handles server rendering, caching and hydration for a plain JSON API.
Yes. Make the same request with fetch in onMounted or in your data layer. Only the place of the request changes.
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 content is fetched at build time then, so edits appear after the next build — there are no webhooks yet to trigger one automatically. For instant edits, render on the server or fetch in the browser.
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