Skip to content

Act on a recommendation and check what changed

How do you act on an aSERP recommendation and see what changed? Move the recommendation from suggestion to done inside aSERP, so it captures a baseline before you start; then read the check, which counts a change only when it is bigger than the uncertainty of both periods.

Outcome
One recommendation acted on inside aSERP, with its baseline captured and its result read honestly
Time to do
Under an hour
When you can judge it
Not in answers (it changes how you work)
Difficulty
Easy
Usually done by
Marketing · Agency
Engines affected
None directly
Uses in aSERP
Recommendations

Use this guide if

  • aSERP has shown you a recommendation and you want to act on it in a way you can check later;
  • you have done the work a recommendation asked for and want to know whether anything changed;
  • you need to tell your team or a client what a change did, without claiming more than the numbers show.

Before you start

  • A brand in aSERP with recommendations on its Recommendations page.
  • Someone who can do the task. For this guide's example, that is whoever writes your tracked questions.
  • The timings in this guide assume daily scans, the default. If Brand Settings›Tracking schedule is set to weekly or monthly, every wait below is that much longer, and aSERP may decline to compare periods with too few measured days.
  1. Step 1. Pick one recommendation

    Open Recommendations, filter by area (On-page, Off-page or General) and sort by Impact: high to low. This guide's example is a question-type recommendation, filed under General: Prompt Strategy, Branded Prompts or Awareness-stage Prompt Coverage. It changes the questions you track, so every engine you track reflects it from the next scan.

  2. Step 2. Read why it was flagged

    Open the recommendation and read Why this was flagged, What to do and Evidence. The evidence says what aSERP measured in the answers, and the product is plain about its limits: “It shows what was measured, not what caused it.”

  3. Step 3. Add it to To-Do before you change anything

    Choose Add to To-Do. As the recommendation itself says, “The baseline is captured the moment this is added to To-Do — so before and after can be compared.” Work you do before this step has no baseline to be compared with.

  4. Step 4. Give it an owner and do the work

    Choose Assign owner, then Start work. Do the task with the guide that fits it; for a question-type recommendation, that is Write the questions your buyers actually ask AI. Add new questions as new questions rather than rewording the ones you track, so your tracked questions go on being asked exactly as before.

  5. Step 5. Mark it ready, then complete it

    When the work is done, choose Ready for verification, then Complete. aSERP then compares the figures from before and after completion.

  6. Step 6. Read the result

    The result appears under Did it work?. It reads Observed improvement, No material change, Declined or Insufficient support, with an attribution level from No attribution to Strong attribution. Before the check period ends there is no result yet, so read nothing into the wait.

Check it worked

  1. Right away

    The moment you choose Add to To-Do, the recommendation leaves the suggestions and joins your To-Do work, with its baseline captured.

  2. In aSERP

    The check is the result. aSERP calls it an observed improvement only when the change is larger than the metric's minimum or the uncertainty of the two periods added together, whichever is greater. Even then, Observed improvement is an observation, not proof that your change was the cause. For this guide's example, the new questions are asked of every engine you track from the next scan: read them on the Topics page, as Write the questions your buyers actually ask AI describes.

  3. With the free audit

    The free audit cannot check a recommendation: it runs once per visitor and asks each question once.

  4. If nothing moved

    No material change means the check found no change larger than its uncertainty; Insufficient support means there were too few answers to judge. Keep the new questions running and read their topic over more measured days before you decide the work did nothing.

What not to do

  • Don't do the work before you choose Add to To-Do: no baseline is captured.
  • Don't read Observed improvement as proof that your change was the cause.
  • Don't reword tracked questions to act on a question-type recommendation; add new ones.
Published 7 Oct 2026Steps checked on 7 Oct 2026

Find out whether AI names your brand.

A first look: three of your buyers' questions, six engines, one capture. Daily tracking turns it into a trend with a range.

Your privacy choices

We use essential cookies to make this site work. With your permission we also use analytics cookies, to understand how the site is used, and marketing cookies, to measure our advertising. Nothing optional is switched on until you choose.

Read the cookie policy