This page explains the source files, parsing rules, page generation logic, QA checks and limits behind nic-india.com.
The main directory is built from the official MoSPI NIC 2025 Excel workbook and cross-checked against the NIC 2025 PDF where source notes or hierarchy context are needed. NIC 2008 is kept as a legacy archive and converter layer, not as the current primary standard.
The build pipeline parses Section, Division, Group, Class and Sub-class rows from the source workbook, normalizes hierarchy relationships, assigns source-backed summaries, builds breadcrumbs and emits one static page for each valid code route.
NIC 2008 to NIC 2025 suggestions are discovery aids based on deterministic matching rules such as title similarity and hierarchy overlap. They are never presented as final legal substitutions. Users should open the current NIC 2025 page and verify the official source before using a code in filings.
Related links to NCO, HSN, SAC and InSCED are navigation aids. They help users move between business activity, occupation, goods, service and education views, but they do not claim official one-to-one equivalence unless a source-backed concordance exists.
Core NIC, guide, trust and index pages are intended for indexing. Thin utility layers, unsupported legacy candidates and untranslated duplicate classifier details are controlled with canonical or noindex rules so search engines do not treat the site as duplicate scaled content.
Before publication, local checks validate source readiness, SEO metadata, Hindi canonical policy, route duplicates, internal links, link density, crosslinks and freshness warnings. Broken internal links fail the build; incomplete optional concordance layers produce warnings.
English is the primary layer. Hindi pages localize UI, trust pages and explanatory copy, while official code titles, raw code values, legal version names and direct source citations are preserved carefully rather than mechanically translated.
Correction reports are reviewed against official sources before changes are accepted. Send the page URL, affected code, issue description and source reference through the contact page or email.