Core ConceptsMurmur: Review Links, Request Links and Split Tests

Murmur: Reviews, Requests and Split Tests

Murmur links let clients review work in progress, request changes on a live site, and compare page versions with split tests, all without a WordPress login.

What Murmur is

A Murmur link is a signed address to a WordPress site. The person who opens it needs no login. A small bar appears on the page, they click the spot they mean and write a note. The note reaches you, and your AI app can read it and act on it.

Nobody who opens a Murmur link can change the site. A note is a note: it changes nothing until you or your agent apply it on a draft and you approve the draft.

Murmur is part of the Builder plan and up. It also runs split tests: two versions of one page, shown to half the visitors each.

Review linkRequest link
ForWork in progress: a page or a staging site you want comments onThe live site after launch: a link your client keeps
CoversOne page, several pages, or the whole siteThe whole site
EndsAfter 14 days by default, 90 at mostNever, until you revoke it
The bar saysleave a commentrequest a change
NeedsAny plugin version with MurmurRespira plugin 9.1.16 and MCP server 8.4.14

Ask your AI app:

Make a Murmur request link for this site, labelled "Atelier Popescu, changes".

The agent calls respira_create_review_link with kind: "request" and gives you the address. Send it to your client. One link per label: asking again with the same label returns the same link, unless you revoked it.

In Respira AER, type the same sentence in the chat.

What your client sees

  1. They open the link. The site looks as it always does, with a small bar at the bottom that says request a change.
  2. They press it and click the spot the request is about.
  3. They write what should change, with their name and, if they want a reply, an email.
  4. After sending, the bar says the request reached the people who look after the site.

They can also see the requests already made on that page and whether each one is done.

What you get

  • The request appears in your dashboard under Murmur.link, in the Inbox, marked as a request, with the page and the spot.
  • The first request on a link sends you an email. Later ones on the same link arrive in an hourly digest.
  • In Respira AER, the /reviews card lists open notes and requests by page.
  • Your agent reads them with respira_list_review_comments (pass kind: "request" to list only requests), applies each one on a draft of the page, and marks it resolved. You approve the draft before anything is live.

Limits and safety

  • A request link shows published pages only. No drafts, no editor, no settings.
  • One person can send up to 10 requests in 10 minutes, and one link accepts up to 30 an hour from everyone together.
  • A request holds up to 2,000 characters.
  • Revoke a link at any time: ask your agent to revoke it, or use the Feedback screen in wp-admin. A revoked link stops working at once.
  • Someone logged in as an editor of the site is never treated as a reviewer.

Split tests

A split test shows two versions of one page to real visitors and counts which one brings more enquiries. It uses the same machinery as a review link: a draft is shown to someone who is not logged in, at the page's own address. The difference is who sees it. A review link shows the draft to one person who leaves notes. A split test shows it to half the visitors and counts what they do. See it on the Murmur page.

  • A is the published page, as it is now.
  • B is a draft copy of that page, made by Respira and changed by your agent.

Split tests need Respira plugin 9.2.28 and MCP server 8.7.1, or later, on the Builder plan and up.

Start one

Ask your AI app:

On the Contact page, try a shorter form and a bigger phone button against the page that is live now. Count the thank-you page and phone taps.

The agent makes a draft copy of the page with respira_create_page_duplicate, changes the copy, and starts the test with respira_start_split_test. It tells you what counts as a win, when the test is planned to end, and what was done about the site's caches. The live page does not change.

If the page has one open draft copy, the agent can leave B out and that copy is used. If it has several, the agent asks you which one is B.

In Respira AER, type the same request in the chat.

When you start a test you choose:

  • The win. The thank-you page a visitor reaches after sending the form (an address on the same site, not the home page), a tap on a phone number link on the tested page, or both. Phone taps are counted unless you turn them off.
  • How long. 1 to 90 days, 14 by default. This is a plan, not a stop: see Nothing ends by itself.
  • A label, if you want one.

What visitors see

On their first view of the page, each visitor is given A or B at random, half and half, and keeps that version on every later visit through a cookie on your own site. Both versions are at the same address. B carries no bar and no notice: it looks exactly like a page of your site. Links to the page and its canonical address stay the page's own.

These people always see A and are never counted:

  • anyone logged in who can edit posts, so you and your team see the live page;
  • search engines and other bots, so B is never indexed;
  • someone working in a page builder's editor;
  • someone opening a review link or a share link, who sees what that link shows.

How wins are counted

  • A visitor is counted once, the first time they are given a version.
  • A form win is counted when a visitor who was given a version reaches the thank-you page.
  • A call win is counted when that visitor taps a phone number link (tel:) on the tested page.
  • Each visitor wins at most once per test, so a visitor who sends the form and then calls is one win.

No personal data is kept. The counts are totals per day and version, the cookie holds only the version and a signature, and no IP address or browser detail is stored with them.

Read the result

Ask your AI app how the test is going. The agent reads it with respira_get_split_test, or every test on the site with respira_list_split_tests, and the answer comes in words, for example:

A: 14 wins (9 forms, 5 calls) from 318 visitors (4.4%). B: 23 wins (15 forms, 8 calls) from 322 visitors (7.1%). B is ahead: 93% likely it is really better. Another week gives a firmer answer.

The last sentence is one of these:

It saysWhat it means
Too early to sayFewer than 30 visitors on one side, or fewer than 60 in all. Keep it running.
A and B are level so farBoth have the same rate.
No clear winner yetOne leads, but less than 80% likely it is really better.
... is ahead80 to 94% likely the leader is really better. Another week gives a firmer answer.
... is clearly ahead95% likely or more.

Nothing ends by itself

A test keeps running until a person decides, even after its planned end. Past that date it says it is due and keeps showing both versions and counting.

To end it, tell your agent what you decided. It calls respira_end_split_test with one of two decisions:

  • Keep A. A stays live for everyone. B stays a draft and is not deleted, so you can keep it for later or delete it yourself.
  • Make B live. B goes live in place of A through the same approval every draft copy takes. The agent asks you first, and a snapshot of the page is saved before the change, so restoring it puts A back. If A was changed after B was made, the publish stops unless you tell the agent to overwrite that change. If publishing B is refused, the test keeps running.

In the dashboard

Every test on your sites is listed under Murmur.link in the dashboard sidebar, on the Split tests tab: the page, the site, when it started and is due, its status, the wins and rate for A and B, and how likely B is really better, with the result in words below each row.

A test that is still open has two buttons. Keep A ends it and leaves B a draft. Make B live asks once more, "Yes, publish B", and then publishes B in place of A. With more than one site, pick a site to see only its tests.

Caches

A page cache stores one copy of a page and hands it to everyone, which would show every visitor the same version. While a test runs, the tested page is marked as never cached, and its cached copy is cleared when the test starts and again when it ends. Respira handles WP Rocket, LiteSpeed Cache, W3 Total Cache, WP Super Cache, WP Fastest Cache, Cache Enabler, SiteGround Optimizer, Hummingbird, Breeze and the Cloudflare plugin, including APO.

  • NitroPack serves pages before WordPress, and Respira with it, runs. Respira clears its copy, but you need to add the page to NitroPack's excluded URLs for as long as the test runs. The start message says so when NitroPack is on the site.
  • Breeze does not clear the home page when one page is cleared. A test on the home page needs its Breeze cache cleared by hand.
  • A LiteSpeed web server without the LiteSpeed Cache plugin is told not to cache the page, but a copy it already holds can only be cleared at the host.

Limits

  • One running test per page. End it before starting the next one on the same page.
  • 1 to 90 days, and no automatic end.
  • B must be a Respira draft copy of the page being tested. If B is deleted or published another way during the test, new visitors see A.
  • Phone taps are counted by a small script on the tested page, so a visitor whose browser blocks scripts can still win through the thank-you page, but not by a call.
  • Split tests are part of Murmur, on the Builder plan and up. Starting a test and making B live need a Respira key whose WordPress user is an administrator, because a running test shows a draft to half the visitors of the live page.