DOC #070 03_DEVELOPER_IMPLEMENTATION

SUBKUZ CANONICAL URL, REDIRECT AND ARCHIVE REGISTER

Subkuz Global Governance Framework | Issued by Subkuz Media Networks Private Limited (CIN: U72900JH2020PTC014521)

Document #070 | Verified Master Version

Permanent Addressing, Legacy Migration, Language Variants and Historical Record Rules

1. Purpose and scope

This Register establishes the permanent public URL architecture for the sixty-eight Subkuz governance instruments and the rules for migrating testing-stage pages. The accompanying canonical_url_registry.csv is the controlling machine-readable list. A URL may be changed after launch only through documented change control because public policies, legal notices, search results, citations, external links and grievance records depend on stable addresses.

2. Canonical design principles

  • Use one HTTPS host, https://subkuz.com, as the canonical production host.
  • Use lowercase ASCII slugs, hyphens between words and one trailing-slash convention.
  • Keep public policy, legal, privacy, transparency, standards, form and commercial paths semantically distinct.
  • Do not encode dates or version numbers in the canonical URL of a continuously maintained current policy.
  • Use dated URLs for periodic reports whose historical editions remain separately available.
  • Do not create city or language parameters as substitutes for stable locale URLs.
  • Do not canonicalise materially different language pages to one language. Use self-canonicals and reciprocal hreflang.
  • Do not include noindex forms in XML sitemaps, but allow crawlers to reach them so the noindex directive can be read.

3. Language and regional URL model

The English governance pages in this package use stable language-neutral canonical URLs because they serve as the global master public record. Complete translations may be published beneath an explicit language prefix, for example /hi/privacy/ or /fi/privacy/. Each translated page uses a self-referencing canonical and reciprocal hreflang to the English master and every other complete equivalent. An x-default reference may point to the English master or a neutral language selector. Incomplete, machine-only or mixed-language pages must not be included in a reciprocal hreflang set.

News and edition content may continue to use explicit language paths such as /hi/ and /en/. Users are offered visible language and edition links. Automatic redirection based solely on IP address, browser language or inferred location must not prevent users or crawlers from reaching another version.

4. Redirect rules

Situation Required response Notes
Permanent one-to-one replacement 301 or 308 Target the closest equivalent page, not a general homepage
Temporary maintenance or staged migration 302 or 307 Use only with a defined removal date
Merged duplicate pages 301 to the strongest consolidated page Preserve relevant anchors where possible
Removed page with no relevant replacement 410 Use 404 only where the absence is not an intentional permanent removal
Historical policy retained for accountability 200 with archived status and noindex Do not redirect an archived version when the historical record must remain readable
Form retired but process continues elsewhere 301 to successor form or process page Preserve reference instructions
Unsafe or unlawful content removed 410 or controlled notice Do not redirect to unrelated content
Language version not yet available Keep current page or link to available language Do not create a permanent cross-language redirect that will later need reversal

5. Redirect quality rules

  • No redirect chain. Every legacy URL resolves directly to the final canonical destination.
  • No redirect loop across language, slash, protocol, www and non-www rules.
  • Preserve query strings only where they remain meaningful and safe.
  • Do not redirect every missing URL to the homepage, Policy Centre or search page.
  • Update internal links, XML sitemaps, canonicals and navigation to the final URL rather than relying on redirects.
  • Keep permanent redirects for at least one year and longer where external links or legal references remain active.
  • Test redirects as logged-out users and with a crawler after cache purge.

6. Known testing-stage redirect map

Legacy URL Final target Status Reason
/hi/pages/about-subkuz /about-subkuz/ 301 Replace testing-stage About page with the authoritative global page
/en/pages/about-subkuz /about-subkuz/ 301 Consolidate duplicate English About URL
/about-us /about-subkuz/ 301 Consolidate older generic About page
/hi/pages/newsroom-team /newsroom/ 301 Replace template newsroom page
/en/pages/newsroom-team /newsroom/ 301 Replace duplicate template newsroom page
/hi/pages/contact /contact-directory/ 301 Use structured public contact directory
/en/pages/contact /contact-directory/ 301 Use structured public contact directory
/hi/pages/advertise-with-us /advertise/ 301 Replace testing commercial page
/en/pages/advertise-with-us /advertise/ 301 Replace duplicate testing commercial page
/hi/pages/editorial-policy /policy-centre/ 301 Replace combined policy with the authoritative centre
/en/pages/editorial-policy /policy-centre/ 301 Replace combined policy with the authoritative centre
/hi/pages/fact-checking-policy /policies/fact-checking-media-forensics/ 301 Replace testing policy
/en/pages/fact-checking-policy /policies/fact-checking-media-forensics/ 301 Replace duplicate testing policy
/hi/pages/corrections-policy /policies/corrections-clarifications-retractions/ 301 Replace testing policy
/en/pages/corrections-policy /policies/corrections-clarifications-retractions/ 301 Replace duplicate testing policy
/en/pages/ethics-independence /policies/editorial-ethics/ 301 Replace combined testing ethics page
/hi/pages/ownership-funding /ownership/ 301 Replace testing ownership page
/en/pages/ownership-funding /ownership/ 301 Replace duplicate testing ownership page
/hi/pages/grievance-redressal /grievance/ 301 Replace testing grievance page
/en/pages/grievance-redressal /grievance/ 301 Replace duplicate testing grievance page
/welcome/privacy /privacy/ 301 Replace obsolete controller and privacy notice
/welcome/terms /terms-of-use/ 301 Replace obsolete terms
/instructions /secure-tips/ 301 Replace legacy contributor submission instructions

7. Crawl-discovered additions

Before activation, the technical team performs a complete authenticated and unauthenticated crawl of production, extracts every URL containing policy, privacy, terms, grievance, ethics, fact-check, corrections, ownership, contact, newsroom, careers, advertising, instructions, copyright, accessibility or security, and compares the result with redirects.csv. Any additional indexed or externally linked legacy URL receives an explicit decision: replace, redirect, archive, noindex or remove. The release must not use a broad wildcard that sends unknown pages to an unrelated destination.

8. Canonical and duplicate controls

Every indexable page has one self-referencing canonical that matches its public HTTPS URL. Protocol, host, slash, uppercase and tracking variants redirect to the canonical. Print pages, preview pages, filtered archives, AMP remnants, translated boilerplate duplicates and application webviews do not compete with the public page. Canonical annotations, redirects and sitemap inclusion should point in the same direction. Canonical is not used as a substitute for noindex on operational forms or private pages.

9. Policy archive

A superseded policy version may remain at /policy-centre/archive/YYYY-MM-DD/document-slug/ when preservation serves accountability. The page displays Archived and Superseded by the Current Version before the historical text, links to the current document, carries noindex,follow, and retains its original effective and superseded dates. Archived versions are excluded from the main sitemap and ordinary navigation but remain linked from the Change Log. A materially corrected current policy is versioned through the Change Log; the previous public version is preserved when readers may have relied on it.

10. Validation and acceptance

  • Every final URL returns 200 and the intended title, canonical, robots directive and language.
  • Every legacy URL in redirects.csv resolves in one hop to the correct final page.
  • No final URL redirects back into a legacy /pages or /welcome structure.
  • No form or archived policy appears in the public XML sitemap.
  • No canonical points to a noindex or error page.
  • Hreflang references are reciprocal, valid and limited to complete equivalents.
  • Search-console inspection confirms representative pages are crawlable and render the same public information visible to users.
DOCUMENT CONTROL DETAILS
Issued by Subkuz Media Networks Private Limited
Corporate Identification Number CIN U72900JH2020PTC014521
Document classification Developer implementation instrument
Effective date 6 August 2026
Last reviewed 7 August 2026
Previous legal name during statutory disclosure period Subkuz Media Networks Private Limited