How to connect your CMS

Supported platforms

WordPress setup (step by step)

WordPress is the most common CMS we see. The connection uses the built-in REST API, authenticated with an Application Password. No plugins required.

1. Generate an Application Password

1. Log in to your WordPress admin at yourdomain.com/wp-admin
2. Go to Users → Profile (or the profile of a user with Editor or Administrator role)
3. Scroll down to the Application Passwords section
4. Enter a name like Aeonic and click Add New Application Password
5. Copy the generated password immediately -- WordPress only shows it once

The Application Passwords feature is built into WordPress 5.6+. If you don't see it, your host or a security plugin may have disabled it. Check with your hosting provider.

2. Enter credentials in Aeonic

1. In Aeonic, go to Settings → Plugins → WordPress
2. Enter your Site URL (e.g. https://yourdomain.com)
3. Enter your WordPress Username (the account that owns the Application Password)
4. Paste the Application Password you copied
5. Click Connect. Aeonic will test the connection by calling /wp-json/wp/v2/users/me to verify your credentials work.

3. What Aeonic can publish to WordPress

• Meta titles -- updates the post title and Yoast SEO title
• Meta descriptions -- updates Yoast SEO meta description
• Schema markup -- adds JSON-LD to post meta or appends to content
• FAQ sections -- appends FAQ HTML + FAQPage schema to post content
• New pages -- creates and publishes a new WordPress page
• Content refreshes -- updates the body content of an existing post or page

Shopify

Aeonic connects via the Shopify Admin API (version 2024-01).

What you need

• Store URL -- your yourstore.myshopify.com domain
• Admin API access token-- create a custom app in Settings → Apps → Develop apps. Grant write_content, write_products, and write_articles scopes.

Aeonic can update meta titles, meta descriptions, and schema on pages, products, and blog articles. It can also create new pages and append FAQ sections.

GitHub Pages

The GitHub integration uses OAuth -- click Connect GitHubin Settings → Plugins, and authorize Aeonic. No tokens to copy.

How it works

Aeonic commits files directly to your repository using the Git Trees API. Each publish creates a single commit with the new or updated content (both Markdown and HTML versions). This works with any Git-based host: GitHub Pages, Vercel, Netlify, or Cloudflare Pages.

What you need

• A GitHub repository with Pages enabled (or auto-deployed by Vercel/Netlify)
• The repo must be publicly accessible and indexable for AI citation to work
• Branch defaults to main -- configurable after connection

Webflow

What you need

• API Key-- generate in Webflow Dashboard → Account Settings → Integrations
• Site ID -- found in your project settings under General
• Collection ID (optional) -- if you want to publish to a specific CMS collection

Vercel

What you need

• Vercel API Key-- generate in Vercel Dashboard → Settings → Tokens
• Project ID -- found in project settings
• Team ID (optional) -- required if the project belongs to a team
• Git credentials -- Aeonic pushes content to your Git repo, which triggers a Vercel auto-deploy. You can specify the repo owner, name, branch, and content directory (e.g. content/blog)

What "one-click publish" does

When Aeonic generates a fix (a new meta description, schema markup, or FAQ section), you see a preview with the proposed change. If your CMS is connected, you get a Publish button that pushes the fix live in one step.

Behind the scenes, Aeonic creates an action record with the proposed change, then calls the appropriate adapter (WordPress REST API, Shopify Admin API, GitHub Trees API, etc.). If publishing succeeds, the action is marked as published with a timestamp and the live URL.

Every published change is logged and rollback-capable. If something goes wrong, you can revert from the action log in your dashboard.

What happens after publishing

When content is published, Aeonic automatically runs a full discoverability pipeline:

1. BlogPosting schema injection — JSON-LD structured data is embedded in the published HTML so AI crawlers can understand the content type, headline, date, and author.
2. IndexNow submission — The published URL is immediately submitted to Bing and Yandex via IndexNow for near-instant indexing. No waiting for the next crawl cycle.
3. Sitemap inclusion — The URL is automatically added to your sitemap.xml, which Google and AI crawlers use to discover new pages.
4. Attribution tracking — Aeonic records the publish event so you can measure its impact on AI citations over time via the dashboard.

Troubleshooting