@ainyc/canonry 1.27.2 → 1.28.1

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/README.md CHANGED
@@ -89,6 +89,7 @@ Once an agent has the skill loaded, it can set up canonry, run sweeps, interpret
89
89
  - **Config-as-code** -- manage projects with Kubernetes-style YAML files. Version control your monitoring setup and let agents apply changes declaratively.
90
90
  - **Self-hosted** -- runs locally with SQLite. No cloud account, no external dependencies beyond the LLM API keys you choose to configure.
91
91
  - **Project-scoped location context** -- define named locations per project, set a default, and run explicit or all-location sweeps without making keywords location-owned.
92
+ - **WordPress publishing workflows** -- manage WordPress pages over REST, compare live vs staging, and generate manual handoffs for `llms.txt`, schema, and staging pushes.
92
93
  - **Scheduled monitoring** -- set up cron-based recurring runs to track citation changes over time.
93
94
  - **Webhook notifications** -- get alerted when your citation status changes.
94
95
  - **Audit logging** -- full history of every action taken through any surface.
@@ -196,6 +197,28 @@ canonry settings provider perplexity --api-key <key>
196
197
 
197
198
  Quota flags: `--max-concurrent`, `--max-per-minute`, `--max-per-day`.
198
199
 
200
+ ### WordPress
201
+
202
+ ```bash
203
+ canonry wordpress connect <project> --url https://example.com --user admin
204
+ canonry wordpress status <project>
205
+ canonry wordpress pages <project> --staging
206
+ canonry wordpress page <project> about --live
207
+ canonry wordpress create-page <project> --title "About" --slug about --content-file ./about.html
208
+ canonry wordpress update-page <project> about --title "About Us" --content-file ./about.html
209
+ canonry wordpress set-meta <project> about --title "SEO title" --description "Meta description"
210
+ canonry wordpress audit <project> --staging
211
+ canonry wordpress diff <project> about
212
+ canonry wordpress schema <project> about
213
+ canonry wordpress set-schema <project> about --json '{"@type":"FAQPage"}'
214
+ canonry wordpress llms-txt <project>
215
+ canonry wordpress set-llms-txt <project> --content "User-agent: *"
216
+ canonry wordpress staging status <project>
217
+ canonry wordpress staging push <project>
218
+ ```
219
+
220
+ WordPress automation uses REST + Application Passwords. `set-schema`, `set-llms-txt`, and `staging push` are manual-assist commands by design. See [docs/wordpress-setup.md](docs/wordpress-setup.md) for the full workflow and constraints.
221
+
199
222
  ### Telemetry
200
223
 
201
224
  ```bash
@@ -294,6 +317,20 @@ The web dashboard now supports the same flow:
294
317
  - Select the matching Search Console property in the project dashboard.
295
318
  - Queue syncs, inspect URLs, review inspection history, and review deindexed pages from the same project view.
296
319
 
320
+ ### WordPress
321
+
322
+ Connect a project-scoped WordPress site with an Application Password:
323
+
324
+ ```bash
325
+ canonry wordpress connect <project> \
326
+ --url https://example.com \
327
+ --user admin \
328
+ --staging-url https://staging.example.com \
329
+ --default-env staging
330
+ ```
331
+
332
+ Canonry can automate page reads/writes, audits, and live-vs-staging diffs through the REST API. `llms.txt`, schema injection, and WP STAGING push remain manual-assist workflows. Full setup instructions live in [docs/wordpress-setup.md](docs/wordpress-setup.md).
333
+
297
334
  ### OpenAI
298
335
 
299
336
  Get an API key from [platform.openai.com](https://platform.openai.com/api-keys).