Search Google Business Profile in Yerevan: How to create and verify
How to create and verify a Google Business Profile in Yerevan: verification methods, the 14-day postcard, and rules for business names and addresses.
Cookies on this site
The site stores what it needs itself: your theme, your animation setting and this choice. Analytics, marketing and external services switch on only with your consent. You can change your mind at any time. More about cookies
Add a three-language website to Google Search Console as one Domain property: it collects data for all URLs, including the /ru/ and /en/ folders. In Yandex Webmaster, add one site and put hreflang tags in the <head> of every page, because Yandex no longer reads sitemaps for language versions. That’s how esaweb.am is set up, and the steps are below.
Google’s documentation lists two property types, and your choice determines what shows up in your reports.
| Type | What it covers | How to verify | When to use |
|---|---|---|---|
Domain, esaweb.am | The domain, all subdomains, and all protocols | DNS record | If you have DNS access at your registrar or DNS host |
URL prefix, https://esaweb.am/ | Only URLs with this exact prefix, including protocol | Multiple methods, no DNS needed | If you don’t have DNS access |
URL prefixes https://esaweb.am/ru/ and /en/ | Only this folder | Same as URL prefix | If you need a separate report per language |
For sections like /france/ and /spain/, Google’s documentation suggests one property per section plus one umbrella property for everything. For a three-language site that isn’t necessary: you can filter the Performance report by URL. In the interface, click ”+ Add filter”, choose “Pages”, then “URLs containing”, and enter /ru/. Treat everything else as the Armenian section. Google adds a caveat: the filter can change totals because of data truncation and hidden queries, so the three languages won’t always add up to the overall number. If you need three separate reports, set up three URL prefix properties.
A common mistake with URL prefixes is adding only https://esaweb.am/ when some URLs live on www or plain http. According to the documentation, a URL prefix needs a separate property for each protocol and each subdomain. A Domain property removes that problem.
Use one sitemap with the URLs of all three languages. On our site, sitemap-index.xml points to one file where every URL lists all three versions through xhtml:link with the language codes hy, ru, and en. The <head> of each page carries the same three tags plus x-default.
Google allows three places for annotations: HTML tags, the Link HTTP header, and the sitemap. It says they’re equivalent and that using all of them at once gives no benefit. Yandex is different.
| Annotation location | Yandex | |
|---|---|---|
Tags in <head> | Supported | Supported |
| Sitemap | Supported | “No longer supports Sitemap files for language versions” |
| HTTP header | Supported, suitable for non-HTML files like PDFs | Not mentioned in documentation |
So if you care about Yandex, <head> tags are a must, while sitemap annotations are redundant for Google but do no harm. The other hreflang rules are the same for both search engines: every version must link to itself and to all other versions, using ISO 639-1 language codes. For details, see the article on building a three-language website.
For a Domain property, Google requires verification through a DNS record: you get a text string to add to your domain’s DNS records, wherever the DNS is hosted. That’s either your domain registrar or the service your name servers point to. For a URL prefix, the docs mention “multiple methods” and link to a separate page; no DNS access is needed. If you don’t know where your domain’s DNS is managed, ask whoever registered it: that decides whether you can use a Domain property.
Yandex Webmaster also requires you to verify the site. On esaweb.am we did it with a meta tag in the <head> of every page. Three languages don’t complicate things here: you add one site, esaweb.am, not three.
That leaves the site’s region. Yandex’s help describes it as a hint for location-dependent queries: you set it under “Search appearance,” moderation takes from a few days to several weeks, and the setting takes effect about two weeks after approval. Armenia and Yerevan aren’t mentioned in the documentation; the only country listed is Russia. Yandex’s share of search in Armenia was 10.51% in October 2026 according to StatCounter, against 87.49% for Google, so set up Yandex after Google, not instead of it. For more, read the article on Google vs. Yandex in Armenia.
Submit your sitemap under Sitemaps and wait. How long a new site has to wait and what statuses like “Crawled - currently not indexed” mean is covered in the article on why your site isn’t showing up on Google.
Putting hreflang tags only on the Armenian pages, with no return links from the Russian and English ones. According to Google’s documentation, if two pages don’t point to each other, the annotations are ignored. Submitting a sitemap for one language only, which slows down how quickly Google finds the others. Adding only an http:// prefix property when the site runs on https://. Placing hreflang annotations only in the sitemap for Yandex, which doesn’t process them at all.
If you want me to set this up and check it, it’s part of my SEO services: tracking and analytics are in the package, which starts at 130,000 ֏ a month. That’s how I make a living, but you can do the setup yourself with this guide.
SEO so people can find you in search, in Armenian, Russian and English. Reports in plain language.
Talk to us
Phone us, write to us or send a short brief. You get a clear next step and, after the first conversation, a written estimate.
Animation is off because your system asks for reduced motion.