For a charity, being visible in Google is only worth anything if it helps somebody find an answer, a person to speak to, or a way to take part. The goals behind those searches differ enormously: joining a local group, booking a place at an event, volunteering, becoming a member, or giving money. SEO for charities starts with making those routes clear, not with chasing a position.
Small teams rarely have a spare week for search work, which is an argument for sequencing it properly rather than ignoring it. What follows assumes volunteers, an inherited site and a content queue longer than the time available. Very little of it depends on publishing more: most of what a charity site gains comes from repairing what is already there — an out-of-date contact, an event page with no date, a form that fails on a phone.
Decide what "ranking well" means for your organisation
A search on an acronym on its own does not summarise an organisation's visibility. Several bodies can share the same initials, and people who do not yet know you search for an activity or for help rather than for a name.
Write a list of needs first: finding a local contact, understanding the conditions of membership, preparing to attend something, or seeing how donations are used. Attach each need to one page and one possible action. A general "about us" page cannot answer all of those with any precision.
Then look in Search Console at the searches that genuinely show your site. Separate name queries from queries about what you do, and note which pages were reached and over which periods — interest in an event rises as its date approaches. Average position alone does not tell you whether visitors reached the right contact. It helps to decide the scope of a review before anyone starts digging.
Make the organisation's identity explicit
Put the full name, the acronym, the mission and the area you cover on the pages that matter. A heading such as "Contact us" should also make clear who answers and on which subjects. Where an acronym is shared, that is far more useful than repeating the letters.
The about page can bring together responsibilities, how the organisation is run, public documents and links to the actual work. If you are a registered charity, the registered name and number belong on the pages people check before they give money. Someone has to own that page, and a visitor needs to be able to tell a past news item from a scheme that is still running.
Google's guidance on title links points towards descriptive, distinct headings. An event page can name the event and the year; a local resource can state the area it genuinely covers. Google may still compose a different result title from the page content, so the page itself has to carry the meaning.
Organise content around the people you help
Build a short navigation from your main areas of work: understanding the organisation, finding help or a resource, taking part, reading news, and getting in touch. The labels have to make sense to somebody who knows nothing about your internal structure — committee names and department titles rarely survive that test.
| What the visitor needs | Content to provide | Next step |
|---|---|---|
| To reach the right person | Role, remit and verified contact details | Contact the right person first time |
| To attend a meeting or event | Date, venue, access, conditions and availability | Book a place or ask a question |
| To understand a process | A dated explanation with useful references | Approach the competent body |
| To support the organisation | Mission, ways to give and relevant documents | Join, donate or offer help |
A news item can point to a durable resource, and that resource to the people concerned. Avoid leaving essential information only inside a PDF that is painful to read on a phone, or in an old social media post. A clear HTML page carries the essentials, with the full document alongside it.
Publish reliable information, and frame personal accounts carefully
Charities hold valuable ground-level knowledge. A write-up of a piece of work, or an answer to a question you are asked every week, offers something a general institutional page never will. Define the subject with the people who actually know it, and check contact details and procedures before publishing.
For a patient or service-user organisation, separate lived experience from medical or legal information clearly. A personal account must not drift into a general recommendation about treatment. Content of that kind should point to competent sources and be reviewed in proportion to what is at stake, and anything about a process should say which scheme it applies to and when it was checked.
Agree the conditions for publishing accounts, photographs and personal information with the people concerned, in advance. You can share a useful experience without exposing an individual case, and review has to cover what the text reveals as much as how it reads.
Set a publishing rhythm your volunteers and reviewers can sustain. Google does not prescribe a word count in its guidance on helpful content. A long guide is justified only when the subject demands it; for an event page, an exact date, an address and clear conditions are the priority.
Check the technical basics before commissioning a rebuild
Test the pages that carry membership, donations and enquiries on a phone and a desktop. Check the menus, the forms, the download links and whether the page can be used from a keyboard. Run the full permitted journey, including confirmation messages, without creating an unnecessary payment.
Treat a performance test result as the start of a diagnosis, not a verdict: it depends on the page, the simulated network and the state of the site that day. The Core Web Vitals currently cover loading of the main content, responsiveness and visual stability, through LCP, INP and CLS. A single score does not replace watching somebody use the journey.
The realistic actions are images sized for how they are displayed, fewer unnecessary scripts, and a cache configuration that does not interfere with forms. Back up before a change and test after it: a speed improvement that breaks sign-up has cost more than it gained.
Keep private areas private and indexing deliberate
Keep three needs apart: protecting a members-only area, keeping a public page out of search results, and organising crawling. Authentication protects private content. A noindex directive can remove an accessible page from results once the engine has processed it — so the engine has to be allowed to fetch the page and read the directive:
<meta name="robots" content="noindex">A block in robots.txt does not guarantee exclusion from results, and Google explains that distinction in its introduction to robots.txt. Do not apply a directory-wide block without looking at what sits inside: it can stop the engine reading an indexing directive, or hide a resource people need. Where pages you want found are missing, trace the cause before rewriting anything — indexing problems usually have a specific, findable reason.
Build the relationships that help people find you
Ask the partners you genuinely work with to check that their pages point to the right resource or contact. A directory entry, a local authority page or a write-up of joint work is useful when the link reflects a real relationship and answers a reader's need.
Choose the destination with care. For an event, the dedicated page is almost always more informative than the home page, and once it has passed the closure needs marking clearly so existing links do not become invitations to something that already happened.
Pages about places need to correspond to a real presence or real help. Repeating the same text across a list of town names does not replace a named contact or verified local arrangements, and local visibility follows the substance, not the page count.
Setting priorities with a team that is already stretched
Start with the faults that stop people acting at all: an out-of-date contact, a form nobody can submit, an event with no date, an essential page that cannot be reached. Then complete the content people ask for most often, and the links between those pages. Once that base is stable, plan the next subjects with a named owner and a review date.
To judge the effect, set the visibility you observe alongside sign-ups, relevant enquiries and what the team reports. Note the campaigns and events that changed the context, because they explain most of the peaks. A tracking sheet should help you choose the next improvement — not turn an audience target into a promise.
Common questions
Should we target our acronym or our full name?
Use the full name and the acronym consistently, then look at the searches you actually receive. People may also look for your activities without knowing your name at all. A clash with another organisation on the same initials is not proof that everything else is failing.
Do we need to publish more to make progress?
Start by checking that the essential pages are accurate, reachable and useful. A higher publishing rate does not help if the team cannot review or maintain what goes out. Choose the next subjects from what your audiences ask for, not from a quota.
Can we block member profiles with robots.txt?
No. Robots.txt organises crawling; it does not protect private data, so a members-only area needs proper access control. For a public page you want kept out of results, use the indexing directives instead and make sure the engine can fetch the page to read them.
What should we do with the page for an event that has finished?
State the date and say clearly that it is over. Keep the write-up and any resources that still have value, then link on to the next meetings. Avoid quietly reusing the old page for a new event under an ambiguous heading: the links pointing at it were about something else.
Our site was built by a volunteer years ago. Do we need a rebuild?
Not necessarily, and it is an expensive first answer. Test the journeys that matter — donations, membership, enquiries — on a phone and a desktop. If those work and the pages are reachable, targeted fixes usually go further than a rebuild the team then has to learn.
Which results should we follow apart from visits?
Sign-ups, enquiries that reach the right person, memberships, or whatever matches your objectives. Add what the team reports: a form can receive fewer messages while the requests arriving are better directed, which is an improvement rather than a decline.