Site setups

Different sites ship differently.Start with who publishes live.

WordPress, Shopify, GitHub codebases, builders, and custom stacks can all work with AEOForged. The first question is simple: who can put the finished page on the production site?

Agent ships or proposes

Best when production access is clear: direct connector on WordPress or Shopify, or a review-gated PR path on GitHub.

Team publishes to production

Works on every platform. AEOForged can still score, draft, verify, and measure while your team handles the final publish step.

Repo-first handoff

For code sites, PRs and branch previews keep changes reviewable and stop one shared staging URL from becoming the source of truth.

Quick chooser

Who ships the finished page?

Pick the live-site publisher first. That one answer tells you whether AEOForged should connect directly, open a PR, or stay in propose-only mode.

Who can put a finished page on your live production site (not staging)?

Pick one option above to see the recommended working mode, any warning flags, and how each package behaves on that setup.

Common setups

The usual site shapes

These are the default working modes behind the chooser. Pick the setup that looks closest to yours and use it to decide whether the right next move is a connector, a PR flow, or a human publish path.

WordPress

AEOForged can connect via WordPress Application Password. Your agent drafts and scores in AEOForged; with ship permission it can apply through the connection. Prefer a personal or staging preview when your team shares one sticky preview URL.

Shopify

Connect with a store API token. Same pattern: measure and score in AEOForged; live apply only when you grant ship permission.

Code site on GitHub

Best agent path: GitHub pull requests (review-gated). Each PR can have its own preview so people stop fighting one shared staging site.

Code site, not on GitHub

Point work access at the git repo and deploy notes. AEOForged does not open GitLab/Bitbucket PRs today — your agent or team deploys, then we measure the live URL.

Builders (Webflow, Wix, Squarespace, Framer, …)

No first-party AEOForged apply connector for these. Retainers still work: agent writes and scores here; your team publishes in the builder; you give us the live production URL for social packs and measurement.

Headless / enterprise / custom CMS

Treat like a builder unless you also have a git repo we can use. Custom CMS is not the same as a Rebuild package — Rebuild is a quoted replatform onto connectable infrastructure, and maintenance after handoff is named separately.

Shared staging / one preview

If everyone shares one staging URL, collisions are normal. Prefer per-change previews (PRs). Never use a staging URL as the Grow/Dominate delivered article URL — production only.

AI crawlers can’t read the site

Measurement retainers can still watch answer engines. On-site fixes need Fix Programme (you/agent apply) or a quoted Foundation / Rebuild path — Grow does not unblock a blocked crawl by itself.

Honesty strip

Connectors today are WordPress, Shopify, and GitHub only.

Other platforms still work with AEOForged, but publishing happens through your team or through git if you have a repo.

Retainers do not require a connection. They can run as measured drafts, content picks, social packs, and live verification against the production URL.

Foundation and Rebuild are quoted we-apply or replatform paths, not instant self-serve connectors.

Next step

Choose the path that fits how your site really ships

Start the diagnostic yourself, hand the setup to your agent, or compare the package paths before you decide who should publish each cycle.

Start with your site Set up your agent See package paths