Domain forwarding sends visitors from one address to another URL. It can support a genuine move, an owned alternate address or a relevant destination for a discontinued resource. For an acquired expired domain, the destination needs a clear relationship to what visitors expect.
Plan that relationship before configuring the redirect. Forwarding does not guarantee that a former site’s traffic, rankings or historical links will benefit the destination.
Choose the purpose and destination
Identify whether the task concerns a whole-site move, a particular old resource or an alternate address you control. For a site move, map important old URLs to relevant new equivalents. A single homepage redirect may be unsuitable for visitors expecting a specific article.
Google’s site-move guidance explains URL mapping and redirect considerations. If no useful equivalent exists, assess the appropriate response rather than creating a misleading destination.
The expired-domain use guide helps decide whether forwarding or a separate original website suits the acquisition.
Understand the redirect type
A permanent redirect is appropriate for a lasting move; a temporary redirect describes a temporary change. A registrar’s masked or framed option is different from a normal redirect that changes the browser’s address.
Namecheap’s forwarding documentation describes its supported options and account configuration. Use your actual provider’s current instructions. A DNS record pointing at a host does not by itself establish the HTTP redirect behaviour you want.
For a genuine permanent migration, choose the documented permanent option or configure the web server appropriately. Avoid masking merely to conceal where visitors are being sent.
Check the acquired name before deployment
Review old content, significant links, naming concerns and current registration control. Confirm you are not presenting the destination as an endorsement or continuation of a former organisation without a proper basis.
Google’s spam policies cover deceptive redirects, manipulative links and expired-domain abuse. The number of domains involved is not a complete assessment; purpose, content and user expectations matter.
The domain spam-check workflow helps organise previous-use evidence and its limits.
Configure without disrupting other services
- Save the existing DNS settings and identify email or other dependencies.
- Set the intended source hosts, including root and www where needed.
- Enter the exact destination and appropriate redirect type.
- Check whether HTTPS requests to the source are supported.
- Remove only conflicting records identified by the provider’s guidance.
The source needs to handle the request correctly before sending the visitor onward. An HTTPS destination does not automatically solve certificate requirements on an HTTPS source. Namecheap’s documentation discusses those distinctions; other services need their own checks.
Test representative requests
Check the root address, www version, HTTP and HTTPS, and several important old paths. Confirm the response type and final destination. Look for loops, unnecessary chains and paths that end at an irrelevant page.
In a hypothetical move, an old walking-route guide should lead to its relevant new guide, rather than an unrelated shop homepage. Keep that mapping in the migration record and verify it after changes.
The hosting guide helps identify DNS and web-serving responsibilities. Maintain the source registration and required service while the forwarding remains useful, with renewal and configuration checks in the domain record.