Most nonprofit founders start in the wrong place. They open Canva, design a logo, buy a domain that felt clever at midnight, and three months later they are stuck: the donation button does not work, and the developer who built the site has disappeared with the passwords.
The website is not step one. It is step seven. And when you do the first six steps properly, the website almost builds itself. This is the full sequence we walk our nonprofit clients through, from naming the organization to publishing your first annual newsletter.
Get the full guide
Unlock all 15 steps, discounts, tools, and checklists.
Phase 1: Foundation — get legitimate before you get pretty
Step 1: Choose a name that carries the mission
Your name is doing three jobs at once: telling people what you do, being findable, and lasting a decade without boxing you in. Run three tests before you commit. The mission test: does it hint at the outcome, not just the activity? The growth test: will it still fit if you expand beyond your first city? And the say-it-out-loud test: if you have to spell it on a phone call, it is costing you.
Then check all four of these before falling in love with it:
- Domain availability — search Namecheap, GoDaddy, or Cloudflare. Nonprofits conventionally use .org, and donors trust it.
- Social handles — Instagram, Facebook, LinkedIn, X. Consistency beats perfection.
- State business name search — your Secretary of State's database.
- Trademark search — a free USPTO search can save you an expensive rebrand.
Buy the .org and the .com if you can. It is about $30 a year and stops someone else trading on your name.
Step 2: Register in the jurisdictions you actually serve
Incorporate first: file Articles of Incorporation with your home state, appoint a registered agent, adopt bylaws, and seat a board. Most states require at least three unrelated directors.
Then apply for federal tax exemption using IRS Form 1023 (or the shorter Form 1023-EZ if you are under the size thresholds). Approval gives you 501(c)(3) status, which makes gifts deductible and unlocks nearly every nonprofit discount in this guide.
Then register where you fundraise. This is the step founders miss most. Roughly 40 states require charitable solicitation registration before you ask their residents for money — and a Donate button on a public website legally counts as asking.
Step 3: Get your EIN
Your EIN is free, takes ten minutes, and is issued instantly on IRS.gov. Never pay a third party for it. You will need it for your bank account, payment processor, Google for Nonprofits, and every discount program. Open a dedicated bank account the same week — commingling personal and organizational money is the fastest way to jeopardize your status.
Step 4: Create the organization's email, and own every account with it
Do not build your nonprofit on your personal Gmail. When a founder leaves or a phone is lost, you lose everything. Instead:
- Create a neutral admin account like admin@yourorg.org that belongs to the organization, not a person.
- Use that account only to create your registrar login, hosting, social profiles, payment processor, analytics, and GitHub.
- Apply for Google Workspace for Nonprofits — free for eligible 501(c)(3)s.
- Turn on two-factor authentication everywhere and use a shared password manager.
- Keep a credentials document listing every account, its owner, and where recovery codes live.
This single step prevents the most common nonprofit tech disaster: nobody can access the website.
Phase 2: Own your digital real estate
Step 5: Domain, hosting, and SSL
Register the domain under the organization's admin email — never a contractor's account — and enable auto-renew, domain lock, and WHOIS privacy. Then pick hosting based on who will maintain the site, not on what is trendy.
| Option | Best for | Rough cost |
|---|---|---|
| Webflow / Framer | Modern sites a non-technical staffer can update | $15–40/mo |
| Squarespace / Wix | Smallest teams wanting everything in one box | $16–30/mo |
| WordPress (managed) | Content-heavy orgs with a maintainer | $10–35/mo |
| Netlify / Vercel | Custom-built sites from a developer | Free–$20/mo |
SSL is non-negotiable — your site must load as https. It is free through Let's Encrypt or Cloudflare. While you are in DNS, add SPF, DKIM, and DMARC records. These prove your email is really from you and are the difference between your newsletter reaching inboxes or quietly landing in spam.
Step 6: Build the brand before you build the pages
You do not need a six-figure identity. You need consistency. The minimum viable brand kit:
- Logo in three forms: primary, horizontal, and a square icon/favicon
- Colour palette — one primary, one accent, two neutrals, with hex codes
- Typography — one heading font, one body font (Google Fonts are free and fast)
- Photography style — real people and real work beat stock photos every time
- Voice — three adjectives for how you sound, plus words you never use
Put it in a two-page brand guideline PDF. That document is what keeps your website, Instagram, and annual report looking like the same organization — which is what builds donor trust. Canva offers free Pro accounts to eligible nonprofits.
Phase 3: Build the site
Step 7: Plan before anyone designs
Write the content first and design around it. Doing it backwards is why so many nonprofit sites are beautiful and empty. The pages almost every nonprofit needs: Home, About/Mission, Programs, Impact, Donate, Get Involved, News/Blog, and Contact.
Apply the five-second test: show your homepage to a stranger, cover everything below the first screen, and ask who you help, what you do, and what to do next. If they hesitate, fix that before anything else.
Step 8: Build it yourself or hire a developer
Build it yourself if your budget is small and someone on the team enjoys this — modern platforms are genuinely good now. Hire when you need custom donation flows, integrations, or you simply do not have the hours.
If you hire, put these five non-negotiables in the agreement:
- You own the accounts. Domain, hosting, analytics, and repository are registered under your admin email. The developer is a collaborator, not the keyholder.
- You own the code, with a written IP assignment.
- You get a handover document covering updates, structure, and deploys.
- Training is included — at least one recorded walkthrough.
- A defined maintenance arrangement after launch.
The most expensive mistake in nonprofit web projects is a site nobody but the departed developer can touch.
Step 9: Use GitHub, and push every update
If any custom code is involved, version control is your insurance policy.
- Create a GitHub organization account under your admin email and add your developer as a collaborator.
- Keep a main branch that is always deployable, with feature branches merged through pull requests.
- Commit early and often with clear messages — "Fixed donate button on mobile" beats "updates".
- Connect the repo to your host so every push deploys automatically, with preview links before anything goes live.
- Keep secrets and API keys in environment variables, never in the code.
- Write a README explaining how to run and deploy the site.
Even if you never read a line of code, this means your work is backed up, every change is reversible, and any future developer can start on day one.
Phase 4: Take money properly
Step 10: Payment gateways and the donation page
Stripe is the standard, with discounted processing for eligible 501(c)(3)s. PayPal suits donors who prefer it. Givebutter adds campaigns, events, and peer-to-peer fundraising. Donorbox does simple embedded recurring forms. Zeffy positions itself as genuinely free by asking donors to cover fees. Most organizations end up with Stripe plus one fundraising layer.
What separates a donation page that converts from one that does not:
- Default to monthly — recurring donors are worth several times a one-time gift.
- Suggest amounts with context — "$50 provides a week of meals" beats an empty box.
- Ask for as little as possible — every extra field costs you donations.
- Test it on a phone — most donors will be on one.
- Offer fee coverage — a surprising share of donors tick that box.
- Send an immediate receipt with your EIN and the required acknowledgment language.
- Run a real $1 test transaction, then refund it.
Never store card numbers yourself — let the processor handle it. That is what keeps you PCI compliant.
Phase 5: Get found
Step 11: SEO fundamentals
You do not need tricks. You need clarity and structure.
- One clear topic per page, with a descriptive title tag and meta description.
- Proper heading structure — one H1, then H2s and H3s in order.
- Alt text on every image, good for blind visitors and for Google.
- Fast and mobile-first — compress images and aim to load in under three seconds.
- Add Organization schema markup so search engines understand who you are.
- Submit an XML sitemap to Google Search Console.
- Write the pages people actually search for. "After-school programs in [city]" gets found; "Our Initiatives" does not.
A quiet advantage: content written clearly and structured well is also what AI assistants surface when someone asks for organizations doing your kind of work.
Step 12: Claim your Google presence, including $10,000/month in free ads
Claim and verify your Google Business Profile — it often appears before your website. Install Google Search Console to see what people search to find you, and GA4 with your donation completion set as a conversion.
Then apply for Google Ad Grants: eligible 501(c)(3)s receive $10,000 per month in free Google Search advertising, up to $120,000 a year. The catch worth knowing is that Google requires a high-quality website with substantive content to qualify and stay compliant. That requirement is the best argument for doing the website properly — a good site is not just a brochure, it is what unlocks six figures of free advertising.
Step 13: Build trust signals off your own site
Donors research before they give. Claim your Candid/GuideStar profile and earn the transparency seal, check your Charity Navigator listing, and publish your Form 990 and annual report directly on your Impact page. Radical transparency converts.
Phase 6: Keep it alive
Step 14: Build a content rhythm you can sustain
A site that has not changed in two years tells donors the organization may not exist anymore. Monthly is plenty:
- Activity updates — short posts on what happened this month, with photos
- Impact stories — one person, one change, told properly and with consent
- Insightful blog posts — answer the questions your community actually asks; this is what earns search traffic
- Donor and volunteer spotlights — recognition drives retention
- An annual newsletter or impact report — your most important fundraising asset of the year, published as a web page and a PDF
Build the email list from day one and put a signup on every page. Your list is the one audience no algorithm can take from you.
Step 15: Maintain, secure, and keep it accessible
Monthly: test the donation flow with a live transaction, review Analytics and Search Console, publish your content, confirm backups ran.
Quarterly: update the platform and dependencies, check page speed, fix broken links, review your Google Business Profile.
Annually: renew the domain, refresh photos and impact numbers, re-file state charitable registrations, and review the site against an accessibility standard.
Aim for WCAG 2.1 AA: sufficient colour contrast, keyboard navigation, alt text, captions, and clear labels. For a nonprofit this is both a legal exposure issue and a mission issue — an inaccessible site excludes the very people many organizations exist to serve. Publish a privacy policy and a cookie notice too.
Your launch checklist
- Domain registered to the organization, auto-renew on
- SSL active; site loads on https
- SPF, DKIM, and DMARC configured
- Tested on a real phone
- Donation page tested with a real transaction, receipt confirmed
- EIN and 501(c)(3) status visible on the site
- Google Analytics, Search Console, and sitemap in place
- Google Business Profile claimed and verified
- Privacy policy and terms published
- Accessibility pass completed
- Backups running automatically
- All credentials in the organization's password manager
A realistic first-year budget
| Item | Typical annual cost |
|---|---|
| Domain (.org + .com) | $30 |
| Hosting / site platform | $180–480 |
| SSL | Free |
| Email (Google Workspace) | Free for eligible nonprofits |
| Logo and brand kit | $0–1,500 |
| Website build (DIY → professional) | $0–15,000 |
| Payment processing | ~2.2–2.9% + $0.30 per gift |
| Ongoing maintenance | $600–3,000 |
Worth applying for: Google for Nonprofits (Workspace, Ad Grants, YouTube), TechSoup, Canva for Nonprofits, Microsoft for Nonprofits, and nonprofit rates from most processors.
Five mistakes that cost nonprofits the most
- Building the site on someone's personal account. When they leave, so does your website.
- Launching without testing the donation flow. Broken donate buttons are common and silent.
- Treating the site as a one-time project. Budget for upkeep from the start.
- Skipping charitable solicitation registration. A Donate button is legally an ask.
- Writing about yourself instead of your impact. Donors give to outcomes.
The bottom line
A nonprofit website is not a brochure. It is your fundraising infrastructure, your credibility, and the gate to $120,000 a year in free Google advertising. Built in the right order, it stops being a project you dread and becomes the thing that quietly grows your mission while you sleep.
Start with the name. End with the newsletter. Do not skip the boring middle — that is where the trust is built.
Want a technical partner for the build? We offer nonprofit pricing.
Book a Free Strategy Call