SEO practice for teams working Yandex and Google in parallel.
SEO experiment methodology: what to test, how to split pages into test groups, how to read statistical significance and not fool yourself.
The Site Metrics Tool blog is a library of long, technical, practical material for anyone doing SEO across Google and Yandex. We don't publish "5 SEO tips from an expert"; instead we run a reference set of deep dives: how Core Web Vitals actually work, how to read Search Console and Yandex Webmaster, how to run a full technical audit in one evening, which keywords to target for a one-page site vs a marketplace, how backlink work differs between Russia and the US. Every article comes out of the Site Metrics Tool team's day-to-day work, gets fresh data from the platform, and ships with real examples.
Blog content splits into four large tracks so it's easy to find material for a specific job: foundational guides ("what is a sitemap", "how does indexing work", "why robots.txt matters"), advanced technical breakdowns (Core Web Vitals under the hood, JSON-LD for e-commerce, Yandex crawling specifics), comparison reviews (Site Metrics Tool vs Ahrefs, vs SE Ranking, vs Semrush), and traffic-growth playbooks for specific niches (e-commerce, local business, SaaS, content sites).
Each article goes through four stages. First we pin down the specific question users actually ask in support or search for on Google / Yandex. Second we gather facts: platform data, GSC and Webmaster exports, Google and Yandex docs, research studies. Third a team expert (engineer, SEO analyst, or product manager) writes the draft with concrete examples. Fourth an editor passes the article through a style + facts + SEO checklist. The result is something you can open, read in 10–15 minutes, and apply immediately.
A large share of the blog is technical guides for developers and senior SEO folks. We dig into how search engines actually see a site: what counts as a "contentful packet" for LCP, why INP replaced FID and how to measure it correctly, how Googlebot handles JavaScript, how Yandex crawling differs from Google's, how to validate structured data. For every topic — concrete actions you can do in a couple of hours.
A separate track is "how to measure the result correctly". We cover why GSC's "average position" can mislead, how to cleanly split branded vs non-branded traffic, what a position-CTR curve is and how to build one on your own data, what correlation between Core Web Vitals and traffic looks like on real sites. Most teams aren't failing to do SEO work — they're measuring the wrong thing, and our material helps fix that.
The blog targets three reader types. One: a beginning webmaster who plans to do SEO on their own site and wants to understand how everything works. Two: a working SEO who needs technical depth and fresh data. Three: a product manager or marketer who needs to explain to leadership why the team is doing what it's doing. Every article is tagged with a difficulty level: beginner, intermediate, or advanced.
The right sidebar has categories and a "Popular articles" block. Inside each article there's a table of contents with direct anchor links and a reading-progress bar at the top. To search for a specific topic — use site search, all content is indexed by both Google and Yandex. The end of each article carries a "Related articles" block — 3–4 connected pieces, usually useful for context.
We publish 2–4 new long-form pieces per month plus targeted updates to existing ones. We update old articles regularly — especially anything that cites Google or Yandex data, since those numbers change yearly. The article header shows the last-updated date, not just the original publish date. So if a piece is a year old, chances are we've refreshed it once or twice with current figures.
The highest-leverage move is to bake articles into your workflow. Example: when adding a new SKU to an e-commerce site, open the JSON-LD-for-Product article and walk the checklist. When Core Web Vitals dip, open the LCP breakdown and see which of the listed problems matches yours. When launching a new language section, open the hreflang guide and verify your markup. Every article is written so it functions as a working tool, not just a thing you read once.
The blog is our biggest trust channel. If you came here for Core Web Vitals and got ten pages of generalities, you're not coming back and you're definitely not buying anything. So we deliberately keep material dense: real numbers, real API calls, real platform examples. The Site Metrics Tool team works with GSC, Webmaster, PageSpeed Insights, and Search APIs every day — and most posts come from work we did for actual users.
Yes — we have an RSS feed (link in the footer) and a fortnightly email digest with fresh and updated material. The digest subscription form is at the bottom of every article.
Because in SEO short answers are usually wrong. Understanding Core Web Vitals or JSON-LD needs examples, context, and step-by-step instructions — we put it all in one article so you don't have to piece things together across the web.
The team is based in Russia and most pieces are written in Russian first, then translated to English. For some material we go the other way because certain sources (the GSC API for example) are better documented in English. Either way both languages are originals, not machine translations.
Yes, with attribution and a link to the original. If you'd like to translate and republish in full, drop us a note — usually we say yes.
Occasionally — when the writer is a real expert and the piece is genuinely useful. We don't accept guest posts that exist to backlink to sketchy sites.
The big difference is that we write for the Russian / CIS market, taking Yandex, Russian regions, and Runet specifics into account. Ahrefs and Semrush cover Google and the global market — we cover both engines simultaneously.
No, blog access is completely free, no limits. You can read every article and use the free tools they reference even without a platform account.
Email support@sitemetricstool.com or hit us in the Telegram channel. Most recent material came directly from user questions.