How SEO Smooth made Respira the backbone of its WordPress delivery

Who they are

SEO Smooth is an agentic AI agency in South Florida. They run client WordPress sites the way an operations team would: pages get built, titles get fixed, menus get restructured, images get optimised, content gets cleaned up, every week, across many installs.

In June 2026 they published their own review of Respira, unprompted. This case study is built from that review. Their words are quoted as written; their reservations are kept.

What Respira is, in their words

“Not another chatbot that spits out HTML you paste in by hand. A plugin plus a Model Context Protocol layer that gives an AI assistant structured, permissioned access to your real WordPress install.”

— SEO Smooth

The thing they weighed Respira against was the plain WordPress MCP server. Their finding was about aggregation: Respira “reads the Abilities API from every installed plugin and rolls them all into one MCP server”, so the assistant sees the whole site, not a handful of core actions.

“One server, every plugin's powers, builder-native output. That is the real unlock.”

— SEO Smooth

How the work runs

Risky work goes through the duplicate-first path: the assistant builds or edits a staged copy, the agency reviews it, and only then does it touch the live page. Every write takes a snapshot first, so a bad edit is one call away from undone.

“Risky work is routed through a duplicate-first workflow, so the AI builds or edits a staged version before anything touches the live page. Pre-edit snapshots mean you can roll back instantly.”

— SEO Smooth

The output stays in the builder's own format. Their example: “A Divi build comes back as real, editable Divi modules.” A human can open the page in the builder afterwards and keep working, which is the whole point for an agency that hands sites back to clients.

Where it shines

“For an agency, the speed is the headline. Building service and location pages, fixing SEO titles and descriptions, restructuring menus, optimizing images, and cleaning up content all happen at a pace manual editing cannot match.”

— SEO Smooth

The work “stays editable by a human afterward” and, in their words, Respira “has quietly become a backbone of how we deliver.”

The honest limitations

They named three, and they are all true today:

• One site context at a time. Switching sites is deliberate, not parallel. The dashboard and the site_id argument make the switch explicit; they do not remove it.
• Verify your writes. On heavily cached hosts a write can look stale until the cache clears. The activity log and the write receipt show what actually happened.
• Solo-founder pace. Rough edges appear now and then. Their observation was that fixes land quickly, usually within days of a report.

“None of these are dealbreakers for us.”

— SEO Smooth

Their verdict

“If you run WordPress and want an AI editor that respects your real site, Respira is where we point people.”

— SEO Smooth

They called it one of the best value tools in their stack. Current plans are on the pricing page; agencies usually land on Builder or Studio.