Setting Up Redirects and Custom Headers Together for a Domain Migration
Redirects and custom headers are both configured from the same settings screen, built to work together when you're moving an existing domain onto Piskes.
Moving an existing domain onto Piskes usually means two jobs at once: making sure old URLs still resolve, and carrying over whatever header-level configuration the old setup depended on. Both are handled directly in Piskes Website Builder now, and they're designed to work together for exactly this situation.
Redirects
From Site Settings → Redirects, map an old path to wherever it should go now — the classic 301 use case when URL structure changes as part of a migration. A redirect can't point a path at itself; that's rejected outright, since a self-referencing rule just produces a browser-visible redirect loop with no indication of which rule caused it. Adding a redirect for a path that already has one simply updates where it points, so you can adjust a mapping without deleting and recreating it.
Custom headers
From the same area of settings, header rules let you set things like cache-control on specific paths — useful during a migration when you want new content to behave differently than it did on the old domain while DNS and caches catch up. Rules are exact-path matches, and a small denylist (security headers the render pipeline depends on) is enforced no matter what you set, so a header rule can adjust caching or CORS-adjacent behavior without being able to weaken how the page runs.
Putting them together
For a typical domain migration: set redirects for any URLs that changed shape, then set cache-control headers on the paths where you want fresher content to propagate faster than the default caching would allow. Both are configured from the same settings screen, so there's no context-switching between two separate tools mid-migration.