- Merge the duplicate Organization/LocalBusiness JSON-LD blocks (home's
LocalBusiness + o-kompanii's Organization) into one shared
getOrganizationSchema() call rendered on every page. Deliberately NOT
wired through the root layout: fetches there get frozen into the
static shell at build time (backend unreachable during image build)
and never revalidate, silently serving stale data to crawlers - each
page calls it directly instead, where revalidation is proven to work.
- Add optional ItemList schema on /uslugi and Offer/OfferCatalog schema
on /aktsii; entity pages (/uslugi/[slug] Service, /blog/[slug]
Article) reference the organization via @id instead of duplicating it.
- Add 8 more real FAQ entries (pricing model, contract terms,
onboarding time, hybrid IT staff setup, supported stacks, backups,
152-FZ compliance, escalation) and give every FAQ its own slug and
dedicated /faq/[slug] page with its own title/H1/FAQPage schema,
modeled on the one-topic-per-page pattern (h/t remontka.pro).
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013otXCiTZsxdZ4SJKZ9wUky
Add canonical URLs and a sitewide Organization JSON-LD (linked via @id
to page-specific LocalBusiness/Service/Article schemas), move FAQ and
Reviews into the top nav, attach the 24/7 support claim to a tooltip
on the header badge instead of leaving it unexplained, drop the
unverifiable incidents_resolved stat from the hero terminal animation,
and clean up the empty-reviews state instead of showing a thin
placeholder.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013otXCiTZsxdZ4SJKZ9wUky
ogrechkoandClaude Sonnet 5