# Stop builder pages from competing with their own copies

Duplicate content on a builder site is the same plan description living on the plan page, three community pages, a spec home page and a campaign landing page. Group the URLs that repeat an answer. Keep one page per reader task. Move the unique lot or project detail onto the surviving page. Check who links to each copy first.

## Where does duplicate builder content come from?

It starts when one description gets reused across page families. A plan is offered in several communities. A spec home inherits the plan description. A campaign adds a landing page. A redesign keeps the old path and publishes a new one. Soon the same copy sits under plan, community, inventory and project URLs.

A repeated sentence, like a standard warranty statement, is not the problem. Several pages with no difference in job is the problem. A buyer lands on one copy and cannot tell whether the house is for sale, finished, configurable or an example.

### Separate shared facts from page purpose

| Page type | Primary purpose | Detail that makes it distinct |
| --- | --- | --- |
| Plan page | Explain layout fit and options | Plan set, structural choices and lot constraints |
| Community page | Explain building in one place | Lot context, review process and available plan fit |
| Spec-home page | Explain one house and its status | Selections, construction stage and inquiry path |
| Project page | Document a completed build | Site response, design decisions and approved photography |
| Process page | Explain how the builder works | Responsibilities, documents and decision points |

A shared base plan connects these pages. It should not turn them into copies. Each page answers a reader question the others do not. The [search and answer engine articles](/articles/search-and-answer-engines/) show how the distinct pages fit the content system.

## How do you choose the permanent page?

Choose the URL that carries the lasting subject. A plan page outlives individual [spec homes](/glossary/spec-home/). A community guide outlives one lot release. A completed project page stays after the inventory page stops answering “is it available.”

Check visits, links and references before you change a URL. A printed brochure, a map profile, an event listing or an agent handout may point at the current page. The permanent choice accounts for those paths, not only the new menu.

### Use a page-decision sequence

1. Inventory every URL covering the subject.

2. Label each page by plan, place, status, project or process purpose.

3. Select the version with the clearest lasting role and strongest source material.

4. Move unique, accurate details into the appropriate surviving page.

5. Redirect retired URLs when a close replacement exists.

6. Update internal links, sitemap entries and campaign destinations.

7. Inspect the live result on mobile and desktop.

Do not merge pages to lower the count. A [spec home](/glossary/spec-home/) and the plan it was built from deserve separate pages because they answer different questions.

## When should similar pages remain separate?

Keep pages separate when the buyer decision changes by place, product or status. The same plan on a wooded homesite and on an [infill lot](/glossary/infill-lot/) carries different orientation, access, grading and garage constraints. Those facts go on the project or place page. The layout stays on the plan page.

Community pages need more than a swapped town name. The [community page article](/articles/search-and-answer-engines/writing-community-pages/) covers lot patterns, design review, build fit and current status without cloning a service-area paragraph.

### Use links instead of repeated blocks

If the process explanation exists, summarize the relevant part and link to the full page. A spec home page says which selections are complete and links to your selections process. A community page names the plans that fit and links to each one instead of pasting every description.

The [internal linking article](/articles/search-and-answer-engines/internal-linking-for-builder-sites/) shows how those links carry readers between plans, places, projects and process pages.

## How should inventory and sold homes be handled?

Inventory pages change faster than anything else on the site. As a spec moves from planned to under construction to complete, the page states the current condition and keeps the useful history. When it sells, decide whether the page becomes a completed project record or points to the plan and current opportunities.

Do not leave an expired inquiry prompt beside current availability language. Do not redirect every sold home to the homepage. Send the visitor to the closest useful page and state the status there.

### Keep status separate from reusable knowledge

- Store plan facts on the permanent plan page.

- Store current construction and availability on the spec-home page.

- Store location context on the community page.

- Store completed design decisions on the project page.

- Store sales and construction expectations on process pages.

This structure supports the [spec home marketing guide](/guides/spec-home-marketing/) and stops each new listing from becoming another full copy.

## How can a builder prevent duplication from returning?

Prevention lives in the publishing workflow. Templates label which fields are shared facts and which need page-specific material. Editors search the site before they create a URL. Content owners know where plan descriptions, specs, community facts and status updates come from.

The [Owned website stage](/process/owned-website/) sets that page structure and keeps publishing in your accounts. Our agents compare page bodies, group similar URLs, trace internal links and draft consolidation notes. People decide what stays public and review every redirect, status statement and field detail.

### Audit by page family, not random samples

Review all plan pages together, then all communities, then inventory, then projects. Shared templates make repeated blocks obvious. Compare titles, opening answers, headings and destination links. Record keep, revise or retire for each URL, with its destination and source owner.

The [Search Console article](/articles/search-and-answer-engines/search-console-for-builders/) shows competing URLs after publication. The page model should fix the root cause before the next content wave.

## Questions about duplicate builder pages

### Is repeated warranty language duplicate content?

Shared warranty wording can support related pages when it is accurate and approved. Keep one complete resource and link concise summaries to it.

### Should sold spec-home pages be deleted?

A sold spec-home page may become a completed project or direct readers to its underlying plan. Decide from lasting value, existing references and privacy requirements.

### Can the same plan appear in several communities?

Keep reusable plan details on the permanent plan page. Explain each community’s lot context, plan fit and status separately instead of copying the full description.

### Will changing a few words fix copied pages?

Cosmetic rewrites do not resolve duplicated page purpose. Give each builder URL a distinct reader task and source set before deciding which wording to retain.