notfair-investigate-drop

Diagnose organic traffic drop causes and produce a ranked recovery plan.

3.3k|414|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/nowork-studio/NotFair --skill notfair-investigate-drop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: notfair-investigate-drop
Source: https://github.com/nowork-studio/NotFair/tree/main/openclaw/skills/notfair-investigate-drop
Command: npx skills add https://github.com/nowork-studio/NotFair --skill notfair-investigate-drop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It identifies the most likely causes of an organic traffic drop for a registered site and turns that diagnosis into a ranked, recovery-focused action plan.

Core Features & Use Cases

  • Traffic-drop investigation: Loads prior audits and compares current state against recent history to isolate what changed.
  • Ranked recovery run: Produces a structured output (audit, action plan, verification) that prioritizes the fastest and safest recovery actions.
  • Page-level follow-up triggering: When a specific URL is implicated, it schedules a follow-up page-improvement task to drive targeted fixes.

Use case: After you notice traffic declining in search results, use this skill to determine whether the issue is more likely technical, content/intent-related, or both, then get a concrete recovery roadmap you can execute safely.

Quick Start

Ask your AI agent to run the notfair-investigate-drop skill for your site domain and generate a ranked recovery plan for the latest organic traffic decline.

Frequently Asked Questions about notfair-investigate-drop

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose the root cause of an organic traffic drop?

To diagnose an organic traffic drop, compare your site's current state against recent history to isolate changes. This skill reads prior audits and applies a canonical SEO investigation workflow to identify whether technical issues or content intent shifts caused the decline.

What is the best way to create a recovery plan after search traffic declines?

The best way to create a recovery plan for declining search traffic is to generate a structured action plan that prioritizes the fastest and safest fixes. This skill outputs a ranked recovery roadmap alongside audit and verification artifacts for safe execution.

How do I find out if my traffic drop is from technical SEO issues or content changes?

Finding out if a traffic drop stems from technical SEO issues or content changes requires a root cause diagnosis comparing current site state against history. The investigation workflow isolates what changed and categorizes the underlying drivers for targeted remediation.

Can I schedule page-level fixes automatically after a site audit?

Yes, you can schedule page-level fixes automatically after a site audit. When a specific URL is implicated in the traffic drop diagnosis, the skill triggers a queued follow-up page-improvement task to drive targeted remediation.

Does the traffic drop investigation require approval before changing CMS content?

Yes, the traffic drop investigation requires explicit approval before executing any repository, CMS, publishing, or PR-changing actions. It generates audit.json, action-plan.json, and verification.json artifacts first to ensure safe recovery execution.