Amaso Wordpress Plugin - Rating, Reviews, Demo & Download
Plugin Description
Amaso Lite brings local SEO/GEO checks and optional AI-provider workflows into
WordPress. Review your business context, inspect answers to customer questions
and record what you changed. English is the source documentation; a short French
summary appears below.
Website: amasoai.com · Guides: AI visibility resources · Pro plans: pricing
The interface uses English source strings. A partial French catalogue covers
core navigation and common actions; untranslated strings fall back to English.
WordPress site/user language settings select the interface language.
Included in Lite
- Keywords and local markets — no artificial Lite keyword or market quota; manual SEO ranking records are included.
- Business Profile — quick and deep scans of supported site content, with manually validated type, location and services retained through rescans.
- AI suggestions — local suggestions and included BYOK suggestions; provider processing is optional and billed by the provider.
- AI citations — manual records plus on-demand and scheduled checks with your own supported provider keys. No artificial Lite monthly citation quota; provider limits, request safeguards and hosting capacity still apply.
- Content Audit — local/full audits and included fix actions, plus BYOK AI content audit and FAQ generation. Review proposed changes and publishable content before applying them.
- Schema and llms.txt — supported automatic/manual JSON-LD, AI metadata and public text indexes. llms.txt is an optional publication format, not a verified ranking or citation signal.
- Crawler/referral observations — local request-based records with the measurement limits below.
- Action plan and exports — a local work journal and CSV/JSON exports for the available datasets.
- IndexNow — optional URL notification after explicit opt-in; off by default.
Separate Pro capabilities
The paid Amaso edition provides Autopilot, Google Search Console and GA4
integrations, Share of Voice, PDF-ready reporting and related client-reporting
features according to the active plan, and letting an AI assistant (Claude, ChatGPT) connect to the site and make changes for you. These are not included in Lite; the Assistant inside the WordPress admin, which reads and audits, is.
A paid subscription does not include or replace your AI-provider usage charges.
Lite’s included local and BYOK features do not require an Amaso product license.
What the measurements mean
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.
Citation check batches and provider usage
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.
Local action plan and journal
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.
Privacy and consent
Lite has no license activation/heartbeat client or custom updater; WordPress.org
handles its plugin updates. It does make external requests for the optional
services documented below, so it is not a zero-outbound-network plugin.
Saving results locally does not mean that provider processing stays on the site.
Stored data and public output
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, 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.
The 404 monitor (Optimize Redirects) records each address visitors could not find: the path without its query string, how many times, the first and last time, and the referring website’s host name only — never an IP address, user agent or cookie. Recording is rate-limited and capped, static files are ignored, and dismissing an address or adding a redirect for it removes the entry. Redirects you create are stored as a path map. The link checker (Optimize Links) stores only the list of problem links found in its last scan. When no SEO plugin is active, the search description you (or the Assistant) 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.
Every action the in-admin Assistant (Optimize Assistant) runs is logged (which
tool, its arguments and result, the calling WordPress user, and a timestamp) so
it can be reviewed or, for the actions that support it, undone. The Assistant’s
own conversation is saved per WordPress user so it is still there next time that
admin opens the page; “Clear conversation” erases it.
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.
External services
Google PageSpeed Insights: only when you click “Test speed” on a page in the technical health check. The address of that page of your site (nothing else) is sent to https://www.googleapis.com/pagespeedonline/v5/runPagespeed, which loads it and returns its speed measures (Core Web Vitals). An optional free API key you enter in Settings is sent with it. Google terms: https://developers.google.com/terms and privacy policy: https://policies.google.com/privacy
Anonymous usage statistics (amasoai.com): OFF by default. Only if you tick “Send anonymous usage statistics” in Settings, Amaso sends once a week to https://amasoai.com/wp-json/gvlm/v1/usage: a random ID created on your site, the edition, plugin/WordPress/PHP versions, the site language, and per-module counters (which modules are on, how often each was used this month). Never your site address, content, keywords or personal data. Untick the box to stop it. Terms and privacy: https://amasoai.com/terms-conditions/
No inbound connections — Amaso Lite does not open a remote-access
endpoint, does not accept connections from outside clients and does not create
Application Passwords or OAuth tokens. The Assistant only works inside the
WordPress admin, for a logged-in administrator, and only calls the AI provider
you configured (see below).
IndexNow — automatic submission is OFF by default on new installs.
Existing saved choices are retained. Explicitly enable it or request a manual
submission to notify participating search engines about public URLs. After
opt-in, eligible publish/update events can submit URLs in the background.
Requests to https://api.indexnow.org/indexnow include the host, URL list,
verification key and key-file URL; the service also receives normal connection
metadata. Notification or HTTP acceptance does not guarantee crawling, indexing,
Google inclusion, AI indexing, citations or an immediate result.
IndexNow terms and website privacy information.
Google Autocomplete — used only when you click “Find real searches” (Setup
wizard, step 2, or Keywords). Amaso requests
https://suggestqueries.google.com/complete/search for up to four topic phrases
taken from your business profile or keyword list (with your city or country when
the business is local), together with your site language and country code. No
page content, no site URL and no personal data are sent; Google receives the
usual connection metadata, including your server’s IP address. Answers are kept
for a week in a WordPress transient. This is a public suggestion endpoint that
Google does not document as an API: it can change or refuse requests, and
Amaso then shows a message instead of results. Autocomplete shows what people
type; it does not provide search volume or keyword difficulty.
Google Terms of Service and
Privacy Policy.
OpenAI, Anthropic (Claude), Google (Gemini) and Perplexity — optional
bring-your-own-key (BYOK) services for supported citation checks, business
classification, suggestions, FAQ generation, the in-admin Assistant (Optimize
Assistant) and AI-assisted content work.
Local heuristics do not require a provider account. AI features require your
configured provider credentials and may incur that provider’s charges, rate
limits or account restrictions; free API access is not promised.
Review the provider policies and the data being submitted before choosing an AI
action or saving credentials for scheduled use. Requests can contain keywords,
questions/instructions, the site URL, business context and relevant page excerpts,
depending on the action. Public source content is still sent externally when
used in such a request. Configured citation checks can run through WP-Cron, and
a scan can use a configured provider for classification; requests are not limited
to clicking a single test button. Review schedules before adding keys and remove
credentials or disable the relevant automation to stop future provider calls.
API requests go to the selected provider using your key.
- OpenAI: API services agreement · privacy
- Anthropic: commercial API terms · privacy
- Google: terms · privacy
- Perplexity: API terms · privacy
amasoai.com (Fosia Ltd) — Upgrade requests public monthly USD catalogue
prices from https://amasoai.com/wp-json/gvlm/v1/plans when you click “Check
current prices”. Automatic price checks are OFF by default. If you explicitly
allow them on Upgrade, opening that page checks again when the last successful
check is at least 12 hours old. Failed automatic checks retry no more often
than every 15 minutes, on a later page view. No background cron is scheduled.
You can turn automatic checks off on the same page; a manual check does not
turn them on. A manual check always requests prices immediately.
The last complete valid catalogue and its check date are stored locally until
replaced or plugin data is explicitly erased. A network failure retains those
prices with a warning; bundled prices are marked as unverified references.
Legacy cached prices have no check date until the next successful request.
Only a cache-busting timestamp is attached to the request, with a generic
Amaso-Pricing user-agent. No license key, site URL or business content is sent
by this integration. The server still receives normal connection metadata,
including the requesting IP address. A price check does not activate a license,
purchase a plan, or change existing subscription charges.
Fosia Ltd: Terms & privacy.
Screenshots
Dashboard — local observations and action plan.
Business Profile — scan findings and validated business details.
Schema Manager — JSON-LD editor and supported schema controls.
Content Audit — heuristic findings and available review/fix actions.
Settings — provider keys, automation settings and data tools.
