Problems We Solve
Traffic decline rarely has a single explanation. Below are the six patterns Pogupo Kujaso checks for on every article, along with how each one tends to show up.
Traffic decline without an obvious cause
An article that performed steadily for months starts losing sessions with no single visible trigger. The alert compares current traffic against the article's own baseline and flags the point where the pattern shifted, giving a clear window to investigate rather than a vague sense that "something changed."
Keyword cannibalization
Two articles on the same site compete for the same search terms, and search engines pick one to rank while the other slides. The platform flags overlapping topics and suggests whether to consolidate, differentiate, or redirect.
Content freshness decay
Statistics, screenshots, product references, or dates embedded in an article become outdated over time, even if the core advice still holds. This is flagged based on publish age combined with a traffic pattern typical of freshness-related decline.
SERP feature loss
An article that once appeared in a featured snippet or a "People Also Ask" panel loses that placement, taking a share of clicks with it even if overall ranking position barely moves. This pattern is tagged separately since the fix usually involves formatting rather than rewriting.
Backlink erosion
Referring domains that once pointed to an article get removed, redirected, or deindexed, gradually reducing the authority signal tied to that page. This is tracked over time and flagged when the drop lines up with a traffic decline.
Technical regressions
A broken internal link, a slow-loading page element, an accidental noindex tag, or a redirect chain introduced during a site update can quietly suppress an otherwise healthy article. These are checked separately from content-related causes since the fix is usually a developer task.
Diagnosis is only useful if it turns into a specific action
Identifying that an article is declining because of freshness decay is a start, not an end point. Each cause tag comes with a matching task template: a freshness alert generates a "review and update outdated references" task for a writer, while a cannibalization alert generates a "compare and consolidate" task for a strategist.
Tasks include the specific data behind the alert, so whoever picks it up does not need to reconstruct the history before starting work.
Handoffs happen without a separate meeting
Once a cause is tagged, the associated task is added directly to the queue for the role responsible, whether that is a single person wearing multiple hats on a small team or a dedicated specialist on a larger one. No separate triage meeting is required to decide who owns what.
- Cannibalization and linking tasks route to strategists.
- Freshness and rewrite tasks route to writers.
- Formatting and structure tasks route to editors.
- Technical regression tasks route to developers.
