WordPress home_url Example: Build Canonical Site Links Safely

Last reviewed: May 6, 2026

Hardcoded site links become technical debt the moment a host, scheme, reverse proxy, or multisite detail changes. home_url() is the supported way to build URLs for the public front end of the current site without guessing the canonical base manually.

This guide shows how to use home_url() safely for front-end links and when to pass an explicit scheme or path.

Build front-end links from the canonical home URL

<?php
$downloads_url = home_url( '/downloads/' );

echo '<a href=\"' . esc_url( $downloads_url ) . '\">'
	. esc_html__( 'Downloads', 'vulnwp' )
	. '</a>';

This is easier to maintain than concatenating domain constants or assuming the site base never changes.

Use the scheme parameter deliberately

The function accepts a scheme context, including http, https, relative, and rest. Most front-end links should rely on the default site behavior, but explicit schemes are useful when the output context requires one.

Remember that home_url() is for front-end accessibility

The WordPress reference frames home_url() as the public-facing site URL. That makes it the wrong helper for admin URLs, plugin assets, or file-system paths. Each of those has its own dedicated API.

Escape the final URL in output

The helper gives the canonical link value. The final output still needs escaping appropriate to the destination context, especially in HTML attributes.

Common mistakes

• Hardcoding the site domain. This becomes brittle during host and scheme changes.
• Using home_url() for admin navigation. That is what admin_url() is for.
• Skipping output escaping. Canonical formation and output safety are different steps.
• Appending paths carelessly. Let the helper manage the base URL and pass a clear path.

Production checklist

• Use home_url() for public site links.
• Pass paths explicitly instead of concatenating the domain by hand.
• Use a different helper for admin and REST URLs.
• Escape the final URL for output.
• Retest generated links after scheme, host, or reverse-proxy changes.

Related reading

Pair this with the rest_url guide when the consumer is an API route, and with the esc_url article when the link is headed straight into HTML output.

References and further reading

• WordPress Code Reference: home_url()
• WordPress Code Reference: get_home_url()
• WordPress Code Reference: esc_url()