---
title: "Writing Short Sentences on WordPress: Five Rewrites and a Counter"
url: https://hostmy.blog/write-sentences-ai-can-quote/
date: 2026-09-15
modified: 2026-11-12
lang: en
author: "Aditya Sharma"
description: "A plain editing method: short sentences that make one claim each, five before-and-after rewrites, and a script that counts the long ones on your own page."
categories:
  - "RankReady"
image: https://hostmy.blog/wp-content/uploads/2026/11/hmb-card-1866-v2-1024x538.jpg
word_count: 1445
---

# Writing Short Sentences on WordPress: Five Rewrites and a Counter

*Update, 4 November 2026: this post used to report figures from one third-party study of sentences that AI tools quoted, and turned them into a length rule. We have removed those figures and that rule. Most of them match the study's own article and data, but the study is self-published and its sentence data comes from Gemini only, so nobody can show they apply to your site. What remains is a plain editing method for writing short sentences that make one claim each.*

Short sentences that make one claim are easier to read. Software that extracts text from a page also handles them better, because each sentence stands alone. That is the case for this method, and it is all we claim.

Open your best performing post and count the words in the first sentence. Then count how many sentences on the page run past 20 words. We use 20 as a rule of thumb. It is our own habit, not a measured limit.

## Put the claim up top

A short sentence buried on line 400 is still buried. Your best short claim belongs near the top, not after the anecdote and the context and the three caveats.

The work happens on article pages, and [your homepage is the wrong page to tune](/homepage-wrong-page-for-ai/).

So the rewrite job has two halves. Shorten the claim sentences, and move them up.

## Five rewrites, with the counts

Here is the method applied to real sentence shapes. Word counts in brackets.

**Before (29 words).** While there are many factors that influence how quickly a page loads, our testing suggests that image size is one of the more significant and consistently measurable variables involved.

**After.** Image size affects load time. (5) Large images slow a page down. (6)

Two sentences, both short, each with one claim. The padding went.

**Before (30 words).** If you're running a WordPress site and you haven't yet checked whether your pages are actually reachable by AI crawlers, this is probably the first thing you should look at.

**After.** Check crawler access before anything else. (6) A page returning 403 cannot be read by that crawler. (10) Run one curl request per crawler and read the status code. (11)

The conditional opener was doing no work. Cutting it moved the instruction to the front of the sentence.

**Before (26 words).** Our plugin, which was built specifically for the problem of machine readability on WordPress, works alongside existing SEO plugins without creating conflicts or duplicating their output.

**After.** RankReady runs alongside Yoast, Rank Math, AIOSEO and SEOPress. (9) It writes the AI-era layer only. (6) Your SEO plugin keeps the Article node. (7)

The subordinate clause in the middle of the original split the subject from its verb by fourteen words.

**Before (29 words).** Sourdough starter typically takes somewhere between five and seven days to become active enough to use for baking, although this can vary depending on the temperature of your kitchen.

**After.** Sourdough starter takes five to seven days to become active. (10) Warm kitchens are faster. (4) Cold kitchens are slower. (4)

The qualifier did not disappear. It moved into its own sentence, where it stands on its own.

**Before (15 words).** This means that it will not work in the way that most people currently expect.

**After.** A caching plugin can serve a stale Markdown page. (9)

The original was short and still useless, because `This` and `it` refer to something the reader cannot see. Length was never the only problem.

## Four edits fix most long sentences

Every rewrite above uses the same four moves.

**Cut the conditional opener.** Sentences that start with `While`, `Although`, `If you`, `Given that` or `When it comes to` spend their opening words before reaching the claim. Delete the opener, start at the claim.

**Split at the conjunction.** Any `and`, `but` or `which` joining two complete thoughts is a sentence boundary you have not used yet. Two sentences of nine words beat one of nineteen.

**Move the qualifier down.** Caveats are real and should stay. They belong in the next sentence, where they stand alone rather than dragging the claim out to a length nobody finishes.

**Make each sentence resolve alone.** A sentence starting `This means`, `It does`, `They can` or `That is why` cannot be understood on its own, because the referent is in a sentence the reader may not have seen. Name the subject again. Repetition reads slightly worse to a human and better to a machine.

## Do not write the entire page at nine words

Worth saying, because the failure mode of this advice is obvious and unpleasant to read.

A page of uniformly short sentences reads like an instruction manual. Nobody finishes it, and the people who leave were the audience.

The working split on the pages here is this. Claim sentences, the ones carrying a fact, a number or a definition, go short and stand alone. That is also [how trust signals get read one line at a time](/eeat-seo-ai-answers/), rather than as a property of the whole page. Connective prose, transitions, examples and the parts carrying voice can run longer.

Aim for the top of the page and the first sentence of each section.

## Measure your own page in one command

Guessing at sentence length does not work. Count it.

`curl -s https://yoursite.com/your-post/ -o /tmp/p.html

python3 - <<'PY'
import re
html = open('/tmp/p.html').read()
body = re.sub(r'<(script|style)[^>]*>.*?</\1>', ' ', html, flags=re.S|re.I)
text = re.sub(r'<[^>]+>', ' ', body)
text = re.sub(r'\s+', ' ', text)
sents = [s.strip() for s in re.split(r'(?<=[.!?])\s+', text) if len(s.split()) > 2]
over = [s for s in sents if len(s.split()) > 20]
total = max(len(sents), 1)
print(f'{len(sents)} sentences')
print(f'{len(over)} over 20 words ({len(over)*100//total}%)')
print('\nLongest offenders:')
for s in sorted(over, key=lambda x: -len(x.split()))[:8]:
print(len(s.split()), s[:100])
PY`

Read the over-20 percentage as your own score. There is no pass mark, so use it to compare the same page before and after a rewrite pass.

The offender list at the bottom is the actual worklist. Ten minutes per page, no tooling required. For [scoring a whole archive rather than one page](/measure-quotable-writing/), the same counting runs against a sitemap.

## Headings: sequential, and fewer than you think

Structure is a separate job from sentence length. Treat this section as house practice, not a finding.

Sequential heading order, H2 then H3 then H4 with no skipped levels, is free and keeps the page easy to parse. Fix any page that jumps from H2 straight to H4.

Volume is a judgment call. A page chopped into twenty sections gives the reader more places to stop than the same page with eight.

That has a direct consequence for FAQ blocks, since every entry generates a heading. Cap them at four to six real questions rather than padding to twenty. More detail on that in [structured data in WordPress](/structured-data-wordpress/).

## What the plugin does and does not do here

None of the rewriting above is automatable, and no plugin should claim otherwise. Sentence work is editing, and editing is you.

The machine readable half is different. Summary blocks near the top of the page, FAQ markup, Markdown copies and crawler rules are repetitive and easy to get wrong by hand. That set is what [RankReady](https://wordpress.org/plugins/rankready-ai-llm-seo/) handles. It is a WordPress AI SEO plugin, it runs alongside Rank Math, Yoast, AIOSEO or SEOPress rather than replacing them, and setup is about five minutes.

What that changes is crawlability and how cleanly your page parses. Nothing here says an AI assistant will quote, cite, recommend or show any given sentence. No plugin controls that, and no vendor should tell you otherwise. To see what one platform does expose, read [the one that still shows you the line it took](/gemini-text-fragments/).

## Where Pro fits

Free: generating summaries and FAQs by hand is unlimited, using your own AI provider key. Pro adds generation on publish, bulk generation across your archive, HowTo and ItemList schema and custom post types. Pro is a one-time payment with lifetime updates and a 14-day money-back guarantee. The current price is in the [pricing section](https://hostmy.blog/plugins/rankready/#pricing). You do not need Pro for anything in this post.

## Run the counter on your best page

Copy the Python block, change the URL, run it. It takes thirty seconds and it gives you a number rather than an impression.

Then fix the eight longest sentences on that page and run it again. That is the whole loop.

Once the sentences are right, the question underneath them is whether machines can reach the page at all, which is layer one of [a full pass over all five layers](/five-layer-ai-seo-audit/).

What percentage of your best page currently sits above 20 words, and would you have guessed that number correctly?