URL structure

Clean URL structure principles

Clean URLs use readable words rather than parameters. /services/web-design beats /page.php?id=123. Readable URLs help users understand where they are and what content to expect. They're easier to remember, share, and type.

Good URLs reflect site hierarchy. /services/web-design/astro-development shows clear parent-child relationships. This helps both users and search engines understand how content relates.

URL best practices

Use hyphens, not underscores: /web-design, not /web_design. Search engines treat hyphens as space, underscores as part of words. Include relevant keywords naturally—they provide context and slight ranking benefit.

Keep URLs short. Every additional folder level adds complexity. /services/design beats /our-company/what-we-do/services/design-services/web-design. Shorter URLs are cleaner, clearer, and easier to share.

Use lowercase consistently. Web servers may treat /Services and /services as different URLs, creating duplicate content issues. Stick with lowercase throughout.

URL changes and redirects

Changing URLs after launch requires 301 redirects to maintain SEO value. Every backlink, bookmark, and indexed URL pointing to the old address needs redirecting. Missing redirects create broken links and waste link equity.

This is why planning URL structure upfront matters. Getting it right initially avoids complex redirect management later. We map URLs during wireframing, before any code is written.

Technical considerations

Trailing slashes should be consistent: either use them everywhere or nowhere. Mixing creates duplicate content issues. Secure HTTPS URLs always. Use canonical tags to consolidate variations.

Every Fernside site uses clean, logical URL structure: keyword-rich, hierarchical, and consistent. We plan this during early design stages, ensuring SEO-friendly URLs from launch.