REFRESH THE ARTICLES ALREADY ON YOUR SITE

Import them from your CMS, see what has changed since they went out, and get the edits with the reason for each one. You approve what you want, republish to the same URL, and Search Console shows what moved.

Your archive is still working. Some of it.

An article goes live and starts drifting. The statistics date. A competitor publishes something more complete. The question buyers type changes shape. The page has not moved, but its position has.

The usual answer is to publish more, which leaves the older work exactly where it was and gives it something new to compete with.

THE ARTICLE THAT BROUGHT YOU BUYERS IN 2024 CAN DO IT AGAIN IN 2026
IMPORT IT · RESEARCH WHAT MOVED · APPROVE EVERY EDIT · REPUBLISH · MEASURE

Search Console picks the targets

Connect Search Console and Eclipse reads your own numbers, page by page and query by query, then puts the pages with something to gain at the top of the list.

Ranking eight to fifteen

Close enough that a stronger version moves it onto the first page.

Impressions without clicks

The page is being shown to buyers and passed over.

Slipping week on week

Position drifting the wrong way while the query holds steady.

Import your existing articles

Connect your CMS and pull the live articles in. Each one lands in your content table as a full Eclipse item, carrying its source, its published URL and the date it went out.

From there it behaves like everything else in your account. Content profiles apply. Research applies. The editor opens. Approvals apply.

  • WordPress
  • Webflow
  • Wix
  • Contentful
  • HubSpot
  • Ghost

Two ways to refresh

Both modes run research before they write, so the material going in is current. A refresh usually takes minutes.

Refresh

Keeps the article's identity, its argument and its voice.

  • Updates the facts and statistics that aged
  • Replaces references that broke
  • Strengthens the sections that were thin
  • Adds the material that is missing

Best practice alignment

A more assertive pass that rebuilds the article against Eclipse's SEO and GEO standards.

  • Rewrites structure rather than patching it
  • Runs through a separate workflow
  • Set as your default, chosen per article, or applied across a selection

Review every change in the editor

Suggestions open in the editor as additions and removals, marked in place where they belong. A panel beside the text explains each edit and counts the ones you have not answered yet.

Accept a change and it becomes part of the article. Decline it and it disappears. Edit it and it becomes yours. Nothing reaches your site until you have been through them.

E-E-A-T scored before and after

CASi scores every article against E-E-A-T. A refreshed article is scored again, and both scores stay on it, so you can see whether the gain came from experience, expertise, authority or trust.

BEFORE61
AFTER88

Republish to the same URL

Approved work goes back to the CMS it came from and replaces the version that was live. The address holds. Eclipse keeps every version, so you can open the one before this and compare them.

See what the refresh did

Eclipse records the date you republished against the URL. Search Console keeps reporting, and Eclipse shows the before and the after for the page and the queries feeding it.

Impressions4,18011,940
Clicks96412
Average position14.26.1

One account, every client's archive

Agencies run this across every client from one account, with each workspace separate. Every client asks the same thing after the first quarter. What happens to everything you wrote for us last year?

Common questions

Put one article to the test

Bring a page that used to perform. We will import it, refresh it, and show you every change and why we made it, before anything goes near your site.