The Strategy Hub now tells you what's wrong in everyday words before it tells you in SEO terms, and the AI Content Studio has been reorganized around what you actually came to do.

New

• The Strategy Hub speaks plain English, without losing any expert depth — Every analysis now leads with a plain-language headline summing up what's going well and what's hurting you, plus a Do this first callout naming the single most important next step. The full expert Executive Summary is still right there, one click away under an expandable toggle (expanded by default for agency users). Each recommendation carries a plain-language "Why this matters" note alongside its technical detail, so non-experts get the stakes instantly while specialists keep the full depth.
• The Strategy Hub listens to your customers, for any kind of business — Analyses now fold in a Voice-of-Customer signal built from your community sentiment (Reddit and brand mentions) and, where available, your review reputation across locations — not just SEO and AI-visibility data. This works for non-local businesses too, so software, services, and online brands get customer-voice insight, not only multi-location local businesses.
• The Strategy Hub refreshes itself automatically — Your hub now re-runs in the background on a 24-hour cadence using your latest saved data, so the dashboard stays current without you clicking Run Analysis. It only refreshes when something has actually changed since the last run, respects your plan's scan allowance (it never silently dips into wallet overage), and never triggers fresh paid scans on its own.

Improved

• The AI Content Studio dashboard is built around a clearer starting point — The Studio home is no longer a wall of cards. The top of the page shows a compact LinkedIn connection status chip next to a single primary New content button, and a new Create content section presents every format you can produce as a channel grid — Blog Article, LinkedIn Article, LinkedIn Short Post — each with Start and See queue actions, plus a Local SEO Content channel that appears automatically when the Local SEO add-on is active. The signals, stats, usage, and recent sections are still there, demoted below the create-content surface, and the duplicate quick-link cards are replaced by a single compact Studio tools row. Nothing was removed — every page is still reachable.
• A real first-run experience for new Content Studio users — With no content yet, the Studio now shows a focused "Create your first piece of content" state with a simple three-step explanation (pick a channel, generate a draft, review and publish) and the channel picker, instead of a page full of empty stat cards.
• Autopilot has one clear home, and Blog Autopilot is easier to understand — All autopilot controls now live together under Studio Settings → Automation, which opens with a short note explaining that LinkedIn and Blog autopilot run independently — you can turn on one without the other, and Blog Autopilot does not require a LinkedIn connection. The card formerly just called Autopilot is now clearly LinkedIn Autopilot, and a new Blog Autopilot card next to it holds the blog on/off switch, posts per month, target word count, cadence, and preferred days. The Blog Targets page now only handles where approved drafts get published.
• Every blog publishing destination is discoverable in one place — The Studio Settings Connections tab is now Publishing and lists everywhere the Studio can send content: LinkedIn for social posts, WordPress and Webflow for blog articles, each with a button that jumps straight to where that connection is managed.
• Studio Settings grouped into tabs — The settings page is now organized into Automation, Planner, Voice, and Connections instead of one long scroll, and deep links open the relevant tab.
• Briefs are explained right where you use them — The Content Brief Queue has a new What's a brief? toggle opening a plain-language explainer: what a brief is (a ready-to-write, signal-backed content plan), why they're powerful (built from your real Search Console, Bing, GA4, keyword, and local-ranking signals), and how they flow through the Studio.
• A clearer path to Local SEO content — The Local SEO content page now leads with a Start local content button that takes you straight into your Local SEO brief queue, and the Local SEO Content channel surfaces directly in the Studio when the add-on is active, so the workflow is explicit and labeled rather than a silent redirect.
• The Content Studio sidebar is decluttered — The standalone LinkedIn Voice Profile and Blog Voice Profile entries have been removed from the sidebar, which now reads Dashboard, Compose, Briefs, Library, Calendar, Analytics, Settings. Your voice profiles haven't gone anywhere — they live under a Voice tab in Studio Settings, and the Compose screen has a contextual Voice button in its header that jumps straight to the matching profile (Blog voice when writing a blog post, LinkedIn voice when writing a LinkedIn post).

Fixed

• Fixed a crash on the AI Content Studio dashboard — The Studio home could fail to load with a blank or error screen for accounts with the Local SEO add-on, because the signal feed didn't recognize the local SEO signal type. Local signals now display correctly with their own color, and the list no longer breaks if an unexpected signal type appears.
• Local SEO content briefs no longer contradict your Local Heatmap — Briefs were only reading the single-point local rank snapshot, so they could tell you a page "isn't ranking" for a keyword even when your Local Heatmap clearly showed you at number one across the map. The two come from separate Google indexes and can disagree. Briefs now cross-reference your latest heatmap scan for each keyword: if the map shows you already winning, that keyword is no longer surfaced as a redundant opportunity, and when the map shows partial coverage the brief states it honestly (for example "top-3 on 20% of the local map") instead of a flat "not ranking".
• The Content Studio no longer creates "add schema markup" technical tasks as content briefs — The local brief planner was generating an "Add LocalBusiness schema" item in the brief queue tagged as a blog article. That's a developer task, not something you write content for, so it's been removed from the queue — this kind of structured-data recommendation already lives in the Strategy Hub's technical health analysis. Genuine local content opportunities are unaffected.