source-checked
Verified against listed official, government, OEM, or high-trust sources. Eligible for indexing.
Methodology
Every indexed page must be tied to a verifiable source. Content that cannot be grounded in an official regulation, SAE standard, or OEM document is withheld from search and sitemap.
How Pages Are Created
Each fault code record starts with structured fields: display code, code type, SPN, FMI, OEM code, manufacturer, system, component, source, symptoms, possible causes, first checks, severity, confidence level, review status, and last-reviewed date.
Factual fields — SPN number, FMI type, affected system — require source support before a page is eligible for indexing. Plain-English explanations must stay grounded in the listed sources and may not copy OEM manuals, PDFs, or competitor pages.
Review Status
source-backed
Supported by a reliable listed source and eligible for indexing when all build-time guards pass.
draft
Source-gating incomplete. Excluded from sitemap and search.
needs-source
Missing a reliable source. Excluded from sitemap and search until a source is added and verified.
deprecated
Retained for historical or redirect purposes only. Not indexed.
Source-Gated Publishing Policy
Content may not invent code meanings, copy OEM text, or make source-free claims. Pages marked draft, needs-source, deprecated, low confidence, or source-free are set to noindex.
Build-time validation checks source requirements and flags risky absolute wording. The sitemap and search index include only pages that pass all publishing guards.
Error Reporting and Corrections
Source-gating reduces errors but does not eliminate them. Regulations change, OEM documents get revised, and a source can be misread. When a reader identifies an inaccuracy:
- Submit a correction via the contact page with the page URL, affected field, and a source citation
- Corrections backed by an official source are reviewed and either updated with a new last-reviewed date or retracted from indexing until fixed
- Errors are not silently left in place — confirmed mistakes result in a visible change to the page or its index status
This site does not operate a public correction log, but the last reviewed date on each page reflects the most recent verified check of that record.
FAQ
Does this workflow require manual page-by-page approval?
No. Source-gating and publishing guards run at build time. Pages that do not pass the source and confidence checks are automatically excluded from the sitemap and set to noindex.
Can a page be published without a verified source?
No. Content must be grounded in a listed source to be eligible for indexing. Pages with no verified source are withheld regardless of how well-written the content is.
Can source-backed pages still be wrong?
Yes. Source-gating reduces error risk but does not eliminate it. Sources can be misread, updated by their publishers, or not fully cover a specific truck configuration. Always verify with official OEM service information.
How do I report an error?
Use the contact page. Include the fault code or page URL, the truck or engine model, and the source document you believe is more accurate. Corrections backed by an official source are reviewed and updated or retracted within a reasonable timeframe.
What happens to a page after an error is confirmed?
Confirmed errors result in either a corrected page with an updated last-reviewed date, or the page being set to noindex until a correction can be sourced. Errors are not left silently in place.