Leadership changes leave two versions of the business online
A new CEO starts on Monday. The company website names her by lunchtime, but the old CEO still appears in team biographies, event profiles and search results. Articles written by the departing leader still show a current-company biography. Organization markup says one thing while the visible About page says another.
The organisation hasn't become a new business. What changed is the relationship between that continuing organisation and particular people. That distinction should control the update. Stable company facts stay stable, current roles change, and accurate history remains recognisable as history.
Without that control, a buyer can meet two plausible versions of the company and has to decide which one to trust. If the problem isn't yet clearly about leadership, start by diagnosing how search and AI systems understand your business. This guide begins once the business has approved the transition facts.
Website edits, structured data and correction requests give external systems better evidence. They don't guarantee rankings, citations, a Knowledge Panel change or a different AI answer. Google's explanation of how Knowledge Panels are generated and updated says they draw on information from across the web and may also use verified feedback. The timing and final display remain Google's decision.
Define exactly what changed
Begin with roles, not names. A founder describes who established the business. A CEO is a commercial leadership title. A director and a company secretary are statutory officeholders in Australia. A senior expert, employee and article author describe other relationships. One person can hold several of these roles, but the roles aren't interchangeable.
Record the announcement date and effective date separately. Then approve the continuing company facts, the outgoing person's relationship after the change and the incoming person's relationship from the effective date. Note any privacy, safety, contractual or legal constraint that changes what can be published.
This precision determines both the owner and the surface. A CEO appointment may require a leadership page, profile and press update. A director appointment may also require a statutory notification. ASIC's current guidance says Australian companies must keep officeholder details current and report changes within 28 days to avoid late fees. It identifies directors and secretaries as officeholders. It doesn't turn every founder, CEO, expert or employee change into the same obligation.
Give statutory decisions to an authorised corporate or legal owner. This article coordinates the public information work and isn't legal advice.
Build one governed change register
Scattered tickets hide contradictions. Use one dated register for the transition, even when communications, web, HR, legal and external partners complete different actions.
Give each row the fact being changed, the surface, the old state, the approved new state, an owner, the effective date, the required action, an evidence URL and a verification status. Group the rows by owned website content, structured data, controlled profiles, third-party references, statutory records and observed search or AI outputs.
That register is an Off Piste operating framework. It turns a collection of edits into an auditable handover and makes unresolved differences visible to the next owner. For a wider inventory of directories, profiles, reviews and outside references, use the third-party business signals audit.
The control works only if another person can tell what should be true and whether it was checked. Use the register before publication so ownership doesn't disappear on the effective date.
Choose what stays changes or retires
A clean handover doesn't mean deleting the outgoing leader from the company's history. Decide page by page whether the content describes a current relationship, a historical event or a person's original work.
Update current leadership pages, team biographies, About-page copy and contact routes on the effective date. A maintained announcement can explain the succession in dated language. Case studies and press releases that accurately describe who led the business at the time can usually remain unchanged.
Preserve a real author's byline on the work they created. Update a biography that wrongly says they're still employed, but don't assign their articles to somebody else for convenience. A former leader's profile may remain as a limited historical author page, use an alumni-style label where appropriate or be retired when it no longer helps readers. Privacy, safety, contractual and legal constraints can require a different treatment.
For each profile, consider whether people still need it to understand existing articles or company history. If the page stays, state the former relationship clearly and remove unsupported current-role claims. If it retires, choose the most useful relevant destination and update internal references rather than redirecting every former profile to the homepage.
Google lists an employee page on a company website as a valid use case in its ProfilePage structured-data guidance. The markup should describe the page that is actually visible. The guide to expert profile pages and Person schema covers the page model, identifiers and implementation details.
Sequence the work around the effective date
Before the effective date, agree the public facts, complete the change register and prepare approved page and profile revisions. Capture a dated baseline for representative company, leader and role queries. Save the visible pages, panels and sampled AI answers that may need comparison later. Assign an owner to every external or statutory action that can't be staged in advance.
On the effective date, publish the coordinated owned changes. Update the About page, current leadership profiles, relevant navigation and visible biographies together. Deploy matching structured-data changes, update profiles the business controls and submit required statutory changes through the authorised owner. Keep the announcement date and effective date accurate instead of making an imminent appointment look current too early.
After the effective date, check the live pages and rendered markup, confirm they remain crawlable and record what external systems show. Follow up with important partners and directories. Log discrepancies instead of repeatedly editing correct source pages in the hope of forcing a faster external change.
This sequence isn't an automated publishing recipe. A listed company, regulated practice or sensitive departure may need approvals and disclosure controls that change the order. The register should record those constraints without confusing them with search implementation.
Update the website and structured relationships together
Visible copy and markup should tell the same story. Review the company About page, leadership or expert profiles, navigation labels, contact information and any reusable biography fields. The About-page entity trust guide explains how to place the current company narrative and supporting proof.
Then inspect the rendered structured data. Preserve the established Organization identity when the company itself continues. Change Person roles, affiliations and profile descriptions only where the new relationship is visible and supportable. Check reused identifiers and sameAs references so an old biography or external profile doesn't silently reintroduce the former role.
Schema.org's Person vocabulary provides properties for describing relationships such as affiliation and works-for relationships. Vocabulary availability doesn't mean Google uses every property for a search feature. Google's Organization structured-data documentation defines the properties it supports and recommends using the most specific applicable organisation type.
Use the existing guide to maintain Organization schema and its identifiers rather than adding untested properties during a sensitive release. Google also states that valid structured data doesn't guarantee a search feature. The job is accurate, consistent implementation, not a promised display.
Correct external records and preserve history
Prioritise external pages that claim a current role or are likely to shape a buyer's decision. These may include professional profiles, company directories, partner biographies, association records, speaker pages, podcast notes and maintained social accounts.
Treat a stale current-role claim differently from a dated historical mention. Ask a conference organiser to correct a speaker page that still says the person is the current CEO. Don't ask a newspaper to rewrite an accurate report of who was CEO when an event happened. Where a page can support context, a dated note or updated biography is often clearer than removal.
Send each correction with the approved wording, effective date and a source that supports it. Record the request and the observed result separately. A sent email proves outreach, not correction.
Complete any officeholder work on its own legal track. ASIC's 28-day guidance applies to relevant company-detail and officeholder changes, not to the wider website checklist. If the commercial title and statutory role differ, maintain that distinction in the register and let the authorised owner determine the filing.
Verify what search and AI systems now show
Repeat the small query set saved before the change. Check the company name, each relevant leader, the role and company together, and likely questions such as who leads the business. Compare like with like where location, account state and platform can affect the result.
Record page discovery, snippets, panels and AI answers as dated observations. OpenAI's current publisher and developer guidance says allowing OAI-SearchBot makes content eligible for discovery in ChatGPT search, but it doesn't guarantee placement or ranking. That guidance is specific to OpenAI and shouldn't be presented as a rule for every AI system.
If a Google Knowledge Panel remains wrong, save the field and supporting evidence before following the dedicated route to correct inaccurate Knowledge Panel information. Don't treat another feedback submission as evidence that the visible result changed.
Move the transition into the entity trust monitoring framework once the planned updates are complete. It provides the baseline, cadence, severity and escalation model for facts that remain wrong, spread to other surfaces or return later.
A clean handover protects the business record
The transition is complete when the register shows what changed, who owned each action, which history was preserved and what buyers can now see. Unresolved external results should have evidence, an owner and a next verification date.
That record gives the business one defensible account and makes the next decision clear. Close the transition when the controlled sources are accurate and remaining observations are assigned to monitoring. Escalate when a material error persists, spreads or creates buyer, legal or reputational risk. Finish with a completed register and a dated verification decision.