@awesomate/hosting-mcp 0.18.0 → 0.19.1

package/skill/awesomate-n8n/references/troubleshooting.md

@@ -3,6 +3,34 @@
 Diagnosis playbook. Work the flow top-to-bottom; do not jump to fixes before
 you have the failing execution's detail.
 
+
+## "Could not create the draft" / writes fail while reads work
+
+If reads, `awesomate_n8n_context` and `validate` all succeed but every WRITE
+(create draft, activate, promote, test-fire) fails, the cause is almost always
+the account's stored n8n API key — not the hub, not Cloudflare, not the
+workflow JSON. Validation runs on Awesomate's side and never touches the
+instance, which is exactly why it keeps passing.
+
+The server says so explicitly: HTTP **409** with `code: n8n_credential_invalid`.
+Older builds reported this as a 502, which reads like an outage — if you see a
+bare 502 on writes only, suspect the key before you suspect the platform.
+
+**Tell the user to do this, in this order:**
+
+1. Open their n8n (the response's `instanceUrl`, e.g. `https://<slug>.awesomate.io`)
+   → **Settings → n8n API** → **Create an API key**. Copy it.
+2. Open **https://hub.awesomate.ai/n8n/settings** → paste it into
+   **"New n8n API Key"** → save. The status chip should go from
+   *Key rejected* to *Connected*.
+3. Retry the action.
+
+Do not retry before they confirm the new key is saved, and do not go probing
+hub or Cloudflare status — a genuine hub problem breaks reads too.
+
+Common causes: the key was revoked or regenerated in n8n, or the instance was
+rebuilt (a rebuilt instance shows 0 workflows and invalidates every old key).
+
 ## Diagnosis flow
 
 1. `awesomate_n8n_context` — confirm consent flags, capabilities, and the

package/skill/awesomate-seo/SKILL.md

@@ -20,9 +20,10 @@ Be honest about limits: these are the signals that *let* you rank and be cited
 - **WordPress** → drive it through WP-CLI via the awesomate-hosting skill
   (`wp` passthrough). Install a free SEO plugin + let it generate the sitemap
   rather than hand-writing files (see §WordPress).
-- **A shop (WooCommerce)** → also use the `woo-agent-storefront` skill for
-  AI-shopping feeds + a store `llms.txt`, and `woo-catalog-perfection` for
-  product-data quality. This skill covers the site-level SEO around it.
+- **A shop (WooCommerce)** → same WordPress path, plus `Product` JSON-LD on
+  product pages and product-data quality (real titles, descriptions, images,
+  prices) — drive it through WP-CLI like any WordPress site. This skill
+  covers the site-level SEO around the shop.
 
 ## 1. Static / Node — write these
 
@@ -56,6 +57,10 @@ Through the awesomate-hosting skill's `wp` passthrough:
 - Confirm the sitemap is live (`/sitemap_index.xml` or `/sitemap.xml`) and
   `robots.txt` references it.
 - Add an `llms.txt` at the site root for AI discoverability (the plugin won't).
+- Posts and pages can be created/updated directly via `awesomate_wp_post`
+  (drafts first — the user approves publishing). Useful for adding the content
+  pages that back up `llms.txt` — a services overview, an FAQ, an about page —
+  when the site is thin on machine-readable substance.
 - WordPress is the recommended stack precisely when SEO/organic reach matters —
   lean into it here.
 
@@ -74,6 +79,36 @@ Through the awesomate-hosting skill's `wp` passthrough:
 Tell the user the next step is submitting the sitemap in Google Search Console
 (you can't do that for them) — offer a one-paragraph how-to if they want it.
 
+## 4. Ongoing upkeep — the seo-healthcheck
+
+SEO decays quietly: a plugin update flips an option, an edge rule starts
+challenging crawlers, a sitemap stops regenerating. Run this routine whenever
+the user asks to "check SEO", and after any content change:
+
+1. **Content in the raw HTML** — `curl -s https://DOMAIN/page` and confirm the
+   key content is actually in the response, not rendered later by JavaScript.
+2. **Sitemap** — `/sitemap.xml` (WP: `/sitemap_index.xml`) returns 200 and
+   `<lastmod>` is fresh. A months-old lastmod on a site that changed last week
+   means generation is broken, not that nothing changed.
+3. **robots.txt + llms.txt** — both exist, and `llms.txt` still mentions the
+   current offerings. A stale llms.txt misdescribes the business to every AI
+   assistant that reads it.
+4. **AI crawlers not blocked at the edge** —
+   `curl -A "GPTBot" -s -o /dev/null -w "%{http_code}" https://DOMAIN/`
+   (repeat with `ClaudeBot`) returns 200, not 403 or a challenge page.
+   Where to fix each case: [references/ai-discoverability.md](references/ai-discoverability.md).
+5. **WordPress only: `blog_public` must be 1** — one checkbox ("Discourage
+   search engines") silently de-indexes the whole site. Read it via
+   `awesomate_run_wp_cli` with args `['option','get','blog_public']`; if it's
+   0, fix with `['option','update','blog_public','1']` (allowlisted).
+
+Report pass/fail per check, with the fix for each failure.
+
+**Make it automatic:** offer — once — to build a scheduled n8n workflow (via
+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.
+
 ## Hard rules
 - Never fabricate content, reviews, or business facts to "help SEO".
 - Never claim these guarantee a ranking — they make the site *eligible* and