Amaso AI – GEO & AI Search Visibility

Local scans, heuristic scores, manual records, schema and text-index generation do not require AI keys. Included AI processing uses your own provider keys and provider billing. Lite does not require a paid Amaso license for those features.

Both can be installed, but only one runtime loads. An active compatible Pro edition takes priority over Lite; an admin notice explains the choice. The plugin does not silently change your activation choices. Back up shared data before changing or deleting editions.

The site's database prefix is used for geo_* tables, including keyword, ranking, citation, schema and request records. Shared installation code can create tables used by the other edition; table existence does not enable a Pro feature. Profiles, corrections, credentials, caches and the private action journal also use WordPress options. See "Stored data and public output" for export limits.

Lite inclut les outils locaux, les suggestions et contrôles IA lancés à la demande avec vos propres clés, les audits et les exports disponibles, sans quota artificiel de mots-clés ou de marchés. Les frais des fournisseurs IA restent à votre charge. IndexNow est désactivé par défaut. Les scores sont heuristiques et ne garantissent ni classement, ni citation, ni vente. Le journal local conserve les 100 derniers événements ; les notes restent privées dans WordPress. Les contrôles IA programmés, les corrections IA et le générateur de FAQ, l'assistant dans l'administration, les redirections et le suivi des 404, les liens cassés, Autopilot, GSC, GA4, Share of Voice et les rapports PDF relèvent des offres payantes. Le compteur mensuel utilise les lots de vérification réussis : un mot-clé et un moteur IA, avec au moins une variante enregistrée, comptent pour une unité AMASO. Un lot peut effectuer 1 à 5 requêtes de variantes ; les nouvelles tentatives et la recherche peuvent ajouter des frais fournisseur. Un lot sans variante enregistrée ne consomme pas ce quota, mais peut entraîner des frais fournisseur. Lite reste sans quota mensuel AMASO de lots de citations.

GEO and content-audit scores are heuristic checklists of observed page signals. They are not a measured probability of citation, a ranking factor supplied by Google, or proof of business results. A good Google position does not guarantee an AI citation, and a citation does not establish a conversion or sale. Provider checks record the query, engine, time and available answer/citation evidence. Results can differ from the provider's consumer app and change across queries, models and dates. Crawler logs recognize request user-agents; they do not prove indexing or citation. First-party AI referral counters count recognized inbound page requests, not unique visitors, qualified leads or revenue. The plugin does not automatically attribute conversions or sales to AI.

The "Check batches this month (UTC)" counter and applicable AMASO commercial quotas count successful keyword-and-engine check batches. One batch concerns one keyword and one AI engine; it consumes one quota unit when at least one query-variant result is stored. A stored result can say the site was not cited. Several stored variants in that batch still consume only one AMASO quota unit. A batch can make 1–5 query-variant provider requests. Retries and provider search tools may add usage and cost. For example, five stored variants from one keyword and one engine count as one successful batch, with separate provider usage. AMASO's batch counter is therefore not a count of HTTP requests or provider fees. A failed batch with no stored variants consumes no successful-batch quota, although provider charges may still apply. Lite has no AMASO monthly citation-batch quota. Provider charges, provider limits, request safeguards and hosting capacity still apply to its included BYOK checks.

The dashboard action plan uses local configuration and saved scan findings. Record an action's status and a private evidence note, then recheck observable conditions. "Reviewed" records a human review; "Verified" applies to the specific local condition checked, not to search rankings or AI recommendations. The journal retains the latest 100 events, including timestamps, WordPress user IDs, task/status changes and submitted notes. Current task notes/statuses and baseline/latest evidence are saved separately; the 100-event cap is not a cap on all saved data. Notes are for authorized WordPress administrators and are not automatically published in llms.txt or sent as AI prompts.

Data is saved in the site's WordPress database: keywords and markets, ranking and citation records, available answer evidence, schema definitions, business profiles and durable manual corrections, discovered public contacts/URLs, settings, encrypted API credentials, the last outcome of each AI provider, caches, usage counters and operational logs. The action plan also stores its evidence snapshots, private notes, user IDs and event history. The Pro edition additionally stores data for enabled competitor, reporting and Autopilot features. Redirects created with an earlier version of Amaso Lite are stored as a path map and keep being followed; this edition does not record 404 addresses. When no SEO plugin is active, the search description you set for a page is stored in the page's own custom field and printed as a single description tag in that page's head; with Yoast, Rank Math, All in One SEO or SEOPress active, Amaso writes to their field instead and prints nothing. A search title you set for a page is stored in a custom field on that page and printed as its title tag only when no SEO plugin is active. Locations (Setup → Locations) stores only the details you type for each place (name, address, phone, email, opening hours, coordinates) and the page it is linked to, and prints them as structured data on that page. Topic clusters (Optimize → Topic clusters) stores only the ids of the pages you mark as pillars; internal-link suggestions are computed from your own content and kept briefly as a temporary cache. Business contact details and user-entered notes can contain personal information. Public pages, active schema, AI metadata, robots.txt and llms.txt/llms-full.txt are readable by visitors and crawlers. Review public business details and author display names before publishing them. The administration email is not a fallback for a public business contact. CSV/JSON downloads cover the datasets offered by the export tool; they are not a complete backup of every option or private note. WordPress personal-data tools provide the plugin's supported site-owner export/erasure workflow, not a blanket guarantee of legal compliance or complete portability. Include the WordPress database in a backup when you need all settings, saved data and notes. Data is retained by default on uninstall; an explicit removal option controls cleanup. Review the resulting database/backup if complete removal is required.