A community or lot page says exactly what you are doing in that place: a lot you control, a house under way, past work, owner-held lots you will review, or a service area you cover. It names the site conditions that shape a build there and gives the buyer one next step. It never dresses coverage up as inventory.
What must a community page tell a serious buyer?
A community page helps a buyer decide whether the place, the lot and your company belong in one conversation. A neighborhood description does not do that. The page has to say what you do there, which project path applies and what gets reviewed before anyone talks plans.
Start with your relationship to the place. You may control a lot, have a house under construction, have finished work there, review owner-held lots or serve the surrounding area. Each needs different words. “Communities we build in” covers all five and hides the one fact the buyer needs.
Use a status the office can defend
| Public status | What it means | What the page should request |
|---|---|---|
| Builder-controlled opportunity | The builder can confirm the current lot position | Buyer goals, plan interests and readiness |
| Active project area | Work is underway, but that does not imply another lot is available | Lot address or desired location |
| Owner-held lot review | The builder will examine a parcel before confirming fit | Parcel record, survey and known site material |
| Completed work | The location is evidence of experience, not current inventory | Project type and intended area |
| General service area | The builder may consider work in the broader place | Lot status, scope and intended start path |
The status must match the lot pipeline, the sales notes and the project records. If the office cannot name the source behind the label, the page is not ready.
Which lot conditions belong on the page?
Public lot content frames due diligence without pretending to finish it. A buyer needs to understand why a plan that fits one parcel fails on the next. Name the categories you review, then keep the actual findings with the parcel and its current documents.
For each public condition, record the source, the reviewer and whether it is still open. Check zoning, setbacks and permit questions with the town or county planning office. Check recorded easements with the title attorney and utility questions with the provider. Publish only findings approved for that parcel.
Connect constraints to builder decisions
Say what each condition changes. Lot width moves plan orientation and garage placement. Grade changes the foundation, the driveway approach and drainage. Architectural review changes elevation materials and submission order. Utilities change which questions get answered before a working scope exists. An infill lot adds neighbor, access and demolition questions on top.
The plan library page article presents a design as a starting point, not a promise that it fits every parcel. For land-specific content, use the infill lot marketing guide.
How should lots, plans and projects connect?
A buyer may arrive through a place name, a plan image or a finished kitchen. Let that buyer move between all three without implying every combination is for sale. Community pages give context, plan pages explain design intent, project pages show what got built.
- Link the place to suitable starting points. Show plans the builder would reasonably discuss there, with a clear parcel-review condition.
- Link completed work back to context. Identify the general location and site challenge without exposing a private address.
- Label every project state. Separate available, under construction, completed example and privately owned work.
- Explain modifications. Note when a photographed home differs from the base plan or standard specification.
- Route the inquiry correctly. Ask whether the buyer owns a lot, is considering one or needs a builder-controlled opportunity.
Carry the same lot-status label onto the linked plan and project cards, then test what the inquiry record shows. This sits inside the Owned website stage, where you control the pages, forms and records.
What information should the lot inquiry collect?
The form collects enough to route the inquiry. It is not a feasibility review. Ask for the location or parcel number, ownership status, any survey or site documents, plan status, intended use and preferred contact method. Give the buyer an honest “still looking” option.
Do not ask a prospect to interpret records you need to read yourself. A buyer may not know whether a recorded easement touches the building area or whether an old soils report still counts. Let the form take the document and the question. The team decides what review comes next.
Preserve the source and status
When the inquiry lands in your CRM, keep the page, the lot status and the plan that produced it. A message from a controlled-lot page needs different handling from a general service-area question. The confirmation restates what was sent and names the next review step. It promises neither feasibility nor a start date.
How do you keep changing lot pages honest?
Lot facts change faster than any other copy on the site. Give each page a source record and a review owner. The record shows public status, internal reference, supporting source, last review and next action. When the status changes, update the linked plan cards, project cards and forms in the same pass.
Build the publishing routine on events the team already tracks: acquisition, reservation, contract, start, sale, release, completion, or the decision to leave an area. Parade weekends get their own review, because signs, printed material and web pages all point at the same inventory that week.
Our agents compare page labels with an approved inventory export, flag broken links and draft updates. People decide which record governs and review every public change. No agent infers availability from an old page, a photo or a permit mention.
Give the place pages a controlled home
The other builder websites articles cover the pages that support this system. Pair place pages with accurate project gallery pages so buyers see the work without mistaking completed examples for open inventory.
Questions about community and lot pages
Should every town in our service area have a page?
Publish a builder town page when you can explain a real service relationship, relevant project context and a useful next step. Assign a source and review owner.
Can we show a lot before every review is complete?
A builder lot page can describe verified current status and open questions. Keep buildability, plan fit and availability marked as unresolved while the relevant review remains incomplete.
Should completed homes appear on community pages?
Completed homes can appear on builder community pages as approved, labeled examples. Identify project-specific modifications so visitors do not mistake past selections for current standard inclusions.
Who should approve lot-page changes?
The role responsible for your lot pipeline should approve lot-page status changes. Your website publisher then verifies related plans, projects, forms and public status labels.