What Your Nonprofit Website Should Say During a Crisis — Governance, Messaging, and Rapid Response

Nonprofit Website Crisis Communication
When a crisis hits — a funding cut, a safeguarding incident, a media investigation — the website becomes the organisation’s public record. What it says, what it does not say, and how quickly it changes all signal institutional competence to every stakeholder watching.
Most nonprofits do not have a plan for how the website should function during a crisis. The homepage still promotes a programme that has been defunded. The team page still lists a staff member who has been suspended. The annual report page links to accounts that are now under scrutiny. These are not communications oversights. They are governance failures that compound the crisis.
Why the Website Matters More During a Crisis
During normal operations, your website is one of many communications channels. During a crisis, it becomes the single authoritative source that every stakeholder consults. Journalists check it before calling your press office. Funders check it before deciding whether to continue their relationship. Board members check it before the emergency meeting. Beneficiaries check it for information about whether services are affected.
If the website contradicts what the organisation is saying in other channels, the website is what people believe. If the website says nothing while a crisis unfolds publicly, silence is interpreted as either incompetence or evasion. Neither interpretation serves the organisation.
The First 24 Hours
The website response in the first 24 hours of a crisis sets the tone for everything that follows.
Assess what the website currently says about the issue. Before publishing anything new, review every page that touches the crisis. If a programme has been defunded, check every page that references it. If a staff member is involved, check the team page, any authored content, and programme pages they are associated with. If a partner organisation is involved, check for logos, testimonials, and joint programme descriptions.
Remove or update content that is now inaccurate or harmful. This is not censorship. It is ensuring the website reflects the organisation’s current reality. A team page listing someone who has been suspended is not transparency — it is negligence. A programme page promoting an initiative that no longer exists is not historical record — it is misinformation.
Publish a clear, factual statement if the crisis is public. If the crisis is in the public domain — media coverage, social media, or stakeholder communications — the website should carry the organisation’s official position. This does not need to be lengthy. It needs to be clear, factual, and attributable to a named individual (usually the Chair or Executive Director).
The statement should cover: what the organisation is aware of, what action is being taken, who is leading the response, and how stakeholders can get further information. Avoid speculation, blame, or commitments the organisation cannot yet make.
What to Publish and Where
A crisis statement should be prominent but not permanent. Do not replace the homepage with a crisis message unless the crisis directly affects every visitor to the site. Instead, add a banner or notification that links to a dedicated statement page.
Crisis statement page. Create a standalone page (e.g. /statement or /update) with the official position. Date it. Update it as the situation evolves. Each update should be timestamped so stakeholders can see the progression of the response.
Homepage notification. A brief, factual banner linking to the statement page. This ensures every visitor is aware without replacing the site’s core content.
Governance section. If the crisis relates to governance, compliance, or regulatory matters, ensure the governance section of the site reflects current reality. If the Board has issued a formal response, it should be accessible from this section.
What to Remove or Update
Staff and leadership pages. If individuals are involved in the crisis, their profiles should be updated or removed in consultation with legal counsel and HR. Do not leave profiles of suspended or departed individuals visible during an active investigation.
Programme pages. If a programme has been defunded, suspended, or is under review, the page should be updated to reflect the current status. Do not delete the page entirely — it may still receive search traffic and should redirect or inform visitors of the current situation.
Partnership references. If a partner organisation is involved in the crisis, review all pages that reference the partnership. Logos, testimonials, and joint programme descriptions may need temporary removal pending resolution.
Impact data and claims. If the crisis involves questions about the organisation’s effectiveness, outcomes, or financial management, review all impact claims on the site. Anything that cannot be substantiated should be removed or caveated until it can be verified.
The Governance Framework for Crisis Response
Website crisis response should not depend on the Communications Director’s judgment alone. The governance framework should define:
Who can authorise website changes during a crisis. Normally, the Communications Director manages the site. During a crisis, changes to public-facing statements may require sign-off from the Chair, Executive Director, or legal counsel. Define this in advance.
How quickly changes must be made. The website should be updated within hours of a crisis becoming public, not days. If your CMS requires developer access for urgent changes, this is a governance risk that should be resolved before a crisis occurs.
What the escalation path is. If the Communications Director is unavailable, who can make website changes? If the Executive Director is the subject of the crisis, who authorises the response? These scenarios should be documented in your website governance policy.
After the Crisis
Once the immediate crisis has passed, the website needs a structured return to normal operations.
Archive the crisis statement page rather than deleting it. It is part of the institutional record and demonstrates the organisation’s response to future funders or regulators who may ask about it.
Review all content that was updated during the crisis. Were temporary changes made that need to be reversed? Were pages updated that now need more considered revisions?
Conduct a governance review of how the website response worked. Was the organisation able to update the site quickly enough? Were the right people able to authorise changes? Did the CMS structure support rapid response? Feed findings into the governance policy.
The Blueprint Audit includes an assessment of the site’s capacity for rapid content updates as part of the governance review. If your current platform or access structure would prevent timely crisis response, the audit identifies this as a specific risk.
For the governance policy framework that should include crisis provisions, see How to Create a Website Governance Policy. For the broader governance context, see Why Your NGO Website Is a Governance Problem.
Frequently Asked Questions
Q1: What should a nonprofit website say during a crisis?
A clear, factual statement covering: what the organisation is aware of, what action is being taken, who is leading the response, and how stakeholders can get further information. Avoid speculation, blame, or commitments that cannot yet be made. Date and timestamp all updates.
Q2: How quickly should a nonprofit update its website during a crisis?
Within hours of a crisis becoming public. If your CMS requires developer access for urgent changes, this is a governance risk. The Communications Director should be able to publish a statement and update key pages without waiting for external support.
Q3: Should we remove staff profiles during a crisis involving that person?
Consult legal counsel and HR before making changes. Generally, profiles of suspended individuals should be removed or updated. Profiles of departed individuals should be removed. Do not leave visible profiles that create a misleading impression of current leadership.
Q4: Where should a crisis statement appear on a nonprofit website?
On a dedicated statement page linked from a homepage banner or notification. Do not replace the homepage entirely unless the crisis affects every visitor. The statement page should be dated, timestamped with each update, and attributable to a named individual.
Q5: Should we delete content related to a crisis from our website?
Generally no. Update content to reflect current reality rather than deleting it. Deleted pages can still appear in search results and cached versions. If a programme has been suspended, update the page to reflect the status rather than removing it entirely.
Q6: Who should authorise website changes during a nonprofit crisis?
Define this in your governance policy before a crisis occurs. Typically, public-facing statements require sign-off from the Chair or Executive Director. If the ED is the subject of the crisis, the Chair or a designated trustee should authorise website changes.
Q7: How do we handle media enquiries about website content during a crisis?
Ensure the website and media responses are consistent. Journalists will compare what the website says with what the press office says. Any contradiction undermines credibility. The website statement should be approved by the same person authorising media responses.
Q8: Should we keep crisis statements on the website permanently?
Archive rather than delete. Remove the homepage banner once the immediate crisis has passed, but keep the statement page accessible. It is part of the institutional record and demonstrates transparency to future funders or regulators.
Q9: What if our website platform prevents rapid updates?
This is a governance risk that should be addressed before a crisis occurs. If routine updates require developer access, the organisation cannot respond to a public crisis within the necessary timeframe. The CMS should allow authorised staff to publish content independently.
Q10: How do we prepare our nonprofit website for a potential crisis?
Include crisis provisions in your website governance policy: who can authorise changes, how quickly updates must be made, what the escalation path is if the Communications Director is unavailable, and who makes decisions if the Executive Director is the subject of the crisis. Test that your team can publish urgent content independently.
Is this familiar?
Most nonprofit websites don't fail at launch. They fail quietly, over time.
The governance gaps, the stakeholder confusion, the Board that's stopped referring people to the site — these don't announce themselves. See what the difference looks like when it's built correctly from the start.
Eric Phung has 7 years of Webflow development experience, having built 100+ websites across industries including SaaS, e-commerce, professional services, and nonprofits. He specialises in nonprofit website migrations using the Lumos accessibility framework (v2.2.0+) with a focus on editorial independence and WCAG AA compliance. Current clients include WHO Foundation, Do Good Daniels Family Foundation, and Territorio de Zaguates. Based in Manchester, UK, Eric focuses exclusively on helping established nonprofits migrate from WordPress and Wix to maintainable Webflow infrastructure.

Ready to understand your current situation clearly?
The Blueprint Audit is where we start.
A two-to-three week diagnostic that maps your stakeholder needs, audits your current site, and gives you a clear strategic brief before any implementation commitment is made. £2,500. No obligations beyond the audit itself.
In case you missed it
Explore more

Nonprofit Website Crisis Communication

Nonprofit Website Analytics for Boards

Website Governance: Leadership Transitions
Join our newsletter
Subscribe to my newsletter to receive latest news & updates
