You upload a photo of your pastor. You name the file “pastor.jpg.” A few weeks later, someone on your team builds a staff page and titles it “Pastor.” WordPress quietly changes the page’s URL to pastor-2. Nobody clicked a warning box. Nobody asked permission. It just happened.
That’s not a glitch. It’s WordPress doing exactly what it’s built to do: making sure no two pieces of content share the same web address. The problem is that it’s making decisions about your site’s URLs, and most churches never find out until the “clean” link they wanted is already gone.
Most churches already know not to name two photos the same thing. Two files called “flyer.jpg” in the same folder is an obvious mess. What catches people off guard is that WordPress treats images, documents, pages, posts, and events as if they’re all pulling from the same pool of web addresses, not separate ones.
Upload an image named “pastor,” and WordPress reserves the URL yourchurch.org/pastor for that image, whether or not it’s ever meant to be its own page. Come back later and build a page called “Pastor,” and WordPress finds that the name is taken. So it bumps the page to pastor-2. The page still works. The clean, easy-to-share URL doesn’t.
Here’s the part that trips people up further: this isn’t consistent. Pages respect the reservation a media file makes. Blog posts, in many WordPress setups, don’t. So the same filename can behave differently depending on what you’re building next, which makes the problem feel random even though it isn’t.
If one person uploads bulletins, another builds event pages, and a third writes blog posts, none of them may realize they’re all drawing from the same namespace. A well-meaning volunteer named “newsletter.pdf” today can quietly claim a URL your communications director wants for a page next spring.
The fix isn’t a plugin, though plugins exist. The fix is a habit: name things specifically, every time, before they go anywhere near your website.
Skip special characters entirely. No apostrophes, ampersands, percent signs, quotation marks, or emoji in filenames. Browsers and servers convert these into strings of percent signs and numbers behind the scenes, which breaks links more often than it should and makes URLs unreadable to actual humans. Stick to lowercase letters, numbers, and hyphens.
Skip spaces too. A space becomes %20 in a web address. Use a hyphen instead: fall-bazaar-flyer.jpg, not “fall bazaar flyer.jpg.”
Be specific, not generic. “Bulletin.pdf,” “flyer.png,” and “photo1.jpg” are exactly the filenames most likely to collide with something else on your site, because everyone reaches for them. Bake the actual content into the name instead.
Build dates into anything recurring. Bulletins, newsletters, and sermon files repeat weekly or monthly. A consistent date format keeps them sortable and collision-proof:
Give pages and posts room to be specific too. “Pastor” invites a collision. “Pastor-james-smith” or “meet-our-pastor” doesn’t. The same goes for events: “harvest-fest” is safer than “fest,” and “harvest-fest-2026” is safer still if the event repeats every year.
Check your Media Library before you build a page. Before naming a new page or post, do a quick search in the Media Library for that word. If a file’s already sitting on that name, either rename the file or choose a different title for your new content. Thirty seconds now saves a mismatched URL later.
Write the convention down. A one-page naming key, shared with everyone who touches your website, whether that’s the office administrator, the youth pastor, or the volunteer who handles social media, does more for your site’s long-term health than any plugin. Consistency across people is the actual goal. A naming rule only one person follows isn’t a system.
None of this requires new software or a redesign. It requires everyone who uploads a file or builds a page to type one extra word into the name field. That’s a small habit for a church staff to build, and it’s a lot cheaper than explaining to a visitor why the link in last week’s bulletin now points somewhere else.
Copyright © 2008 - 2026. Worship Times. All rights reserved.
