The Owned website stage turns your Operating profile and Positioning into the site a buyer studies between the model visit and the first call. AgAI Labs builds pages for process, plans, specs, projects, communities, warranty, cost factors and common questions. You keep the domain, hosting, analytics, source files and inquiry paths in your accounts.
| Asset | A. Rented | B. Owned |
|---|---|---|
| Domain | Platform URL | Your domain |
| Hosting | Their account | Your account |
| Analytics | Their dashboard | Your property |
| Leads | Portal inbox | Your CRM |
| Content | Limited export | Your files |
| Profile | Their login | Your login |
What should a custom builder website do?
Answer the questions between the visit and the call
Buyers want to know whether you will build on their lot, how plans change, when selections lock, what the allowances cover, how draws work and who picks up the phone on a warranty call. A gallery cannot carry that load. The site is built around the approved profile and positioning, and the page set usually covers these jobs:
| Page group | Buyer question answered |
|---|---|
| Process | What happens from lot review through warranty? |
| Plans and specifications | What is fixed, adaptable, included or selected? |
| Projects | What was built, where, under what constraints and with which decisions? |
| Communities | Where do you work and what kind of lot belongs there? |
| Cost guide and FAQ | Which variables move scope, allowances and feasibility? |
| Warranty | How are punch and warranty items submitted and handled? |
Structured data describes the published content to search engines. Check the supported markup and eligibility rules in the search platform's current documentation before adding it, and review the visible copy and the markup together.
Why do you need to own the accounts?
Business assets stay under your control
The domain, hosting and analytics are business assets. They sit in accounts you control, with named access for approved partners. Forms route to destinations you own. Measurement history stays with you if a marketing relationship ends.
Portal listings and social profiles still have a role, especially around Parade weekends and active inventory. They are rented distribution. The owned site is the stable reference those channels point back to, where plan context, process detail and inquiry data stay yours.
What makes the site ready to build?
Approved source material and accounts in your name
We need the approved profile and positioning, access through accounts you own, current brand assets and the best project files you have. Useful project inputs: photography, plan excerpts approved for publication, spec context, and short notes from the people who ran the job.
- You approve the page set, each page's purpose and the account ownership.
- Agents research, draft and check how the pages connect.
- A person reviews claims, field language, privacy and project context.
- Agents build and test the pages, forms, metadata and structured data.
- A person runs device, browser and inquiry-path checks before handoff.
The schedule follows the approved page set, account access and your review lane. Missing project context, slow approvals or a large plan library add dependencies that get cleared before publication. You keep the domain, hosting, analytics, source files and published content.
How does the site connect to the rest of the process?
Position first, then expand the answers
The site closes the Site engagement and is the base for everything in Growth. Compare owned assets with rented profiles in owned website versus portals, then read the technical and editorial side in the home builder search guide.
What else should you know about your Owned website?
Who owns the domain and hosting?
You do. Both stay in accounts your company controls.
Can we keep our current domain?
Yes, that is the starting preference. We inspect ownership, access and the existing setup before proposing any change.
Do we need every plan ready before launch?
No. Publish the approved, useful plan material first and add the rest through reviewed updates.
Will project pages be generic galleries?
No. Project pages explain the constraints, decisions and build context beside the photos. Private buyer information stays off the page.
Can another partner manage the site later?
Yes. You keep ownership, the source files and the runbook, so an approved replacement can take over after handoff.
Back to 02 Positioning for the message source, then on to 04 Semantic content to extend the answers. See the full stamp.