A church in Forest, Virginia

Make disciples.
Gather the families.
Lead the flock. This is about none of that, and all of it.

The mission has not changed, and we are not here to change it. We are here about the front door. Specifically, about the people standing outside it tonight who cannot find the handle.

Keep reading

Right now, somewhere nearby

Someone is looking for a church tonight.

A young family that just moved to the area. A man who has not been inside a church in twenty years and finally feels ready. A mother awake at the kitchen table who does not know where else to turn. None of them know your name yet. So they do what everyone does. They pick up the phone and search.

We ran the search from four nearby towns. For "baptist church near me," Living Word does not appear in Google's local map box at the top of the page. The church with half your reviews does.

Watch what that person sees. Then see what changes when the door is open.

Doing this poorly is worse than not doing it at all.

A website is not a brochure that sits quietly in a rack. It speaks for you, in your name, to a stranger who has never met you, at the exact moment they are deciding whether to walk in. So the only question that matters is what it says about you. There are three futures. Hear what each one tells that searching family.

It says

Your doors are open. A neglected website quietly tells strangers otherwise.

Why any of this matters

This was never about a website.

Strip away the screens and the searches, and underneath is the same work the elders were given. The site is only worth building if it carries that work further than a Sunday morning can reach.

Disciples

Teaching that does not stop on Sunday

A place where the Word keeps flowing through the week, so a believer can grow on a Tuesday night and not only in a pew. Discipleship that follows people home.

Families

A way for families to reach in

Parents finding their children's ministry, the next event, the sermon they missed, the people to call, all from the phone already in their hand. Belonging made easy to step into.

The flock

A shepherd who can still lead

Your voice and your teaching reaching the flock between gatherings, in seasons of sickness, distance, and doubt. Leading that is not confined to the room.

The one thing we ask of you

We will carry the rest. This part is yours.

The hard, technical, tiring parts are not your burden. But a website built on the wrong answers is just a fast tool pointed the wrong way. Before a single page is built, there are questions only the leadership can answer: who you are, who you are for, and what success would even look like. That conversation is the most important hour of this whole project.

Open the questions Where you stand today

The honest mirror

Where you stand today.

We pulled the real numbers: live Google data, cross-checked against two independent tools, and a full page-by-page crawl of the current site. We will show you all of it, the strong and the weak. We are starting with the strong, because it is real, and it changes what comes next.

What is already working for you

You are the most trusted name in town

Thirty-eight Google reviews at 4.8 stars. The church that currently outranks you on the map has nineteen. That is a reputation lead, not a deficit.

Your content is solid

A clear mission, real ministries, a sermon archive, and active Planning Center giving and events. There is a foundation here worth keeping.

Your host is not the problem

Pages answer in about a quarter of a second. The slowness people feel is the old page builder, not the server. A rebuild fixes it. You do not need to buy anything bigger.

Reviews: the social proof you already own

Living Word38

Forest Baptist19

St Paul Baptist14

The honest gap: you are found only by people who already know you

For the branded search "baptist church forest va," you show up at number two or three. But for the two searches a newcomer actually types, you do not appear in the local map box in any of the four towns we checked.

Map-pack position by town, live results
Town	"baptist church forest va"	"baptist church near me"	"churches in forest va"
Forest	#2	Not shown	Not shown
Evington	#2	Not shown	Not shown
Bedford	#3	Not shown	Not shown
Lynchburg	#3	Not shown	Not shown

Below the map, in the ordinary blue links, the rival church's website ranks first. Yours sits fifth to eighth, depending on the town. The rival's site is simply doing more of what Google rewards.

What a page-by-page scan of the current site found

64 of 64

Pages with no description, so Google writes its own under every link.

Dead link: the Youth ministry page returns a 404.

Titles too long, cut off mid-sentence in search results.

Pages too thin to rank for "plan your visit" searches.

Duplicate blog addresses splitting Google's trust.

~0.23s

Average server response. The host is fine. The build is the issue.

The profile also points to a non-secure address with a "www" split, so Google sees two versions of the site and fully trusts neither. And there is no church structured data, so Google cannot cleanly read your service times, address, and ratings.

None of this is a reputation problem. It is a findability problem, and findability is fixable. You already out-review the church beating you. The gap is the website and the Google profile, and a rebuild closes both by default.

A discussion guide for the leadership

Before we build: the questions only you can answer.

Most of the choices in this project are ours to carry. A handful are not, and no skill on our end can answer them for you. They are about who this church is, who it is for, and what you are actually trying to accomplish. Work through them together, out loud, in a room. "We do not know yet" is a completely valid answer, and a useful one.

Part 1

The heart: who you are, and who you are for

If these are clear, the whole site will be clear. If they are fuzzy, the site will be fuzzy.

1.Why would someone choose Living Word over the thousands of other churches in the Lynchburg area?

Why we ask: The single most important question on the page. If you can say it in a sentence, we can build the whole site around it.

2.Picture one specific person you most hope finds this website. Who are they? What are they carrying when they search?

Why we ask: A site built for everyone reaches no one. A site built for one real person reaches many.

3.Is there anyone Living Word is honestly not the right fit for?

Why we ask: Clarity about who you are not for is what makes you magnetic to the people you are for.

4.Is this website first a tool for outreach and evangelism, or first a tool for discipleship of the people you already have? If both, which leads?

Why we ask: These two goals pull a website in different directions. Knowing which comes first tells us what goes on the front page.

5.A year from now, what would have to be true for you to say this project was worth it?

Why we ask: This is how we define success together, in your words, before we start.

6.What happens if you do nothing? If the current site stays exactly as it is for three years, what is the cost to the mission?

Why we ask: The hardest question, and the one most worth sitting with. Doing nothing is a real option worth weighing honestly.

Part 2

Discipleship and content: keeping it alive

A website is not a building you build once. It is a garden. The question is who tends it.

7.Is there anyone in the church willing and able to regularly write, or record short videos, to keep teaching content fresh?

Why we ask: The discipleship value lives or dies on whether new content shows up. We can make it take two minutes. We cannot make someone want to.

8.Is there one person you trust who could be trained to post updates? Not a tech person, just a faithful, reliable one.

Why we ask: We will train them and leave a one-page guide. We just need to know who to hand the keys to.

9.When something is ready to go live, what should that look like? Who writes it, and who gives the final yes?

Why we ask: A clear approval path keeps the site current and keeps it from saying something the leadership did not intend.

10.If an elder steps down, or there is a season of difficulty within leadership, would that change who controls or approves content?

Why we ask: Better to plan for this calmly now than scramble during a hard season. The site should serve the church through any transition.

11.Will there be a newsletter? If so, who would write it, and how often?

Why we ask: It shapes whether we build a signup and a rhythm, or leave it out cleanly.

12.Where is the podcast currently hosted, and who manages it today?

Why we ask: We will pull it onto the site automatically wherever it lives. We just need to know where that is.

13.Do you want a strong, growing YouTube presence as a teaching and sermon library, or is YouTube just where the Sunday stream happens to land?

Why we ask: This decides whether YouTube is a back room or a front door. Both are fine. They are built differently.

Part 3

Reach: how people find you, and how families plug in

14.Do you want the congregation to interact with content from their phones, for example an app or app-like experience? Or is a fast website enough?

Why we ask: Most churches your size are better served by a great mobile website than a true app, which carries real upkeep. But if reaching families on their phones is central, we want to know now.

15.Which of these do you want a real presence on, and just as important, who would run each? Facebook. Instagram. YouTube. TikTok.

Why we ask: A neglected social account does the same harm as a neglected website. Better to do one well than four poorly.

16.Are you able to ask Liberty, Thomas Road, or other established Lynchburg-area institutions to link to your site once it is finished?

Why we ask: A link from a trusted local name does more for your standing on Google than almost anything we can do on the page. This is a door only you can open.

17.Should the events calendar be open for anyone to see, or only for members?

Why we ask: A public calendar reaches newcomers. A members-only one protects privacy. There are good reasons for each.

Part 4

Money and practical matters

18.For giving, do you want the website to simply link out to your existing Planning Center page, or for people to give without ever leaving the site?

Why we ask: This looks small, but it is not. Linking out keeps the heavy responsibility, the card security, the donor data, and the tax-receipt paperwork, on a platform built to carry it. Collecting gifts directly on your own site feels more seamless, but it moves real legal and security weight onto the church. We almost always recommend linking out, and would walk you through what anything more involved truly requires before you decide.

19.What budget works for you? Not what you think we want to hear. What is actually comfortable for this church?

Why we ask: We would rather build the right thing inside your real budget than oversell you something that strains the church.

Part 5

Convictions: how you want the work handled

20.Do you have a philosophy or conviction about technology we should know about, anything that would shape or limit how this work is done?

Why we ask: Some churches have firm views on data, privacy, advertising, screens, or simplicity. We want to honor yours from the first day, not discover them halfway through.

For the technical folks

Everything the rest of the site leaves out.

For the people who want the full picture. It lives here on purpose, so the elders never have to wade through it and the technical members can read all of it. Plain answers, in one place.

Platform and hosting

Astro 5 (SSR on Node), static-first build. No database, minimal attack surface.
Runs on our Contabo VPS with a US replica, so Virginia visitors are served from a nearby box. HTTPS via Let's Encrypt throughout.
Sveltia CMS at /admin for non-technical, form-based editing.
Deploys by git push, rsync, and a systemd service. No plugin-patching treadmill.

Integrations

Planning Center: events calendar feed plus giving.
YouTube: newest sermons pulled automatically by channel or playlist.
Podcast "The Dive Q&A": Spotify, Apple, and YouTube embeds, plus an RSS episode list.
Newsletter form into Planning Center People and the mailing list.

Giving, and why it links out

A deliberate choice, not a shortcut.

Giving sends people to your existing Planning Center page rather than collecting card details on the site itself.
That keeps the payment-security standard, the donor-data protection, and the tax-receipting for deductible gifts on a platform built to carry it, and keeps the site's attack surface near zero.
On-site giving is possible, but it pulls real legal and security weight onto the church. We would only build it as a deliberate, eyes-open decision.

SEO and visibility

Meta descriptions on every page. The current site has zero of sixty-four.
Title-length fixes, and the dead Youth 404 resolved.
Church, LocalBusiness, and Event JSON-LD schema. One canonical HTTPS host, retiring the http and www split.
Sitemap, an AI-crawler robots.txt, and llms.txt. Google Search Console and Business Profile set up.
The goal: first place in the local map pack for "church near me" terms.

The Learning Center (Phase 2)

A content collection with a type field: Videos, Worksheets, Books, Podcast, Small Groups, Home School, Sermons.
Multi-select left-rail filters with a card grid. Public, no logins.
PDF downloads for worksheets and books. Curriculum pages for small groups and home school.
Migrates the lwbcpress.com (WordPress) content, then retires it.

What each package includes technically

Foundation: the full Phase 1 site, integrations, SEO foundation, CMS, and launch with a 48-hour monitor.
Complete: Foundation, plus the Phase 2 Learning Center system and the content migration.
Ministry Plus: Complete, plus podcast production setup, advanced curriculum tooling, extra design rounds, and priority scheduling.

Make disciples.Gather the families.Lead the flock. This is about none of that, and all of it.