A WordPress excerpt can stay unchanged because it comes from a manual excerpt, an automatic summary, or a builder field separate from the article body. Find the source used by the affected card before changing cache settings or rewriting the post.
Identify the surface showing stale text
Copy the public archive URL and the exact sentence that looks wrong. Check whether the same text appears on the homepage, category page, site search, and post itself. These views can use different templates.
A Google search snippet is another surface altogether. Updating an excerpt does not force Google to use it or refresh it immediately. Keep this diagnosis focused on text your website currently renders. For a post missing entirely, use blog listing diagnostics.
Inspect the stored content choices
Open the post editor and find the excerpt control available in your editor setup. Check for a manually saved summary. If it exists, editing the introduction may not change the archive's excerpt.
If there is no manual excerpt, inspect the template. A native Excerpt block can generate summary text from the post. A Content block, custom field, or builder card may follow different rules. The More block is not a universal override for every excerpt renderer.
| Where the old sentence lives |
Smallest useful change |
| Manual excerpt field |
Edit and save that field |
| Beginning of article body |
Confirm automatic summary behavior |
| Builder custom field |
Update the field the card reads |
| Shared pattern or static card |
Edit the shared source intentionally |
Locate the sentence: Which public archive or card is stale?. Find its owner: Excerpt, body, custom field, or template. Change one source: Use a harmless staging sample. Verify the archive: Check summary, truncation, and destination. Explanatory checklist, not a customer test result.
Prove the source without publishing test copy
Use a staging post with a distinctive, harmless summary. Change one source at a time and inspect the matching archive card. Record which change reaches the public output. Do not publish test keywords on a live page just to track the path.
For a developer handoff, provide the post ID, template name, card or block type, and before-and-after excerpt. This is more useful than saying that all caches have been cleared. If a template displays the wrong post's text, inspect its query context before changing the content itself.
Then examine cache scope
Save the corrected source and load the affected archive signed out. The individual post page can be fresh while the archive containing its card remains cached. Purge the archive or relevant fragment through the site's supported cache controls, then compare again.
Check translated versions separately. A language-specific post may have its own excerpt. Also check whether a content API supplies the card, since its cache can differ from the server-rendered page.
Verify the summary as editorial content
Make the summary a useful description of the answer, not a string of keywords. Confirm it does not expose private notes, broken shortcodes, or raw markup. Check truncation on mobile and ensure the Read More destination opens the correct canonical post.
Keep a note of which field owns each important listing template so the next editor does not have to rediscover it. If the repair affects a shared template, spot-check another post that uses a manual excerpt and one that does not.
HandL WP can trace stale archive content when a builder, API, or cache layer obscures the source.
Reference: WordPress Excerpt block.
References reviewed October 2, 2026. Examples are explanatory; production changes require an appropriate backup and authorized access.