Church Communications6 min read•

Church Website Launch Announcement: Templates and Checklist

Announce your new church website with sample email, Sunday announcement, and social copy, plus a launch checklist and a simple feedback process.

Key takeaways

  • +Announce useful visitor tasks rather than a list of website features.
  • +Share the public website only after checking its essential links and information.
  • +Give members one clear destination and a practical way to report mistakes.

Free AI makeover

Build a free first draft of your church homepage.

Paste your church's web address, create a free account, and confirm your details. Review your homepage draft, then request the remaining pages free. Pay only when you publish.

Free makeover · Saved securely · No credit card required · No website yet? Start fresh

By Nils Smith · · Editorial responsibility: ChurchPress Editorial

01

How do you announce a new church website?

Announce a new church website by explaining what people can do there, sharing its public address, and inviting one specific action. Coordinate the announcement across Sunday notices, email, and the church's official social channels. Before sharing, confirm that the site is live and that directions, gathering times, contact forms, and other essential destinations work.

Members rarely need to know which technology powers the redesign. They need to know where to find the next event, send a friend the visit page, or listen to a message. Choose two or three tasks that the actual website supports and build the invitation around those. If a feature is still being prepared, leave it out of the launch announcement.

02

Use this church website launch email template

Subject: “Our new church website is ready.” Opening: “You can now visit [public website address] to [verified task], [verified task], and [verified task]. We have updated the site to help our church and our neighbors find [specific information] more easily.” Replace every placeholder with a detail you have checked on the public site.

Next step: “This week, take a look at [specific page] and consider sharing it with someone who has asked about [relevant gathering or ministry]. If you spot an incorrect detail or a link that does not work, please let us know through [monitored contact route]. Thank you to [approved team acknowledgment, if appropriate].” Link to the page with a descriptive label rather than repeating “click here.”

Keep the main email focused. A longer explanation of the redesign process can live elsewhere if the congregation needs it. Do not imply that members must create an account to read public information unless a particular task actually requires one. If the old website address still works through a redirect, explain any change only when it helps readers avoid confusion.

03

Adapt the message for Sunday and social channels

Sunday announcement: “Our new website is live at [short, readable address]. You can find [two confirmed tasks] there. If you are inviting someone to church, the [visit page name] has [verified details]. Please take a look this week and send any corrections to [contact route].” Read it aloud before using it; a web address that looks tidy on a slide may be awkward to say.

Social caption: “Looking for [current church information]? Our updated website brings [two useful tasks] together at [public address]. Start with [specific page or action].” Use a genuine screenshot if you want to show the site, but include the link as text where the channel supports it. Do not make the image the only place the address appears.

For slides and printed notices, pair any QR code with a readable address. Test the code from a normal viewing distance using the final artwork. Point it to a stable public page rather than an editor preview or temporary review link. The same invitation should work for someone who cannot scan the code.

04

Check the public site before scheduling the announcement

Review the actual production address in a browser where you are not signed in as an editor. A preview can work perfectly while the public domain still needs attention. Confirm the church name, gathering schedule, venue, entrance instructions, and contact details with their owners. Follow the main navigation and test every destination mentioned in the announcement.

Submit a harmless test inquiry and have the assigned recipient confirm it arrived. Check giving and registration destinations without making an unnecessary payment or booking. If the website address changed, test important old links and update the official profiles and printed materials your team controls. Do not announce completion while a necessary destination is still unavailable.

  • Open the production website while signed out of the editor
  • Verify every task and destination named in the launch announcement
  • Send a test inquiry and confirm that the responsible person receives it
  • Test the final QR code and readable website address
  • Assign a person to review launch feedback and correct confirmed errors

05

Turn launch feedback into useful corrections

Provide one monitored route for reporting problems. Ask people to include the page address, what they expected, and what happened. Avoid requesting personal account details or screenshots containing private information. A report such as “the Wednesday event link opens last year's registration” is easier to act on than a general request to make the website better.

Prioritize incorrect gathering details, broken forms, and misleading links before cosmetic preferences. Record the reported issue, the person responsible, and the result of checking the correction. When a report is a preference rather than an error, consider it alongside the site's visitor goals instead of redesigning immediately around the loudest response.

After the initial announcement, point to useful pages in ordinary church communications: the next event, a current ministry opportunity, or the visit information. A launch message introduces the site; accurate ongoing links make it part of the congregation's routine. Judge success by whether people can complete the advertised tasks, not simply by a launch-day spike in visits.

Put it into practice

Your action plan

  1. 1Announce useful visitor tasks rather than a list of website features.
  2. 2Share the public website only after checking its essential links and information.
  3. 3Give members one clear destination and a practical way to report mistakes.
  4. 4Open the production website while signed out of the editor.
  5. 5Verify every task and destination named in the launch announcement.

How to know it worked

The message has a named audience, owner, channel, next action, and review date—and the team can sustain the rhythm.

Frequently asked questions

Quick answers

Should we announce the website before it is live?

You can explain that a redesign is coming, but reserve the invitation to use it for when the public site and essential destinations have been verified.

Should every announcement link to the homepage?

Use the destination that matches the invitation. A general launch notice can point to the homepage, while an invitation to explore visiting should link directly to the visit page.

Do we need a launch event for a new church website?

Usually a coordinated email, Sunday notice, and official social post are enough to introduce it. Choose the approach that fits your congregation and the significance of the change.

Sources and further reading

1 · Use the resource

Run the free website audit

Open →

2 · Find the gaps

Run the free website audit

Score your site →

3 · Build your website

Let ChurchPress build your new church website—free.

Share your current website and ChurchPress will create a polished new version for your church. Build it, preview it, and refine it before you decide whether to publish.

Build My Church Website Free →

No credit card required