Choose Which WordPress Articles to Update First

Update first the articles that are wrong, then the ones customers depend on, then the ones missing a task readers need, and weigh observed search demand alongside those three. An old publication date is not on that list. An accurate three-year-old article can wait; a six-month-old article with a discontinued price cannot.

The content maintenance section of the WordPress SEO reference explains why updates should respond to a finding. This guide turns that into a queue: an inventory, a scoring worksheet, and a bounded assignment for each update.

Why age is the wrong trigger

Google’s guidance on helpful content lists warning signs of content made for search engines rather than people. Two of them apply directly to refresh programs: changing the date of pages to make them seem fresh when the content has not substantially changed, and adding or removing a lot of content mainly because you believe it will help your search rankings by making the site seem “fresh.” Google’s answer on the second is “No, it won’t.” Google’s guidance on creating helpful content, checked September 27, 2026.

Dates themselves should be honest. Google’s byline date documentation recommends a visible date labeled as published or last updated, and says the dates must describe the publication or update of the page. Google’s documentation on byline dates, checked September 27, 2026. Change the “last updated” date when you make a substantive change, and not otherwise.

There is a second reason not to rewrite by age. Google’s guide to debugging traffic drops recommends avoiding radical changes to a page that is already performing well. Google’s guide to debugging Search traffic drops, checked September 27, 2026. A refresh should fix something specific.

Inventory what is wrong or missing

List the articles in a spreadsheet with these columns. Fill the editorial columns by reading, not by guessing from titles.

For search data, Google Search Console’s Performance report shows clicks, impressions, click-through rate, and average position per page, and can compare two date ranges. Google’s Performance report help and its page on advanced filtering and comparison, checked September 27, 2026. Use the same period for every row, and treat the numbers as one input rather than the ranking.

Ask support and sales which pages they send to customers and which questions keep coming back. Search Console does not record that information, and it can point to the most important updates.

Score editorial need with observed demand

Give each article a score from 0 to 3 on four criteria, then sort. The criteria and scale below are a starting point you should adjust to your business, not a formula from any search engine.

A worked example for the fictional garden.example site, with invented numbers for illustration only:

Two rules override the total. A factual error that could mislead a customer about money, safety, or legal obligations goes to the top regardless of its score. And an article that scores zero is not automatically a deletion candidate; that decision needs its own review, covered in audit low-traffic WordPress content before deleting it.

Assign a bounded update with an owner

Each item in the queue gets a short assignment, so the update does not turn into an open-ended rewrite:

Article: /consultation-prices/
Reason: Price changed on September 1; page still shows old price
Change: Replace price table; update the booking paragraph
Do not change: Process section, examples, URL
Evidence: Current price list from the owner, dated
Owner: Studio manager
Reviewer: Editor
Update the "last updated" date: Yes (substantive change)

The “do not change” line protects the parts of the page that work. The date line forces a decision about whether the change is substantive.

If two articles in the queue turn out to answer the same question, stop and decide whether to combine them before updating either. See two articles answer the same question: merge or separate.

Use plugin checks as prompts, not the queue

SEO plugins can flag missing metadata and other mechanical issues. WP Visibility’s wp visibility audit reports an estimate of published content without a hand-written description, and wp visibility post-audit <id> checks one post’s title length, description length, word count, and number of H1 headings, among other checks. See Run the site audit. These are useful prompts when you open an article for an update. They cannot tell you whether a price is wrong or whether customers need a missing section, so they should not decide the order of the queue.

After each update

1. Read the published page in a private window and check the changed sections, links, and any forms.
2. If the title or description no longer matches the updated content, revise them.
3. Record the date, what changed, and why, in the inventory.
4. Set the next review date by how fast the subject changes: a price or software procedure may need checking after every change; a stable explanation may need attention only when new questions arrive.
5. If you compare search data later, use Search Console’s date comparison and remember that other events, such as periodic changes in user sentiment, news, or a competing site’s improvements, can also move the numbers. Google’s Performance report guidance notes that it can be difficult to determine whether a specific change caused an improvement. Google’s Performance report common tasks, checked September 27, 2026.