Put a directory at company.com/resources without an iframe
Keep the domain, navigation context, authority, and website stack you already have. Directoryz only handles requests inside the directory path.
How the route works
Choose a hostname and base path. Directoryz installs a scoped Worker through Cloudflare OAuth or generates Worker source and a route pattern for manual installation.
What stays untouched
Requests outside the selected path continue to the existing origin. A /resources deployment does not take over /, /blog, /pricing, or any unrelated application route.
How public pages render
Directory, search, category, listing, submission, robots, and sitemap requests under the path are served through the Directoryz API with canonical links using the customer URL.
Operational safeguards
Directoryz validates the hostname, base path, Cloudflare zone, route ownership, and a deployment verification token before marking a path live.
Frequently asked questions
Must the domain use Cloudflare?
Automatic OAuth installation requires a Cloudflare-managed zone. The generated manual Worker option also runs on Cloudflare Workers.
Can I use the root domain instead of a path?
Yes. Directoryz supports a full hostname, a subdomain, or a nested path.
Will the path show Directoryz in the URL?
No. Visitors remain on the configured customer hostname and path.