---
title: "How to generate summaries inside the post editor"
url: https://hostmy.blog/docs/rankready/generate-in-post-editor/
date: 2026-08-24
modified: 2026-08-25
lang: en
author: "Aditya Sharma"
description: "Generate a summary for the post you are working on, check what it wrote to the post, and know when to regenerate."
word_count: 832
---

# How to generate summaries inside the post editor

Most RankReady generation happens one post at a time, while that post is the thing you are thinking about. This page covers that workflow: what has to be in place first, what generation writes to the post, and how to confirm it worked before you move on.

## Why per-post, and not a bulk run

Bulk regeneration and automatic generation on publish are both listed as coming soon. They are not in 1.3.0. Generation in this version is something you trigger for a specific post.

That constraint is less annoying than it sounds, because a summary is a published claim about a page and benefits from being read before it ships. Doing it at the moment you finish writing, when you still have the article in your head, is when you are best placed to spot an inaccurate bullet.

## What has to be true before you generate

- **A provider key is saved.** Go to the **RankReady** menu, then the **Settings** tab, and paste a key for OpenAI, Anthropic Claude, Google Gemini or DeepSeek. Summaries and the FAQ generator are the only two features that need one.
- **The selected provider matches the key you saved.** A key saved for one provider while another is selected is the most common reason nothing happens.
- **The post has real content.** Generation reads the article. A stub produces a summary of a stub.

Generation is unlimited, so there is no counter to conserve and no reason to hold back on a post that deserves one.

## Generate, then read it

Run the generation for the post. The bullets that come back are the description your site will publish about that page, including in your [Article schema](https://hostmy.blog/docs/rankready/add-article-speakable-schema/), so read them before you carry on.

Reject a summary and regenerate if:

- A bullet states something the article does not say
- A number, date or name appears that you cannot find in the article
- The bullets would fit any article on the topic rather than this one

## What generation writes to the post

The output is stored as post meta on that post. The summary is stored as a set of bullets, and generated FAQs are stored as a flat list of question and answer pairs.

Two consequences worth knowing:

- **It travels with the post.** Exports, migrations and backups carry it. Moving a post between environments brings its summary with it.
- **It survives redesigns.** Changing theme or rebuilding a template does not remove it, because it is attached to the post rather than to the layout.

## Confirm it on the front end

Do not stop at the wp-admin screen. Two checks take a minute:

- **Load the published post.** Confirm what you expect to be visible is visible.
- **Run Google's Rich Results Test on the live URL.** Open **Detected items**. If you generated a summary, expand `Article` and read the `description`. It should sound like your bullets. If you generated FAQs, expand `FAQPage` and check the questions match the set you kept.

Use the published URL rather than a preview link, because the test fetches your page the way a crawler would and cannot sign in.

Here is the connection that catches people: Article schema is built from the summary. RankReady returns early and emits no Article JSON-LD when a post has no summary. If `Article` is missing from the test results, check that you generated on the same post you are testing.

![The WordPress posts list with RankReady columns showing generation state per post](https://hostmy.blog/wp-content/uploads/2026/08/rr-posts-list-v2-scaled.png)The posts list is the fastest way to see where you have generated and where you have not.

## Working through an existing archive

With no bulk runner in this version, order matters. A workable sequence:

- Start with the pages you would most want described accurately: product and service pages, your best-read guides, anything you link to often.
- Then work down by traffic or by business value, not by publication date.
- Handle the rest as you touch them. Any post you edit is a post worth generating for while you are already there.

## Regenerating after an edit

Nothing regenerates by itself. If you substantially rewrite an article, its stored summary now describes the old version, and so does the Article description built from it. Regenerate the post, then purge your page cache so the updated markup is served rather than a stored copy.

A light typo fix does not need a regeneration. A change to what the article actually claims does.

## If nothing happens

| Symptom | Likely cause |
| ------- | ------------ |
| No output at all | No key saved, or the saved key belongs to a different provider than the one selected. |
| Provider error | Key revoked, or no credit or quota left. Check the provider's own dashboard. |
| Admin shows new text, front end shows old | Page cache or CDN. Purge and reload. |
| Schema missing after generating | Wrong post, wrong URL tested, or a cached page. |

## What generating proves

It proves your post now carries an accurate, machine-readable description of itself. It is not evidence that anything read the page, quoted it or sent a visitor. Generate for the posts where an accurate description matters, and measure only what you can see.