How to Use LinkGoWhere - Complete Guide
How to Use LinkGoWhere
LinkGoWhere is a powerful yet simple tool for tracing URL redirects. This guide will help you get the most out of our service.
📚 Table of Contents
- Basic Usage
- Understanding User-Agents
- Reading Results
- Advanced Features
- Common Scenarios
- Best Practices
- Troubleshooting
Basic Usage
Step 1: Enter URLs
Navigate to the homepage and enter the URLs you want to check in the text area.
Tips:
- One URL per line
- Maximum 10 URLs per batch
- URLs must start with http://orhttps://
Example:
https://example.com
https://bit.ly/example
https://t.co/example
Step 2: Select User-Agent
Choose the User-Agent you want to test with from the dropdown menu.
Available Categories:
- 🤖 Robots: Search engine crawlers (Google, Bing, Yandex)
- 📱 Mobile: Mobile devices (iPhone, Android)
- đź’» Desktop: Desktop browsers (Chrome, Firefox, Safari, Edge)
Why does this matter? Some websites serve different content or redirects based on who’s visiting.
Step 3: Check Links
Click the “Check Links” button and wait for results.
What happens:
- Each URL is checked in real-time
- All redirects are followed automatically
- Results display the complete redirect chain
- Duration and status codes are shown for each step
Step 4: Review and Export Results
Once complete, you can:
- đź“‹ Copy results to clipboard
- 📥 Export as JSON for further analysis
- 📊 Export as CSV for spreadsheets
Understanding User-Agents
What is a User-Agent?
A User-Agent is a string that identifies the browser or device making the request. Websites use this information to serve appropriate content.
When to Use Different User-Agents
🤖 Googlebot
Use when:
- Checking how search engines see your site
- Verifying SEO redirects
- Testing Google’s access to your content
Example scenario: You want to ensure Googlebot can access your new site after a domain migration.
📱 Mobile User-Agents
Use when:
- Testing mobile-specific redirects
- Checking responsive website behavior
- Verifying mobile app deep links
Example scenario: Your site redirects mobile users to a different subdomain (m.example.com).
đź’» Desktop Browsers
Use when:
- Testing standard website redirects
- Checking compatibility across browsers
- Verifying general user experience
Example scenario: Testing if your affiliate links work correctly for desktop users.
Popular User-Agent Combinations
| Scenario | Recommended User-Agent | 
|---|---|
| SEO Audit | Googlebot/2.1 (Desktop) | 
| Mobile Testing | iPhone/Safari iOS | 
| General Checking | Chrome (Latest) | 
| Bot Detection | Various robots | 
Reading Results
Understanding the Result Display
Each result shows the complete redirect journey:
Step 1:
  From: https://example.com
  To: https://www.example.com
  Status: 301 (Moved Permanently)
  Duration: 0.123s
Final Destination:
  URL: https://www.example.com
  Status: 200 (OK)
  Duration: 0.045s
Status Code Meanings
2xx Success
- 200 OK: Final destination reached successfully
- 201 Created: Resource created (rare in redirects)
3xx Redirects
- 301 Moved Permanently: SEO-friendly permanent redirect
- 302 Found: Temporary redirect (not ideal for SEO)
- 307 Temporary Redirect: Preserves HTTP method
- 308 Permanent Redirect: Like 301 but preserves method
4xx Client Errors
- 404 Not Found: URL doesn’t exist
- 403 Forbidden: Access denied
- 410 Gone: Resource permanently removed
5xx Server Errors
- 500 Internal Server Error: Server problem
- 502 Bad Gateway: Proxy/gateway error
- 503 Service Unavailable: Server temporarily down
Color Coding
- 🟢 Green: Success (200-299)
- 🟡 Orange: Redirects (300-399)
- đź”´ Red: Errors (400-599)
Duration Interpretation
- âś… < 0.5s: Excellent
- ⚠️ 0.5s - 2s: Acceptable
- ❌ > 2s: Slow (may affect user experience)
Advanced Features
Batch Checking
Check multiple URLs simultaneously to save time.
Best for:
- Auditing multiple pages after migration
- Checking a list of affiliate links
- Validating sitemaps
Limitations:
- Maximum 10 URLs per batch
- Results may take longer for large batches
Export Options
đź“‹ Copy to Clipboard
Perfect for quick sharing in emails or documents.
Format: Plain text with formatting
📥 JSON Export
Ideal for developers and automated analysis.
Contains:
- Source URL
- User-Agent used
- Complete redirect chain
- All metadata (status, duration)
Use cases:
- API integration
- Data analysis
- Automated testing
📊 CSV Export
Great for spreadsheet analysis and reporting.
Columns:
- Step number
- Type (Redirect/Final)
- URL
- Destination
- Status
- Duration
Use cases:
- Client reports
- Bulk analysis
- Database imports
Common Scenarios
Scenario 1: Affiliate Link Verification
Goal: Verify affiliate links redirect to correct destinations
Steps:
- Enter affiliate URLs
- Select Desktop Chrome User-Agent
- Click Check Links
- Verify final destination matches expected partner site
- Check that tracking parameters are preserved
What to look for:
- Status 301 or 302 redirects
- Tracking parameters in URL
- Correct final destination
- Reasonable redirect count (< 3 hops)
Scenario 2: Website Migration Check
Goal: Ensure old URLs redirect to new site correctly
Steps:
- List old URLs (one per line)
- Select Googlebot User-Agent
- Check all links
- Verify 301 status (permanent redirect)
- Confirm new URLs are correct
What to look for:
- Status 301 (not 302!)
- Direct redirects (avoid chains)
- Fast response times
- Consistent redirect patterns
Scenario 3: Shortened URL Safety
Goal: Verify where a shortened URL leads before clicking
Steps:
- Enter shortened URL (bit.ly, tinyurl, etc.)
- Select your preferred User-Agent
- Check the link
- Review final destination for safety
Safety checks:
- Does the domain look legitimate?
- Are there suspicious parameters?
- Is it an unexpected file download?
- Does the URL match what you expected?
Scenario 4: Mobile Redirect Testing
Goal: Test mobile-specific redirects
Steps:
- Enter your URLs
- Select iPhone/Safari iOS or Android
- Check results
- Compare with desktop results
What to look for:
- Different redirect paths for mobile
- Mobile-optimized final URLs
- App store redirects (if applicable)
Scenario 5: SEO Redirect Audit
Goal: Audit site redirects for SEO best practices
Steps:
- Check critical pages with Googlebot
- Verify 301 status codes
- Check redirect chains (should be minimal)
- Measure response times
SEO best practices:
- Use 301 for permanent moves
- Minimize redirect chains (< 2 hops)
- Avoid redirect loops
- Keep response times fast (< 1s)
Best Practices
✅ Do’s
- Use appropriate User-Agents for your testing needs
- Check in batches to save time
- Export results for record keeping
- Verify regularly during site changes
- Test with multiple User-Agents for comprehensive coverage
- Document your findings for future reference
❌ Don’ts
- Don’t exceed 10 URLs per batch
- Don’t check private URLs requiring authentication
- Don’t abuse the service with excessive requests
- Don’t ignore redirect chains (optimize them)
- Don’t use 302 when 301 is appropriate
- Don’t trust shortened URLs without checking
Pro Tips
đź’ˇ Tip 1: Bookmark frequently used User-Agents Create a note with your most-used combinations.
đź’ˇ Tip 2: Save export files Keep JSON exports for comparison over time.
đź’ˇ Tip 3: Check before and after Test redirects both before and after site changes.
đź’ˇ Tip 4: Use CSV for reporting Export to CSV for easy client reports in Excel/Google Sheets.
đź’ˇ Tip 5: Monitor key pages regularly Set calendar reminders to check critical redirects monthly.
Troubleshooting
Issue: “Invalid URL format”
Cause: URL doesn’t start with http:// or https://
Solution:
❌ example.com
âś… https://example.com
Issue: “Limit: 10 URLs”
Cause: More than 10 URLs entered
Solution: Split into multiple batches of 10
Issue: “Request timeout”
Cause: Target server too slow or unresponsive
Solutions:
- Try again later
- Check if the URL is accessible in browser
- Verify server is online
Issue: Status 0 (No Response)
Cause: Server completely unreachable
Possible reasons:
- Server is down
- Domain doesn’t exist
- Firewall blocking request
Issue: Too many redirects
Cause: Redirect loop detected
What it means: Site configuration error causing infinite redirects
Action: Notify the website owner
Issue: Different results for different User-Agents
Cause: Website serves different content based on User-Agent
This is normal if:
- Mobile users get redirected to mobile site
- Bots get served different content
- Regional redirects are in place
Understanding Redirect Types
301 vs 302: Which to Use?
| Feature | 301 Permanent | 302 Temporary | 
|---|---|---|
| SEO Value | ✅ Transfers | ❌ Doesn’t transfer | 
| Use Case | Site migration | A/B testing | 
| Cache | Long-term | Short-term | 
| When | Content moved forever | Content temporarily moved | 
Meta Refresh
What it is: HTML-based redirect (not HTTP-level)
Detection: LinkGoWhere detects and flags meta refreshes
SEO impact: Generally less preferred than HTTP redirects
When used: Often in older websites or special cases
Advanced Insights
Interpreting Redirect Chains
Ideal: Direct redirect (1 hop)
example.com → newsite.com
Acceptable: 2 hops
example.com → www.example.com → newsite.com
Problematic: 3+ hops
example.com → www.example.com → subdomain.example.com → newsite.com
Why fewer hops matter:
- Faster page load
- Better SEO
- Improved user experience
- Lower server load
Tracking Parameters
Common tracking parameters you’ll see:
- utm_source,- utm_medium,- utm_campaign(Google Analytics)
- fbclid(Facebook)
- gclid(Google Ads)
- ref,- referrer(Generic tracking)
These are normal and expected in marketing links.
Integration Ideas
For Developers
Use cases:
- CI/CD validation of redirects after deployment
- Automated testing of affiliate links
- Monitoring redirect health
- API endpoint testing
Export formats make integration easy:
- JSON for programmatic access
- CSV for database imports
For SEO Professionals
Workflow integration:
- Pre-migration redirect testing
- Post-migration validation
- Competitor redirect analysis
- Client reporting
For Marketers
Campaign management:
- Validate tracking links before launch
- Monitor affiliate program redirects
- Check landing page accessibility
- Verify A/B test redirects
Frequently Asked Questions
Can I check password-protected URLs?
No, LinkGoWhere can only check publicly accessible URLs.
Are my URLs stored?
No, we don’t store any URLs you check. Everything is processed in real-time only.
Can I check more than 10 URLs?
Not in a single batch, but you can run multiple batches sequentially.
How long are results cached?
Results are not cached. Each check is performed in real-time.
Can I automate checks?
Currently, LinkGoWhere is designed for manual use through the web interface.
Do you offer an API?
Not currently, but it’s on our roadmap. Contact us if you’re interested.
Getting Help
Still need help?
- đź“§ Email: [email protected]
- 🏠Home: LinkGoWhere.com
- âť“ FAQ: Frequently Asked Questions
- đź“– Docs: HTTP Status Codes
Report Issues
Found a bug or have a suggestion? Email us with:
- What you were trying to do
- What happened vs. what you expected
- Browser and device information
- Screenshots (if applicable)
Next Steps
Ready to start checking links?
- 🏠Go to Homepage to start checking
- đź”§ View Tools for more helpful resources
- 📚 Read About LinkGoWhere
Happy link checking! 🚀