@xyleapp/cli 0.11.0 → 0.12.0

package/bin/xyle.mjs

@@ -8,7 +8,7 @@ const program = new Command();
 program
   .name("xyle")
   .description("SEO & AEO Intelligence Engine CLI")
-  .version("0.11.0");
+  .version("0.12.0");
 
 registerCommands(program);
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@xyleapp/cli",
-  "version": "0.11.0",
+  "version": "0.12.0",
   "description": "CLI for the Xyle SEO & AEO Intelligence Engine",
   "type": "module",
   "bin": {

package/src/seed.mjs

@@ -114,6 +114,21 @@ npx @xyleapp/cli <command> [options]
 
 Always use \`--json\` when parsing output programmatically.
 
+## Sites Hub & Auto-Discovery (Dashboard)
+
+Every account has a per-site hub in the dashboard at \`/dashboard/sites/[siteId]\` with four tabs: Overview, Crawl, Analysis, and Competitors. Use it when the CLI alone can't help.
+
+**Why this matters:** \`xyle competitors --query\` needs a query string from Search Console. For freshly onboarded sites (no GSC sync yet), there's no meaningful query to pass. The dashboard fills this gap with **Gemini-grounded auto-discovery**: one click finds the top 5–10 direct competitors for a domain, enriches each with a lightweight crawl, and links them to the site.
+
+**When to point the user to the Sites Hub:**
+- **New site, no GSC data** → tell the user to open \`/dashboard/sites/[siteId]\` → Competitors tab → "Discover via Gemini". Come back to the CLI after it finishes to continue the audit.
+- **User asks "who are my competitors?" without naming a query** → Sites Hub, not \`xyle competitors --query\`.
+- **User wants a persistent per-site view** → Sites Hub has all four tabs in one place.
+
+**Rate limits:** 10 discoveries/user/day, 1 run/site/6h. If the user hits a 429 there's nothing to fix, just wait.
+
+**Not in the CLI (yet):** Auto-discovery is dashboard-only. There is no \`xyle competitors discover\` subcommand. When a user is onboarding a fresh site from the CLI and has no query data, explicitly direct them to the dashboard instead of trying to improvise.
+
 ## Strategic Workflows
 
 ### 1. Full-Site Audit (Screaming Frog replacement)
@@ -196,6 +211,8 @@ When the user asks something SEO-related, route to the right workflow:
 | "What content am I missing?" / "Find gaps" | Content Gap Sprint | Ready to create, need briefs |
 | "Why is my CTR low?" | Page Optimization (CTR focus) | Likely a title/meta problem |
 | "Help me rank for [query]" | Page Optimization + Competitor Analysis | Need to see what's working for competitors |
+| "I just onboarded my site, what now?" / "No queries yet" | Sites Hub → Discover via Gemini | Bootstrap competitor context before GSC catches up |
+| "Who are my competitors?" (no query named) | Sites Hub → Discover via Gemini | No GSC query means \`competitors --query\` can't help |
 
 **After every analysis, proactively recommend the next step.** Don't just present data — interpret it and suggest action.
 
@@ -208,6 +225,7 @@ When the user asks something SEO-related, route to the right workflow:
 - Classify queries by intent before suggesting optimizations
 - Consider the user's ICP when recommending content topics
 - Use \`status\` first to verify API connectivity
+- **For fresh sites with no GSC history, point the user to the Sites Hub (\`/dashboard/sites/[id]\`) to run Gemini auto-discovery** — don't try to improvise competitor context with \`competitors --query\` when there's no query to pass
 
 **Don't:**
 - Optimize for zero-impression queries (no audience there)