@awesomate/hosting-mcp 0.76.0 → 0.86.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/index.js +383 -69
- package/package.json +1 -1
- package/skill/CHANGELOG.json +70 -2
- package/skill/awesomate-hosting/SKILL.md +3 -3
- package/skill/awesomate-knowledge/SKILL.md +18 -11
- package/skill/awesomate-knowledge/evals/provision-first-run/graders/grader.md +2 -1
- package/skill/awesomate-knowledge/references/faqs.md +22 -7
- package/skill/awesomate-knowledge/references/from-your-files.md +52 -8
- package/skill/awesomate-knowledge/references/ingestion-sources.md +1 -1
- package/skill/awesomate-knowledge/references/n8n-connection.md +6 -4
- package/skill/awesomate-n8n/SKILL.md +1 -0
- package/skill/awesomate-n8n/references/decisions.md +64 -0
- package/skill/awesomate-onebrain/SKILL.md +48 -19
- package/skill/awesomate-seo/SKILL.md +26 -1
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: awesomate-seo
|
|
3
|
-
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.
|
|
3
|
+
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.
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
# 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
|
|
|
229
229
|
result. A weekly email is what turns "SEO as ongoing" from a good intention
|
|
230
230
|
into a mechanism.
|
|
231
231
|
|
|
232
|
+
## 5. Is it working? AI visibility (Support Plus and above)
|
|
233
|
+
|
|
234
|
+
The gates above say whether a page CAN be found. `awesomate_ai_visibility` says whether the real
|
|
235
|
+
ChatGPT and Gemini apps actually name the business when its customers ask. Use it when the user
|
|
236
|
+
asks "does ChatGPT recommend us", "are we showing up in AI", or after a round of fixes.
|
|
237
|
+
|
|
238
|
+
- `action: "status"` returns the score (0 to 100, with a likely range), the questions where neither
|
|
239
|
+
app named the business, who they named instead, and the sites the apps relied on.
|
|
240
|
+
- **Fix from that evidence, in this order:**
|
|
241
|
+
1. a page on the site that directly answers each question never named, in the customer's words
|
|
242
|
+
and naming the place the business serves;
|
|
243
|
+
2. the directories, review sites and "best of" lists the apps relied on: get the business on
|
|
244
|
+
them, or ask the owner to;
|
|
245
|
+
3. the Google Business Profile (category, services, reviews), because Gemini answers local
|
|
246
|
+
questions from Google Maps.
|
|
247
|
+
- **Do not promise a lift from schema or llms.txt.** Studies found none. They are good hygiene,
|
|
248
|
+
not a visibility fix.
|
|
249
|
+
- `action: "check"` starts a new check (about five minutes). Owner checks are limited to 3 per site
|
|
250
|
+
per week, and sites the owner put on weekly checks are re-checked automatically: check again only after a
|
|
251
|
+
real change, never to watch the number within a day.
|
|
252
|
+
- **The owner approves the questions, in the hub, never you.** If `questions_approved` is false,
|
|
253
|
+
send them to the site's page in the hub (Website, the site, AI visibility).
|
|
254
|
+
- Scores move slowly and vary between checks. Read the trend over several weeks, and never tell
|
|
255
|
+
the owner a single check proves a fix worked.
|
|
256
|
+
|
|
232
257
|
## Hard rules
|
|
233
258
|
- Never fabricate content, reviews, or business facts to "help SEO".
|
|
234
259
|
- Never claim these guarantee a ranking — they make the site *eligible* and
|