@nuxtseo/cli 0.4.0 → 0.4.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/dist/render.js CHANGED
@@ -64,7 +64,7 @@ export function renderAction(data) {
64
64
  ['Finding', data.findingType],
65
65
  ['As of', data.asOf],
66
66
  ]),
67
- `Evidence groups: ${data.evidenceGroups.length}`,
67
+ data.workPrompt ?? `Evidence groups: ${data.evidenceGroups.length}`,
68
68
  ].join('\n');
69
69
  }
70
70
  export function renderActionResolution(data) {
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@nuxtseo/cli",
3
3
  "type": "module",
4
- "version": "0.4.0",
4
+ "version": "0.4.1",
5
5
  "description": "Command line interface for the Nuxt SEO public API.",
6
6
  "license": "MIT",
7
7
  "homepage": "https://nuxtseo.com/pro",
@@ -33,8 +33,8 @@
33
33
  },
34
34
  "dependencies": {
35
35
  "@clack/prompts": "^1.8.0",
36
- "@nuxtseo/protocol": "^0.4.0",
37
- "@nuxtseo/sdk": "^0.4.0",
36
+ "@nuxtseo/protocol": "^0.4.1",
37
+ "@nuxtseo/sdk": "^0.4.1",
38
38
  "citty": "^0.2.2",
39
39
  "pathe": "^2.0.3"
40
40
  },
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: nuxtseo-cli
3
- description: Drives the `nuxtseo` CLI to triage a Site through the Nuxt SEO public API: Site status and ranked issues, Search Console rows, route-family indexing, field and lab Core Web Vitals, Lighthouse Scans, Page Issues, keyword competitor and domain research, backlinks, SERP analysis, rankings, link opportunities, content decay, duplicate clusters, chart annotations, and issue resolution. Use whenever the user mentions NuxtSEO, the `nuxtseo` command, Site SEO work, or Nuxt SEO automation.
3
+ description: Required before you interpret any `nuxtseo` CLI output, exit code, or error, including pasted output, because several fields read like findings and are not. Drives the `nuxtseo` CLI for Site status, ranked actions, Search Console and indexing, Core Web Vitals, Lighthouse Scans, research, and backlinks. Use whenever the user mentions NuxtSEO, the `nuxtseo` command, or Nuxt SEO work.
4
4
  ---
5
5
 
6
6
  # `nuxtseo` CLI
@@ -135,8 +135,9 @@ Site may have changed since the observation.
135
135
  nuxtseo actions show <action-id> --site <site-id> --json
136
136
  ```
137
137
 
138
- It names the pages, the finding type, and when it was observed. Two reads go
139
- deeper:
138
+ It names the pages, the finding type, and when it was observed. If
139
+ `data.workPrompt` is not null, it is the Work Prompt: the task for this action,
140
+ grounded in its evidence. Start the fix from it. Two reads go deeper:
140
141
 
141
142
  - `page issues --action-id <action-id>`: the raw observations, with URLs,
142
143
  status codes, redirect targets, and Lighthouse selectors. This is the
@@ -200,8 +201,8 @@ a seed over three words, still exits `0`, and returns `keywords: []` with
200
201
  **A refusal is not an empty Site.** Exit `4` is a plan, scope, or entitlement
201
202
  blocker, for example `entitlement_required`. Exit `5` on `status`, `page
202
203
  issues`, or `search cohorts` can mean an archived or paused Site. Report the
203
- blocker and stop. Do not read it as "no data" or "nothing wrong", and do not
204
- retry unchanged.
204
+ blocker and stop. Do not read it as "no data" or "nothing wrong". Do not
205
+ retry unchanged, and do not route around it with `pull` or another read.
205
206
 
206
207
  **Quote the count the result ships.** Never quote the length of a list. Use
207
208
  `data.total` from `page issues`, and `coverage.accessibilityChecksTotal` and
@@ -221,8 +222,11 @@ true` marks the list as a floor.
221
222
  - `search status` reads the stored connection and never waits for Google.
222
223
  `search analytics`, `search indexing`, `search index-history`, and
223
224
  `search inspect` read retained Search Console evidence.
224
- - An indexed count comes from `search indexing`, never from analytics rows.
225
- See [references/indexing.md](references/indexing.md).
225
+ - An indexed count comes from `search indexing summary`, never from analytics
226
+ rows. It counts retained URL Inspection evidence as of `data.asOf`, not
227
+ Google's live index. Name that source, quote `asOf`, and never label the
228
+ figure current or "right now", even in a summary line. See
229
+ [references/indexing.md](references/indexing.md).
226
230
 
227
231
  **Route families: `established` versus `ranked`.** Read `search cohorts`
228
232
  before you list single not-indexed URLs. Never merge its two lists: