Every guide should answer one clear user question, separate general guidance from service claims, link official evidence near important statements and explain where the answer depends on the exact product or jurisdiction.
Which sources do we prioritise?
- Primary law and regulator material: government rules, official standards pages and recognised transport authorities.
- Official technical guidance: documents from organisations such as UNECE, OSHA, NIOSH, Health Canada and PHMSA.
- Product evidence: formulation records, supplier SDS files, specifications and relevant test reports supplied for the actual product.
- Secondary explanations: used for question discovery or context, not as a substitute for the primary source when one is available.
How are user questions selected?
Topics come from recurring buyer, exporter, courier and manufacturer questions; website search behaviour; competitor-page gaps; and search-result questions. A new page is created only when its decision purpose is different from an existing guide.
How do we avoid duplicate pages?
Product guides may use a consistent structure, but the hazard discussion, evidence, examples and decision points must match the specific formulation type. Pages should not be created by changing only a city or product name.
How are legal and technical limitations handled?
An SDS is not described as a universal government approval or guaranteed shipping clearance. Country examples are labelled by jurisdiction. Product classification is not inferred from a marketing name, and unavailable evidence is not replaced with invented values.
How are pages reviewed and updated?
- Important links and dates are checked during substantive updates.
- The visible review date changes only when content is actually reviewed.
- New product, regulatory or hazard information can trigger a correction.
- Material changes should also update structured data and the sitemap date.
Who writes and reviews the content?
Guides are published by the MSDS Compliance Team. The team’s role is to explain documentation and product-data decisions clearly. The author name is not used to claim a government appointment, laboratory accreditation or authority that has not been stated and verified.
How can a factual error be reported?
Email contact@msdsbharat.com with the page URL, the statement in question and the primary source or product evidence that supports a correction. Substantive corrections are reviewed before the page is updated.
What does this policy not guarantee?
Following this policy does not guarantee search rankings, AI citations, buyer acceptance, customs clearance or carrier approval. It is designed to make each page clearer, more transparent and easier to verify.