Existing content
Check what you already published before adding more.
Search performance can help identify articles that deserve attention. A decline is a reason to investigate, not automatic proof that a page needs rewriting or that another article should replace it.
Use performance signals to choose a review
Review Search Console clicks, impressions, and position alongside Essel's available decay signals. The decay detector uses estimated traffic, tracked rankings, and citation recency—not Search Console clicks or impressions. Missing data, seasonality, and changes in demand can affect the pattern.
Decide what changed
Check whether product details are outdated, customer questions remain unanswered, sources have changed, or a better page already exists. An accurate page may need a clearer example or stronger internal links rather than a complete rewrite.
- Update an obsolete claim or broken reference.
- Add original evidence or an implementation example.
- Resolve overlapping intent before creating another URL.
- Leave useful, accurate content alone when no substantive change is needed.
A recommendation is not a completed update
Detection, rewriting, approval, and republishing are separate actions. Do not treat a refresh suggestion as evidence that an existing page has changed. Review the revised article and use the linked publishing flow when it is ready; check destination behavior before assuming any imported page can be updated automatically.
Keep the URL and a record of the change
Where possible, update the existing useful URL and record what changed. Recheck the same queries and periods after publication. A subsequent lift or decline is an observation, not proof that the edit alone caused it.