@awesomate/hosting-mcp 0.85.0 → 0.86.0

package/dist/index.js

@@ -41680,6 +41680,7 @@ var TITLES = {
   awesomate_skill_update: "Update Awesomate skills",
   awesomate_site_create: "Create WordPress site",
   awesomate_site_audit: "Audit site for SEO and AEO",
+  awesomate_ai_visibility: "Check how often AI apps name the business",
   awesomate_php_extensions: "Check or fix PHP extensions",
   awesomate_uninstall_site: "Delete WordPress site",
   awesomate_snapshot_site: "Snapshot site",
@@ -44341,6 +44342,54 @@ server.registerTool(
     }
   }
 );
+server.registerTool(
+  "awesomate_ai_visibility",
+  {
+    description: "How often the real ChatGPT and Gemini apps name the business when its customers ask the questions it sells to, for ONE of the user's public sites (Support Plus and above). `status` returns the latest score (0 to 100, with a likely range), how many answers named the business, the questions where neither app named it (the content gaps), the businesses named instead and the sites the apps relied on: use those to decide what to fix with the awesomate-seo skill (a page that answers a missed question, the directories and review sites the apps cite, the Google Business Profile, which Gemini reads for local questions). `check` starts a new check (about five minutes, runs in the background; read it later with `status`). Approving the questions is the owner's own click in the hub, never this tool: if the questions are not approved, send the owner to the site's page in the hub. Owner checks are limited to 3 per site per week; never start one just to see whether anything changed within a day. Weekly checks are the owner's choice, switched on in the hub.",
+    inputSchema: {
+      domain: external_exports.string().min(3).max(253).describe("one of the user's public sites, as the address customers use"),
+      action: external_exports.enum(["status", "check"]).default("status").describe("status reads the latest result; check starts a new check")
+    },
+    annotations: annotate("awesomate_ai_visibility", MUTATING)
+  },
+  async ({ domain, action }) => {
+    try {
+      const dom = encodeURIComponent(domain.toLowerCase());
+      if (action === "check") return textResult(await hubPost(requireConfig(), `/api/ai-visibility/sites/${dom}/checks`, {}));
+      const v = await hubGet(requireConfig(), `/api/ai-visibility/sites/${dom}`);
+      const latest = v?.latest;
+      const s = latest?.summary;
+      const scored = (latest?.questions ?? []).filter((q2) => q2.kind !== "branded");
+      const rowsFor = (q2) => (s?.questions ?? []).filter((r) => r.questionId === q2.id);
+      const measured = scored.filter((q2) => rowsFor(q2).some((r) => r.of > 0));
+      const gaps = s ? measured.filter((q2) => !rowsFor(q2).some((r) => r.named > 0)).map((q2) => q2.text) : [];
+      const unmeasured = s ? scored.filter((q2) => !measured.includes(q2)).map((q2) => q2.text) : [];
+      return textResult({
+        domain: v?.domain,
+        questions_approved: Boolean(v?.profile?.approvedAt),
+        weekly: v?.profile?.weekly ?? null,
+        running: v?.running ? { done: v.running.progress?.done, total: v.running.progress?.total } : null,
+        last_check_failed: Boolean(v?.lastFailed),
+        latest: s ? {
+          checked_at: latest.finishedAt,
+          score: s.score,
+          likely_range: latest.range,
+          named_in: `${s.namedIn} of ${s.of} answers`,
+          score_by_app: s.byEngine,
+          rank: s.rank ? `${s.rank} of ${s.marketSize} businesses named` : "not named",
+          questions_never_named: gaps,
+          questions_not_measured: unmeasured,
+          named_instead: (s.market ?? []).filter((m) => !m.isTarget).slice(0, 8).map((m) => `${m.name} (${m.score})`),
+          sites_the_apps_relied_on: (s.hosts ?? []).slice(0, 8).map((h) => `${h.host} (${h.answers} answers)`)
+        } : null,
+        history: (v?.history ?? []).slice(0, 8).map((h) => ({ at: h.at, score: h.score })),
+        next_step: !v?.profile ? "No questions yet: the owner sets them up on the site\u2019s page in the hub (Website, the site, AI visibility)." : !v.profile.approvedAt ? "The questions need the owner\u2019s approval in the hub before a check can run." : !s ? 'No finished check yet: start one with action "check", or wait for the running one.' : "Pick the questions never named and the sites the apps relied on, and fix those first."
+      });
+    } catch (err) {
+      return errorResult(err);
+    }
+  }
+);
 server.registerTool(
   "awesomate_wp_media_import",
   {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@awesomate/hosting-mcp",
-  "version": "0.85.0",
+  "version": "0.86.0",
   "description": "Awesomate MCP server — lets Claude manage your Awesomate WordPress hosting, plan, limits, n8n automations, and build Node/static apps + databases",
   "license": "UNLICENSED",
   "type": "module",

package/skill/CHANGELOG.json

@@ -1,5 +1,11 @@
 {
   "versions": [
+    {
+      "version": "0.86.0",
+      "highlights": [
+        "Claude can read how often ChatGPT and Gemini name your business for your site (awesomate_ai_visibility): the score, the questions where neither app names you, who they name instead and the sites they rely on, so it knows what to fix first. Approving the questions stays your own click in the hub."
+      ]
+    },
     {
       "version": "0.85.0",
       "highlights": [
@@ -490,13 +496,13 @@
       "highlights": [
         "Search your knowledge base with filters and ask questions within a slice of your content",
         "People & entities: your knowledge base now recognises who appears in your content, and you can name and merge them",
-        "Build AI agents from your own content — drafted, tested privately, and published only when you approve"
+        "Build AI agents from your own content \u2014 drafted, tested privately, and published only when you approve"
       ]
     },
     {
       "version": "0.14.0",
       "highlights": [
-        "Tools built for business owners, not developers — plain-language answers about your account, plan and limits",
+        "Tools built for business owners, not developers \u2014 plain-language answers about your account, plan and limits",
         "New support skill: get help, understand credits, or request a done-for-you build without leaving Claude",
         "New database skill: Claude picks the right place to keep your data and sets it up for you"
       ]

package/skill/awesomate-seo/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: awesomate-seo
-description: Make the user's site findable by Google AND quotable by AI assistants (SEO + AEO). Runs the build gates with awesomate_site_audit, then fixes what fails: title/meta/Open Graph, sitemap.xml, robots.txt, canonical tags, JSON-LD, answer-shaped content structure, and llms.txt. Works for static sites, Node apps, and WordPress. Use when the user says "SEO", "AEO", "GEO", "answer engine optimisation", "get found on Google", "get cited by ChatGPT", "rank higher", "make my site discoverable", "sitemap", "meta tags", "schema", or after building/changing any public page. Companion to awesomate-app-builder.
+description: Make the user's site findable by Google AND quotable by AI assistants (SEO + AEO). Runs the build gates with awesomate_site_audit, then fixes what fails: title/meta/Open Graph, sitemap.xml, robots.txt, canonical tags, JSON-LD, answer-shaped content structure, and llms.txt. Works for static sites, Node apps, and WordPress. Use when the user says "SEO", "AEO", "GEO", "answer engine optimisation", "get found on Google", "get cited by ChatGPT", "does ChatGPT recommend us", "AI visibility", "rank higher", "make my site discoverable", "sitemap", "meta tags", "schema", or after building/changing any public page. Companion to awesomate-app-builder.
 ---
 
 # Awesomate SEO — get found on Google and AI
@@ -229,6 +229,31 @@ the awesomate-n8n skill) that runs these checks weekly and emails the user the
 result. A weekly email is what turns "SEO as ongoing" from a good intention
 into a mechanism.
 
+## 5. Is it working? AI visibility (Support Plus and above)
+
+The gates above say whether a page CAN be found. `awesomate_ai_visibility` says whether the real
+ChatGPT and Gemini apps actually name the business when its customers ask. Use it when the user
+asks "does ChatGPT recommend us", "are we showing up in AI", or after a round of fixes.
+
+- `action: "status"` returns the score (0 to 100, with a likely range), the questions where neither
+  app named the business, who they named instead, and the sites the apps relied on.
+- **Fix from that evidence, in this order:**
+  1. a page on the site that directly answers each question never named, in the customer's words
+     and naming the place the business serves;
+  2. the directories, review sites and "best of" lists the apps relied on: get the business on
+     them, or ask the owner to;
+  3. the Google Business Profile (category, services, reviews), because Gemini answers local
+     questions from Google Maps.
+- **Do not promise a lift from schema or llms.txt.** Studies found none. They are good hygiene,
+  not a visibility fix.
+- `action: "check"` starts a new check (about five minutes). Owner checks are limited to 3 per site
+  per week, and sites the owner put on weekly checks are re-checked automatically: check again only after a
+  real change, never to watch the number within a day.
+- **The owner approves the questions, in the hub, never you.** If `questions_approved` is false,
+  send them to the site's page in the hub (Website, the site, AI visibility).
+- Scores move slowly and vary between checks. Read the trend over several weeks, and never tell
+  the owner a single check proves a fix worked.
+
 ## Hard rules
 - Never fabricate content, reviews, or business facts to "help SEO".
 - Never claim these guarantee a ranking — they make the site *eligible* and