Semantec SEO · Evidence standard
Claims Policy
Statements about Semantec SEO, its services, project fees, comparisons and outcomes must have evidence for the wording used. An intention, illustration or confident sentence is not proof.
This policy sets the standard for claims in website copy, proposals, examples, media and structured data. Keep the source, scope, date and qualifications beside the claim so a reader can understand what the evidence supports.
Define the claim and its scope
Record the exact statement, who or what it concerns, its date, audience and relevant limits. A headline, price label, comparison, image caption or missing qualification can imply a claim even when the surrounding prose is cautious.
Evidence for one project, service, market, period or device does not establish a universal result. Keep project scope, fee conditions and other material limits visible before a reader decides what to do.
Use evidence suited to the claim
Agency and service facts need the relevant business record or agreed project document. Claims about an external platform need current official documentation. Legal or regulatory statements need authoritative sources and suitable specialist input where required.
A performance statement needs its method, data, period, responsible party and limitations. A client statement needs permission, exact wording and context. A provider’s certification cannot be presented as certification of Semantec SEO.
Keep qualifications visible
Place limits close to the claim they qualify. A fee statement needs its scope, currency, tax treatment and relevant payment conditions. A comparison needs a fair basis, current sources and consistent units, dates and criteria.
Do not remove a qualification from a quotation, crop it out of an image or leave it behind a misleading summary. A reader should not need to discover a hidden condition after acting on the main statement.
Do not present unsupported claims as facts
Do not invent clients, reviews, citations, awards, qualifications, certifications or results. Do not turn a plan, draft configuration or provider statement into a claim that the agency has completed the work or holds the assurance.
A single example does not prove a general outcome, and correlation does not establish causation. Client names, project details and results require appropriate permission and confidentiality checks. Structured data must support the same claims as the visible page.
Decide before publication
Publish a claim only when its source supports the exact wording, scope and date. Use a visible qualification when the evidence supports a narrower statement. Hold a claim when evidence is missing, stale or disputed.
Remove or reject a claim that is false, misleading, unlawful or outside the agreed page purpose. Identify the person responsible for confirming business or specialist facts. An attractive layout or a tool’s suggestion does not replace that decision.
Review changes and correct errors
Review claims when a source, project offer, fee, service, law or platform rule changes. A cosmetic website update does not refresh the evidence date. Check the pages, proposals and other material that depend on a changed statement.
Report a concern to privacy@semantecseo.com with the URL, disputed wording and supporting source. Project questions go to support@semantecseo.com. A claim that could mislead readers needs correction, qualification or removal while the issue is resolved.
