Product directory methodology

Selection

A product enters the public directory only after the site owner names it for inclusion. Editors and AI systems may suggest candidates, but suggestions cannot publish automatically. The product must have a direct, explainable use in AI-search visibility, citation analysis, content optimization, technical auditing, shopping visibility, or GEO reporting.

Facts and claims

Domain registration, company formation, product launch, and the earliest public product evidence are recorded separately. A domain date does not prove when a company or product started. Exact dates are used only when a source supports that precision.

Product capabilities usually come from official documentation and remain attributed to the vendor. This directory is a public-source reference, not a product review or performance benchmark.

Sources

Registration records, legal pages, launch announcements, product documentation, and changelogs receive the most weight. Investor pages and established reporting can corroborate company facts. Commercial databases and WHOIS aggregators are fallback sources, not the preferred record.

Landing page images

Each profile uses one screenshot of the product’s official Landing Page at the top of the page. The capture is limited to the initial 1440 × 900 desktop viewport. GEO Wiki does not capture logged-in interfaces, full-page composites, or screenshots from third-party directories. Images are stored in the Cloudflare R2 geo-wiki bucket and served from cdn.geo.wiki, with the source URL, viewport, and capture date shown on the product page.

Updates and corrections

Pricing and trials are reviewed most frequently, followed by engine coverage and capabilities. Company facts and Landing Page captures use a longer review cycle. A visible review date describes editorial checking, not an automated claim that every vendor field is live. Corrections can be sent to support@geo.wiki.