Wargaming is hiring 44 people across Belgrade, Nicosia, Vilnius, Prague, Warsaw, Berlin and Austin, including hard-to-fill senior art and design roles open since spring. Yet every vacancy page on wargaming.com has the same title, "Wargaming Vacancies | Wargaming", and the same description, and none carries JobPosting data. In search results a Senior UI Designer page and a Facility Officer page look identical, and none of them can appear as a rich result in Google's job search.
First action
Rewrite the title and description template for vacancy pages and ship it with JobPosting markup on one role.
How to measure it
Organic applications per open role
- Now
- –
- Target
- +30%
- By
- 90 days
Steps
Map the fields
Role, game, city, work mode, posted and closing dates from the job record.
Web Team Lead (wargaming.com) 1 day
Template the head
Unique title and description per vacancy.
Web Team Lead (wargaming.com) 2 days
Add JobPosting
JSON-LD with location, employment type and validThrough.
Web Team Lead (wargaming.com) 2 days
Validate
Rich Results Test on ten vacancies.
Web Team Lead (wargaming.com) 1 day
Handle closures
Remove markup and return 410 or redirect when a role closes.
Web Team Lead (wargaming.com) 1 day
Resubmit
Sitemap with lastmod and indexing requests.
Web Team Lead (wargaming.com) 1 day
Track
Search impressions, clicks and applications by source per role.
Talent Acquisition Lead weekly
Why it works
Template the vacancy page head from the job record: title "<Role> (<Game>) - <City> | Wargaming Careers", a description built from the first line of the job overview, and JobPosting JSON-LD (title, description, datePosted, validThrough, hiringOrganization, jobLocation, employmentType, and the work mode such as hybrid or on-site). Remove the markup when a role closes, add the sitemap lastmod per vacancy, and request indexing for the 44 live pages.
Job search is where experienced game developers look first. Distinct titles lift click-through from every search, and structured job data puts the roles into Google's job results for free, cutting time-to-hire and agency spend on the roles that have stayed open longest.
Ready to use
CopyVacancy page head
Title: {Role} ({Game}) - {City} | Wargaming Careers
Description: {First sentence of Job Overview} Hybrid in {City}. Apply on wargaming.com.
JSON-LD JobPosting: title, description, datePosted, validThrough, employmentType FULL_TIME, hiringOrganization Wargaming (sameAs wargaming.com), jobLocation {City, Country}, directApply trueRisks and how to handle them
Stale postings in search
Set validThrough and remove markup on closure.
Duplicate listings with Greenhouse
Mark the wargaming.com page as the canonical apply page.
Evidence
- Your websiteAll 44 vacancy pages on wargaming.com/en/careers carry the same title, "Wargaming Vacancies | Wargaming", and the same description ("find your perfect job with WG vacancies"); only the H1 names the role. None has JobPosting structured data, so they cannot appear as rich results in Google's job search.Source
- HiringThe Greenhouse board lists 44 open roles (October 21, 2026): Belgrade 16, Nicosia 14, Vilnius 6, Prague 3, Warsaw 3, plus Berlin and Austin. New this month: Senior UI Designer (World of Tanks Console, UI that supports "engagement, retention"), UI Designer and Economy Game Designer (World of Warships), DevOps, QA and a Project Manager. Several art roles have been open since April-July 2026, including Senior Concept Artist and Art Manager/Lead Art Owner for World of Tanks.Source
- Your websiteSitemap (718 URLs, checked October 21, 2026): 23 listed URLs return 404, 16 written with a doubled slash (/en/about//, /en/careers//, /en/games/world-of-tanks// and others) and 7 under /en/game/. Of the 650 news URLs, 241 are dated 2015 and 9 are dated 2026. No Russian URLs are listed and no page has hreflang, although every page has a Русский switch.Source