Open the media library of any website that has been running for a couple of years and you will see it: “IMG_0042.jpg”, “banner-new-2.png”, a page titled “Untitled”. Content management systems make it easy to publish and just as easy to lose track. If you build or maintain sites, a little CMS naming discipline pays back every single week. Here are eight habits, in the order I would adopt them, that keep a site easy to manage for you, your editors and whoever inherits it next.
1. Give every page a title and a slug that say the same thing
The page title is for people; the slug, the part of the web address after the domain, is for people and search engines. When they drift apart, editors lose the thread. A page titled “Our Services” with a slug of “page-2” is a trap waiting to be sprung during a redesign. Write the slug as a short, lowercase, hyphenated version of the title, and change it deliberately, with a redirect, if the title ever changes materially.
Clear slugs also help visitors. A short, readable address is easier to share and easier to recognise in a browser history. Pages that sell a service benefit most, which is why guides on turning service pages into client enquiries always start with the basics: say plainly what the page is.
2. Rename images before you upload them
Camera and stock-photo names are useless in a media library. Before uploading, rename the file to describe the picture: “team-planning-session-whiteboard.jpg” tells an editor what it shows and gives search engines a clue as well. Add alt text that describes the image for people using screen readers; that is a separate job from the file name and deserves its own sentence.
If you inherit a library full of numbered files, resist the urge to fix the whole archive in one sitting. Rename the images on your top pages first, then fix others as you touch them.
3. Name content types and fields for what they hold
Custom content types are where naming mistakes become permanent, because other things depend on them. A content type called “Item” and a field called “Text 2” will puzzle every editor. Call the type “Case study” and the field “Client challenge”. Editors see these names every day; developers see them in templates. Plain names reduce training time and cut support questions.
4. Make category and tag names boring and consistent
Taxonomies grow messy fast: “News”, “news”, “Latest news” and “Updates” all appearing together. Decide a short list, use singular or plural consistently, and write it down. A tag should be something a visitor might actually search for. If two terms mean the same thing, merge them and set up a redirect for the old archive page.
5. Label templates and blocks by purpose, not by appearance
“Blue box” works until the brand colour changes. “Callout: key takeaway” works forever. In page builders and block editors, name reusable blocks and template parts by what they do. Your editors can then pick the right block without previewing five of them.
This also helps the page structure itself. Pages built from clearly named blocks are easier to audit. A homepage assembled from “hero”, “proof points” and “contact prompt” can be reasoned about, which is the kind of clarity discussed in a closer read on homepage design and the impression it leaves.
6. Name your environments and branches without ambiguity
If your project uses a staging site, a development copy and live production, put the environment in plain sight: the admin bar colour, the site title and the login page. Branches in version control deserve the same honesty. “fix-contact-form-validation” says what it does; “test2” does not. When a deployment goes wrong at an awkward hour, nobody wants to ask what “new-staging-final” means.
7. Keep a readable names list for forms, menus and redirects
Forms and menus quietly accumulate. A form named “Form 3” sends emails nobody can trace. Name forms for their job: “Quote request, services page”. Name menus by location: “Main header menu”, “Footer legal links”. Keep a short note, even a shared text file, listing redirects and why they exist. Six months later, that note will save an hour of detective work.
8. Write an About page that names the people and purpose plainly
Naming is not only technical. Visitors judge a site by whether they can tell who is behind it and what it does. A page that states its purpose in ordinary words builds more confidence than one dressed up in slogans, a point developed in the piece on how an About page supports online trust. Think of it as naming the site itself: who, what and for whom.
The most common slip-ups
Even tidy teams trip over the same few things. Renaming a published page without a redirect is the classic one: the old address still circulates in emails and bookmarks, then returns an error. Another is stuffing keywords into every slug until the address reads like a sentence. Keep slugs short and natural; three or four words do the job. A third is letting a plugin or theme generate names automatically and never looking at them again. Automatic names are fine as a starting point, but review them once a quarter and tidy anything that confuses you, because it will confuse your editors too.
A quick naming template you can steal
If you need a starting point, use this pattern for anything that is not a public page:
- Files: subject, type, detail. “homepage-hero-illustration-warm.png”.
- Branches: verb-and-object, short. “add-newsletter-signup-footer”.
- Blocks: purpose first. “callout-key-takeaway”.
- Forms: action and place. “quote-request-services-page”.
Check how others label their sections
When you are stuck for ideas, borrow from sites whose sections announce themselves. GujaratOrbit is a Gujarat-focused events site whose menu leads to its event pages, venue pages, a discussion forum and a blog, so a visitor never has to guess what a link leads to. Menus that state what lies behind them are easier to use and easier to maintain.
Putting a number on the benefit, without inventing one
You do not need statistics to see whether this works. Before you start, ask each editor to note how many times in a week they open the wrong page, template or image. Ask again a month after adopting the habits. Even a rough tally from a few people shows whether the confusion is shrinking, and the result is an easy answer for any client or manager who wonders why you spent an afternoon renaming things.
Common questions from editors
Will renaming break my links? Changing a slug can. Use redirects, or let the CMS create them automatically if it supports it. Changing a media file name usually means re-uploading the file, so do it before the image is in use.
Is it worth doing on a small site? Yes, because small sites are often run by one person who forgets things. The habit costs minutes.
Who enforces the rules? Keep them short enough to fit on a card by the editor’s desk, and mention them during onboarding. Rules that need a manual do not get followed.
Where to begin
You do not need all eight today. Pick the one that annoys you most, probably the media library or the page slugs, and apply it to everything new. After a month you will feel the site getting easier, and the remaining habits will follow naturally. A CMS is only as friendly as its labels, so spend a little time making them honest.