Hybrid 301/302 Domain Redirect Strategy
A comprehensive guide to implementing a hybrid redirect strategy that enables star ratings in SERPs while maintaining branded vanity URLs for optimal click-through rates.
Executive Summary
The Dross:Network implements a hybrid 301/302 redirect strategy that combines subdirectory-based architecture with vanity domain canonicals for optimal SEO performance.
Root Section Pages
Use 301 redirects → canonical on dross.net to enable star ratings in SERPs
All Subpages
Use 302 redirects → canonical on vanity domain for branded SERP URLs
Star Ratings in SERPs
Branded Vanity URLs in SERPs
Authority Consolidation
How the Hybrid Strategy Works
Visual Flow Diagram
User visits vanity domain
Root page?
e.g., /aviation/
301
Permanent
dross.net/aviation/
canonical: dross.net
302
Temporary
dross.net/aviation/shop/
canonical: drossaviation.com
Why Star Ratings Work on Both Paths
Star ratings (⭐) appear for both root and subpages because the aggregateRating property is included in the Schema.org structured data on every page. Google extracts this rating from the JSON-LD markup regardless of which URL is canonical.
Alternative: 302-Only Setup
If your CDN or hosting only supports one redirect type, you can use 302 redirects for all pages including root pages. This works but may result in minor authority loss (~10-15%) since search engines treat 302s as temporary and may not fully transfer link equity.
Redirect Rules by Page Type
| Page Type | Redirect | Canonical | Reason |
|---|---|---|---|
| Root pages (/aviation/, /media/) | 301 | dross.net | Star ratings in SERPs |
| All subpages (/aviation/shop/) | 302 | vanity domain | Branded URLs for higher CTR + Star ratings in SERPs |
Complete Domain Mapping
| Vanity Domain | Subdirectory | Section |
|---|---|---|
| alexanderdross.com | /alexander/ | Personal portfolio/CV |
| drossair.de | /air/ | Sightseeing flights |
| drossmedia.de | /media/ | SEO/GEO agency services |
| drossaviation.com | /aviation/ | Aviation tech & Stratux |
Configuration Generator
Enter your domain details to generate customized redirect configurations for any platform.
⚡ Hybrid: Root pages use 301 (star ratings preserved), subpages use 302 (branded URLs in SERPs). Best of both worlds.
Live Preview - How URLs Will Redirect:
💡 301 = permanent (for star ratings on root) • 302 = temporary (keeps branded vanity URL in SERPs for subpages + shows star rating)
🔍 Test Any URL
Enter a URL path (e.g., /shop/, /de/products/, /) to see where it will redirect.
📋 Batch URL Tester
Enter multiple URLs (one per line) to test them all at once.
CDN Configuration Examples
Download All (.zip)Cloudflare Page Rules
For Cloudflare, create these Page Rules in your dashboard (order matters - most specific first).
# Root page → 301 redirect
drossaviation.com/ → 301 → dross.net/aviation/
# Language roots → 301 redirect
drossaviation.com/de/ → 301 → dross.net/de/aviation/
drossaviation.com/es/ → 301 → dross.net/es/aviation/
# All subpages → 302 redirect
drossaviation.com/* → 302 → dross.net/aviation/*Why Root Pages Use dross.net Canonical
The Star Rating Advantage
Google only displays aggregateRating star snippets for pages that are considered "subpages" of a domain. By canonicalizing root section pages (like /aviation/) to dross.net, they qualify as subpages and can display star ratings in search results.
How 302 Redirects Preserve Vanity URLs
SEO friendly
URL
drossaviation.com/shop/
302 redirect
canonical points to
Product
Page URL
dross.net/aviation/shop/
The 302 redirect tells search engines "this is temporary" so they index the vanity URL, while the canonical tag on the destination ensures proper content attribution.
How It Works
Root Pages (301 → dross.net)
- •User visits:
drossaviation.com/ - •301 redirects to:
dross.net/aviation/ - •Canonical:
dross.net/aviation/ - •Result: Stars appear in Google
Subpages (302 → vanity)
- •User visits:
drossaviation.com/shop/ - •302 redirects to:
dross.net/aviation/shop/ - •Canonical:
drossaviation.com/shop/ - •Result: Branded vanity URL in SERPs + Star rating appears in SERPs
Schema.org Dual-URL Implementation
All pages include both dross.net and vanity domain URLs in Schema.org structured data to strengthen entity signals.
Entity Consolidation Flow
Entity Recognition
Understands as single entity
Consolidated Brand Entity
sameAs + url[]// Schema.org JSON-LD
"@id": "dross.net/..."
"url": [
"dross.net/aviation/",
"drossaviation.com/"
],
"sameAs": "drossaviation.com"
Both domains included
Primary Domain
Vanity Domain
WebPage Schema Structure
Root Pages
{
"@type": "WebPage",
"@id": "dross.net/aviation/#webpage",
"url": [
"https://dross.net/aviation/",
"https://drossaviation.com/"
],
"sameAs": "https://drossaviation.com/"
}Subpages
{
"@type": "WebPage",
"@id": "drossaviation.com/shop/#webpage",
"url": [
"https://drossaviation.com/shop/",
"https://dross.net/aviation/shop/"
],
"sameAs": "https://dross.net/aviation/shop/"
}sameAs References by Page Type
| Page | Schema Type | @id Domain | sameAs Includes |
|---|---|---|---|
| / | Organization | dross.net | All 4 vanity domains + socials |
| /aviation/ | Organization, WebPage | dross.net | drossaviation.com |
| /aviation/shop/ | Product, WebPage | drossaviation.com | dross.net/aviation/shop/ |
Sitemap Architecture
The network uses a dual-sitemap strategy: primary sitemaps on dross.net for main indexing, and vanity sitemaps for subpage URLs on their respective vanity domains.
Sitemap Hierarchy
References
Master Index - lists all XML sitemaps
Root + Legal
dross.net/*
Aviation
dross.net/aviation/*
Media
dross.net/media/*
Air
dross.net/air/*
Portfolio
dross.net/alexander/*
drossaviation.com/*
drossmedia.de/*
drossair.de/*
alexanderdross.com/*
Primary Sitemaps (dross.net)
| Sitemap | Content | URLs |
|---|---|---|
| /sitemap-index.xml | Master index | References all section sitemaps |
| /sitemap.xml | Network root + legal | dross.net URLs |
| /aviation/sitemap.xml | All aviation pages | dross.net/aviation/* URLs |
| /media/sitemap.xml | All media service pages | dross.net/media/* URLs |
| /air/sitemap.xml | All air/flight pages | dross.net/air/* URLs |
| /alexander/sitemap.xml | Portfolio + blog | dross.net/alexander/* URLs |
Vanity Sitemaps
| Sitemap Location | Contains URLs for |
|---|---|
| /aviation/vanity-sitemap.xml | drossaviation.com/* (incl. root) |
| /media/vanity-sitemap.xml | drossmedia.de/* (incl. root) |
| /air/vanity-sitemap.xml | drossair.de/* (incl. root) |
| /alexander/vanity-sitemap.xml | alexanderdross.com/* (incl. root) |
Why Subdirectory Architecture
1. Authority Consolidation
- •All sections contribute to single domain authority
- •New content benefits the entire network
- •Avoids zero-authority starts on each domain
2. Backlink Power
- •Links to any section benefit the whole network
- •No link equity dilution across domains
- •Internal linking passes full PageRank
3. Technical Simplicity
- •Single SSL, robots.txt, sitemap-index
- •Unified analytics and tracking
- •Shared codebase and components
4. Multilingual Coherence
- •Seamless /de/, /es/ language integration
- •Unified hreflang across sections
- •Single sitemap-index for all languages
Video Explanation
Learn more about the subdirectory vs. subdomain architecture decision from this expert explanation:
DNS/CDN Redirect Configuration
Performance Best Practice: CDN-Level Redirects
Redirects should always be implemented at the CDN edge, not at the origin server. CDN-level redirects offer significant performance advantages:
Reduced Origin Load
Requests are handled at the edge, never reaching your origin server - saving compute resources and reducing costs
Lower Latency
Edge nodes are geographically distributed - users get redirected from the nearest PoP (Point of Presence) with sub-10ms response times
Better Uptime
CDN redirects work even if your origin is temporarily unavailable, improving overall reliability
SEO Signal Preservation
Faster redirects mean Googlebot crawls more efficiently, preserving link equity during the redirect chain
Latency Comparison: CDN Edge vs Origin Server
| Metric | CDN Edge Redirect | Origin Server Redirect | Improvement |
|---|---|---|---|
| Response Time (same region) | 5-15ms | 50-150ms | 10x faster |
| Response Time (cross-continental) | 20-50ms | 200-500ms | 10x faster |
| Time to First Byte (TTFB) | <20ms | 100-300ms | 5-15x faster |
| Origin Server Load | 0 requests | 1 request per redirect | 100% |
| Availability During Origin Outage | Fully operational | Redirect fails | ∞ |
* Values are typical ranges based on global CDN providers (Cloudflare, Vercel Edge, AWS CloudFront). Actual performance depends on CDN configuration and geographic distribution.
Regional Latency Comparison (ms)
6x faster
7x faster
7x faster
6x faster
6x faster
8x faster
* Origin server located in US-East. CDN latency assumes edge PoP in each region.
Required Redirect Rules
Configure these rules in your CDN (Cloudflare, Vercel, etc.) for each vanity domain:
# Generic Pattern
# vanity.com/[lang]/x/y → primary.net/[lang]/section/x/y
# Example: drossaviation.com → dross.net/aviation/
# Root page → 301 redirect
drossaviation.com/ → 301 → dross.net/aviation/
drossaviation.com/de/ → 301 → dross.net/de/aviation/
drossaviation.com/es/ → 301 → dross.net/es/aviation/
# Subpages → 302 redirect
drossaviation.com/x/y → 302 → dross.net/aviation/x/yGoogle Search Console Setup
| Property | Submit Sitemap |
|---|---|
| dross.net | /sitemap-index.xml |
| dross.net | /sitemap.xml |
| drossaviation.com | dross.net/aviation/vanity-sitemap.xml |
| drossmedia.de | dross.net/media/vanity-sitemap.xml |
| drossair.de | dross.net/air/vanity-sitemap.xml |
| alexanderdross.com | dross.net/alexander/vanity-sitemap.xml |
SEO Benefits Summary
Star Ratings in SERPs
Root pages display aggregateRating stars
Branded URLs + Star Ratings
Subpages show vanity URLs with star ratings
Entity Consolidation
Dual-URL schema links all domains
Authority Preservation
Consolidated domain authority
Knowledge Panel
Improved unified Knowledge Panel chances
AI/LLM Understanding
Helps AI connect cross-domain info
Implementation Checklist
Completed
Pending
Need Help Implementing This Strategy?
Get expert assistance with your multi-domain SEO architecture from Dross:Media, our SEO and digital marketing agency.