1. Go to the Quickleap dashboard
2. Click Get Started or Sign Up
3. Choose your authentication method:
   • Email and password
   • OAuth with Google
   • OAuth with GitHub
4. Complete the registration process

1. Navigate to the dashboard
2. Click Add Redirect or Create New Redirect
3. Fill in the redirect details:

{
  "fromDomain": "old-domain.com",
  "toDomain": "https://new-domain.com",
  "redirectType": "permanent",
  "pathForwarding": true,
  "queryForwarding": true,
  "samplingRate": 1.0
}

• From domain - The domain you want to redirect (e.g., old-domain.com)
• To domain - The target URL (e.g., https://new-domain.com)
• Redirect type:
  • permanent (301) - For permanent domain changes and SEO value transfer
  • temporary (302) - For temporary campaigns and testing
• Path forwarding - Preserve the URL path structure
  • If enabled: old-domain.com/blog → new-domain.com/blog
  • If disabled: old-domain.com/blog → new-domain.com
• Query forwarding - Preserve URL query parameters
  • If enabled: old-domain.com?utm_source=email → new-domain.com?utm_source=email
• Sampling rate - Analytics sampling rate (0.0 to 1.0)
  • 1.0 = Track 100% of traffic
  • 0.1 = Track 10% of traffic (useful for high-traffic domains)

4. Click Create Redirect

​

DNS configuration

1. Go to your domain registrar’s DNS management panel
2. Update your DNS records according to Quickleap’s instructions:
   • For root domain (example.com): Add an A record pointing to Quickleap’s servers
   • For subdomain (www.example.com): Add a CNAME record pointing to Quickleap

​

Verify domain status

1. Return to the Quickleap dashboard
2. Find your redirect in the list
3. Click Verify Domain
4. Quickleap will check your DNS configuration

const response = await fetch('/verify-domain', {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    domain: 'old-domain.com'
  })
});

const result = await response.json();
console.log(result.verified); // true or false

​

Browser test

1. Open a web browser (ideally in incognito/private mode)
2. Navigate to your source domain (e.g., http://old-domain.com)
3. Verify you’re redirected to the target URL
4. Check that the URL path and query parameters are preserved (if enabled)

​

Command line test

# Test basic redirect
curl -I http://old-domain.com

# You should see:
# HTTP/1.1 301 Moved Permanently
# Location: https://new-domain.com

# Test with path forwarding
curl -I http://old-domain.com/blog/post-1

# You should see:
# HTTP/1.1 301 Moved Permanently
# Location: https://new-domain.com/blog/post-1

​

Access analytics

1. Go to your dashboard
2. Click on your redirect to view details
3. Navigate to the Analytics tab

​

Available metrics

• Basic stats - Total hits, unique visitors, time range comparisons
• Time-based analytics - Traffic over time with customizable intervals
• Geographic data - Visitor locations by country and region
• Device information - Breakdown by device type, browser, OS
• Referrer data - Traffic sources and referring domains
• Hourly patterns - Peak traffic times and usage patterns
• Bot detection - Separate human vs bot traffic
• Campaign tracking - UTM parameter analysis

​

Fetch analytics via API

const response = await fetch(
  `/analytics/redirect/${redirectId}/stats/basic?start=2024-01-01&end=2024-01-31`
);

const stats = await response.json();
console.log(stats);
// {
//   totalHits: 15420,
//   uniqueVisitors: 8234,
//   averagePerDay: 497,
//   peakDay: "2024-01-15"
// }

const response = await fetch(
  `/analytics/redirect/${redirectId}/stats/geo?groupBy=country`
);

const geoData = await response.json();
console.log(geoData);
// [
//   { country: "US", hits: 8420, percentage: 54.6 },
//   { country: "GB", hits: 2134, percentage: 13.8 },
//   { country: "CA", hits: 1876, percentage: 12.2 }
// ]