> ## Documentation Index
> Fetch the complete documentation index at: https://www.lettercamp.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Use search queries to plan a post

> Read Google Search Console queries from the Lettercamp CLI and use them to choose a new draft or an existing post to revise.

From your publication folder, run:

```bash theme={null}
npx lettercamp insights
```

You get up to 20 queries in JSON, ordered by clicks and then impressions. To focus on a subject, pass a word or phrase. Matching ignores capitalization.

```bash theme={null}
npx lettercamp insights "sourdough starter"
```

## Connect your site

In Lettercamp Cloud, open the site's **Insights** page and select **Connect Google Search Console**. Choose a Google account with access to the property you want to share. It can differ from your Lettercamp account.

A [paired workspace](https://www.lettercamp.com/docs/cli/connect.md) uses its own site automatically. With a [CLI login](https://www.lettercamp.com/docs/cli/account.md), the command uses the folder's deployment site or, in an unbound folder, your only accessible site. If you have several sites, select one explicitly with `npx lettercamp insights --site my-blog`.

## Choose what to write

Look at the reader's wording and the reported `landingPage` together. For example, if “how to feed a sourdough starter in winter” leads to your starter care guide, read its feeding instructions. A short section on cold kitchens may answer that question. If Google returns `landingPage: null`, search your existing posts before starting a new one.

Use a view when you have a specific editorial question:

| View | Queries it returns |
| - | - |
| `--view long-tail` | Phrases of four or more words, useful for finding specific questions. |
| `--view rising` | Queries with more impressions than in the prior period, sorted by the increase. |
| `--view no-clicks` | Queries with impressions and zero clicks, useful for reviewing how well a post addresses the search. |

## Read the JSON

A ready report includes the selected Google `property`, the reporting `scope`, the last sync time (`syncedAt`), and date ranges for the latest 28 days and the previous 28 days. Each query includes clicks, impressions, click-through rate as a fraction, and average position. The `prior` object holds the same metrics for the earlier period. A value of `null` means Google did not report a comparison row. Google can omit low-volume queries.

Check `status` before reading `queries`. For `not_connected` or `setup_required`, open `insightsUrl` and select the named Lettercamp site. For `pending`, retry shortly. For `unavailable`, read `message`. A ready report with an empty `queries` array means the current selection has no matching rows.

For a larger batch, use `--limit` (1–100). Pass the returned `nextOffset` to `--offset` with the same topic and view to get the next batch. A null `nextOffset` marks the end.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.