Pages only accessible in panel

Hello. This go around I was considering creating pages for global sections of content (e.g. footer, closing call to action, etc.). What would be the approach. I was just going to create pages, keep them as unlisted, but what if someone happens to navigate to one of these pages (e.g. I guess I can create a 301 redirect in routes. Maybe returning a 404 would be better. Is that possible with a route?

Yep, pages you don’t want to be accessible you can hide with a 404 in a route. You don’t need a different route for each page, but can pass an array of ids or reroute based on some sort of condition (page status, intendedTemplate etc.)

Excellent. Thanks @texnixe