Projects and Sites Guide
The structure layer that keeps routing, ownership, and destinations readable as your account grows.
Use This Layer to Create Boundaries
Domains alone are not enough once multiple brands, offers, or teams share the same account. Projects and sites are how 301.st helps you avoid one giant flat surface with no operational boundaries.
The goal is not complexity for its own sake. It is clarity: who owns what, which destinations belong together, and where routing logic should live.
Projects
- Create logical workspaces for brands, traffic programs, offers, or teams.
- Keep related domains and work grouped together without forcing every asset into the same pool.
- Make ownership and review easier once multiple people are involved.
Sites
- Attach destinations or site-level context to the project that owns them.
- Keep downstream routing easier to reason about.
- Provide clearer structure for site-scoped workflows, including newer routing surfaces.
A Practical Modeling Approach
- Start from a synced and trusted domains layer.
- Create projects around business or operational boundaries, not around arbitrary micro-grouping.
- Add sites where explicit destination structure will make routing easier to maintain.
- Only then apply redirect workflows inside a model your team can still understand six months later.
When Small Setups Can Stay Simple
Not every account needs deep structure immediately. If the operation is still small, it is fine to keep the model light and add more explicit boundaries only when they start reducing confusion.
The signal to add more structure is usually operational pain: too many domains in one place, unclear ownership, or redirect logic that stops being obvious.
FAQ
Do I need a project for every domain?
No. Projects should reflect real operational groups, not one-domain-per-project fragmentation.
Should I create sites before redirects?
Only when explicit destination structure helps. Sites are valuable when they make routing easier to understand, not when they add ceremony.
Can I skip this layer?
Sometimes for small setups. As operations grow, skipping structure usually makes everything harder later.