LinkShift.App for migrations and campaign links
Protect rankings while moving URLs and launch short branded links from your own domains. LinkShift centralizes redirect rules so teams stop editing infrastructure-level configs.
Watch the first domain + redirect rule setup
A quick walkthrough showing how to attach your first domain and publish a rule on LinkShift.App.
Three building blocks, one predictable workflow
LinkShift.App keeps your rules structured. Domain groups own the routing logic, domains inherit it, and rules stay ordered and explicit.
Domain group
One group defines the redirect rules, limits, and defaults that apply to each assigned domain.
Domains
Attach production, staging, or regional domains and keep routing consistent by design.
Redirect rules
Ordered rules support regex sources, placeholders, modifiers, and inline conditions.
Built for SEO-safe migrations and branded shortlink operations
Keep redirects precise, reusable, and observable across every domain you manage.
SEO-safe migration control
Preserve path structure with exact, wildcard, or regex-based redirect mappings.
Branded shortlinks
Run an internal Bitly workflow on your own domain using link maps and short keys.
Built-in analytics
Track redirect hits, top link-map keys, and top request variants per rule.
API-first operations
Manage domains, redirect rules, link maps, and test cases through authenticated API keys.
Regex-ready sources
Match literal paths or /pattern/flags with capture groups for precise routing.
Path + query match modes
Use path prefix matching with query exact, ignore, or subset rules.
Link maps for short links
Resolve short keys into destinations with fallback routing and case controls.
Automatic SSL
HTTPS certificates are provisioned automatically for connected domains after DNS setup.
Domain-group governance
Set rules once and reuse them across production, staging, and typo domains.
Built-in robots.txt control
Manage robots.txt per redirect group with ready policies or custom content for advanced SEO control.
Support path prefix routing alongside query match modes (exact, ignore, or subset) to keep redirects precise without losing flexibility. Add link maps to resolve short keys into full destinations with optional fallbacks, and configure robots.txt directly at the group level.
Plans that grow with your traffic
Start free and scale only when your redirect inventory demands it.
SSL is included for every domain, so traffic is always served over HTTPS.
Rule syntax that mirrors real traffic
Use regex, placeholders, and conditions to build consistent redirection logic.
Campaign capture with source tracking
Regex groups keep the identifier, placeholders keep the context.
/^\/promo\/(\d+)$/https://app.example.com/campaign/$1?from={domain.fqdn}The destination stays valid for any assigned domain in the group.
Preserve query parameters
Carry UTM data while moving to a new host.
/^\/go\/(.*)$/https://store.example.com/$1?utm={query.utm}Use modifiers like {query.utm:url_encode} when values can include spaces.
Method-aware routing
Route by method without duplicating rules for each domain.
/^\/support\/(.*)$/method == "POST" ? https://api.example.com/write/$1 : https://api.example.com/read/$1Conditions support operators like ==, !=, <=, >=, ~=, and includes.
Variables are resolved from request context including path, query parameters, segments, and domain metadata.
Keep routing safe, fast, and auditable
Domain groups help teams work in parallel without losing control of critical redirects.
Predictable governance
Centralize rules at the group level and avoid divergent redirects across brands, regions, or environments.
30-day satisfaction window
If the platform is not the right fit, request a refund within 30 days with no explanation required.
Questions teams ask before switching
Quick answers for architects, developers, and ops teams.
In most cases, no. Rules live at the domain group level and apply to each domain assigned to that group.
Yes. Provide regex patterns in /pattern/flags format and reference capture groups with $1, $2, and so on.
You can use {path}, {query.*}, {segments.*}, and {domain.*}, plus modifiers.
If the platform is not a fit, you can request a refund within 30 days with no explanation required.
Launch migration-safe redirects in minutes
Set up domain groups, publish rules, and run branded shortlinks with shared governance.