Tracked actions

Overview#

Tracked Actions is a log of what you did: published a page, updated an old one, fixed a technical issue, got listed on a directory, launched a campaign: with the date.

It is the least glamorous feature in Seerly and the one that makes the rest defensible. Without it, every improvement is a story told after the fact.

The attribution problem#

AI visibility moves slowly and from several causes at once. Three months in, visibility is up and you have done six things. Which one worked?

Without a record, the honest answer is that nobody knows, and the answer people give is whichever thing they advocated for. With a record, you can line movement up against a dated timeline and see which changes preceded which shifts.

That is the difference between "AI visibility improved" and "these two changes moved it, and these four did not", which is what decides where the next quarter goes.

Interpreting results#

Actions appear against your trend lines, and movement following an action is suggestive rather than proof. Several things are always in flight at once, and AI answers vary on their own without anybody's help, so the timeline narrows the field of plausible causes rather than settling the question.

Lag is expected, and it varies quite a lot by the kind of action. A technical fix can surface within a cycle or two. A published page has to be discovered and indexed before anything can happen at all. A directory listing can take a good while to be picked up. Reading a two-week window and concluding that the directory listing did nothing is a mistake people make regularly.

An absence of movement is a finding in its own right, and a useful one. An action that produced no effect after several cycles is worth knowing about precisely because it stops you doing more of the same thing next quarter.

Panels and controls#

Actions arrive from several places and the screen groups them by source, covering Agent Suggestions, Content suggestions, Brand reputation actions and Advisor Chat. This is not purely a manual log, then: work that Seerly proposed for you lands here alongside whatever you added yourself.

Mark Complete closes an action and Reopen brings it back. Tracked and Untrack control whether something counts toward your timeline at all, and Dismiss action removes a proposal you have no intention of doing. Focus Keyword and Secondary Keywords attach the terms an action was aimed at, which is what makes it possible to connect it to movement weeks later rather than eyeballing two charts side by side. Create Content starts a draft from an action, and View content or View conversation opens whatever produced it. No tracked actions yet is the empty state on a new project.

Tracked action

Publish a comparison page for agency project management

Source

Content suggestions

Focus Keyword

project management for agencies

Secondary Keywords

agency time tracking, client onboarding

Status

Tracked

Best practices#

• Logged as you go. Reconstructing three months afterwards produces a fiction with convincing dates on it.
• Specific rather than general. "Published comparison page for X" is worth something later; "content work" is not.
• Everything relevant, not only content. Technical fixes and third-party listings frequently move more than publishing does.
• Enough separation to attribute anything. Six changes made in one week cannot be told apart afterwards by any method.

Next steps#

1. Log it at the moment you do it. Thirty seconds then is worth more than an hour of reconstruction later.
2. Include the non-content actions. Getting listed on a directory that already gets cited is often the highest-impact thing anybody does in a given month, and it is the thing least likely to get written down.
3. Review against trends monthly rather than weekly, since weekly is too short for most of these to have surfaced.
4. Use it in reports. A brand report connecting actions to movement is far more useful to a reader than one showing numbers on their own.

Limitations#

Tracked Actions records what you tell it and nothing else. It does not detect changes automatically, so anything left unlogged is simply invisible to the timeline.

Correlation is also not proof. It narrows the field of plausible causes; it does not settle which one was responsible.