vercel-networking-domains_skill

Overview

This skill covers Vercel networking and routing for domains, DNS, redirects, rewrites, headers, CDN, edge cache, and regions. It helps you configure domain ownership, routing rules, caching behavior, and regional execution to optimize traffic delivery and control. It is intended for teams managing production routing and global performance on Vercel.

How this skill works

The skill inspects and guides configuration of Vercel domain settings and DNS records, and it helps you author routing rules such as redirects and rewrites. It also guides the application of custom headers, compression, and cache controls for the CDN and edge cache. Finally, it assists in selecting deployment regions and purge strategies to align execution and cache behavior with traffic patterns.

When to use it

• When adding or verifying domains and configuring DNS records
• When implementing redirects, rewrites, or custom request/response headers
• When tuning CDN and edge cache TTLs, cache keys, or purge policies
• When optimizing regional execution and selecting deployment regions
• When troubleshooting unexpected routing or cache behavior

Best practices

• Verify domain ownership and point authoritative DNS to Vercel for predictable routing
• Prefer rewrites for internal routing and redirects for observable URL changes (use proper status codes)
• Set explicit Cache-Control and Edge-Cache headers to avoid stale content and enable safe purges
• Use region selection for latency-sensitive functions and stateless edge logic; avoid coupling state to region-specific execution
• Test routing rules and header changes on a staging alias before promoting to production
• Document DNS changes and maintain rollback steps when modifying authoritative records or global redirects

Example use cases

• Add a new custom domain, create required DNS records, and verify ownership
• Create a set of redirects from legacy paths to new SEO-friendly URLs with 301 status codes
• Rewrite requests for clean internal routing while keeping public URLs unchanged
• Set Cache-Control and Edge-Cache headers to extend CDN TTLs and configure on-demand purge workflows
• Limit an edge function or deployment to specific regions to reduce cold-start latency for target users