SEO Ops bundles four Python tools for search work. A content attack brief builds a topic fingerprint from your content library, ranks bottom-of-funnel keywords, shows trending terms, lists competitor gaps and flags pages whose traffic dropped more than 30 percent. A Search Console client lists queries, pages, devices and striking-distance keywords. A trend scout reads Google Trends, Hacker News, Reddit, X and YouTube outliers.
The skill also defines a closed loop for SEO, AEO and GEO changes: compare baseline and candidate windows before promoting a playbook change.
What You Get
- A weekly brief with ranked money keywords, trending terms, competitor gaps and decaying page alerts
- A Search Console command line and Python client with striking-distance keywords at positions 4 to 20
- A trend report from Google Trends RSS, Hacker News, Reddit, X and YouTube outlier detection, saved as JSON and markdown
- A scoring model: impact from volume, CPC, funnel stage and trend, confidence from difficulty, position and topic authority
- A readback template with change made, windows, metrics, caveats and a promote, keep testing, rollback or unproven decision
Common Use Cases
- A weekly keyword and competitor gap review for a content team
- A daily check of queries that sit just below page one
- Spotting trending topics twice a week before writing
- Judging whether a content refresh or technical SEO fix raised clicks
What Makes It Unique
It combines keyword scoring, Search Console data and trend detection with a closed-loop readback rule that sets how long to wait before judging each kind of change. The trend scout works for basic use with no API keys.
Under The Hood
The scripts run as Python commands and call external services over the network: Ahrefs when a token is set, the Google Search Console API after a one-time OAuth sign-in in your browser, Brave Search for X trends, and public trend sources. Credentials come from environment variables and a locally saved token. Reports are printed and written as JSON and markdown files in an output directory. A preamble at the start runs the repository’s version check and telemetry setup scripts, which log usage locally and make remote reporting opt-in.