From AI Answer to Prioritised Client Work

Seeing the answer is the easy part now. Anyone can open an engine and type a question. The difficulty is the next move: turning that observation into a ranked piece of work that someone can start on Monday.

Most teams skip that step and jump straight to action. They rewrite a page, publish three articles, add schema, and check again in a month. Then they cannot explain what changed, because they never identified what was broken.

The discipline is simple, and it is the difference between a project and a habit: classify the failure, map it to a work type, score the opportunity, then sequence.

Step one: classify the failure

Take one prompt and one answer. There are five possible outcomes, and each has a different cause.

Not searched. The engine ran searches that your content does not address at all. You were never a candidate, because the question the engine rewrote was a comparison, a price question or an objection you have not written about.

Searched, not retrieved. There is content, and it is not winning the retrieval step: too buried, too thin, wrong format, or on a page whose title does not match the facet.

Retrieved, not reranked. The page came back as a candidate and the passage lost. This is almost always a writing problem: the answer is implied, split across paragraphs, or drowned in preamble.

Reranked, not cited. The passage survived and another source was cited. Usually an evidence problem: the competing source has attribution, corroboration or currency that yours does not.

Cited, but wrong. You are in the answer and the claim is inaccurate or stale. This is a source-chain problem, and it is the most expensive of the five.

Writing the classification down is the whole exercise. "We are not visible in AI" becomes five specific diagnoses with five different owners.

Step two: map the class to the work

Each classification implies one kind of work, and only one.

| Classification | Work type | Typical owner | | --- | --- | --- | | Not searched | Content architecture: pages for the facets that get searched | Content strategy | | Searched, not retrieved | Page and title structure, crawlability, internal links | SEO and dev | | Retrieved, not reranked | Passage rewriting: the answer in the first sentence | Editorial | | Reranked, not cited | Corroboration: named expertise, quotes, third-party sources | Content and PR | | Cited, but wrong | Canonical facts and source correction | Content and comms |

The value of the table is that it stops the reflex. A reranking failure does not need more articles. A retrieval failure does not need better writing. Doing the wrong work type is the most common reason AI visibility programmes run for a quarter and change nothing.

Step three: score the opportunity

Rank on three factors, not one.

Commercial value of the prompt. A comparison question late in a buying journey is worth more than an educational one. Say so explicitly, even if the educational prompt is easier.

Likelihood of movement. Some prompts are defended by a source the engine clearly trusts, and moving them takes months. Others are open because nobody has written a direct answer. Be honest about which is which.

Effort and dependency. Some work needs a developer, some needs an interview with a subject expert, some needs a client decision. A queue that ignores dependencies stalls in week two.

The score does not need to be sophisticated. Value multiplied by likelihood, divided by effort, in whatever units you like, produces a defensible order. The point is that the order is written down and argued, not assumed.

"Fractional CMOs wear 10 hats. Content strategy shouldn't be one of them, not manually. Topical Authority Content Strategy automates the execution, you focus on strategy."

John Russell, Director, Digital Womble

Step four: sequence into a queue

A queue, not a plan. Plans get rewritten. Queues get worked.

Keep the queue short enough to finish and visible enough to trust. Each item should state the prompt it serves, the classification it addresses, the deliverable, and the owner. Anything that cannot name its prompt is not on the queue.

Two rules keep it honest. First, do not work the same classification twice in a row if a cheaper item exists elsewhere in the queue. Second, never start a corroboration item before the architecture exists, because you will be adding evidence to a page nobody retrieves.

"An agency will charge you £1-3k per month. We built Topical Authority Content Strategy to cost £48 per cluster, the exact same strategic architecture, just automated."

John Russell, Director, Digital Womble

Step five: close the loop with evidence

Rerun the same prompt set, the same way, and compare. Not against a score, against the classification.

Did an "absent" prompt become "cited"? Did a "cited but wrong" prompt get corrected? Did a "not cited" prompt stay stuck, and if so, which source is still winning?

That comparison is also the report. It answers the only question a budget holder asks: what did we do, and what changed.

The two traps

Working the easy prompts. Easy prompts flatter the dashboard and do not move revenue. If the queue is full of educational questions, the programme will look productive and sell nothing.

Doing everything at once. When architecture, passages and corroboration all change in the same month, nothing is attributable. Sequence the work types and the evidence stays readable.

Running it without a strategist spare

The classification is a skill, but the execution behind it is repeatable: content built to a brief that already knows the prompt, the passage and the evidence required.

That is what our content strategy platform automates, and where the free SEO and AI search growth toolkit shows the workflow before you commit. For the managed version, see what an engagement includes.

Earlier in this series: how an AI answer gets built and the cost of an inaccurate AI answer.