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 content in a Server Component with a regular fetch and revalidate, keep your App Router and your components. Editors change texts and images on the live site, not in a separate admin panel.
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 menuNext.js already caches and revalidates fetch requests, so a CMS does not need its own client library, a GraphQL layer or generated types to fit in. It needs a fast API and a predictable JSON shape.
Sitecog is exactly that: a REST endpoint per page, cached responses with an ETag, and on-page editing that works on your rendered Server Components.
A regular fetch with next: { revalidate: 60 } in a Server Component. The key lives in process.env and never reaches the browser.
When the site is open in the CRM, the URL carries crm_live=1 — skip the cache for that request and editors see their change at once.
data-crm-text and data-crm-image on the elements that render blocks. One frame-ancestors header lets the CRM open the site.
Pass the locale from your route: ?lang=de,en returns the language and the fallback in one response.
Structured content for landing pages plus a blog API for articles with their own covers and texts.
Even if it leaks to the client, the key only reads one site’s published content.
CRM_KEY in .env.local for Server Components; NEXT_PUBLIC_CRM_KEY only if client code also fetches.
One request per page with revalidate. Render the blocks with your own components.
The widget script in the root layout, data-crm-* attributes on the elements and the frame-ancestors header in next.config.js.
// app/page.tsx — a Server Component: the key stays on the server
const API = 'https://back.sitecog.com/content';
export default async function Home() {
const res = await fetch(API + '/v1/pages/home?lang=en', {
headers: { 'x-crm-key': process.env.CRM_KEY! },
next: { revalidate: 60 }, // ask the API at most once a minute
});
if (!res.ok) throw new Error('Content API: ' + res.status);
const page = await res.json();
const hero = page.content.hero.content;
return <h1 data-crm-text="hero_title">{hero.hero_title.content.en}</h1>;
}
// app/layout.tsx — once: <script src="https://widget.sitecog.com/widget.js" defer /> before </body>
// next.config.js — let the CRM open your site in Live mode
module.exports = {
async headers() {
return [{
source: '/:path*',
headers: [
{ key: 'Content-Security-Policy', value: "frame-ancestors 'self' https://sitecog.com" },
],
}];
},
};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.
Both. The examples use the App Router and Server Components; in the Pages Router make the same request in getStaticProps or getServerSideProps.
With revalidate: 60, visitors see an edit within about a minute. While an editor is working, the page is opened with crm_live=1 — fetch with cache: no-store for that request and the change shows immediately.
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.
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.
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 an edit appears after the next build — there are no webhooks yet to trigger it automatically. For instant edits, keep the pages rendered on the server with revalidate.
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