This is a narrative example with realistic (fictional) values, to show how the pieces from this guide fit together in practice. Every screen, button, and field named here is real — only the specific website and numbers are illustrative.

​
The scenario

Acme Clinic is a healthcare practice with a website, acmeclinic.example, that hasn’t had any dedicated SEO attention. Priya, their marketing coordinator, has just been given a MAEL login by the agency managing their account.

​
Day 1: Getting oriented

Priya logs in at the URL her agency gave her (see Login). Since she’s a regular team member, not a platform administrator, she lands straight on Overview — empty for now, since nothing has run yet. She checks Settings and sees acmeclinic.example already listed — the agency’s administrator added it and connected Google Search Console before handing off the account. She asks the administrator for the domain’s ID and gets: f47ac10b-58cc-4372-a567-0e02b2c3d479 (see Start Here → Step 4 for why this step exists).

​
Day 1: First workflow — a safety check

Before touching content, Priya runs the safest possible workflow: technical-audit. She opens the trigger dialog (⌘K → “Trigger a workflow”), types technical-audit, and enters:
Ten minutes later, the run completes. The findings: two broken internal links, a slow-loading images page, and one article missing structured data. Nothing urgent, but useful to know. She notes them for the agency’s web developer and moves on.

​
Day 2: Finding what to write about

Next, Priya runs keyword-gap-analysis to find a real opportunity rather than guessing:
The result includes a gap: “migraine treatment options” — a topic competitor clinics rank for that Acme Clinic doesn’t cover at all, with a strong gap score. That’s the target.

​
Day 2: Generating the content

Priya triggers full-content-pipeline:
She sets publish_mode to draft deliberately — her first time through this workflow, she wants to be extra sure nothing goes live without her reading it first, even though the approval gate would have stopped it either way. She opens the run and watches the execution timeline: keyword research, SERP analysis, competitor research, an outline, then the writer — and because this is medical content, the medical-fact-checker step runs too (it’s automatically skipped for non-medical topics, but this qualifies). Four review agents run in parallel. Twelve minutes later, the run’s status changes to waiting_approval.

​
Day 2: Reviewing before it goes live

Priya gets a badge on Approvals. She opens the card:
  • SEO score: 84 (green — strong)
  • Readability score: 76 (yellow — acceptable, could be tighter)
  • The draft itself, right there in the card
She reads it in full — this is medical content, so she’s especially careful, per Take Action’s warning about YMYL content. It reads accurately and matches the clinic’s tone. She adds a comment, “Verified against Dr. Chen’s notes — approved,” and clicks Approve.

​
Day 2: It publishes

The workflow resumes and completes. The article now shows published in Content Studio, with a live link. Priya clicks through to confirm it looks right on the actual site.

​
Weeks later: Measuring the result

Two weeks in, Priya checks Analytics for acmeclinic.example, 30-day range. The new article is showing impressions and a handful of clicks — early, but real. Average position is around 18 and trending down (remember: on this chart, down is good — see Understand Your Results).

​
A month later: Maintaining it

Six weeks after publishing, position has plateaued instead of continuing to improve. Priya finds the article in Content Library, notes its article ID, and triggers content-refresh:
The assessment step decides a light refresh is warranted, revises a section, and the whole thing goes through the same review-and-approve cycle again before republishing.

​
What this example shows

Research before writing

keyword-gap-analysis found a real opportunity instead of guessing.

Nothing publishes unsupervised

A human read and approved the draft before it went live — every time.

Results are real, not simulated

Analytics numbers come straight from Google, weeks after the fact — SEO takes time, and MAEL doesn’t pretend otherwise.

Maintenance is a workflow too

content-refresh closed the loop once performance plateaued.