Currently, there is no mechanism for users to control domain redirection between www and non-www versions of their domain. Users cannot configure whether their domain redirects from www.example.com to example.com or vice versa.
SEO Impact: Lack of consistent redirection can harm search engine rankings due to duplicate content issues and split domain authority
User Experience: Visitors may encounter inconsistent URLs, creating confusion and potential trust issues
Brand Consistency: Organizations cannot enforce their preferred URL format across their web presence
Technical Compliance: Missing proper redirection can affect analytics tracking and third-party integrations that expect consistent URL patterns
Enable users to have full control over their domain redirection preferences, allowing them to configure and manage www/non-www redirections according to their brand and technical requirements.
Add Redirection Control Interface
Create a new section in domain settings for redirection management
Provide clear options for redirection direction:
Redirect www.domain.com → domain.com
Redirect domain.com → www.domain.com
Example from Webflow, but we need the simple version:

Implement Backend Logic
Build server-side logic to handle the redirection rules
Ensure redirections only work within the same root domain for security
Implement proper HTTP 301 permanent redirects for SEO benefits
User Interface Requirements
Simple toggle or radio button selection for redirection preferences
Real-time preview showing the redirection behavior
Clear explanations of SEO implications for each option
Validation to prevent infinite redirect loops
Security & Validation
Restrict redirection to same-domain only (prevent malicious redirects)
Validate domain ownership before allowing redirection changes
Implement rate limiting for redirection rule updates
Domain settings page enhancement
Backend redirection engine
User interface for redirection control
Security validation layer
Documentation for users on SEO best practices
Users can access redirection controls in their domain settings
All three redirection options (www→non-www, non-www→www, no redirection) function correctly
Proper 301 redirects are implemented for SEO compliance
Security validation prevents cross-domain redirections
User interface clearly explains each option and its implications
Changes take effect within reasonable time (< 5 minutes)
Comprehensive testing covers edge cases and security scenarios
#domain-management #redirection-control #seo-optimization #www-redirect #domain-settings #user-control #web-infrastructure
Please authenticate to join the conversation.
In Progress
Feature Request
3 months ago
Support Team
Get notified by email when there are changes.
In Progress
Feature Request
3 months ago
Support Team
Get notified by email when there are changes.