How to redirect a parked domain to your main website
A parked domain usually displays a registrar’s holding page rather than a working website. On a GoDaddy placeholder page, visitors may see a welcome message, hosting attribution, copyright details and a privacy-policy link, but no useful business information. Redirecting that address can turn an otherwise inactive domain into a clear route to your established website.
The process is straightforward when you separate the registrar, DNS, hosting and website settings. The right setup depends on whether you want a permanent redirect, whether email uses the old domain, and whether the domain is an Australian address such as a .com.au or .au name. The steps to redirect a parked domain to your main website should therefore begin with checking ownership and end with testing every version of the address.
Check the domain and choose the destination
Sign in to the registrar account that controls the parked domain and confirm that the domain is active, paid for and unlocked. If it is registered through GoDaddy, open the domain management area and check its expiry date, nameservers, forwarding settings and DNS records. A domain that has expired, entered redemption or is awaiting verification cannot reliably send visitors anywhere.
Next, select the precise destination URL. Sending the parked address to your homepage is suitable when the old name represents the whole business. A more relevant landing page may be better when the domain relates to a particular campaign, product, suburb or former brand. For example, an old Melbourne business domain might point to a current “Melbourne services” page rather than forcing visitors to search through the new site.
Use a full HTTPS address, such as https://www.example.com.au/, and decide whether the old domain should work with both www and without www. Also decide whether paths should be preserved. A redirect from oldsite.com.au/about to newsite.com.au/about is useful when equivalent pages exist, while a blanket redirect to the new homepage can confuse visitors and reduce relevance.
Prepare the main website and DNS
Before switching the redirect on, make sure the destination website loads correctly on mobile devices, responds over HTTPS and has a valid certificate. Australian users may reach a site through mobile data in regional Queensland, a workplace connection in Sydney or a slower connection outside the capital cities. A redirect cannot fix a destination that is slow, insecure or incorrectly configured.
Check that the new website accepts the hostname you intend to use. If the destination is hosted on WordPress, Shopify, Wix, Squarespace or another platform, add the old domain only if the platform requires it for forwarding or domain verification. Some systems need a CNAME, A record or platform-specific connection before they will serve the domain safely.
Be careful with DNS changes. An A record points a hostname to an IP address, while a CNAME points one hostname to another hostname. Neither record is automatically the same as a web redirect. DNS tells browsers where to connect; an HTTP redirect tells them which new URL to open. This distinction matters when moving from a GoDaddy parking page to a separate hosting provider.
If you need to check whether DNS changes have reached different networks, a DNS propagation guide can help explain the checking process. Propagation is often quick, but some resolvers retain old information for the duration of the record’s TTL, so changes may appear at different times across Australia.
Set up forwarding at the registrar
The simplest approach is registrar-level domain forwarding. In GoDaddy, look for an option labelled Forwarding, Domain Forwarding or a similar setting. Enter the destination URL, choose HTTPS where available, and select a permanent redirect, usually identified as a 301 redirect. Save the change and allow the registrar to apply the relevant DNS or forwarding records.
Choose whether forwarding should include the path after the domain name. Path forwarding can preserve useful addresses, but it may create poor results if the old site structure bears no relation to the new one. If the domain was only parked and has never had meaningful pages, forwarding the root address and common variants to the new homepage may be adequate.
A 301 redirect communicates that the move is permanent to browsers and search engines. A 302 redirect indicates a temporary change and is more appropriate for short campaigns, testing or limited maintenance. Avoid stacking several redirects, such as old domain to an intermediate domain and then to the final website. Each extra hop adds delay and creates another point of failure.
If the registrar’s forwarding service does not provide HTTPS for the old address, visitors who type https://old-domain.com.au may see a certificate warning before the redirect can occur. In that situation, use a hosting service, CDN or web server that can issue a certificate for the old domain and return the redirect directly. Security should cover the address visitors actually enter, not only the final site.
Protect email, search visibility and analytics
A website redirect does not redirect email. If the old domain has addresses such as hello@old-domain.com.au, changing its web destination will not automatically forward those messages. Review MX records, aliases and mailboxes before editing DNS. Keep the old domain’s email service active for as long as customers, suppliers and government contacts may still use it.
For Australian organisations, this can include messages from local councils, suppliers, accountants or customers who retain an old .com.au address in their contacts. If the domain is tied to a registered business name, check that the legal entity still satisfies .com.au eligibility requirements and keep registration details current with the relevant registrar. A redirect does not replace the need to maintain the domain registration.
Search engines generally transfer signals through a correctly implemented 301 redirect, but the result is strongest when the old and new pages are closely related. Update Google Search Console, analytics settings, business listings, social profiles and directory records. Australian listings such as local chamber directories, industry associations and map profiles can continue sending traffic to the parked address for years.
Keep the old domain registered and forwarding for an appropriate period. Cancelling it too soon can allow another party to acquire the address and intercept visitors, email or links. Review referral traffic and server logs to identify outdated links. If visitors still arrive at an old product page or a prominent local landing page, create a specific redirect rather than sending every request to the homepage.
Compare the available redirect methods
The best method depends on how much control you have over DNS and hosting. Registrar forwarding is convenient for a simple parked domain, while a web-server rule provides finer control over paths, headers and complex migrations. A CMS plugin can work for smaller sites, but it adds another software dependency and should not be the first choice when the redirect can be handled at the server or registrar level.
| Method | Best suited to | Main advantage | Important limitation |
|---|---|---|---|
| Registrar forwarding | A parked domain with one main destination | Fast setup and little technical work | Limited path and HTTPS control |
| Web-server redirect | A domain with several old URLs | Precise rules and reliable 301 responses | Requires hosting and configuration access |
| CDN or edge rule | High-traffic domains or complex routing | Fast redirects close to visitors | Needs a suitable CDN plan and technical setup |
| CMS redirect plugin | A website managed through a CMS | Convenient interface and logging | Depends on the CMS, plugins and hosting |
| DNS-only change | Connecting a domain to a host | Useful for pointing services to a platform | DNS alone does not redirect browsers |
Use these recommendations when finalising the change:
- Record the current DNS, MX and nameserver settings before editing anything.
- Use a permanent 301 redirect for a genuine, long-term domain move.
- Test the root domain,
wwwversion, HTTP version and HTTPS version. - Keep email records separate from web-forwarding records.
- Redirect important old paths to matching new pages where they exist.
- Monitor search traffic, referral visits and enquiries after launch.
After saving the configuration, test from a private browser window and from a mobile device. Check that each version reaches the intended HTTPS page, that there is no redirect loop, and that the browser address bar changes to the new domain. Online redirect checkers can confirm the status code, but real-device testing can reveal certificate, caching or regional network problems.
Allow time for DNS and browser caches to clear, then review the setup over the following days. A properly configured parked-domain redirect should be quick, quiet and predictable: visitors arrive at the relevant main website, search engines receive a clear permanent signal, and existing email continues to function. Set the forwarding in your registrar account, verify every domain variation and keep the old registration active while traffic moves across.