CMS integrations
effectly.ai writes natively to your CMS. No JavaScript injection. No pixel scripts. We connect via REST API, SSH, or Git. Your content lives in your systems. Cancel your subscription — the changes stay.
Model A — REST API (Tier 1)
Covers WordPress, Contentful, Sanity, Webflow, and Shopify. We use Application Passwords for WordPress (built into WP 5.6+, no plugin needed). API keys for headless CMSs. We write title tags, meta descriptions, schema JSON-LD, canonical URLs, Yoast/RankMath meta, new posts, and slug rewrites. Editor role only — we never hold master admin passwords. You revoke access from your own dashboard.
Model B — SSH (Tier 2)
Covers WordPress on VPS, custom PHP CMS, Laravel, custom Next.js sites. We use scoped SSH keypairs. You add the public key to ~/.ssh/authorized_keys with a command= restriction — we execute only the wrapper script, no open shell. We write theme files, functions.php, template files, real PHP/template code. Path-restricted to /var/www/site/ only. No sudo.
Model C — Git/GitHub (Tier 3)
Covers Next.js, Vercel, Netlify, Cloudflare Pages, any Jamstack/headless site. We use fine-grained GitHub Personal Access Tokens — contents:write on target repo only. Flow: clone → branch → commit → PR with description of every change + expected score delta → CI runs Lighthouse + schema validation → auto-merge if all checks pass. Production is never touched until the PR merges. Full audit trail. Safest model.
What each CMS gets written
| CMS | What effectly.ai writes |
|---|---|
| WordPress | functions.php, Yoast meta via API, theme templates |
| Headless CMS | Content entries via API, schema.org JSON-LD, slug rewrites |
| Next.js / Vercel | metadata.ts files, sitemap.ts, robots.txt, hreflang |
| Shopify | Liquid templates, product meta via API, structured data |
Our MCP server runs in our cloud (Railway). Never on your server. No JS injection ever. Custom or legacy CMS? We say "give me the credentials" — we support REST, SSH, and Git.