How to Change the Joomla Site Name After Installation
You can change the name of an installed Joomla site from Global Configuration. The change is simple, but it is worth checking the frontend, browser titles, template branding, metadata, and mail identity afterward because not every visible brand name on a Joomla site necessarily comes from the global Site Name value.
Change the Site Name
- Sign in to Joomla Administrator.
- Open System → Setup Panel → Global Configuration.
- On the Site tab, locate Site Name.
- Enter the new name.
- Select Save or Save & Close.
The Site Name is a global Joomla configuration value and is used in multiple contexts, including Joomla's offline presentation and places where the site or template chooses to display the configured name.
Check page-title behavior
Changing Site Name does not mean every page title will become exactly that text. Joomla can combine menu-item or content titles with the site name depending on SEO/page-title configuration. After saving, open several frontend pages and inspect the browser tab/title. If the old name remains there, review the site's SEO title settings and the affected menu item's page-display/browser-title settings before assuming the global change failed.
Check your template and logo
A template may display a logo image, template-specific brand text, or a custom module instead of Joomla's global Site Name. Changing the global value will not rewrite text embedded in an image and may not alter template-specific branding. Check the active site template style and any header modules if the old name remains visible.
Check outbound mail identity
Mail settings can contain a separate From Name. If your site's brand name changed, review the Mail section of Global Configuration and any third-party mail/newsletter extension settings. Do not assume changing Site Name automatically changes every sender name configured elsewhere.
Check metadata and content that contains the old name
Existing article text, menu metadata, category metadata, structured-data settings, custom HTML modules, template overrides, and extension configuration may contain the old name as literal text. Joomla does not perform a global search-and-replace when Site Name changes. Search deliberately and edit only the records that are actually branding references.
Do not edit configuration.php unless necessary
For a working Administrator interface, Global Configuration is the preferred place to change the site name. Joomla stores the configuration in configuration.php, but hand-editing that file introduces avoidable syntax and permission risks. Manual editing is mainly a recovery technique when the normal configuration interface cannot be used.
If the new name will not save
If Joomla reports a configuration write error, check the ownership and writability of configuration.php and the hosting environment. Do not solve a write problem by giving broad write permissions to the whole site. Correct the specific ownership or permission issue, save again, and restore an appropriately restrictive state.
Verify the change
- Reload Administrator and confirm the configuration still contains the new Site Name.
- Open the frontend in a fresh browser session.
- Check the home page and several internal page titles.
- If the site uses offline mode, briefly verify the offline presentation in a safe maintenance window if needed.
- Check header/logo branding and outbound mail identity separately.
If only one part of the site still shows the old name, trace that specific output to its template, module, menu item, article, metadata, or extension setting rather than repeatedly changing the global value.
Need More Help with Joomla?
Still having trouble? Open a support ticket with QuantaCade Support and we'll be happy to help where we can.
Support priority is given to QuantaCade products, services, and customers. However, we're also happy to assist fellow Joomla users with general Joomla questions and troubleshooting when possible.
QuantaCade is an independent Joomla extension developer and is not official Joomla support. Some issues involving third-party extensions, hosting environments, server configurations, or other systems outside our development control may be beyond what we're able to resolve.