Architecture

Product pages and app subdomains: give each destination a clear job

Why the Neo ecosystem keeps product explanations on neoweb.ai and working experiences on their own subdomains.

By NeoWeb editorial2 min read
A blue architectural hallway branching into four separate doorways.

Explain before asking for an account

A public product page should establish what the product does, who it helps, how it works and what a visitor needs to know before using it. A working application should make the actual task accessible once the necessary account or purchase steps are complete.

For Neo, those destinations are connected but have different jobs. The public product page introduces the offering; the application is where the work happens.

Give every product a permanent address

The builder is introduced at /web/, Presence at /presence/, Pay at /pay/ and Domains at /domains/. Product applications use editor.neoweb.ai, presence.neoweb.ai, pay.neoweb.ai and domain.neoweb.ai.

Consistent navigation helps visitors understand these relationships. Descriptive link labels distinguish learning about a product from opening it.

Keep public catalogs public

A store has useful pages beyond its brand introduction. Destination and plan pages belong in NeoPay’s public storefront when they contain current offers. Private orders and installation credentials belong behind the appropriate access controls.

The same principle applies elsewhere: public explanations are discoverable; customer projects and reports stay private.

Choose structure for the work it supports

Google says it has no indexing or ranking preference between subdirectories and subdomains. Organization, maintainability and clear linking are better reasons to choose a structure than an assumed automatic ranking advantage.

When existing pages move, map the old URLs to the relevant new destinations, update internal links and keep permanent redirects. Monitor the transition because changing the homepage’s topic can affect which searches it matches.

A future unified workspace can live at /app/ while product pages retain their public addresses. That lets the platform evolve without repeatedly moving the information customers and search engines already use.

Sources & further reading

Primary sources used for the specific guidance in this article. Product instructions and the actual offer take precedence for your transaction.

Your next step

Explore the product that fits the task in front of you.

Explore the ecosystem