PHASE 01

Getting Started

From zero to your first Strata-deployed article in under five minutes. No agency. No developer. The engine handles the rest.

01Create your Strata account

Navigate to /onboarding and complete the 4-step wizard. You will need a business email address and your primary website URL. Your first two deployments are included at no cost (no credit card is required to start).

⚡

Note: If you arrived from the landing page URL input, your domain is pre-filled. Continue through the wizard to proceed.

02Connect your domain (GSC verification)

Strata reads your Google Search Console data to detect impression velocity and average position changes. To connect:

Go to Google Search Console

Navigate to search.google.com/search-console. Add and verify your property if you haven't already.

Generate a verification token

In your Strata Dashboard → Settings → Integrations, click "Connect GSC". Copy the verification code shown.

Paste token into GSC

In GSC → Settings → Users and permissions → Add user. Paste the Strata service account email and grant Read permissions.

ℹ

GSC data has a 48-hour reporting lag. Your telemetry panel will show "Awaiting data" for the first 2 days after connection.

03Add your competitor URLs

The Extraction Pipeline requires at least one competitor URL to run. You can add up to 5 competitors per account. Go to Dashboard → Competitors → Add URL and paste the root domain (e.g. competitor.com, no trailing slash, no protocol).

INPUT	VALID?	NOTE
competitor.com	✓ Yes	Preferred format
https://competitor.com	✓ Yes	Protocol stripped automatically
competitor.com/blog	⚠ Partial	Crawl limited to /blog subtree
competitor.com/page-1	✗ No	Use root domain only

04Run your first extraction

With at least one competitor added, click "Run Extraction" in the Dashboard. The pipeline scans your competitors' sitemaps, extracts their ranking entities, and cross-references against your indexed content to identify unclaimed gaps.

LOG strata://engine : vampire.log

[14:02] Fetching sitemap: competitor.com/sitemap.xml [14:02] Discovered 847 indexed URLs [14:03] Extracting entities from top 200 ranking pages... [14:05] Gap matrix built. Your unclaimed intents: 47 [14:05] Brief queue populated. Engine ready to publish.

05Review your first article batch

After extraction, the engine queues your first batch of articles for review. Go to Dashboard → Content → Pending to read each draft. You can Approve (deploy immediately), Edit (open in editor), or Reject (remove from queue). Approved articles are pushed to your CMS within 60 seconds.

⚠

Important: Enabling auto-deploy authorises the engine to publish without per-article review. Review the Autonomous Deployment clause in Terms of Service before activating.

PHASE 02

Integrations

Connect Strata to your CMS. The engine deploys articles directly, without manual copy-paste or CMS logins.

WFConnecting Webflow

Strata deploys to Webflow via the CMS Items API. You need a Site-level API token with CMS read/write access.

Open Webflow Site Settings

Go to your Webflow site → Site Settings → Integrations → API Access.

Generate API token

Click Generate API Token. Set scope to: CMS: read & write. Copy the token.

Paste into Strata

Dashboard → Settings → Integrations → Webflow. Paste your token and select the target Collection.

WPConnecting WordPress

Strata uses the WordPress REST API to create posts. You need an Application Password (WordPress 5.6+).

CONFIG Dashboard → Settings → Integrations → WordPress

Site URL: https://yoursite.com Username: your-wp-username App Password: xxxx xxxx xxxx xxxx xxxx xxxx Post Status: draft | publish (choose "draft" to review first) Default Author: your-wp-user-id

NXConnecting Next.js

For Next.js sites, Strata pushes content via a webhook endpoint you add to your project. Add this API route:

TS src/app/api/strata-deploy/route.ts

import { NextRequest, NextResponse } from 'next/server' export async function POST(req: NextRequest) { const secret = req.headers.get('x-strata-secret') if (secret !== process.env.STRATA_WEBHOOK_SECRET) { return NextResponse.json({ error: 'Unauthorized' }, { status: 401 }) } const { slug, title, content, schema } = await req.json() // Write to your content layer (MDX, Contentlayer, etc.) // Then revalidate the path: // revalidatePath('/blog/' + slug) return NextResponse.json({ ok: true }) }

STRStripe Attribution Setup

To track which articles drive revenue, pass the Strata article ID to your Stripe Checkout Session as a metadata parameter.

JS Add to your Stripe session creation API

const session = await stripe.checkout.sessions.create({ payment_method_types: ['card'], line_items: [{ price: 'price_H5gg...', quantity: 1 }], mode: 'subscription', metadata: { ref_article: articleId // e.g. "1042" — captured from URL parameter }, success_url: 'https://yoursite.com/success', cancel_url: 'https://yoursite.com/cancel', })

Strata reads this field from Stripe webhooks and attributes the transaction to the source article automatically. Revenue appears in Dashboard → Revenue Attribution within 2 minutes of a successful payment.

PHASE 03

Dashboard Guide

Reading the data your engine generates and knowing when to act on it.

📊Reading your Telemetry panel

The Telemetry panel displays live GSC data for all Strata-deployed assets. Key metrics:

METRIC	WHAT IT MEANS	TARGET
Impressions	Times your articles appeared in search results	+40%/month after Day 30
CTR	Click-through rate on impressions	>4% for target queries
Avg. Position	Average rank for your target query cluster	<10 within 60 days
AI Citations	Confirmed citations in Google AI Overview / Perplexity	1+ per pillar cluster

$Understanding Revenue Attribution

Revenue Attribution shows the total Stripe revenue (in USD) attributed to each Strata article. An article is credited when a buyer visits it and completes a Stripe transaction within the same session (tracked via the ref_article metadata parameter). Attribution window: 30 days (last-touch).

💡

Note: Articles with high impressions but low attributed revenue indicate a conversion gap. The content is capturing intent but not closing it. Flag these for a CTA review.

⚡Compute Credits & Node Limits

Each active node includes a monthly credit allocation. A full autonomous cycle (competitor scanning, research, LLM draft expansion, and L2 anchoring) consumes approximately 2,120 credits. If your compute balance runs low, you can buy credit packs directly or enable Auto Credit Top-Up. On Growth Architect and Master Architect tiers, capacity can be expanded dynamically.

TIER	CREDIT CAPACITY	DEPLOYMENTS
Foundation Node	35,000 credits/mo	15 per month
Growth Architect	150,000 credits/mo	50 per month
Master Architect	Custom SLA	Unlimited

STRATA SUPPORT

Need help? Ask Aria.

Aria is our intelligent support inbox. For technical questions, integration issues, or account queries, reach out directly.

aria@aeostrata.com help@aeostrata.com