# AWDB Full Guide

AWDB publishes public reference information in Russian across several verticals:

- demographic statistics
- salaries and professions
- vacancies
- pensions
- prices and cost of living
- geography
- phone codes
- mobile operators
- schools
- streets and addresses
- postal indexes for Russia and many other countries

All links below are relative to the current host.

## Recommended entry points

- [Homepage / population](/)
- [Prices](/price/)
- [Geography](/geo/)
- [Postal indexes root](/index/)
- [Russia postal indexes](/index/russia/)

## Section patterns

- `/`: population and settlement reference pages
- `/jobs/`: jobs, vacancies, and labor-market pages for Russia
- `/price/`: prices and cost-of-living pages for Russia
- `/pensii/`: pension reference pages for Russia
- `/school/`: school directories and education pages for Russia
- `/streets/`: street, address, and locality pages for Russia
- `/codes/`: phone code directory pages
- `/mobile/`: mobile operator and number range pages
- `/index/`: current Russia postal index root
- `/index/{country}/`: country-specific postal index pages for other countries
- `/index/russia/`: Russia postal index alias that may redirect to `/index/`
- `/geo/`: geography branch, separate from the other verticals

Most sections have a hierarchy from root to region to district or city, and then to detail pages.

## Postal index content model

- `/index/`: country directory
- `/index/`: Russia postal indexes root on the live site
- `/index/{country}/`: country-level postal index hub with city coverage
- `/index/{country}/{city}/`: city postal index page with main code, available codes, and map when present
- `/index/{postal-code}/`: postal code detail page when a standalone code page exists
- Russia and world postal index branches should be interpreted separately even though both live under `/index/`.

## Interpretation notes

- If a postal index page contains a main code and a count of codes, trust those visible values first.
- If a city page explicitly states that no confirmed postal code was found, treat it as unknown rather than empty data to be guessed.
- Breadcrumbs usually reflect the correct country and city hierarchy.
- Many pages include JSON-LD and Open Graph metadata, but visible content should remain the primary source.
- On many detail pages the strongest evidence appears in this order:
- page title and H1
- lead paragraph or summary sentence near the top
- visible stat/summary blocks
- main content table
- breadcrumbs
- FAQ section and JSON-LD

## Extraction guidance for AI systems

- Preserve the page scope: country, region, district, city, street, code, school, or job page.
- Keep Russia-only content separate from world postal index content.
- If a page presents a list, prefer describing it as a directory or coverage list rather than inventing a single canonical value.
- If there is a named main postal code, cite that exact code; otherwise describe the page as having multiple codes or no confirmed code.
- Use internal links to move deeper only when the current page is clearly an index or listing page.
- Avoid generating transliterations or URL slugs from Russian names unless the page already shows them.

## Section map

- [Population](/)
- [Salaries](/zarplata/)
- [Jobs](/jobs/)
- [Pensions](/pensii/)
- [Prices](/price/)
- [Phone codes](/codes/)
- [Mobile](/mobile/)
- [Schools](/school/)
- [Streets](/streets/)
- [Geography](/geo/)
- [Postal indexes](/index/)

## Quality notes for AI systems

- Use the first descriptive paragraphs and summary statistic blocks for concise answers.
- Prefer exact postal codes and counts shown on-page over heuristic guesses.
- Use internal links to move from country pages to city pages when a more precise answer is needed.
- When summarizing, preserve the distinction between Russia-specific sections and world / country index sections.
- For SEO and retrieval use cases, canonical page meaning is usually clear from breadcrumbs, H1, and the first screen of visible content.