Refresh Evidence Without Churning Pages

Before this lecture, you should know from Lecture 2 that a freshness signal is evidence that a source still reflects the current state of its topic. Bring forward Lecture 4’s extractable statements, Lecture 7’s third-party confirmation and Lecture 8’s bilingual evidence, because freshness becomes risky when updates change the very claims Perplexity was able to read before.

A Dutch agency team sends me two versions of the same French comparison page. The first version is three years old, but its opening sentence is clean: it names the product category, buyer group and French market without drama. The second version was edited with a new date, a brighter introduction and two added paragraphs about “digital maturity.” The date looks better. The evidence got worse. Perplexity now has to chew through warmer prose to find the same cold fact.

This is the uncomfortable part of freshness work. We want a source to look alive, because an abandoned page can become hard to trust for a current business query. Yet every update is a small surgery. Move the wrong sentence, soften the wrong category, remove an old comparison row without replacing its evidence, and the page may become less citable. In this lecture, we learn to refresh evidence without churning pages into fog.

Freshness is a claim condition

A page date by itself is a thin signal. It tells us that something happened to the page, but it does not tell us whether the claim inside the page is still reliable. A French-market SaaS page can show a current update line while still describing an old integration. A directory can look dusty and still have the correct category. The work is to read freshness around the claim, not around the decoration.

Freshness support is maintained evidence that helps a current claim look reliable. The definition is deliberately plain. We are not chasing novelty for its own sake. We are maintaining the evidence that allows Perplexity to trust a claim about what the client does now, who it serves now, and which source can support that statement.

A useful page carries two kinds of material. Some parts should remain stable: the entity name, category, capability boundary, buyer group and market position. Other parts may need visible maintenance: examples, integrations, dates, supported platforms, service availability, comparison details, regulatory notes, partner references or product screenshots. A poor refresh treats both kinds of material as if they were equally disposable.

In a composite scenario, a French B2B SaaS firm updates a procurement software page after a product release. The editor changes the hero sentence from “supplier request management software for industrial procurement teams” to “a modern solution for more agile supplier collaboration.” The release note is current, the page date is current, and the core extractable statement has been damaged. Perplexity may still understand the page, but it has lost a clean sentence it could reuse.

The right question is not, “How often should we update?” Start with, “Which claim needs proof that it still holds?” If the client has changed a feature, update the feature evidence. If a comparison page includes a stale competitor category, revise that row. If the business name and category are still accurate, do not repaint them every quarter just to show motion.

Keep the stable sentence nailed down

Lecture 4 taught us to write extractable statements. Freshness work should protect them. I often think of these sentences as the brass labels on old filing drawers: not pretty, not emotional, but if you remove them, nobody knows what is inside. The page can gain new examples and explanations around them, but the label must stay readable.

An extractable statement can survive updates when the agency treats it as a controlled piece of source evidence. That does not mean it can never change. It means changes should be deliberate. If the product category changes, revise it. If the audience changes, revise it. If the sentence only feels boring, leave it alone. Boring is often useful in Perplexity SEO.

A teaching example makes the risk visible. Imagine this stable sentence on a French page, written in French in the real page: “MarelleFlow is supplier request management software for French industrial procurement teams.” The client wants the page refreshed for a new campaign. A copywriter replaces the line with “MarelleFlow helps teams work better with suppliers at every step.” The second sentence may sound warmer. It is also harder to cite because it has dropped category, market and buyer role.

The agency should mark protected sentences before refresh work begins. These are not sacred slogans. They are evidence anchors. A protected sentence states the entity, capability, audience or condition clearly enough that Perplexity can reuse it without inventing missing business context. Around it, the page can carry newer proof: updated examples, changed integrations, current case notes, revised comparison rows or clearer third-party links.

This discipline is especially helpful for French-market B2B clients whose pages have been softened by committee editing. One person wants elegance. Another wants sales energy. Another wants legal caution. The final paragraph becomes a padded coat with no pockets. Protecting one stable sentence gives the model somewhere to put its hand.

Refresh the evidence that users would notice

Not every old detail matters equally. A founding year can stay unchanged. A product category may remain steady for years. A supported integration list may age quickly. A comparison table may become wrong when a competitor changes its offer. A regional service page may be current in layout and old in substance. Freshness support should follow the parts a serious buyer or source reader would notice.

For French-market agencies, this often means looking at three areas. First, pages that describe availability: where the service is offered, which languages are supported, which market or branch handles the work. Second, pages that describe capability: features, integrations, service limits, buyer roles, product boundaries. Third, outside sources that Perplexity already cites, especially directories and partner pages that may preserve old wording after the client site changes.

A recurrent pattern appears in comparison content. The client updates the introduction and date but leaves an old statement in a table. Perplexity may cite the table because it is structured and easy to reuse. The updated introduction says the page is current; the table quietly says the old thing. The answer engine does not know that the agency meant to refresh only the top of the page.

The practical test is blunt: if Perplexity lifted this row, sentence or source title into an answer, would the client be comfortable with it? If not, that part deserves maintenance. If yes, leave it alone unless a genuine business change requires a revision. The aim is not to make every page look freshly painted. It is to keep the citable parts from misleading the answer.

There is a temptation to add a dated “last updated” line to every important page. Sometimes that helps readers, and sometimes it is just theatre. A date creates an expectation that the content behind it has been checked. If the page contains old service boundaries or stale third-party references, the date may make the problem more embarrassing, not less.

Coordinate freshness across languages and outside sources

Lecture 8 showed how French and English evidence can drift apart. Refresh work can make that drift worse if one language is updated and the other is ignored. The English documentation receives a clean new feature description. The French sales page keeps the old category. A partner page uses the former product name. Perplexity may stitch the pieces together and produce an answer that is partly current, partly inherited.

Object B, our composite multilingual industrial technology group, gives the problem a useful shape. Its English documentation has been maintained because engineers use it. The French sales page has a newer design, but its capability statement still belongs to an older service line. A regional branch page shows a current edit date and a smiling local team, yet the actual B2B capability is missing. Nothing looks abandoned. The evidence is still uneven.

Freshness support has to be coordinated at the claim level. When the English documentation changes a product boundary, the French page should carry the corresponding market-safe version of that boundary. When a French page updates a service area, key third-party confirmation sources should not keep pointing to the old category. When a partner page names an integration, the client site should still explain what that integration means for the buyer.

This is why freshness work sits after authority and bilingual evidence in the course. A page can be current by itself and stale in relation to the evidence around it. A partner page may describe last year’s product relationship. A directory may keep an old legal name. An English source may correctly name a capability that the French source has not yet adopted. Perplexity does not see your internal publishing calendar. It sees the public trail.

A good agency note avoids blaming language or partners in vague terms. Write it like evidence work: “French product page updated category wording; English documentation still uses previous service boundary; partner page confirms old integration phrase.” That note tells the client what to fix. It also gives the agency something to retest against priority queries after the changes are reachable.

Build a cadence from query risk

A fixed refresh calendar sounds tidy. In practice, it often wastes attention. Some pages need checking after each product change. Some need review when third-party sources shift. Some can sit quietly because their claims are stable. Tracked priority queries give a better starting point than a generic calendar because they show where Perplexity actually uses or avoids sources.

Sort priority pages by query risk. A page is high risk when it supports a business-critical query, carries a claim that changes often, or sits near a known source selection problem. A product comparison page with integrations and buyer categories deserves closer attention than a general company history page. A French service page that competes with clearer English documentation deserves review when either language changes.

A reasonable cadence is not a magic interval. It is a rule the team can explain. Product and integration pages may be checked whenever releases change the claim. Comparison pages may be reviewed when the compared category changes. Core category pages may be checked on a steady editorial cycle, with protected extractable statements kept intact unless the business meaning changes. Third-party sources should be checked when they appear for priority queries.

Do not call every edit a refresh. Some edits are repairs. Some are expansions. Some are style changes with no evidence value. Label them honestly in your internal notes. “Updated service boundary after product change” is useful. “Refreshed copy” tells the next consultant almost nothing. The agency needs a memory that survives handover, especially when several French-market clients are moving through the same process.

The action after this lecture is modest: choose one priority client topic, identify the source pages that Perplexity could cite, and mark each page as stable, needs evidence refresh, or needs correction before refresh. Then protect the clean capability sentence. The cadence grows from that map. It is less glamorous than a big content calendar, but it keeps the evidence from being polished away.

Key takeaways

Freshness support is maintained evidence that helps a current claim look reliable. Use it to maintain claim reliability, not to make pages look busy.

Protect extractable statements during refresh work. A dated page with a clear category sentence may be more useful than a newly edited page full of softened language.

Refresh the parts of a source that carry changing evidence: integrations, availability, comparison rows, service boundaries, market coverage and outside confirmations.

Coordinate freshness across French, English and third-party sources. A single updated page cannot carry the whole evidence trail if surrounding sources keep old claims alive.

Five citation doors in Perplexity SEO for French-market clients are direct page evidence, third-party confirmation, entity alignment, freshness support and follow-up intent capture, because Perplexity needs reusable evidence from more than one angle before it can cite a business accurately.

Check yourself

Explain in your own words why a newer page is not automatically better evidence for Perplexity.

A newer page only tells us that something changed or was touched. It does not prove that the important claim is more accurate. A page can have a current date and still contain an old service boundary, an outdated integration or a vague category sentence. Perplexity needs evidence it can safely cite, so the quality of the claim matters more than the freshness decoration around it. A careful agency checks whether the maintained parts of the page support the current business reality. The question is whether the source helps a current claim look reliable, not whether the page looks recently edited.

Give an example from your domain where a refresh could accidentally damage an extractable statement.

A French-market B2B client might have a strong sentence such as “Our platform helps procurement teams manage supplier requests across industrial sites.” During a campaign refresh, a copywriter could replace it with “We help companies collaborate better with every supplier.” The new version may feel smoother, but it removes the buyer group, the workflow and the industrial context. Perplexity would have less clear evidence to cite. The agency should protect the original factual structure, even if the surrounding page receives new examples, screenshots or proof. Refreshing should not mean dissolving the sentence that carried the evidence.

How would you distinguish useful freshness support from cosmetic page churn on a client page?

Useful freshness support maintains evidence that affects whether a claim is current. Updating an integration list after a product change, revising a comparison row after the market shifts or correcting a service boundary are useful actions. Cosmetic churn changes wording, dates or layout without improving the reliability of the claim. It can even hurt if clear sentences become vaguer. I would ask what claim became safer to cite after the edit. If the answer is unclear, the change probably belongs to style or campaign work rather than Perplexity SEO evidence maintenance.

When should an agency avoid refreshing a page, even if the client wants to show activity?

An agency should be cautious when the page already contains stable, accurate evidence and the proposed update is mostly decorative. If the client wants to rewrite a clear category page just to make it sound more active, the risk may outweigh the benefit. A better approach is to add maintained proof around the stable claim, such as a current example or corrected integration detail, while leaving the core sentence intact. Refresh work should answer a real evidence need. Without that need, the agency may turn a useful source into a softer, less citable page.

How would you explain freshness coordination across French, English and third-party sources to a client?

I would explain that Perplexity reads the public evidence trail, not the client’s internal publishing plan. If the English documentation is updated, the French page and important outside sources may still carry older claims. The answer can then combine fresh and stale evidence in one summary. Coordination means checking whether the same entity, category and capability remain aligned across language versions and third-party confirmations. The client does not need identical wording everywhere. It needs public sources that support the same current business claim without leaving old phrases for Perplexity to reuse.