Nonprofit FAQ Pages: What to Include, What to Remove
Key takeaways
- Left ungoverned, a FAQ page becomes a dumping ground with no owner, no review process, and outdated answers that no one has authority to remove.
- A well-run FAQ page serves three legitimate purposes: reducing repetitive enquiries, serving specific stakeholder groups, and supporting question-based search.
- Where a FAQ page serves distinct audiences, it should be split into clear sections or separate pages rather than mixing donor, beneficiary, and journalist questions together.
- Google retired the FAQ rich result in May 2026, so FAQPage markup no longer changes how a page looks in Search, and no special structured data is needed to appear in AI features.
- A FAQ page is not a substitute for a clear programme page, a formal policy, or aspirational messaging; those belong in their own properly maintained locations.
- A content audit should remove outdated answers, questions no one actually asks, questions better answered elsewhere, and duplicate variations of the same question.
Summary
FAQ pages on nonprofit websites are one of the most governance-significant content types and one of the most poorly managed. In their worst form, they are content dumping grounds: every question anyone has ever asked is added to the list, nobody is named as responsible for keeping the answers current, there is no review process for removing questions that are no longer relevant, and the page grows without structure or purpose until it is too long to be useful and too entrenched to be deleted without political difficulty. In their best form, FAQ pages are a governance asset: a structured, maintained resource that answers the questions institutional stakeholders actually need answered, from funders asking about governance to donors asking about track record and beneficiaries asking about eligibility. This post covers what a well-governed FAQ page looks like for a nonprofit website: how to determine which questions genuinely belong on a FAQ page versus which should be answered on programme or service pages, how to name a content owner and establish a review cycle so questions do not become outdated, how to structure the page so different stakeholder groups can navigate to the questions relevant to them, what FAQPage schema markup does and no longer does now that Google has retired the FAQ rich result, and how to audit an existing FAQ page against governance criteria and decide what to keep, update, and remove.
The FAQ page is where content goes to die
Most nonprofit FAQ pages were created to solve the same problem: there was content that did not fit anywhere else. A question came up frequently enough to warrant an answer, but not frequently enough to justify its own page. A donor asked something the team could not find on the site. A funder raised a concern about the lack of information on a particular topic. The FAQ page absorbed all of it.
Over time, this creates a page that serves no single audience clearly. It answers questions that donors have, questions that beneficiaries have, questions that journalists have, and questions that the team wishes people would stop asking. It is organised by the order in which questions occurred to the person who wrote it, not by the information needs of any specific stakeholder group. And it grows without a removal process, which means it includes answers to questions that are no longer relevant, about programmes that have ended, about processes that have changed, and about policies that have been superseded.
A badly structured FAQ page does not just fail to help visitors. It signals that the organisation could not decide where information belongs. That signal is read differently by different audiences, but it is never read positively.
What a FAQ page is actually for
A FAQ page serves three legitimate purposes, and each requires a different approach to content selection and organisation.
Reducing administrative burden
The most defensible purpose of a FAQ page is to answer questions that otherwise reach the team by phone or email. If the same questions arrive in the inbox every week, those questions belong on the FAQ page, answered clearly and completely. This is a straightforward information architecture decision: identify the high-frequency questions, answer them well, and direct people to the page before they reach the inbox.
The questions that belong here are specific: how to apply for a programme, what documents are required, how long the process takes, what the eligibility criteria are, how to access services in a different location. These are the questions where the answer is stable, the audience is identifiable, and the failure to answer them creates a predictable administrative cost.
Serving specific stakeholder groups
Different audiences have different questions, and a FAQ page that mixes them creates a navigation problem for all of them. A donor trying to understand Gift Aid does not want to scroll past questions about programme eligibility. A beneficiary trying to understand how to access a service does not want to parse answers written for grant-makers.
Where a FAQ page serves multiple distinct stakeholder groups, it should be structured accordingly, either through clear sections with headings, or through separate FAQ pages for each audience. This is a straightforward multi-stakeholder navigation problem: the same principle that governs the rest of the site architecture applies here. The multi-stakeholder navigation post covers this framework in more detail.
Supporting SEO through question-based search
FAQ content is usually defended on search grounds, and that defence needs updating. For several years, FAQ schema markup could expand a listing in Google by showing question and answer pairs directly beneath it. It cannot any more. Google added a deprecation notice on 8 May 2026, stopped showing the FAQ rich result from 7 May 2026, and removed the documentation for the feature on 15 June 2026. FAQPage markup now earns a nonprofit nothing in Google Search.
Nor is markup the way into AI answers. Google's guidance on AI features states that “There's also no special schema.org structured data that you need to add”, and that to be shown as a supporting link in AI Overviews or AI Mode a page must be indexed and eligible to be shown with a snippet. Structured data still does real work elsewhere on a charity site: Organization markup helps Google tell your organisation apart from others with a similar name. The schema markup for nonprofits resource covers the technical implementation, and AEO for nonprofits covers answer-engine visibility.
What survives is the simpler point, and it never depended on markup. Question-based content aligns with how people actually search: “how do I apply for [programme]”, “what does [organisation] do”, “is [organisation] a registered charity”. FAQ content answers those questions directly, in the words they were asked in. The standard that makes it work is editorial, not technical: questions in a consistent format, and answers that fully address the question without requiring the reader to navigate elsewhere.
What a FAQ page is not for
A FAQ page is not a substitute for a well-organised programme page. If visitors are asking basic questions about what a programme does or who it serves, the problem is not that the FAQ page lacks an answer. The problem is that the programme page does not communicate clearly enough. Adding those questions to the FAQ page papers over a structural failure in the information architecture.
A FAQ page is not a content governance policy. Many organisations use FAQ pages to explain things that should be explained in formal policies: safeguarding procedures, complaints processes, data protection rights. These deserve their own pages with appropriate review cycles and named ownership. When they live only in the FAQ, they are harder to find, harder to maintain, and less legible to funders and regulators who expect to find them in predictable locations.
A FAQ page is not a place for aspirational content. Answers to FAQ questions should be factual and specific. “What is your approach to safeguarding?” should answer the question, not direct the reader to a statement of values about how seriously the organisation takes its responsibilities.
What to remove
Most nonprofit FAQ pages contain content that should be removed or relocated. A content audit of the FAQ page should identify several categories of removable content.
Outdated answers: questions that reference programmes that have ended, processes that have changed, contact details that are no longer current, or statistics that have been superseded. These are the most damaging items on the page because they actively mislead visitors and, when discovered by funders or journalists, signal that the organisation does not actively maintain its digital presence.
Questions no one asks: FAQ pages frequently contain questions that were added by someone in the team who thought a particular piece of information was important, rather than questions that visitors actually ask. If there is no evidence that a question is regularly posed, it does not belong on the FAQ page. It may belong on a programme page, a policy page, or nowhere at all.
Questions better answered elsewhere: if the answer to a FAQ question would be better served by a dedicated section on a programme page, a link to a policy document, or a resource guide, the question should be removed from the FAQ and the content it points to should be improved. The FAQ page should not compensate for deficiencies elsewhere in the site architecture.
Overlapping questions: a FAQ page that contains several variations on the same underlying question, because different team members added their own version at different times, should be consolidated. One well-answered question is more useful than several partially answered ones.
The governance process behind a good FAQ page
A FAQ page without a governance process deteriorates regardless of how well it was designed at launch. It needs three things to remain useful: a named owner, a review cycle, and a removal criterion.
The named owner is responsible for reviewing the page at least annually, assessing whether all answers are current and accurate, and identifying content that should be added, updated, or removed. In many organisations this is the Communications Director, but the responsibility for providing accurate information belongs to the programme or operational team whose area the question covers.
The review cycle should be tied to the annual content audit and, where possible, to programme or policy changes that affect the answers. A FAQ page reviewed only when someone notices it is wrong will always contain outdated content. A FAQ page reviewed on a fixed schedule, as part of the content governance framework, will stay accurate.
The removal criterion is the most often absent. Most FAQ pages have no defined point at which content is removed. The result is accumulation over time, with the page growing as questions are added and never shrinking as they become irrelevant. The criterion should be simple: if an answer has not been updated in two years, or if the underlying programme or policy it describes has changed, the answer is reviewed and either updated or removed.
For more on the broader content governance framework, the nonprofit website content governance post covers the ownership and review processes that apply across all content types on the site.
FAQ
If your FAQ page has not been reviewed recently, or if your site lacks clear audience-specific navigation, the Blueprint Audit identifies these structural problems as part of the information architecture assessment. Learn more about the Blueprint Audit.
Free download
Your website, for the board.
A two-page briefing you can fill in and put in the next board pack. It covers the six things funders check, how to see what AI tools say about you, and the options to put to trustees.
That did not send. Email hello@socialectric.com and I will send you the briefing.
Frequently asked questions
- Should a nonprofit have a single FAQ page or multiple FAQ pages?
It depends on how many distinct stakeholder groups the site serves and how different their questions are. A small organisation serving a single audience with a limited set of programmes may be well served by a single, well-organised FAQ page with clear sections. A larger organisation serving multiple distinct audiences, donors, beneficiaries, referral partners, and funders, with significantly different questions, is better served by audience-specific FAQ sections, either on the same page with clear navigation or on separate pages linked from the relevant audience entry points. The governing principle is whether a visitor can find the answer to their specific question without being required to read through content written for a different audience.
- How does FAQ schema markup help with search visibility?
In Google, it no longer does. FAQ schema markup tells search engines that specific content on a page is structured as a question and answer pair, and for several years Google used those pairs to expand a listing in search results. That feature has been withdrawn: Google added a deprecation notice on 8 May 2026, stopped showing the FAQ rich result from 7 May 2026, and removed the documentation for it on 15 June 2026. It is not a route into AI answers either. Google's guidance on AI features states that "There's also no special schema.org structured data that you need to add", and that to appear as a supporting link a page must be indexed and eligible to be shown with a snippet. Structured data still does real work elsewhere: Organization markup helps Google tell your charity apart from other organisations. The schema markup resource covers the technical implementation, and AEO for nonprofits covers answer-engine visibility.
- What is the biggest mistake nonprofits make with FAQ pages?
The most common and consequential mistake is using the FAQ page as a catch-all for content that does not fit elsewhere on the site, rather than as a structured response to identifiable stakeholder questions. This produces a page that is long, poorly organised, and difficult to navigate. The second most common mistake is failing to maintain the page after launch, so that it accumulates outdated answers, redundant questions, and references to programmes or processes that no longer exist. Both problems have the same root cause: no named owner, no review cycle, and no removal criterion.
- How often should a nonprofit FAQ page be reviewed?
At least annually, by a named owner, and additionally whenever a programme or policy changes in a way that affects an answer. Tying the review to the annual content audit is what keeps it from happening only when somebody notices an answer is wrong. The review needs a removal criterion as well as an accuracy check: if an answer has not been updated in two years, or the programme or policy it describes has changed, it is reviewed and either updated or removed. The content governance framework sets out how ownership and review cycles work across the rest of the site.
- Can safeguarding or complaints information live on the FAQ page instead of on its own page?
It should not. Safeguarding procedures, complaints processes and data protection rights are formal policies, and they deserve their own pages with appropriate review cycles and named ownership. When they exist only as a FAQ entry they are harder to find, harder to maintain, and less legible to funders and regulators, who expect to find them in predictable locations. A FAQ entry can point at the policy page; it should not be the only place the policy exists.