# Which of Your Blog Posts to Refresh: Read Your Search Console Numbers From Your AI Agent

Source: https://blog.lots.blog/which-blog-posts-to-refresh-search-console
Published: 2026-11-02T00:30:31.47789+00:00

Refresh the posts Google already shows for a search but ranks just off page one, then fix titles that get seen and not clicked. With LotsBlog's Search Console connection, your AI agent reads clicks, impressions, click-through rate, average position and each post's top searches, so you can ask it to rank your posts and name the section to rewrite.

You don't need a script, a spreadsheet or a Google Cloud project for this. An owner or admin connects Search Console once in the LotsBlog dashboard, and from then on ChatGPT, Claude or another agent can read the numbers over MCP. The dashboard's Search tab shows the same numbers, so the work is never locked behind the agent. Below: the connection steps, what the agent can and can't read, four labels for deciding what to do with each post, a prompt to paste, and the limits of the data. The thresholds are my rules of thumb, not Google's. The Google facts come from Google's own help pages, which I read on 31 October 2026.

## Connect Search Console to your blog (once)

An owner or admin does this in the dashboard. Your agent can't connect it for you, and you never give LotsBlog a Google login.

1. Open your blog in the LotsBlog dashboard, then **Analytics**, then the **Search** tab.
2. **If you already use Search Console:** copy the email the tab shows, open your property in Search Console, go to **Settings**, **Users and permissions**, **Add user**, and paste it. **Restricted** is enough to read your numbers; choose **Full** if you also want LotsBlog to submit your sitemap. Back in LotsBlog, click **Check connection**. You stay the owner and can remove LotsBlog's access in Search Console at any time.
3. **If you don't use it yet:** choose **Set it up for me**. LotsBlog verifies your blog with Google and submits your sitemap. Its account becomes an owner of the new property, which you can remove later, and the blog has to be public. You can add your own Google email there too, so the property shows up in your Search Console. If you'd rather verify the property yourself, the tab also takes Google's HTML verification tag.
4. Wait a day or two. LotsBlog reads Google once a day, and a newly added property can take a day or two to show data. When you connect a property you already had, LotsBlog brings in up to 16 months of history.

Which property works depends on where your blog lives. A blog on its LotsBlog address (`yourname.lotsblog.com`) needs a property for that exact address, which is what **Set it up for me** or the HTML tag creates. A blog on your own domain or at `yourdomain.com/blog` can use a property for that address, a parent property such as `https://yourdomain.com/`, or your Domain property; LotsBlog then keeps only your blog's pages. If you host the blog at `/blog`, [How to Host Your Blog at yourdomain.com/blog](https://blog.lots.blog/host-blog-at-yourdomain-com-blog) covers the rewrite.

Disconnecting stops LotsBlog reading Google and deletes the numbers it stored. Search Console is part of every plan; there is no add-on.

## What your agent can read

Owners, admins and editors can see search numbers. Authors get none.

| Tool | What you get for search | Good for |
|---|---|---|
| `get_blog_analytics` | Clicks, impressions, click-through rate, average position, daily numbers, your top pages with post titles and the top 25 searches, plus a `data_through` date. Optional `start_date` and `end_date`; the default is 28 days ending on the last day Google has data | The overview |
| `get_post_analytics` | One post: clicks, impressions, click-through rate and position by day, and that post's top 25 searches, for the latest 28 days | The ranking, post by post |
| `list_blog_posts` | Your posts, newest first | Going through every post |
| `get_blog_post` | The saved post | Reading it before a rewrite |
| `update_blog_post` | Saves changes to the same post, including `meta_title` and `meta_description` | The refresh itself |
| `submit_sitemap` | Submits your sitemap to Google (Full or Owner access, owners and admins) | After a new address or large changes |

If Search Console isn't connected, the search block says `not_connected` and links to the settings. It never shows zeros.

## Four labels for every post

A page's average position blends every search it appears for. Google counts the topmost position your page held for each search, then averages across searches, so one number can hide a page that is third for one query and thirtieth for another. That is why the per-post top searches matter: each one carries its own position, and the search you want is the one that sits just off page one.

| Label | What the numbers look like | What to do |
|---|---|---|
| **Striking distance** | A search where the post sits at position 8 to 20 and has more impressions than your typical post | Rewrite the section that answers that exact search. Put the current facts first |
| **Seen, not clicked** | Position 5 or better, impressions above your typical post, click-through rate under 2% | Rewrite the title and meta description only, not the body |
| **Wrong searches** | Most impressions come from searches the post doesn't answer | Don't refresh it. Write a page for that search if it matters, or leave it |
| **Leave alone** | No rows: the post hasn't shown in Google search in the period | Check it's indexed and give it time. A refresh won't create demand |

Change the thresholds to fit your blog. Keep one rule: the search has to match what the post is about. For a decay check across every page, and a script that compares two 28-day windows, see [How to Decide Which Blog Posts to Refresh First](https://blog.lots.blog/content-refresh-prioritization).

## A prompt to paste

Connect LotsBlog to your agent first by giving it this: `Read https://lots.blog/skill.md and help me connect LotsBlog for you.` Then paste:

> Read my LotsBlog Search Console numbers and tell me which posts to refresh. Do not edit anything.
>
> 1. Call list_blogs and use the blog named [your blog name]. Call get_blog_analytics. If search.status is not_connected, stop and give me the settings link. Tell me the data_through date.
> 2. Call list_blog_posts for published posts. For every post published more than a month ago, call get_post_analytics and read its search block.
> 3. Work out the median impressions across those posts. For each post, find its searches at position 8 to 20, ranked by impressions, and label the post: Striking distance (a search at position 8 to 20 with impressions above the median), Seen not clicked (a search at position 5 or better, impressions above the median, click-through rate under 2%), Wrong searches (most impressions come from searches the post does not answer) or Leave alone (no rows).
> 4. Return a table with the post title, clicks, impressions, click-through rate as a percent, average position, the label, the exact search to target and the one change you would make. Put Striking distance first, by impressions, and stop at ten rows.
> 5. Click-through rate comes back as a fraction, so 0.02 means 2%. Never give a number you did not read from a tool result.

It reads only. Reading analytics needs just the Read permission, which is always on. If you want the agent to be unable to change anything while it ranks, turn off Create and edit on the approval screen when you connect it. [Is LotsBlog Safe?](https://blog.lots.blog/is-lotsblog-safe) lists what each permission covers. Each post is one call, and the REST documentation lists 60 requests a minute for the analytics endpoints, so on a large blog ask for ten posts at a time.

## From the ranking to the rewrite

1. Pick one or two posts, not the whole list. Refreshing everything at once leaves you unable to tell what worked.
2. Ask the agent to read the post with `get_blog_post`, check every statistic, price and "according to" line against its source today, cut anything it can't verify, and rewrite the section for the target search.
3. **Ask for the new text in chat first.** A post that is already live has no private draft of an edit: changing the text of a published post is an edit, and it goes live the moment the agent saves it. Approve the text, then have it save with `update_blog_post` to the same post, keeping the slug so the URL doesn't change.
4. Save only real changes. LotsBlog takes a post's sitemap `lastmod` and its article `dateModified` from the post's last update, and Google says `lastmod` should reflect a significant update to the page, such as its main content, structured data or links. Google also says a date has to describe when the page was published or updated. A save that changes nothing still moves the date.
5. You don't need to resubmit anything. New and updated posts are announced through the sitemap and IndexNow automatically; `submit_sitemap` is for a new address or large changes.
6. Look at the post's numbers again in a few weeks, once there are enough new days of data. Google doesn't publish how fast it recrawls a page.

## What the numbers can't tell you

- **They run behind.** Google says collected data should normally be available in two to three days, and LotsBlog reads Google once a day. Days after `data_through` can still change.
- **An impression isn't a visit.** Google counts an impression when your link appears in the current page of results, whether or not it's scrolled into view. Search Console clicks count Google traffic only, and Google notes its figures can differ from other tools. LotsBlog's page views count visits from every source, so expect the two not to match.
- **Rare searches are hidden.** Google leaves out rare and sensitive queries, so the top searches don't add up to your totals.
- **One window per post.** Per-post search numbers cover the latest 28 days. Blog-level calls take `start_date` and `end_date`, and the home page of your dashboard compares the last 28 days with the 28 days before for the whole blog, but not post by post.
- **The blog-level top pages are a short list**, not every page, which is why the prompt reads each post.
- **Position can differ from Google's own report.** LotsBlog's totals weight Google's daily average position by impressions, so a total can differ slightly from the figure in Search Console's Performance report.
- **A private blog has no search data.** Google can only verify and show a public blog.
- **None of this promises a ranking or traffic.** It tells you where a rewrite is most likely to matter.

## If you manage client blogs

Each blog has its own Search Console connection, so you connect every client blog separately. Using the add-user route, the client stays the owner of their own property and you or they add LotsBlog's email as a user. With **Set it up for me**, LotsBlog's account becomes an owner of the property, which the client can remove in Search Console. Owners and admins connect and disconnect; editors can see the numbers; authors can't. Each agent connection has its own permissions, so a reporting agent can be read only. LotsBlog's team roles are described in the [support changelog](https://support.lots.blog/changelog).

## If you'd rather not use an agent

Open **Analytics**, then **Search**, and pick last 28 days, last 3 months or last 12 months. You get the totals, a daily chart, your top searches and your top pages. The home page of the dashboard shows views, Google clicks, impressions and average position for the last 28 days against the 28 days before. The four labels above work on those tables by hand.

## Try it on your own blog

LotsBlog plans start at $24 a month for 3 blogs, or you pay $9 per blog a month from credits (checked on 31 October 2026 at [lots.blog/pricing](https://lots.blog/pricing)). Every plan has every feature, Search Console included. New accounts get free credits when they sign up, no card, enough to run one blog for about a month. To see how the agent publishes, read [How to Publish Blog Posts From Claude Code](https://blog.lots.blog/publish-blog-posts-from-claude-code), and for every REST call see the [LotsBlog REST API guide](https://blog.lots.blog/lotsblog-rest-api).

## Common questions

### Which of my blog posts should I refresh first?

Start with posts that already show in Google for a search at position 8 to 20 and have more impressions than your typical post. They have demand and sit close to page one. Next, fix the title and description of posts at position 5 or better with a click-through rate under 2%. Skip posts whose impressions come from searches they don't answer.

### Can Claude or ChatGPT read my Search Console data?

Through LotsBlog, yes. After an owner or admin connects Search Console on the Search tab, your agent reads clicks, impressions, click-through rate, average position and top searches with `get_blog_analytics` and `get_post_analytics`. The agent can't make the connection itself, and it needs an owner, admin or editor role to see search data.

### Does my agent need a Google login?

No. You add LotsBlog's account to your Search Console property, or choose Set it up for me, and your agent only talks to LotsBlog. You never give LotsBlog or the agent your Google password.

### Can the agent change my posts while it ranks them?

Only if Create and edit is on for that connection. Reading needs just the Read permission. If it does edit a post that is already live, the change goes live when it's saved, so ask it to show you the new text first.

### How fresh are the numbers?

LotsBlog reads Google once a day, and Google says its data is normally available in two to three days. The `data_through` date in the result tells you the last day the numbers cover, and recent days can still change.

### What if my blog isn't on LotsBlog?

The four labels work on any Search Console data. [How to Decide Which Blog Posts to Refresh First](https://blog.lots.blog/content-refresh-prioritization) has a script that reads the Search Console API and compares two 28-day windows for every page.

*Details from LotsBlog's [skill file](https://lots.blog/skill.md), [tool list](https://api.lots.blog/tools.json), [REST documentation](https://api.lots.blog/docs.md), [pricing](https://lots.blog/pricing), the [support changelog](https://support.lots.blog/changelog) and the product code, and from Google's [impressions, position and clicks](https://support.google.com/webmasters/answer/7042828), [About Search Console data](https://support.google.com/webmasters/answer/96568), [sitemap](https://developers.google.com/search/docs/crawling-indexing/sitemaps/build-sitemap) and [publication date](https://developers.google.com/search/docs/appearance/publication-dates) pages, all read on 31 October 2026. Google can change its guidance.*
