Choose which source host should match: the apex, www, both or a supported wildcard. Decide whether the incoming path and query string should be kept. Record expected results for the home page, a deep path, a query-string URL and an unmatched path.

Send destination_url, status_code, matching settings, path_mode, query_policy, source_host_mode, priority and enabled deliberately. The default code is 301. A temporary code can be more appropriate during testing when you do not want clients retaining a permanent move.

1. POST to the preview resource with the owned forwarding_domain_id and a sample_url, together with the proposed rule settings.
2. Inspect the simulated status and destination. Repeat with the other representative paths and queries.
3. List existing rules and check their priority, host selectors and destinations. Avoid duplicate rules or a redirect chain that eventually returns to the source.
4. Create the rule under the forwarding domain. For an edit, PATCH the rule ID with the intended destination and settings; use the current If-Match version where appropriate.
5. Deploy through the forwarding workflow and test actual HTTP and HTTPS responses for every source hostname.

• Create a forwarding domain and complete DNS ownership verification
• Deploy or roll back a forwarding runtime generation
• Create a website redirect with Domain Forwarders
• Inspect and renew TLS certificates for forwarding domains