Initial sync, verification and day-to-day use

Mirror your existing content, confirm the connection is healthy and start publishing.

14. Initial sync

  1. 1On the connection card, click Sync now.
  2. 2AI Explorer Media reads your documents through the connector and mirrors them into the content workspace.
  3. 3Bodies, statuses, taxonomy, featured images and metadata are mapped through the schema mapping — your source rows are not modified.

The first sync is read-only

Nothing is written back to your project until you save an edit from AI Explorer Media.

15. Verify the connection

  • Connection health shows Healthy with a recent successful check.
  • The document count matches what you expect in your project.
  • Open one document — the body renders as formatted content, not raw markup.
  • Make a small edit and save: the status should reach Synced after read-back verification.

Every write is verified by reading the row back and comparing the fields that were sent. A save is only reported as Synced when your project confirms the stored result.

16. Start managing content

  • Draft, edit and publish using your project's own status vocabulary.
  • Attach featured images and media where your schema supports them.
  • Manage categories and tags declaratively — attaching terms never rewrites the body.
  • Edit SEO and GEO metadata as separate fields, so a metadata save cannot touch content.
  • Restore an earlier version when revision history is available; restores are additive.

Two-way sync

Edits made directly in Supabase flow back into AI Explorer Media. Changes AI Explorer Media made itself are recognised and never re-applied, so there are no echo loops.