Summary: BuildQuantities publishes a page when it solves a distinct user task, supports factual claims with appropriate evidence, states its limits, identifies review ownership truthfully, and passes the page-type quality gate.
Content purpose and eligibility
A new page starts with a specific audience, problem, and useful outcome. Calculator output variants, unit variants, material nicknames, and close keyword phrasings share one canonical page when the underlying task stays the same.
A separate page needs a different method, decision, dataset, workflow, or practical outcome. Publication requires that user-value distinction.
Research pack required before drafting
| Record | Required detail |
|---|---|
| Intent brief | Primary task, audience, market, close variants, result types, and overlap risk |
| Competitor review | Pages checked, 10-second understanding, trust signals, gaps, and one concrete improvement |
| Claim map | Claim, source, issuing body, scope, retrieval date, and geographic or material limitation |
| Calculation pack | Formula, variables, unit conversions, material states, rounding, fixtures, and invalid cases |
| Page brief | Title, description, H1, answer-first opening, section order, tables, links, schema, and publication state |
Source policy
Technical claims begin with the responsible primary source: government or issuing authority, official standard publisher, manufacturer documentation, supplier product data, project drawings, or project specifications. Secondary industry sources can supply context and user questions after the primary record is clear.
Competitor pages support intent and gap analysis. Their copy, unsourced numbers, density defaults, price ranges, experience claims, and conclusions are excluded from BuildQuantities evidence.
Google, Semrush, and Prompts99 roles
- Google Search Central sets the people-first, quality, spam, and generative-AI compliance boundary.
- Semrush informs intent analysis, page structure, readability, on-page review, and competitor questions. Verified metrics are recorded only when the selected database and export are available.
- Prompts99 supplies briefing and review questions. Factual and technical authority comes from the applicable source record.
Drafting standard
Sections open with a direct answer and then explain the reasoning, conditions, and next action. Paragraphs stay focused. Headings describe the real question or workflow. Tables appear when they make units, comparisons, decisions, or repeated fields easier to check.
Article length follows the task and evidence. Supporting blog articles normally reach the depth required by the approved brief; trust pages stay concise enough to use. Keyword use follows clarity and natural meaning.
Accuracy and writing rules
- Use real, traceable facts and label derived calculations.
- State the country, unit system, material state, product, date, or project scope when it changes the answer.
- Identify fictional examples and hypothetical inputs beside the example.
- Keep measured geometry, assumptions, supplier rounding, price, and professional decisions separate.
- Use direct language and remove filler, hype, fabricated quotations, invented experience, and formulaic AI transitions.
- Preserve uncertainty and “it depends” conditions when variables change the outcome.
Automation and generative AI
Software can help organize source records, compare page structures, calculate fixtures, draft text, scan writing patterns, and run QA. Each factual claim still needs evidence, each calculation needs tests, and each page needs truthful editorial and technical ownership before indexing.
Every page requires its own publication approval. The workflow finishes one page, records its evidence and checks, then moves to the next page.
Review roles and labels
| Role or state | Responsibility |
|---|---|
| Research or editorial owner | Intent, draft, source presentation, originality, clarity, metadata, and internal links |
| Calculation owner | Formula, variables, conversions, fixtures, edge cases, and rounding |
| Technical reviewer | Assigned technical scope, limitations, source fit, examples, and material-state handling |
| Technical reviewer pending | Development page stays outside the public index until a qualified named reviewer accepts the assigned scope |
| Development policy reviewed | Policy copy and implementation have passed the current editorial and rendered checks |
Page-type publication gates
- Calculator: working interface, formula disclosure, unit and invalid-input behavior, fixtures, sources, limitations, named technical review, and rendered QA.
- Blog article: distinct supporting intent, source pack, checked examples, useful internal route, honest byline and review state, and rendered QA.
- Chart: documented data provenance, units, derivation or update method, interpretation limits, and responsive table behavior.
- Category or directory: useful current children, accurate counts, clear scope, and direct crawlable links.
Metadata, schema, and internal links
Titles, descriptions, H1s, canonical URLs, breadcrumbs, and internal anchors describe the visible page. Structured data matches content a visitor can read. Each child links to its hub, and hubs link to every current child.
Commercial independence
Advertising, affiliate relationships, sponsorships, and lead generation receive visible disclosure when enabled. Formula, testing, technical, product-acceptance, and correction decisions remain editorially independent.
Updates and corrections
Material changes to facts, formulas, examples, sources, limitations, authorship, or review ownership trigger a new date and applicable review. Confirmed errors follow the corrections policy.