A URL is part of the customer journey
A website address appears in search results, messages, bookmarks and printed material. A clear address helps a person recognise where a link leads and makes the site easier for a team to maintain. It should reflect the page’s purpose without exposing private information or using a long list of search phrases.
A good structure is only one part of a useful website. Clear navigation, relevant content and working links matter too. A descriptive URL does not guarantee a ranking, and an old address is not necessarily a problem simply because it looks different from a new naming preference.
Name pages for their purpose
Start by listing the important pages and the questions they answer. A page explaining website design might have a short, recognisable service name in its path; a guide to preparing a project brief can have its own descriptive path. Use language your visitors understand, rather than internal department codes or an accumulation of closely related terms.
Plan how services, locations and articles relate before creating directories. A structure can be useful when it helps people and your team understand the page, but extra folder levels do not automatically make a page more valuable. Keep the path as simple as the content and platform reasonably allow.
Keep addresses readable and consistent
Use ordinary descriptive words and a consistent convention for separating them. Google recommends simple URLs and readable words; it supports hyphens as separators. Avoid spaces, unnecessary punctuation, session identifiers and long strings that a person cannot interpret. Ensure the system properly encodes characters when required.
Decide how your platform handles upper and lower case and trailing slashes, then link consistently to the intended final version. Some servers treat variations as different addresses. Ask a developer to check redirects and canonical signals when multiple versions can be accessed, rather than creating conflicting rules in several plugins.
A readable URL decision
- ClearDescribes the page’s purpose
- StableChanges only for a good reason
- PrivateContains no personal details
- ConnectedOld addresses redirect when changed
Do not expose information in a URL
A URL can be copied, stored in browser history or included in analytics and logs. Avoid putting names, email addresses, private booking details or other sensitive information into public paths or query parameters. This is especially important for forms, account links and customer-specific documents. Use your provider’s secure design for any necessary private access.
A simple URL is not a security control. A private document needs appropriate access restrictions even if its address is difficult to guess. Equally, blocking a crawler is not a substitute for access control. Ask the person responsible for the website how sensitive resources are protected before sharing them online.
Protect useful existing addresses
Before changing a live page’s path, identify where it is linked from, whether people have bookmarked it and whether it appears in printed material or relevant search results. If the current address works and describes a useful page, a cosmetic rename may create more disruption than value. Record the reason for any proposed change.
When an address must change, map the old URL to the most relevant new equivalent and arrange a suitable permanent server-side redirect where possible. Update internal links to point directly to the destination and check the final page. Do not send every retired page to the homepage when it does not answer the original need.
An illustrative page plan
Imagine a local design studio planning a service page and a separate practical guide. The team chooses one short service path that describes the actual offer and another article path that explains the guide’s subject. Both pages have clear titles and link to one another where a reader may want more detail.
The team keeps an older project page at its existing address because customers still use it and its content remains relevant. If the page is later combined with a current portfolio, the old-to-new mapping is documented and tested. This is an illustrative planning exercise, not a report of a real project.
Make the path understandable
A useful exercise is to show a proposed address to someone unfamiliar with the project and ask what they expect to find. For example, a short service path should suggest the actual service, while an article path should indicate the question answered. If a label could refer to several unrelated offers, choose more precise wording before publishing.
Avoid creating a separate page for every slight wording variation merely because different phrases exist. A single well-structured page can answer related questions where the customer intent is the same. Use headings and navigation to make the content understandable rather than relying on the URL alone.
Keep an address inventory
For each significant page, record its current URL, content owner, purpose and any planned replacement. Add known important links from printed items or other controlled properties, but do not store visitor identifiers or passwords in the document. This inventory becomes useful when a service changes or a redesign is proposed.
Review the inventory with the team before a launch. If the site has a large number of parameterised or filtered URLs, ask a developer which are meaningful customer destinations and how the platform treats them. The right solution should support real navigation and a maintainable set of preferred pages.
A practical naming sheet can also record whether the page will be linked in a printed document or from another website you control. Those uses make stability especially valuable. Before committing to a new slug, check that it is not already used for a different active page and that the destination remains clear to someone unfamiliar with the project. Once published, update navigation and maintain the record when responsibility changes. A descriptive heading should still explain the offer in full.
A pre-publication URL check
Ask whether the address reflects the page, avoids unnecessary words and follows the site’s convention. Confirm that it does not reveal personal information, that the page loads on a phone and that internal links reach the intended final version. Record the URL in your content inventory so colleagues can find and maintain it.
If changing an existing address, test both the old and new routes and update the sitemap if applicable. Give the change time to be discovered and monitor important errors. The goal is a stable, understandable route for real users supported by technically usable links, not a promise that a particular wording will produce a ranking.
