How pages are written
Pages are built from structured project records, calculator assumptions, public-source research, and clear buyer questions. Public copy should read naturally for real people, not like an exposed keyword sheet.
- A single useful page may answer several related commercial searches when the visitor intent overlaps.
- Content should explain tradeoffs, risks, limits, and next actions in plain language.
- Internal labels such as primary keyword, target keyword, or evidence variable should never appear in public copy.
Sources and freshness
Cost, construction, directory, and market claims should be tied to source records or clearly labeled as modeled assumptions.
- Source records store source name, URL where available, source type, date checked, claims used, and limitations.
- Cost and model assumptions should be reviewed more often than evergreen explanatory pages.
- Vendor or public-source directory information is not treated as verification unless a documented review method supports that label.
Corrections
Visitors, vendors, and builders can request corrections through the contact page. The correction request should identify the page, the claim, and the source or evidence supporting the change.
- Obvious factual errors should be corrected as soon as practical after review.
- Material updates should preserve conservative labels and limits instead of turning vendor claims into endorsements.
- Private lead, vendor, and admin records are not published as proof or source material.
Commercial boundaries
The site may monetize through qualified leads, sponsorships, reports, or future partnerships, but commercial relationships must stay labeled and should not change editorial claims silently.
- Sponsored placement does not mean verified quality.
- Calculator outputs are planning estimates, not quotes, guarantees, engineering opinions, financial advice, or legal advice.
- No fake testimonials, fake field inspections, fake lab tests, fake expert reviews, or invented project outcomes are allowed.
AI and answer use
AI discovery files and read-only agent APIs should promote pages that are useful enough to cite: concrete, dated, sourced, transparent, and limited.
- Do not promote a page to AI-facing discovery only because it targets a keyword.
- Answer-eligible pages need responsible operator visibility, source dates, schema, useful tables or tools, and clear limits.
- Agents must not submit personal data, route leads, contact vendors, or imply builder verification without explicit consent and implemented workflow support.