Some URL paths in a Scroll site are reserved for built-in features and internal assets. This article lists those paths, explains what happens when your content or redirects use them, and shows you how to resolve a conflict.
If a page, redirect, or link uses a reserved path, you may see an unavailable page, broken navigation, a built-in system page instead of your content, or missing site assets.
Which Paths Are Reserved
Scroll Sites reserves the following paths at the root of your site. Avoid them when you choose a path for your own content, and make sure your redirects neither target nor capture them.
|
Reserved path |
Used for |
What to avoid |
|---|---|---|
|
|
Help desk integration pages |
Assigning this path to your own page, or using it as a redirect destination |
|
|
Built-in site search |
Creating content or redirects that replace the search page |
|
|
The releases or changelog page |
Reusing this path for unrelated content |
|
|
Internal theme assets and system resources |
Creating redirects or rules that override or capture this prefix |
The /__ entry is a prefix, not a single page. Scroll Sites treats every URL that begins with /__ as an internal resource.
Why Reserved Paths Matter
Reserved paths are part of how Scroll Sites delivers core functionality. The app claims them before it resolves your content, so treat them as protected system routes.
This has four practical consequences:
-
A page published at a reserved path may never load for visitors.
-
A redirect that points to a reserved path may not work as intended.
-
A link to custom content under a reserved path may send visitors to a built-in feature or an unavailable page.
-
A redirect rule that captures the
/__prefix can stop internal assets from loading and break parts of your site.
You can't release a reserved path for custom use. These paths stay protected because Scroll Sites relies on them.
Symptoms of a Reserved Path Conflict
Compare your paths against the table above if visitors report any of the following:
-
A published page returns an unavailable or not-found page.
-
A redirect sends visitors somewhere unexpected, or does nothing at all.
-
Navigation, styling, or images break after a redirect change.
-
A built-in page such as search appears where your own content should be.
How to Fix a Reserved Path Conflict
Move your content to a path that isn't reserved:
-
Choose a new URL path for the affected page or redirect destination.
-
Update any links that point to the reserved path.
-
Update your redirect rules so they point to the new path.
-
Update your site, then test the new URL in your browser.
Descriptive alternatives work well, as long as your site doesn't already use them:
-
Use
/helpor/customer-supportinstead of/support. -
Use
/release-notesinstead of/releases. -
Use
/findinstead of/search, or leave the built-in search page on/search.
Guidance for Redirects
Reserved paths need particular attention when you configure redirects, because one broad rule can affect many URLs at once.
When you create simple or advanced redirects:
-
Don't use a reserved path as the destination for your own content.
-
Don't write patterns broad enough to capture
/__URLs. -
Put your most specific rules first, because the first matching rule fires.
-
Review your existing rules if system pages or site assets stop working after a redirect change.
This matters most for advanced RegEx redirects. A broad pattern such as /(.*) captures every path on your site, including protected ones. Anchor your patterns to the paths you actually want to redirect.
Frequently Asked Questions
Can I use a reserved path if I am not using that feature?
No. Reserved paths remain protected because they are used by Scroll Sites internally or by built-in functionality.
Why does a page under a reserved path not open correctly?
Because Scroll Sites intercepts that path for a system feature or internal asset handling, your content may not be reached as expected.
What should I do if an old redirect points to a reserved path?
Change the destination to a different, non-reserved path and update any related links or references so visitors reach the correct page.