Should you update an article or write a new one?
Inspect sources and measurements associated with an intervention. The supported automatic review path currently uses WordPress and Search Console.


Inspect sources and measurements associated with an intervention. The supported automatic review path currently uses WordPress and Search Console.
Publishing a new article feels like progress. Sometimes it is the wrong move. If an existing URL already answers the same question, a second page can divide signals, confuse internal linking and create two incomplete resources instead of one strong answer.
The decision is not “old content versus fresh content”. It is same intent or different intent. Search Console shows where your pages already appear; the content inventory shows what you have promised; business context shows which answer matters.
Start with the reader’s job
If the proposed page would satisfy the same reader, at the same stage, with substantially the same answer as an existing URL, update or consolidate. A new article is justified when the task, audience stage or required format is meaningfully different.
Read the page-query relationship
Google Search Console reports clicks, impressions, CTR and average position by dimensions such as page and query. Compare complete, equivalent periods and inspect the queries associated with the candidate URL. Do not make the decision from total traffic alone.
Use three checks:
- Does an existing page already receive impressions for the target query family?
- Does that page actually answer the dominant intent?
- Are several URLs sharing similar queries without a clear winner?
The Search Console action guide explains how to turn those metrics into a diagnosis. If the issue is simply a declining page, use the traffic-drop workflow before commissioning new content.
Update when the intent already belongs to the page
Choose an update when the URL is still the right destination but its answer is incomplete, outdated or poorly presented. Typical evidence includes:
- relevant impressions already reaching the page;
- stable intent but missing subtopics;
- obsolete screenshots, product behaviour or examples;
- good position with weak CTR caused by a mismatched title or snippet;
- internal links pointing to the correct URL, but insufficient depth on the page.
An update may involve a new section, better evidence, a clearer introduction, refreshed visuals or metadata. It does not automatically require a full rewrite. Rank candidate changes with the evidence-based content update method.
Consolidate when two pages do the same job
Two URLs can target the same intent even when their keywords are not identical. Compare their queries, headings, incoming links and conversion role. If neither page has a defensible separate purpose, choose a primary destination, merge useful material and plan redirects or canonical handling with technical care.
Do not delete a URL merely because it has fewer clicks. It may hold links, serve a different locale or support a narrower task. Consolidation needs a URL-level review and a migration plan.
Create when the intent is genuinely distinct
A new article earns its URL when it needs a different answer. Examples include:
- definition versus step-by-step configuration;
- comparison versus troubleshooting;
- general workflow versus a provider-specific guide;
- measurement methodology versus interpretation of a result;
- beginner explanation versus an implementation reference.
Before drafting, assign the new page to a cluster and identify published pages that can link to it. If no natural path exists, the topic may sit outside the site’s useful territory.
Reject or postpone weak ideas
Not every keyword deserves a page. Reject or postpone when the idea has no distinct intent, no relevance to the offer and no supporting evidence. A strategic product guide can proceed without search volume, but label the rationale honestly; do not invent a demand figure.
Seasonal changes, SERP redesigns and lower demand can reduce clicks without creating a content gap. Google’s own guidance recommends comparing periods and looking for patterns across affected pages before drawing conclusions.
A practical decision table
| Evidence | Best first action |
|---|---|
| Existing page ranks for the intent but is incomplete | Update |
| Two pages answer the same task | Consolidate or differentiate |
| No page answers a distinct relevant task | Create |
| Impressions stable, CTR weak, promise mismatched | Test title/snippet alignment |
| Demand fell across the query family | Monitor or reassess demand |
| Topic has neither evidence nor strategic value | Reject |
Keep EN, IT and ES as one editorial unit when they cover the same intent, but review each locale’s query language separately. Localisation can change examples and phrasing without multiplying the underlying topic.
Frequently asked questions
Is an old publication date a reason to rewrite?
No. Accuracy, intent fit and evidence matter more than age alone.
Can two pages rank for related keywords?
Yes, when they solve different tasks. The risk appears when they compete to provide essentially the same answer.
Should a low-performing article be deleted?
Not automatically. Check intent, links, conversions, locale and technical status before choosing an action.
Does a new article always increase topical authority?
No. Redundant or weak pages can make the site less coherent.
Give every URL one clear job
Update when the existing destination is correct, consolidate when two pages duplicate that job, and create only when the user needs a distinct answer. The result is a smaller, clearer plan built on evidence rather than publishing volume.
What BeKnow keeps
Keep interventions, hypotheses, assets, observations and decisions in a searchable workspace. Record what is known and what still needs checking.
A change in performance after an intervention does not prove that the intervention caused it. Cross-platform attribution and a complete analytics dashboard are not available today.
Project memory and data imports do not require an AI model key. A compatible external AI client may have its own costs. BYOK applies only to available functions that actually call an external provider.
Next step
Start with one project, one documented change and the evidence needed to review it. Source connections.
About the author
Marco Salvo is the founder of BeKnow. With more than 20 years in SEO, he created BeKnow to connect project changes with real-world results and turn that history into knowledge people and AI can use.
Record your first intervention
Start with one project, one documented change and the evidence needed to review it.
Create a free workspace