# Separate subdivision launch facts from changing lot status

SEO for a new subdivision starts with one permanent page for the place, built before the first lot release. Keep the lasting facts (location, your role, lot character, design review) in one section and the changing ones (release groups, [spec homes](/glossary/spec-home/), events) in another with a named owner. Link to plan pages instead of pasting plan descriptions under every lot.

## Which subdivision facts are ready before lot releases?

Publish what is approved for public use and helps a buyer judge fit: the location, your role, general lot context, the plan approach, the design review process and how you will announce updates. Do not fill gaps with guesses about release dates, amenities or plan availability.

The early page becomes the permanent source for your work in that place. Event announcements, map profiles, agent materials and later spec home pages all point to it. A stable URL matters because the sales phase changes faster than the subdivision does. The [search and answer engine articles](/articles/search-and-answer-engines/) connect this page to the related search work.

### Separate durable facts from changing status

| Content layer | Examples | Review trigger |
| --- | --- | --- |
| Durable place context | Location, access pattern and general lot character | Approved plan or development changes |
| Builder fit | Plan approach, lot fit and build process | Product or operating change |
| Design review | Submission path and buyer expectations | Current guidance changes |
| Lot pipeline | Release group and builder assignment | Every confirmed status change |
| Spec inventory | House, plan and construction stage | Field or sales update |
| Events | Preview, open house or Parade details | Before and after each event |

Keep the changing sections easy to find and edit. Do not rewrite the page every time a lot moves through the pipeline.

## Which launch fields need a source and update owner?

Answer the questions that decide whether someone keeps reading: what you are offering, which plans or design paths fit, how lots are evaluated, what review steps apply and where current availability is confirmed. Say when an image shows this subdivision and when it shows a representative project elsewhere.

Skip the lifestyle paragraph that could describe any development. Explain the building context a principal, an architect or a superintendent would recognize: lot orientation, streetscape goals, plan width, garage treatment, review sequencing. Approved facts only.

### Collect subdivision source material in order

1. Confirm the builder's role and approved public description.

2. Collect the recorded or issued materials the builder is allowed to publish.

3. Review lots against the current plan library and design direction.

4. Document the inquiry and plan-review path, and the listing agent's contact when lots are listed.

5. Identify who owns lot, inventory and event updates.

6. Prepare internal links before the public launch begins.

7. Schedule a field review when construction conditions become visible.

The page does not replace a buyer's due diligence or a project-specific review. It tells the buyer what you can explain next.

## How should plans, lots and spec homes connect?

The subdivision page is the place hub. Each plan has a permanent page for layout, structural options and general lot fit. Each [spec home](/glossary/spec-home/) has its own status page. The subdivision page connects them and explains why those plans or houses belong on this ground.

Do not paste the same plan description under every lot. Summarize the fit and link to the plan page. When a spec finishes or goes under contract, update its status and keep its link to the subdivision.

### Build an internal-link path around decisions

- Subdivision to plan: understand the layout and option framework.

- Subdivision to spec home: see current construction and selections.

- Plan to subdivision: understand where the plan is being considered.

- Spec home to plan: compare this house with the reusable base plan.

- All three to process: understand lot review, selections and warranty expectations.

The [internal linking article](/articles/search-and-answer-engines/internal-linking-for-builder-sites/) shows how these page roles support each other. The [spec home SEO article](/articles/search-and-answer-engines/seo-for-spec-homes/) covers status pages from planning through completion.

## How does local search support a subdivision launch?

Use the same place language on the owned site, the map profiles, event listings and partner references. State the location in the terms buyers and agents use, and stay exact about your service and role. Do not build several near-identical location pages for one development.

Event and Parade pages link to the permanent subdivision or house page. After the event, remove the expired access details and keep the project information. Give partner pages the exact destination so they do not guess between a campaign page and the homepage.

### Write local detail that survives the launch

The [community page article](/articles/search-and-answer-engines/writing-community-pages/) shows how to write about lot patterns, review context and build fit without dropping place names into a template. It also helps the subdivision page support the local profile and citation work.

Check amenity and access descriptions against the current development documents. Do not state school assignments. Link to the district's assignment lookup. Check design review with the architectural reviewer and permit requirements with the county or town permitting office. Leave unconfirmed claims off the launch page.

## Who keeps subdivision content current?

Give each data type a source. Sales owns availability. Construction owns field stage. Design owns current plan and exterior references. The website editor never settles conflicting reports by guessing; the conflict goes back to the responsible person first.

The [Semantic content stage](/process/semantic-content/) sets the page relationships and the review queue. The [custom builder website pages guide](/guides/custom-builder-website-pages/) places the subdivision page beside plans, projects, process and contact paths.

### Use agents for checking, not authority

Our agents compare lot labels, trace internal links, draft updates and flag conflicting status language. People set the public facts and review every output. An agent notices that two pages disagree about a plan. It cannot decide which field report controls.

Keep a change log for release groups, spec homes, plan assignments, images and events. Use it to find which owned pages and follow-up materials need the same status correction.

## Questions about SEO for new subdivisions

### Should the subdivision page launch before inventory?

A subdivision page can precede inventory when approved place, builder-fit and process information exists. Separate confirmed facts from future updates and unconfirmed release details.

### Does every lot need its own page?

A lot needs a separate page when it has a distinct house, status or buyer task worth maintaining. A maintained lot table can cover early pipeline information.

### Can several builders share the same subdivision page?

A builder’s subdivision page should describe its own role and work. Use official shared resources where useful without implying control over other builders or the development.

### What happens after the subdivision sells through?

After subdivision sell-through, remove stale availability and event details. Keep approved project, plan and place information when it still serves readers.