Editorial policy: how we write and check

Our sources, in order

We start with primary sources and move down the list only when a primary source does not exist:

1. Law and official registers: the Legislative Herald of Georgia (matsne.gov.ge) for the text of laws, the National Agency of Public Registry (napr.gov.ge) for ownership and cadastral data, the Public Service Hall for procedures and fees, the Revenue Service (rs.ge) and the Ministry of Finance (mof.ge) for tax, the National Bank of Georgia (nbg.gov.ge) for exchange rates and lending data, Geostat for statistics.
2. Market research: Colliers Georgia, Galt & Taggart and TBC Capital reports, cited with the report and date.
3. Our own observations: site visits, dated photos and client cases, used only with consent and never invented.

We open the page we cite. A search-engine snippet, a forum post or another agency's article is not a source. Every page lists its sources with the date we accessed them.

Numbers, estimates and dates

• Every number on the site comes from a central facts register that records the value, the source and the date it was checked. A number without a source is not published.
• Prices, rents and yields are estimates and are labelled as such on the page. They describe a market at a date, not a promise.
• Every page shows a "Last checked" date in the byline and a change log at the end. When a rule changes, the page is updated and the change is dated.
• We do not use words like "guaranteed residency", "guaranteed income" or "risk-free" in any language.

Legal, tax and residency pages

Pages about law, taxes and residence permits are reviewed by our partner lawyer or accountant before they are considered final. Until then the page carries a visible notice that it is being reviewed. The reviewer is named in the byline. Even a reviewed page is general information: your case may differ, and a lawyer checks it before you buy.

How we use AI tools

We use AI tools for drafting, structuring, summarising long documents and supporting translation between our five languages. We do not publish anything an AI tool produced without a person doing three things first: verifying every fact against the cited source, reading the page in the language it is published in, and signing it as author. AI is never cited as a source, and AI-generated images are not used as photos of real places or projects.

Five languages, one set of facts

Each page is written in English first and then adapted into Georgian, Russian, Hebrew and Arabic by people who know how buyers from those countries search and what they need to know. The facts and structure are the same in every language; the examples and the context may differ. Technical terms follow one approved list so that a term means the same thing on every page.

Independence

Nothing on avi.ge is paid for by a developer, a bank or a seller. There are no sponsored guides, no paid rankings and no star ratings. The full rules, including how we are paid, are on the independence page.

Corrections

If you find a mistake, write to info@avi.ge or send a WhatsApp message with the page address and what you believe is wrong. We check the claim against the source. If the page is wrong, we correct it and note the correction, with the date, in the page's change log. The report-an-error page describes the procedure step by step.

What we never publish

• Invented reviews, testimonials or client stories. Client experiences appear only with the client's consent.
• Property listings or project reviews we have not checked ourselves. A project review is written only after a site visit with dated photos.
• Claims about a developer, positive or negative, without a source that would stand up to the developer's lawyer.
• Copied text. Quotes are short, attributed and rare.

Photos

Photos of districts, buildings and construction progress are taken by the team and dated. Where we have no photo yet, the page says so instead of using a stock image.

How to cite us

You may quote and link to any page. Please name avi.ge, link to the page and keep the "Last checked" date, because numbers change.

How a page is produced

1. Brief

   Every page starts from the content plan, which assigns it one question, one URL and one type, and lists the other pages in its cluster so that it does not repeat them. A page that would answer the same question as an existing page is not written; the existing page is improved instead.

2. Research from primary sources

   The author reads the law, the official procedure or the published report, not a summary of it, and records each fact in the facts register with its source and the date.

3. Draft in English

   The English master is written to the structure for its type: short answer first, key facts, body, FAQ, sources, change log. AI tools may help with drafting and structure under the rules below.

4. Fact check

   A second person checks every number and claim against the register and the cited source, and every internal link against the site. Numbers that cannot be sourced are replaced with a "to be added" box.

5. Review where required

   Legal, tax and residency pages go to the partner lawyer or the accountant. The page is published with a visible notice until the reviewer confirms it in writing.

6. Adaptation into four languages

   The page is adapted into Georgian, Russian, Hebrew and Arabic by people who read those markets, keeping facts and structure and changing examples and emphasis. Terminology follows one list.

7. Publish and index

   The page is added to its hub, the sitemap, the on-site search index and the machine-readable summary, and its structured data is validated.

8. Re-check

   Each page has a next-check date tied to its sources. When a rule or a figure changes, the page is updated and the change is dated in its log.

Page types and what each must contain

The site uses a small number of page types, each with a fixed structure, so that a reader who has read one guide knows where to look in the next. A complete guide, or pillar, covers a whole subject with a link to every article in its cluster and a diagram or table that summarises the process. A step guide gives numbered steps with the time and cost of each where known and the documents needed. A checklist puts the list itself first, as a form that can be ticked and printed, and explains why each item matters. A comparison opens with a table that applies the same criteria to both sides and ends with a verdict by buyer type rather than a winner. An explainer gives a definition, how the thing works in Georgia, an example with numbers and the common misunderstandings. A data page puts the table or chart first and the methodology, sources and date beneath it. A place page follows a fixed template so that districts can be compared. A glossary entry gives a one-sentence definition, an example and the term in five languages. A tool explains every input and its source. A service page states what is included, the timeline, what we need from you and the price basis. A country guide covers only what is specific to that country. A developer profile contains verifiable facts with sources and no ratings. A report shows headline numbers, charts, methodology, sources and the date of the next update. Every type carries the shared blocks: byline with author and reviewer, last-checked date, sources, change log and related pages.

Three dates on every page

A page carries a published date, a last-checked date and, in its own records, a next-check date. The published date tells you how long the page has existed; the last-checked date tells you when a person last compared its facts with their sources and is the one to read; the next-check date is tied to the publication cycle of the page's sources, monthly for market figures, on change for legal rules and at least yearly for everything. The change log at the end of each page lists what changed on which date, so that a reader who saw the page a year ago can see what is different. A page whose last-checked date is old is not necessarily wrong, but it is a page to read with that date in mind, and we would rather show the date than hide it.

Structured data and machine readers

Every page carries structured data in the schema.org vocabulary describing what it is: an article with its author and reviewer, a frequently-asked-questions block, a how-to with its steps, a place, a dataset, a defined term, a tool, a service, an organisation. We mark up only what is on the page and only what is true: a review that has not happened is not marked as a review, an author without a published name is marked by role, and a page under review is not marked as reviewed. The site also publishes a plain-text summary for language models and other automated readers, listing the sections, the key facts and the sources, so that a machine that summarises this site has the same facts and the same caveats as a person. We do this because an increasing share of readers meet our pages through an assistant rather than a browser, and the assistant should be able to tell them where a number came from and when it was checked.

Readers', clients' and developers' rights

Readers may quote and link to any page under the conditions in the section on citing us, and may ask for a correction through the report-an-error page; every correction is answered and, if made, dated in the change log. Clients' experiences appear on the site only with their written consent, anonymised unless they ask otherwise, and never invented or composited into a "typical client". Developers and other companies written about on the site receive the text before publication, may respond, and have their response published next to the text with its date; a factual correction supported by a source changes the text, and a disagreement without a source is published as the company's view. Nobody, client, developer or advertiser, can pay for a change to a page, as the independence page sets out.

What "reviewed" means, and what it does not

A page marked as reviewed by the partner lawyer or the accountant has been read by that person against the primary source and confirmed in writing on a date. It means the general statements on the page were correct on that date. It does not mean the page is advice for your case, that the rule has not changed since, or that an official will read the rule the same way at the counter; practice at the Public Registry, the Public Service Hall and the Revenue Service can differ from the text, and where we know it does the page says so. A reviewed legal page is the starting point for a conversation with a lawyer about your own purchase, which is also why every legal page links to the service that provides exactly that.

Why the pages are long

Every page on this site is written to be complete on its own subject, and that makes most of them long. The reason is the reader: a buyer who opens a page about the residence permit at midnight in another country should find the rule, the exceptions, the documents, the risks and the sources on that page, not a teaser that sends them to a consultation. Length is never filler, though. A page may not repeat another page, and a page that could be shorter without losing a fact or a caveat is shortened. The short answer at the top of each page exists for readers who need only the conclusion; the rest is for readers who need to be sure.

Who writes and who signs

Every page is signed by a named author, or by a role until the owner publishes the team's names, and the author's profile lists the pages they sign. The founder signs the guides on buying, investing and residency and the company pages; the property adviser co-authors the place and project pages from site visits; the partner lawyer reviews the legal, residency and tax-law pages and the site's own legal pages. A signature means that a person is responsible for what the page says, can be asked about it and will correct it. Writers and editors who join under the conditions on the team page get a profile before their first signed page appears.

Frequently asked questions

Is the information on avi.ge legal advice?

No. The guides are general information checked against official sources. Your case may differ, and a lawyer confirms it before you buy. Pages marked as being reviewed may still change.

Who is responsible for a page?

The author named in the byline. For legal, tax and residency pages a reviewer is named too, and the review notice stays on the page until the reviewer has approved it.

How do I report a mistake?

Use the report-an-error page, or write to info@avi.ge or on WhatsApp with the page address and what you think is wrong. We check it against the source, correct the page if needed and record the change in the page's change log.

Do you use AI to write pages?

AI tools help with drafting, structure and translation. Every fact is verified by a person against the cited source before publishing, and a person signs the page. AI is never a source.

Change log

• 11 October 2026 - Published.