Publish one owned answer with evidence, useful structure, honest limits, and a maintained route.

One page, one durable job

Every page must own a distinct user task and canonical query home. Closely related wording belongs inside the owner unless the intent, evidence burden, audience, lifecycle, or action genuinely changes.

A hub routes the category; a policy states the rule; a product page explains the offer; a practitioner page teaches or provides a method.

Stay inside source context

The page must reinforce Semantec SEO, MIRENA, semantic SEO, topical mapping, content briefs, drafting and rewriting, entities, information gain, internal links, answer formats, structured data, or the company, trust, legal, and governance layer required to operate the product.

Generic marketing, AI news, or unrelated business content is rejected unless it serves the same buyer, workflow, and entity system.

Lead with the answer or operative rule

An informational page should answer the query early. A product page should state what the product is and is not. A trust page should state the control and boundary. A legal page should present the operative document without promotional filler.

Use entities and terms consistently

Semantec SEO is the organisation, MIRENA is the product, Kevin Maguire is the founder, and OpenAI controls ChatGPT. Preferred labels, aliases, roles, dates, and relationships should match the canonical record.

Evidence and information gain

Material facts require current sources. The page should add a useful decision, model, example, source, limitation, comparison criterion, process, or route rather than repeating the same generic definition.

Information gain does not justify unsupported novelty.

Passage and component jobs

Each heading should answer a real sub-question. Tables compare stable dimensions; lists show bounded sets; timelines show sequence; FAQs resolve residual questions; visuals carry a model that text alone cannot show.

Do not add a tool, prompt, chart, or accordion merely to make a serious institutional page look interactive.

Language and voice

Use short, declarative, precise language. Prefer concrete verbs and named owners. Avoid hype, vague superlatives, fake certainty, boilerplate transitions, repeated sentence shapes, and claims that sound stronger than the source.

Legal and trust documents use calm, readable, consistent language rather than the promotional voice of a sales page.

Internal links and calls to action

Links should route to the owner of the next distinct question. Anchor text should set the correct expectation.

Institutional pages use contact, policy, support, correction, or related-document actions. Product CTAs belong on product and commercial pages, not inside operative legal clauses.

Accessibility and responsive parity

Headings, links, forms, tables, disclosures, focus, contrast, images, source order, mobile layouts, and print documents must preserve essential meaning and operation.

Do not hide evidence, limitations, clauses, or review controls on mobile.

Review, publication, and maintenance

Check facts, sources, claims, rights, legal fit, product state, links, accessibility, technical rendering, and approval before release.

Record the version, owner, review date, correction route, and trigger for future review. A live page remains subject to source changes, broken routes, product changes, policy changes, and user feedback.