# SEO Brain- Search Console turned into a ranked action register Source: https://nexoflow.ai/seo NexoFlow reads a site's own Search Console data, finds the pages losing clicks, ranks the fixes by estimated upside, and writes the ones that are approved. ## What it is NexoFlow compares the last 28 days against the 28 before, finds the four things costing you clicks, and turns the ones you approve into the next batch of content. An SEO audit that produces fifty findings gets ignored. This one is tuned the other way: “ten findings you trust beat fifty you have to triage.” Every action carries the evidence that produced it and an estimate of the clicks it could return. 28-day windows · four detectors · outcomes measured 28 days later ## Find it, approve it, measure it 1. It reads real performance- Clicks, impressions, CTR, and position from your own Search Console, aggregated over a 28-day window and compared with the previous one. 2. You approve what matters- Findings arrive as an action register you can approve or dismiss, ranked by estimated click upside rather than a made-up score. 3. It writes and then checks itself- Approved Create actions become Autopilot's topics. Twenty-eight days later NexoFlow measures whether the traffic actually moved. ## Each one names a specific problem No generic “improve your content” advice. Every detector has a threshold and a matching fix. - Pages quietly losing traffic- A page that had at least 20 clicks and then dropped 35% of them, or slid three positions, becomes a Refresh action with the before-and-after numbers attached. - Two pages fighting each other- When one query with 100+ impressions pulls two of your own pages into the top 30, that's cannibalization- and the fix is Consolidate, not another post. - Ranking well, nobody clicking- With 100+ impressions and a CTR under half of what your position should earn, the ranking is fine and the title isn't. That's a Fix title action. - Demand you don't cover yet- Queries pulling 50+ impressions where you sit at position 12 or worse are Create actions- proven demand you have no real page for. ## Advice you can audit Automated SEO recommendations are only useful if you can see where they came from and whether they worked. - Every action shows its evidence- Each finding carries the metrics that triggered it- the clicks lost, the impressions counted, the positions compared- not just a verdict. - Ranked by estimated clicks- Priority is an estimated click upside derived from your own numbers, so the top of the list is the biggest opportunity, not the loudest warning. - Nothing acts without approval- Actions sit as proposals. Only ones you approve are ever consumed by Autopilot. Dismiss one and it stays dismissed. - Conservative on purpose- The thresholds are deliberately strict. A short register you act on is worth more than an exhaustive one you scroll past. - Stale proposals expire- A proposal you never acted on clears itself out after 45 days, so the register reflects the site as it is now. - Outcomes get measured- Applied actions are re-measured against a matching 28-day window afterwards, so the loop reports back instead of assuming success. Why the outcome window is 31 days, not 28: Search Console finalizes data roughly two days behind, so measuring an outcome at exactly 28 days would compare a complete before-window against an incomplete after-window and flatter every result. NexoFlow waits the extra days instead. Small detail, but it is the difference between measuring an outcome and manufacturing one. ## Four findings. Four fixes.- Actions it proposes - create- Real demand with no page behind it yet - refresh- A page that has started losing clicks - fix_title- Good position, poor click-through - consolidate- Two pages splitting one query ## Four findings. Four fixes.- Signals it reads - clicks- Current window against the previous one - impressions- How much demand the query actually has - ctr- Measured against expected CTR for your position - position- Average position and how far it moved - query × page- Which of your pages each query pulls in - ga4- Connect a GA4 property for on-site behaviour ## Common questions Do I need to give NexoFlow access to my site? You connect Google Search Console, which is read-only access to your own performance data. Connecting a GA4 property is optional and adds on-site behaviour alongside search performance. How is this different from a generic SEO audit tool? Two ways. It reads your real Search Console data rather than a third-party crawl estimate, and every finding is tied to a specific action NexoFlow can then carry out- a post to write, a title to change, two pages to merge. It is a work queue, not a report. What does “approved actions become topics” actually mean? When you approve a Create action, its query and evidence are handed to Autopilot as the topic seed for the next cycle. So instead of inventing plausible topics, Autopilot writes against demand your own Search Console already proved exists. Nothing is consumed unless you approved it. Why 28 days? It is long enough to smooth out weekday and weekend swings and short enough to catch a decline while you can still act on it. Every window comparison uses 28 days against the previous 28. Will it flood me with recommendations? The thresholds are set conservatively on purpose- a page needs real prior traffic before a decline counts, a query needs real impressions before a gap counts. The goal is a register short enough to work through. How do I know if any of it worked? Applied actions are measured again after the outcome window, against the same 28-day basis plus a few days for Search Console to finalize its data. The result is reported back rather than assumed.