RedirectDuck team
Taking responsibility for a client's old domains starts with an inventory. Before changing DNS, establish who owns each domain, what it serves and which links still matter.
A short written plan makes the later redirect configuration easier to review with the client.
1. Audit ownership and existing use
For each domain, record:
- The registrar, account owner and renewal date.
- The current DNS records and who can change them.
- The website or service it currently reaches.
- Important old paths, downloads and campaign links.
- Available traffic reports and their date ranges.
Check for email and other services that use the domain. A website redirect does not replace mail hosting; preserve the records those services need.
2. Organize access in RedirectDuck
The Agency plan provides separate client spaces. Add the client's domains and rules in the appropriate space, then invite the people who should have access and choose their roles.
Client spaces share the parent workspace's subscription and plan limits. They do not each receive a separate RedirectDuck subscription or invoice automatically. Include that distinction when agreeing how your agency will charge the client.
If the client needs an independently owned account later, plan that transition explicitly. Creating a client space is not an automatic ownership-transfer workflow.
3. Create and test the mappings
For each important old URL, choose the closest relevant replacement page. Use path forwarding where the structure is unchanged and explicit mappings where it differs.
Review imports before applying them. Agency includes the import preview, redirect history and configuration rollback tools. Keep the original mapping file alongside your project notes.
After connecting the domain, test representative old URLs over both HTTP and HTTPS. Include a nested path, a query string and any special rule. Confirm the final destination rather than checking only that a redirect response exists.
4. Report with a clear scope
Use the client's space when reviewing traffic. Pro and Agency provide a CSV export of retained events, and Agency supports report branding with your agency's name, color and footer.
State which domains and time period the report covers. If you need a per-domain dataset, filter the exported rows by host or use the analytics API's domain filter for a summary.
Finish with a short list of missing mappings, rules to review and upcoming domain renewals. The Agency plan details and setup documentation provide the current limits and configuration steps.
