Content editing and maintenance guide
Audit Low-Traffic WordPress Content Before Deleting It
Low search traffic alone does not mean a page should go. Check its other uses, accuracy, and overlap, then decide to keep, improve, consolidate, or retire it.
On this page
Before deleting a page because few people find it through search, check three things: whether it is used in other ways, whether it is accurate, and whether another page already does its job. Then record one of four decisions: keep, improve, consolidate, or retire. A traffic threshold cannot make that decision for you, because a page with ten visits a month can be the one your support team sends to every new customer.
Google does not recommend pruning for its own sake. Its helpful content guidance lists “removing a lot of older content primarily because you believe it will help your search rankings overall” as a warning sign, and answers the idea that this makes a site seem fresh with “No, it won’t.” Google’s guidance on creating helpful content, checked September 27, 2026. Retire a page because it no longer serves anyone, not to shrink the site.
Check uses beyond Google visits
Search traffic is one way a page gets used. Before judging a page on it, look for the others.
| Use | How to check |
|---|---|
| Support and sales | Ask the teams whether they link the page in emails, help replies, or proposals |
| Internal links | Search your content for the URL; see the command below |
| Navigation and forms | Check menus, footers, and whether the page holds a form, download, or embed |
| Printed and external material | Brochures, invoices, partner sites, social profiles, and email sequences |
| Conversion help | In your analytics, check whether visitors who view it go on to contact or buy |
| Legal or policy role | Terms, privacy, returns, and accessibility pages can be required or expected regardless of traffic |
| Seasonal demand | Compare the same months in previous years |
To find posts that link to a URL, WP-CLI’s wp db search command searches the text columns of the site’s WordPress tables for a string (checked September 27, 2026):
wp db search "garden.example/soil-testing/"The address is illustrative. The command reports matches and does not change anything. A link saved as a relative path, such as /soil-testing/, will not match a search that includes the domain, so search for the path as well. It finds the URL in stored content and settings, such as post bodies and custom menu links, but not in theme files or on external sites. A classic menu item added from the Pages or Posts list stores no URL of its own; WordPress blanks it and uses the linked object’s address (wp_update_nav_menu_item(), checked September 27, 2026), so check menus by hand.
On seasonality, Google’s guide to traffic drops suggests filtering the Performance report by query and checking Google Trends to see whether demand changed across the web rather than just for your site. Google’s guide to debugging Search traffic drops, checked September 27, 2026. A page about frost protection may look dead in July.
Inspect accuracy and duplication
Read the page as a customer would.
- Is it accurate? Check prices, services, products, steps, screenshots, and links against current facts. Ask the factual owner about anything you cannot verify.
- Does it have a distinct purpose? Name the reader and the task in one sentence. If you cannot, the page may never have had a clear job.
- Does another page do the same job? If so, you are looking at a consolidation, which needs its own comparison. See two WordPress articles answer the same question: merge or separate.
Four sample decisions
These fictional pages from garden.example show how the evidence leads to different outcomes. For each, the last column names the evidence that would change the recommendation.
| Page | Findings | Decision | What would change it |
|---|---|---|---|
| “Soil testing before planting” | Few search visits; linked in every consultation confirmation email; accurate | Keep | The email sequence changing to link elsewhere |
| “Watering schedule for new beds” | Modest visits; recommends a watering product the studio no longer stocks | Improve: replace the product section | The owner confirming the whole method is outdated, which would make it a rewrite |
| “Spring planting tips” | Few visits; covers the same ground as the fuller “Spring planting guide” | Consolidate into the guide and redirect | Evidence that it serves a different reader, such as a beginner audience |
| “2021 open garden weekend” | No visits in two years; event over; no links or other uses | Retire | A request to keep it as an archive of past events |
The “Keep” row is the clearest case a traffic threshold would have gotten wrong.
Retire a page without breaking things
When the decision is to retire, choose what the old URL should do. Google documents the options:
- Remove it and let it return 404 or 410. Google’s documentation on HTTP status codes says that for these codes the indexing pipeline removes the URL from the index if it was previously indexed, and crawling gradually decreases. Google’s HTTP status code documentation, checked September 27, 2026.
- Redirect it to a relevant replacement. Only do this when a page genuinely covers the same need. Google warns that redirecting many old URLs to one irrelevant destination, such as the homepage, can confuse users and might be treated as a soft 404. Google’s documentation on site moves with URL changes, checked September 27, 2026.
- Keep it available but out of search with noindex. Google notes that a noindex tag only keeps the page out of Google results; users and search engines that do not support noindex can still reach it. Google’s documentation on removing a page from Google, checked September 27, 2026. This suits pages customers still need by link, such as an order confirmation guide.
In WP Visibility, the Redirects module (off by default) can send a retired URL to its replacement or answer 410, as described in Redirect a changed URL. Setting Noindex on a page that should stay reachable is covered in Keep a page out of search. Make the editorial decision first; the plugin carries it out.
Before deleting anything, confirm you have a current site backup you can restore, and export the page’s content if it might be useful later.
Record the decision and its dependencies
For each page, write a short entry in your content inventory:
URL: /2021-open-garden-weekend/
Decision: Retire (410)
Evidence: Event over; no internal links found; no support or sales use
Dependencies checked: menus, email sequences, printed program (none)
Decided by: Editor, with studio manager
Date:
Review: none neededThe dependencies line matters most. Update any internal links, menus, or email templates that pointed at a retired or redirected page so they go straight to the right place.
After the change, open the old URL in a private window and confirm it returns what you intended; the page you see does not always name the status code, so check it in your browser’s developer tools. Check that it no longer appears in your sitemap if it was retired or redirected; a page that is still published stays listed in WP Visibility’s sitemap even when a redirect rule answers for its address, so trash it. For pages marked “Improve”, add them to the update queue described in choose which WordPress articles to update first. The WordPress SEO reference covers maintenance decisions more broadly.