Quickstart: Build Your Digital Presence

Before publishing, open the SEO tab in the right sidebar and click the magic-wand icon. AeionClaw reads your page structure and generates:

• Meta title (60-char target, keyword-aware)
• Meta description (160-char target, click-through optimized)
• OpenGraph image (auto-cropped from page hero or generated via AI)
• OG title + description (variants for social sharing)
• Schema.org JSON-LD (auto-detected: Article, Product, FAQPage, HowTo, etc.)
• Canonical URL (set automatically; override available)
• Keywords (extracted from page content + competitor analysis)

Continuous SEO monitoring: the AI re-analyzes pages weekly and surfaces:

• Pages where the title doesn't match search intent
• Pages missing structured data for rich snippets
• Pages with thin content (< 300 words on a topical landing page)
• Pages with broken internal/external links

Multi-language SEO via Aeion Localization — every translated page gets locale-appropriate title/description/keywords.

Build once, embed everywhere.

Global Patterns (Admin → Content → Layouts → Patterns):

• Save any block as a reusable pattern
• Embed the pattern on 100+ pages
• Update the pattern once → syncs to every embedding instantly
• Variants per locale / per site if needed

Common pattern use-cases:

• Hero banner with current promotion (update the promo, every page reflects it)
• Call-to-action footer (consistent across product, blog, support pages)
• Testimonial carousel (curated set of best testimonials, reused everywhere)
• Pricing summary (one source of truth, embed on pricing + landing pages)

typescript // Programmatically embed a pattern await aeion.api.patch(/v1/content/pages/${pageId}/blocks, { position: "after-hero", block: { type: "pattern", patternId: "pat_promotional_banner_q3", props: {/* per-instance overrides */}, }, });

A/B testing patterns — Marketing's built-in A/B testing engine runs across patterns. Test two CTA variants; let the engine pick the better-converting version.

Two paths to render your content.

Option A — Use the Aeion-hosted frontend (default). Aeion serves your pages directly at your configured domain. Zero developer involvement; SEO, performance, and CDN handled for you. Pages render server-side with React for fast first-paint + crawler-friendly HTML.

Option B — Bring your own frontend with the headless API. Fetch a page's block tree as JSON over Aeion's standard REST API and render it with your own components — no proprietary SDK to install:

bash # Fetch a published page by site + slug GET /api/v1/pages?where[site][equals]=corp-hq&where[slug][equals]=/pricing

```typescript // In Next.js getStaticProps / Astro server component / etc. const { data } = await fetch(pagesUrl).then((r) => r.json()); const page = data[0]; // page.blocks is an array of typed block configs ready to render

function renderBlock(block: { type: string; [key: string]: unknown }) { switch (block.type) { case "hero": return <Hero {...block} />; case "pricingTable": return <PricingTable {...block} />; // map every block type you use to your own component default: return null; } } ```

ISR / SSR / SSG — all rendering modes work, following your own framework's data-fetching conventions. Aeion sends content.page.published webhooks when pages change so your Next.js / Astro / Gatsby site can trigger a rebuild.