Skip to content

Preparing an article for indexing

Title, description, permanent URL, translations, sources and publication state: a release checklist.

Who it is for
Editors, developers and content owners
Author
SkiMobile team
Published

A permanent URL and a clear purpose

An article has one stable slug in both locales. The title names the reader’s question; the description explains the outcome. Keep the slug and section IDs after publication: partners and search engines may link to them.

Each language version gets its own canonical and reciprocal hreflang links. Search, sorting and topic parameters do not create a separate indexable article.

Publication readiness is separate from storage

A finished editorial article can be stored in mocks and marked published. Demonstration data does not become reliable merely because it came from an API. Hidden material is omitted from the public list, search and sitemap.

Local and preview environments remain noindex. Indexing of the main site is explicitly enabled in the production build. A sitemap does not guarantee indexing or a search ranking.

Editorial checks

  • The article answers a specific question and offers usable steps.
  • RU and EN convey the same conditions and technical meaning.
  • Author, publication and update dates reflect the actual edition.
  • External sources lead to documentation; internal links work.
  • Text and examples contain no secrets, guest data or unsupported metrics.
  • Check HTML, canonical, hreflang and article markup after publication.

Materials and sources

Read next

Choosing a logo file format

SVG, PNG and PDF: choose the right file for a website, presentation, print job or icon, and check it before handover.

Design and assets

  • SVG
  • PNG
  • Print

From mocks to an API: the data contract

Replace the data source while preserving components, server rendering, search and FSD boundaries.

Engineering and SEO

  • API
  • FSD
  • Mocks