NGO Website Development in India: Making Campaign and Donation Links Look Trustworthy When Shared on WhatsApp, Facebook and X
When someone shares your donation link on WhatsApp, the preview card that appears, with an image, a title and a line of description, is often the only thing a potential donor sees before deciding to tap. That card is controlled by a few lines of code in the page's head, called Open Graph tags, and an NGO website that sets them properly makes every shared appeal look credible and specific, while one that does not shows a blank grey box, a random logo or the wrong text. This guide explains, in plain language, what those tags are, what a good share card for an NGO looks like, how to set them up and test them, and what to avoid, as part of sound NGO website development in India.
It is written for trustees, communications leads and volunteers who manage campaigns, and for developers who build NGO sites. We do not quote figures about how many donations come from shared links, since we cannot source a reliable number. The reasoning holds whatever your volume.
Why share previews matter so much for NGOs
Indian NGOs raise a large share of their support through personal networks: a trustee forwards an appeal to a family group, a volunteer posts on Facebook, a supporter shares a campaign on Instagram stories with a link. Each share is effectively a recommendation from someone the recipient knows, and the preview card is where that recommendation either looks real or looks like spam.
A good card does four things quickly:
- Shows what the cause is. A clear title and a relevant image tell the reader what they are being asked to support.
- Shows who is asking. Your organisation's name, visible in the card, reassures people who may not know the sender's context.
- Gives a reason to tap now. A specific line, such as the need and the target, beats a generic tagline.
- Looks safe. A recognisable domain and a clean preview reduce the suspicion that the link is a scam, which is a real concern for donors who have seen fraudulent fundraising links.
Without these tags, each platform guesses. It may take the first image on the page, which might be a tiny icon, a banner with text cut off, or nothing at all, and it may take a description from unrelated text. The result is a card that looks unfinished at exactly the moment you are asking for money.
What Open Graph tags are
Open Graph is a protocol, originally from Facebook, that lets a web page describe itself to other services as a rich object. It is documented at ogp.me. The protocol names four required properties: og:title (the title as it should appear), og:type (the kind of object, such as a website or article), og:image (an image URL representing the page) and og:url (the canonical address, used as the page's permanent ID). If a page includes an image, the protocol says it must also include og:image:alt, a description of the image's content, and it lists optional properties such as image width and height. Beyond the required four, a description is optional in the protocol, though platforms use it, and og:site_name is widely used for the organisation name.
Platforms read these tags when a link is shared and build the card from them. Facebook, Instagram's link handling, LinkedIn, Messenger and many other services use Open Graph. X uses its own card tags and falls back to Open Graph when its own are missing. WhatsApp, in our experience of building and testing sites, shows a link preview using the Open Graph title, description and image when it can read them; behaviour is controlled by WhatsApp, so always test rather than assume.
What a good NGO share card contains
Title
The title should name the campaign or the page, concisely. It is displayed truncated on many platforms, so put the important words first and keep it short. A page title written for search can differ from the share title; for search you may want the cause and location, while for sharing you want the human hook.
Examples of the pattern (not real campaigns): "Winter blankets for 500 families" is better than "Home". "Support a child's school year" is better than "Donate – Our Trust". If you state a target or number, it must be true and current. Do not invent urgency or a deadline.
Description
Keep to one or two short sentences. Say what the donation does and who runs it. Avoid promising specific outcomes you cannot guarantee, and do not state tax benefits unless your organisation's registrations and wording have been confirmed by your adviser; our guide to 80G compliant donation platforms explains why that wording needs care.
Image
The image does most of the work. Practical points:
- Use a landscape image, commonly around a 1.91:1 ratio such as 1200 by 630 pixels, which is the size widely recommended for large link cards. Confirm current recommendations in each platform's documentation, since they change.
- Keep the subject and any text in the middle. Platforms crop differently, and a tight crop on a phone can cut the edges off.
- Use a real, relevant photograph or a clean graphic with your logo, not a screenshot of the page or a dense poster with tiny text.
- Keep the file size sensible. A very large image can fail to load in the preview in time.
- Use an absolute URL on your own domain, with HTTPS. A relative path or a link to a protected file is likely to fail.
- Add alt text through
og:image:alt, as the protocol requires when an image is present.
People in images: a consent and safety point
NGO campaigns often feature beneficiaries, and a share card spreads an image far beyond your website. Only use photographs for which you hold documented consent for use in this kind of outreach, and take particular care with children. Our guide on publishing beneficiary stories and photos without breaking trust or the law goes into consent, children's images and takedown steps in detail. If in doubt, use an illustration, a photograph of the activity without identifiable faces, or your volunteers rather than the people you serve.
Site name and URL
Set og:site_name to your organisation's name and make sure og:url is the clean canonical address. If the shared URL carries tracking parameters, the card should still point to the same canonical page.
How the tags look in the code (for your developer)
For a campaign page, the head section would contain tags along these lines:
<meta property="og:type" content="website" />
<meta property="og:site_name" content="Example Trust" />
<meta property="og:title" content="Winter blankets for 500 families" />
<meta property="og:description" content="Help Example Trust reach families in Pune this winter." />
<meta property="og:url" content="https://example.org/campaigns/winter-blankets/" />
<meta property="og:image" content="https://example.org/images/winter-blankets-1200x630.jpg" />
<meta property="og:image:alt" content="Volunteers handing out blankets" />
<meta name="twitter:card" content="summary_large_image" />
The example is illustrative: the name, address and wording are placeholders, and you must replace them with your own, accurate content.
Each campaign page needs its own set of values. If every page shares the site-wide defaults, a link to your flood-relief appeal will show your general "About us" card, which wastes the opportunity.
Where NGO sites usually go wrong
One card for the whole site
A theme that sets a single default image and description gives every page the same preview. Fix it by making the title, description and image fields editable per page, with sensible fallbacks.
Pages that build their head with JavaScript
Link-preview crawlers generally read the HTML your server returns and do not run your scripts the way a browser does. If the tags are added by JavaScript after load, the card may be blank even though the page looks fine to a visitor. Make sure the tags are present in the initial HTML, through server-side rendering or prerendering. This is a common issue on sites built with single-page application frameworks; your developer can check by viewing the page source rather than the inspector.
Images that are blocked or too big
An image behind a login, on a domain that blocks bots, or served as a huge file may not load. Check that the image address opens in a private browser window.
Stale cards
Platforms cache previews. After you change an image or title, the old card may continue to appear for a while. Facebook offers a Sharing Debugger tool for refreshing and inspecting how it reads a page; other platforms have similar tools or simply refresh on their own schedule. Plan campaign pages in advance rather than editing them after you have shared them widely.
Wrong or missing canonical URL
If og:url points to a different address than the one people are sharing, shares can be split across versions. Keep the canonical consistent.
Generic text that looks like spam
"Donate now, urgent!!!" with a stock photo is what scam links look like. Be specific, plain and calm.
Making the destination as trustworthy as the card
A good preview earns the tap; the page must then keep the promise. Check these points:
- The page matches the card. The headline and image should be recognisable when the page opens.
- The page works on a phone and loads quickly. Many shared links are opened on mobile networks. Our article on low-bandwidth mobile donors covers this.
- Your registration details and contact information are visible, so a cautious donor can verify who you are.
- The donation path is short. See our guide to donation page design.
Also consider how the link looks in text. A short, readable address such as a /campaigns/winter-blankets/ path on your own domain looks safer than a long string of parameters or a third-party shortener that hides the destination. If you must track sources, use consistent tags, which we explain in measuring campaign attribution for fundraising.
Share buttons, QR codes and WhatsApp-first sharing
Not everyone copies and pastes. Make sharing easy on the page itself.
- A WhatsApp share button that opens WhatsApp with a prepared message and the link is the most useful for most Indian NGOs. Write the pre-filled message in plain language, in the language your supporters use, and include your name.
- A "copy link" button for people who prefer another app.
- A QR code for posters, event banners and printed reports, pointing to the exact campaign page, not the home page. Test it on several phones before printing, because a printed code cannot be corrected. Our guide on building event registration pages discusses QR codes at events.
- Peer-to-peer pages need card tags too. When a supporter creates a personal fundraising page, the card should show their name or story and your organisation, within the limits of their consent. See peer-to-peer fundraising pages for how those pages are structured.
Where WhatsApp is also used for donor communication, remember the consent rules for messages you send, as opposed to links people share on their own. Our WhatsApp opt-in compliance checklist covers that.
Testing before you share
Test every important campaign page before you announce it:
- View the page source and confirm the Open Graph tags are present in the HTML, not only added later by scripts.
- Paste the link into a WhatsApp chat with yourself or a test group, and look at the card on both an Android phone and an iPhone if you can.
- Use the Facebook Sharing Debugger to see how Meta reads the page and to refresh its cache.
- Check on LinkedIn and X if those channels matter to your audience.
- Open the image URL directly and confirm it loads.
- Test the link with tracking tags, to be sure the card still appears.
- Check the page on a slow connection.
Keep a short record for each campaign page: title, description, image file, date checked. It saves time when a campaign returns next year.
A worked example (hypothetical)
Imagine a made-up Pune NGO running a school-supplies drive. Its website is a single-page application, and when a trustee shares the campaign link in a family WhatsApp group, the card shows only the domain name and a grey square. Nobody taps.
The fix might be:
- Prerender the campaign page so the Open Graph tags appear in the HTML that crawlers fetch.
- Create a 1200 by 630 image showing volunteers with school bags (photographed with documented consent) and the organisation's logo kept clear of the edges.
- Set a title ("School supplies for 300 children this June"), where the number matches the campaign's real target, and a one-line description naming the NGO.
- Add a WhatsApp share button with a pre-filled message in Marathi and English.
- Test on two phones, then in the Facebook Sharing Debugger, then share.
- After the campaign, review GA4 to see how many sessions came from WhatsApp, using the tags from the GA4 donation funnel guide.
The figures here are illustrative only and describe no real campaign.
Security and honesty reminders
- Do not use a card to mislead. The title and image must match the page. Misleading cards can be reported and will damage trust.
- Do not include personal data in the card. Names of beneficiaries, phone numbers and similar details do not belong in a preview that anyone can see.
- Protect your accounts. Anyone who can edit your site's head or SEO plugin can alter every card. Use strong access control, as set out in our guide on donation site security.
- Keep the claim in line with reality. If the campaign has ended or hit its target, update the page and card rather than leaving an out-of-date appeal in circulation.
Questions to ask your developer or agency
- Can we set a different title, description and image for each campaign page?
- Are the tags in the server-delivered HTML, or added by JavaScript?
- What image size and format do you produce, and who creates it?
- Do cards still work when a link has tracking parameters?
- Who tests new campaign pages on WhatsApp before launch?
- How do we refresh a stale card after an edit?
Working with Govindani Infotech on NGO campaign pages
Govindani Infotech is a Pune-based website design and development company at 2nd Floor, Landmark Plaza, 206 Satara Road, Parvati Paytha, Pune 411009. We have engineered more than 500 non-profit websites, and campaign pages, donation flows and share previews are part of how we plan an NGO build. See our NGO website solutions, and if you run social channels, our social media service for NGOs.
If you are not sure what your campaign links look like when shared, send us one and we will describe, before any price is discussed, what we see and what we would change. You can message us on WhatsApp at wa.me/919201958278 or write through our contact page.
Frequently Asked Questions
Why does my donation link show no image on WhatsApp?
Common causes are missing Open Graph tags, tags added only by JavaScript, an image that is too large, blocked or behind a login, or a cached preview from before you fixed it. View the page source, check the image address, and test again, using a refresh tool where the platform provides one.
What image size should I use for link previews?
A landscape image of about 1200 by 630 pixels, roughly a 1.91 to 1 ratio, is widely recommended for large cards. Keep important content in the centre and check the platform's current guidance, as recommendations change.
Do Open Graph tags affect Google rankings?
They are not a ranking factor that we can point to in Google's documentation. They control how links look when shared on social and messaging platforms, which affects clicks and trust from those channels.
How do I update a preview after changing the image?
Change the tag, then use the platform's debugging or refresh tool where one exists, such as Facebook's Sharing Debugger. Some platforms cache for a while, so test with a fresh link and expect a delay.
Can I use photographs of beneficiaries in share cards?
Only with documented consent for this kind of use, and with extra care for children. A card travels far beyond your website, so consider illustrations or images that do not identify individuals.
Sources: The Open Graph protocol. Recommended image sizes, caching behaviour and WhatsApp preview handling are platform-controlled and change; confirm them on each platform's current documentation and test before each campaign.