Title: Amaso
Author: FOSIA Ltd
Published: October 14, 2026
Last modified: October 14, 2026
---
Search plugins
# Amaso
By [FOSIA Ltd](https://profiles.wordpress.org/fosialtd/)
[Download](https://downloads.wordpress.org/plugin/amaso.1.0.25.zip)
* [Details](https://wordpress.org/plugins/amaso/#description)
* [Reviews](https://wordpress.org/plugins/amaso/#reviews)
* [Installation](https://wordpress.org/plugins/amaso/#installation)
* [Development](https://wordpress.org/plugins/amaso/#developers)
[Support](https://wordpress.org/support/plugin/amaso/)
## 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](https://amasoai.com/) · Guides: [AI visibility resources](https://amasoai.com/resources/)·
Pro plans: [pricing](https://amasoai.com/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](https://www.indexnow.org/terms).
**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](https://policies.google.com/terms)
and [Privacy Policy](https://policies.google.com/privacy).
**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](https://openai.com/policies/services-agreement/)·
[privacy](https://openai.com/policies/privacy-policy/)
* Anthropic: [commercial API terms](https://www.anthropic.com/legal/commercial-terms)·
[privacy](https://www.anthropic.com/legal/privacy)
* Google: [terms](https://policies.google.com/terms) · [privacy](https://policies.google.com/privacy)
* Perplexity: [API terms](https://www.perplexity.ai/hub/legal/perplexity-api-terms-of-service)·
[privacy](https://www.perplexity.ai/hub/legal/privacy-policy)
**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](https://amasoai.com/terms-conditions/).
## Screenshots
[⌊Dashboard — local observations and action plan.⌉⌊Dashboard — local observations
and action plan.⌉[
Dashboard — local observations and action plan.
[⌊Business Profile — scan findings and validated business details.⌉⌊Business Profile—
scan findings and validated business details.⌉[
Business Profile — scan findings and validated business details.
[⌊Schema Manager — JSON-LD editor and supported schema controls.⌉⌊Schema Manager—
JSON-LD editor and supported schema controls.⌉[
Schema Manager — JSON-LD editor and supported schema controls.
[⌊Content Audit — heuristic findings and available review/fix actions.⌉⌊Content
Audit — heuristic findings and available review/fix actions.⌉[
Content Audit — heuristic findings and available review/fix actions.
[⌊Settings — provider keys, automation settings and data tools.⌉⌊Settings — provider
keys, automation settings and data tools.⌉[
Settings — provider keys, automation settings and data tools.
## Installation
1. Install and activate Amaso Lite through WordPress, or upload the amaso folder.
2. Open Amaso Setup and review the detected business profile, public contacts and
tracked queries.
3. Run a local audit and review the action plan. Check public schema and llms output.
4. For AI features, review the data/cost disclosures, add your own supported provider
keys and review the configured schedule before starting checks.
5. Leave IndexNow off unless you choose to submit public URLs to that service.
Minimum requirements: WordPress 6.0+, PHP 8.1+, MySQL 5.7+ or MariaDB 10.3+. Hosting
capacity, WordPress cron execution and provider availability affect runtime.
## FAQ
### Do I need an API key or a paid Amaso license?
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.
### Can both editions be installed?
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.
### Where is the data?
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.
### Résumé en français
Lite inclut les outils locaux, les suggestions et contrôles IA avec vos propres
clés, les audits, la génération de FAQ 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. Autopilot, GSC, GA4, Share
of Voice et les rapports PDF relèvent de Pro.
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.
## Reviews
There are no reviews for this plugin.
## Contributors & Developers
“Amaso” is open source software. The following people have contributed to this plugin.
Contributors
* [ FOSIA Ltd ](https://profiles.wordpress.org/fosialtd/)
[Translate “Amaso” into your language.](https://translate.wordpress.org/projects/wp-plugins/amaso)
### Interested in development?
[Browse the code](https://plugins.trac.wordpress.org/browser/amaso/), check out
the [SVN repository](https://plugins.svn.wordpress.org/amaso/), or subscribe to
the [development log](https://plugins.trac.wordpress.org/log/amaso/) by [RSS](https://plugins.trac.wordpress.org/log/amaso/?limit=100&mode=stop_on_copy&format=rss).
## Changelog
#### 1.0.25 – 2026-10-10
* CHANGED: requires WordPress 6.2 or later.
* CHANGED: the admin screens load their scripts and styles as files through the
WordPress script and style API; translated text reaches them through wp_localize_script.
* CHANGED: every database query goes through $wpdb->prepare(), with table names
bound as identifiers.
* FIXED: some admin styles (Assistant, Keywords, Schema, Settings and others) were
not applied.
* FIXED: when you choose to remove data on uninstall, the AI sources and missions
tables are now removed too.
#### 1.0.24 — 2026-10-04
* CHANGED: Amaso Lite no longer includes the remote MCP server, Application-Password
and OAuth connection. The Assistant inside the WordPress admin stays: it reads
and audits your site and can track and pause keywords and mark pillar pages.
The changes to pages (titles, descriptions, links, redirects, structured data)
are made on the Amaso screens, which are all in Lite; having an assistant apply
them for you is part of the separate paid edition.
* NEW: the Dashboard opens on your week: how often AI assistants cited you in the
last 7 days against the 7 before, your missions, and the three fixes worth doing
now (a blocking technical problem first).
* NEW: Visibility Missions: choose a search you want to be recommended for; Amaso
records where you start, builds a plan (on your site and across the web) and
measures the result at every check, with an honest verdict (“too early”, “no
change yet”, “improving”).
* NEW: AI Citations shows the websites the assistants actually consulted for your
searches (your site, reviews and directories, social and video, guides and forums,
other websites), each with what to do.
* NEW: Optimize Technical health: what stops Google and AI assistants from reading
your key pages (errors, redirects, noindex, canonical, titles, H1, phone viewport,
HTTPS, image descriptions, hreflang, robots.txt, sitemap), most severe first,
with the fix. Optional speed test per page through Google PageSpeed Insights,
only when you click (see External services).
* NEW: Optimize Shop (WooCommerce): product pages missing what AI shopping answers
need (price, photo, descriptions, category, reviews, identifiers), worst first.
WooCommerce products are now included in every content feature.
* NEW: Amaso panel in the block editor: the GEO score updates as you write, with
a Google preview, and the search title and description can be edited there (or
written with your own AI key). The classic editor keeps the meta box.
* NEW: the Assistant has ready-made workflows (weekly review, why am I not recommended,
start a mission, improve my product pages, write the missing cluster articles)
and tools for AI sources, page comparison, technical and shop audits.
* IMPROVED: after a redirect, a search title or a search description is saved,
the cached copy of that page is cleared in LiteSpeed Cache, WP Rocket, W3 Total
Cache, WP Super Cache or SiteGround Optimizer, so the change shows at once.
* NEW: Redirects suggests the page an old address used to be (matching words in
the address and your page titles) and redirects the confident ones in one click;
addresses your own pages link to are listed first, with the page that holds the
link; automatic probes are no longer recorded.
* NEW: the Assistant can read a page, pause weak keywords and mark a pillar page,
each undoable.
* IMPROVED: internal links read pages built with Divi, Elementor and other builders
as visitors see them.
* NEW: Keywords flags single common words, pricing words and past years (each tracked
keyword costs AI credit) and pauses them in one click; the setup wizard no longer
pre-selects them.
* IMPROVED: readability and accessibility: larger small text, stronger contrast,
visible keyboard focus, reduced motion respected, plain-language activity log.
* IMPROVED: French translation of every new screen.
#### 1.0.23 — 2026-10-03
* NEW: “Fix these first” after setup and on the Dashboard: up to five concrete
findings with the screen that fixes each.
* NEW: optional monthly email report (off until you turn it on).
* NEW: the Assistant can diagnose why AI assistants may not recommend you for a
search, and list what to fix first.
* NEW: MCP tools get_cluster_gaps and draft_cluster_article: a connected Claude
or ChatGPT can write the articles a topic cluster is missing, saved as drafts
linked to the pillar page.
* FIX: Plugin Check errors (exception messages now escaped, a translator comment,
a WordPress 6.5 function on a 6.0 minimum).
* NEW: optional, off-by-default anonymous usage statistics (see External services).
* FIX: the setup wizard no longer spins forever after the site scan.
* SECURITY: request data is sanitized as soon as it is read (business profile,
Schema JSON, service account, utm_source, Schema form fields).
#### 1.0.22 — 2026-09-28
* NEW: Setup Locations — describe each shop, clinic or office once (address, phone,
opening hours, coordinates) and link it to its page. Amaso prints that place
as its own LocalBusiness structured data on that page only, refuses invalid values
with a reason instead of dropping them silently, and warns when the page text
does not show the details the structured data claims. The Assistant gets get_locations.
* NEW: Search title. The Assistant can now set a page’s search title — the headline
shown in Google — written into your SEO plugin’s field when you use one, or printed
by Amaso when you don’t (as the whole title tag, only on themes that support
title tags). Undoable, like every change.
* IMPROVED: Settings AI Engines MCP now shows, in plain steps, how to connect
Claude.ai or ChatGPT to your site (paste the connection URL, approve on the consent
screen, switch the connector on in a chat) — the instructions used to be hidden
behind the Application Password button.
#### 1.0.21 — 2026-09-28
* NEW: the Assistant now works with Claude, ChatGPT (OpenAI) or Gemini using your
own key, remembers your conversation between visits, and every change it makes
is listed under “Recent actions” with an Undo button.
* NEW: connect Claude.ai, ChatGPT or any MCP client with a sign-in flow (OAuth)
instead of an Application Password; connected apps can be disconnected at any
time from Settings.
* NEW: Optimize Links scans your published content for broken links, in small
batches so it never slows the site.
* NEW: Optimize Redirects — a 404 monitor (path, count and referring host only;
no IP, user agent or cookie) and a redirect manager.
* NEW: Optimize Internal links lists published pages that nothing links to and,
for each, the pages that could link to it using words already written there.
Links are added one click at a time, never inside headings or existing links,
and never in page-builder pages.
* NEW: Optimize Topic clusters — mark a pillar page and see which supporting pages
link to it and which it links back to, with a one-click fix for each gap.
* NEW: Schema import structured data from a URL (private and local addresses are
refused).
* NEW: a fallback XML sitemap when WordPress’s own is unavailable.
* FIX: with no SEO plugin active, a search description set by Amaso was stored
but never printed in the page head. Amaso now prints a single description tag
in that case only; with Yoast, Rank Math, All in One SEO or SEOPress active it
writes to their field and prints nothing. Unfilled template values such as %%
excerpt%% are never printed.
* FIX: plain Gutenberg content was wrongly detected as built with a page builder.
* FIX: restoring or writing content through Amaso could corrupt backslashes and
accented characters in some cases.
* FIX: uninstall now removes all of Amaso’s tables, options and saved conversations.
#### 1.0.20 — 2026-09-27
* NEW: Assistant tab (Amaso Optimize Assistant) — a chat built into Amaso’s own
admin, backed by the same tools the MCP server exposes to an outside client.
It runs your own configured Claude key server-side, so no external app or MCP
client is needed for day-to-day questions and actions; every tool call it makes
is shown in the conversation as it happens. Free, like the rest of the BYOK model.
* NEW: MCP/Assistant can now write a full blog article draft on a topic (grounded
in your real business profile, always saved as a draft — never published automatically)
and can preview then apply an FAQ section to help a page’s GEO score, in the
same reviewed-before-saved pattern the existing Content Audit fix flow already
uses.
* NEW: Settings AI Engines MCP now has a one-click “Generate an Application Password
for MCP” button, a “Test connection” button that verifies the connection live
from the browser, and a ready-to-copy Claude Desktop configuration snippet.
* FIX: the MCP “Test connection” button could fail with an unrelated 401 because
the browser’s own logged-in session cookies were sent alongside the Application
Password, triggering WordPress’s cookie nonce check before the password was even
considered.
#### 1.0.19 — 2026-09-27
* NEW: MCP server, off by default. Turn it on in Amaso Settings AI Engines and
paste the connection URL into Claude, ChatGPT or any other MCP client (using
a WordPress Application Password — no separate key to create). Your assistant
can then read this site’s GEO score, tracked keywords, citation stats, business-
page audit, site structure and real searches, and — only when you ask it to and
see it happen in the conversation — track a keyword, set a page’s search description,
or add structured data through the guided Schema builder. Free in both editions;
nothing here is gated by plan.
* NEW: every MCP tool call is a single, explicit, named action, validated field
by field before anything runs — there is no open-ended “do whatever seems right”
tool.
* FIX: the business-pages audit occasionally returned a stale “limit” figure when
serving a cached result for a smaller request than the one already cached.
#### 1.0.18 — 2026-09-24
* FIX: activating the plugin now schedules the weekly automated check correctly.
The weekly interval was not yet registered at activation time, so the schedule
silently failed while the plugin recorded a next run that did not exist.
* SECURITY: opening the Content Audit page or the post editor no longer saves GEO
scores. Scores are stored only when a post is saved, when you click “Rescan all”
or “Re-analyse” (both nonce and permission checked), or by a background batch
after an update.
* SECURITY: the GEO score saved alongside a post no longer depends on an optional
nonce; it reads no request input and checks that the user can edit the post.
* IMPROVED: the Content Audit filter tabs carry a nonce.
* IMPROVED: the AI Citations screen’s script and styles are now loaded as files
through WordPress instead of inline tags; JSON-LD is printed with WordPress’s
own script-tag helper.
* FIX: the Terms & privacy link in this readme pointed to a page that does not
exist.
#### 1.0.17 — 2026-09-24
* FIX: WordPress Plugin Check reported four errors in the guided Schema builder(
a text-cleaning function WordPress discourages). They are fixed: text typed into
a Schema form field is now cleaned with WordPress’s own function.
* IMPROVED: code-quality clean-up flagged by Plugin Check, with no change in behaviour.
Queries on the plugin’s own tables now state in place why they are safe, the
two places that read posted data say how it is cleaned, and the requests that
ask PHP for more time (asking several AI engines, scanning many pages) go through
one helper instead of five copies.
* FIX: the kinds of business offered in the guided Schema form (Restaurant, Hotel,
Pharmacy…) can now be translated; they could not be extracted before.
* FIX: on the Lite edition, Settings and the setup checklist no longer raise PHP“
undefined array key” warnings (visible with WordPress debugging on) when there
is no Search Console detector to describe.
#### 1.0.16 — 2026-09-22
* FIX: Schema Markup (“Structured data about the business is switched off”) no
longer accuses your own settings when it isn’t the cause. Every check is now
read from the published page itself — the one search engines and AI actually
receive — so a site where Yoast SEO, Rank Math or another SEO plugin already
writes the structured data is credited for it by name, instead of Amaso claiming
there is none.
* NEW: Guided Schema — add LocalBusiness, Service, Product, Event, FAQ, How-to
or Software structured data by filling in a form (name, address, phone, opening
hours, prices, questions and answers…), with one clear message per missing or
wrong field. No JSON-LD to write, and it works whether or not an SEO plugin is
also active.
* FIX: on a page built with a page builder whose content only exists on the public
site (Divi 5 and similar), Amaso now reads the published page itself for its
Schema check too, instead of silently seeing nothing.
#### 1.0.15 — 2026-09-21
* FIX: pages built with a page builder that renders only on the public site (Divi
5, Bricks, Oxygen…) showed “0 words” and a score of 16 in Content Audit, because
their content does not exist in the admin. Amaso now reads the published page
as a visitor gets it (main content only, without menu, sidebar or footer), keeps
the result for twelve hours and never asks more than a few pages per screen.
If the server refuses to reach its own address, the page is marked “not scored:
could not be read” instead of “Poor”.
* FIX: a page that is only a grid of articles (a blog page built with a page builder),
and the WooCommerce Shop page, are no longer scored or listed among your business
pages: they are listings, judged through what they list.
* FIX: on a site where Yoast SEO, Rank Math or AIOSEO writes the structured data,
the homepage check no longer says “Auto-Schema is switched off”: the SEO plugin
owns the schema.
#### 1.0.14 — 2026-09-21
* NEW: “How your site is organised” in Content Audit. Amaso now reads how WordPress
serves your content: which page is the homepage, whether a Blog page lists your
articles, your categories and tags, the content types your theme or plugins add,
and whether tag, author and date pages can be indexed. It keeps three kinds of
address apart: pages (the business), articles (your topics) and listing pages.
* NEW: it flags what goes wrong when they are mixed up: a homepage that is only
a list of latest articles, a homepage and Blog page that are the same page, articles
with no listing page, articles left in the default category, tags that hold a
single article, category pages with no introduction, author and date pages that
repeat the Blog page, and a missing XML sitemap. A one-page site with no articles
gets no findings.
* IMPROVED: nothing is guessed. Indexing is read from Yoast SEO and Rank Math settings;
with another SEO plugin it says “not readable” instead of blaming a setting it
cannot see.
* NEW: each finding becomes an Action Plan task and is marked verified once it
is no longer raised.
#### 1.0.13 — 2026-09-21
* NEW: “What people actually search”. Amaso can show the real searches around your
topics from Google Autocomplete (what people type; free, no key, in your language;
a local business is asked about its city, then its country). It is available
in Setup wizard step 2 and on the Keywords page, only runs when you click, and
gives no search volume or difficulty because Autocomplete has none. Documented
under External services.
#### 1.0.12 — 2026-09-21
* NEW: “Fix first: your business pages” in Content Audit and the Action Plan. Homepage,
services, contact, pricing, about and FAQ pages are checked for what each one
must say — a search description, enough text, a phone number a crawler can read,
a way to write (form, email or WhatsApp), prices, a clear next step, your city—
and listed most urgent first. Articles are not part of this list.
* NEW: pages are listed most urgent first: homepage, contact, services, pricing,
about, then FAQ. Amaso makes no claim about how Google treats a page unless it
has real data for it.
* NEW: the Action Plan tracks these pages one by one and marks a page verified
once a re-audit finds nothing left to fix.
* FIX: the homepage is scored on its own text — the titles and excerpts of the
articles a theme lists on it no longer count as homepage content.
#### 1.0.11 — 2026-09-21
* FIX: the setup wizard and Business Profile now read the site the way its owner
describes it — SEO title and description, tagline, menu, page and product names,
headings — instead of counting words across page-builder text. A WordPress-plugin
SaaS is no longer classified as a café, and “chatgpt perplexity” / “inside wordpress”
are no longer suggested as keywords.
* FIX: the business type is only pre-selected when the scan is confident (and shows
the words it was based on). Otherwise the wizard asks, because whatever it shows
is saved as the business profile that every other feature trusts.
* IMPROVED: keyword suggestions carry the reason they were chosen (“your homepage
SEO title”, “your menu”), only the strongest are pre-checked, the business’s
own city is added once (not “… Douala Douala”), and keywords are saved in the
site’s language instead of always “en”. English and French sites are supported.
* FIX: GEO Score and Content Audit no longer confuse pages and articles. Each item
is judged as what it is (article, homepage, service page, product, about, contact,
pricing, FAQ) — a Contact page is no longer asked for an author bio and external
citations. Legal, cart, login and account pages are not scored, so they never
appear as “poor content”; Autopilot no longer proposes fixes for them.
* NEW: Content Audit has Pages / Articles / Products tabs and a “Not scored” list.
* NEW: a saved API key can be replaced or removed from Settings API Keys (Remove
asks for confirmation).
* IMPROVED: business-type labels no longer carry emoji.
#### Unreleased
* FIXED: Remove a request header rejected by WordPress Playground networking, which
caused HTTP 400 on manual/automatic price checks. Preserve the cache-busting
URL, validated catalogue and consent settings.
* FIXED: Keep the last verified plan prices when the cache ages or a request fails;
show the last successful check and validate complete responses, including zero-
priced plans.
* NEW: Explicit, reversible automatic price checks on Upgrade page visits (12 hours),
off by default; manual checks remain available.
* CLARIFIED: Preserve the existing successful keyword-and-engine batch quota unit(
at least one stored variant), separate it from 1–5 variant requests and possible
retry/search costs, and explain that failed batches do not consume AMASO successful-
batch quota. Lite remains unlimited.
* DOCUMENTATION: Reconcile Lite’s included local/BYOK features and remove obsolete
Lite keyword, market and citation quotas. Separate Autopilot, GSC/GA4, Share
of Voice and PDF reporting from Lite; provider charges remain separate.
* CORRECTED: Describe scores as heuristic page checks and distinguish citations,
crawlers, referrals and business outcomes. No ranking, AI-indexing, conversion
or revenue guarantee is made.
* PRIVACY: Document optional provider processing, background schedules, public
output, stored configuration/private notes, export limits and IndexNow’s default-
off opt-in. Retain the explicit public-price check and disclose request metadata.
* DOCUMENTED: Local action plan with baseline/latest evidence, private notes, user
IDs and a journal capped at the latest 100 events; current notes/statuses are
stored separately.
* FIXES DOCUMENTED: Exact-host referral attribution, durable business corrections,
passive Divi content extraction and explicit query-filter preservation.
* Historical entries below are retained as release history; the current sections
above describe the updated behavior.
#### 1.0.10 — 2026-09-08
* CHANGED: Amaso now has its own dedicated domain, amasoai.com — replacing fosiarw.
com (Fosia Ltd’s agency site) as the license/pricing server referenced by this
plugin, and fokwasiaka.com (the developer’s personal domain) as the Author URI.
No functional change for Lite users: this build still makes zero outbound calls
except the two documented opt-in exceptions (your own AI provider key; the “Check
current prices” button), which now point at amasoai.com instead of fosiarw.com.
#### 1.0.9 — 2026-09-07
* NEW: SEO Rankings now has a “Striking Distance” panel — active keywords currently
ranking #11-#20 (page 2), the cheapest wins available, instead of only showing
a raw list mixed with harder long-shot keywords.
* NEW: Business Profile’s Deep Scan results now include a “Manual action list for
the GEO specialist” — concrete, numbered to-dos (write the N missing meta descriptions,
connect GSC, review auto-extracted keywords for generic/template noise) instead
of raw counts a human has to interpret themselves.
* FIX: a rejected/expired AI provider API key now shows an actionable message (“
this key was rejected — generate a fresh one and re-save it”) instead of just
echoing the provider’s raw error text.
#### 1.0.8 — 2026-09-07
* IMPROVED: reworded the plugin description and reordered the free feature list
to lead with the SEO fundamentals (keyword tracking, schema markup, IndexNow)
that make AI citation possible in the first place, instead of presenting AI-citation
features as a separate, disconnected track.
* IMPROVED: llms.txt is now described honestly as an unofficial, not-yet-widely-
adopted file — not “the standard” — and moved lower in the feature list, matching
its actual (unconfirmed) adoption by AI crawlers today.
#### 1.0.7 — 2026-09-07
* IMPROVED: the GEO Score meta box now shows a plain-language disclaimer — it’s
a heuristic on-page checklist correlated with AI citation, not a guarantee, and
ranking well in classic Google search is still the main prerequisite.
* IMPROVED: the Dashboard’s System Health panel now detects a WP-Cron event that
is scheduled but overdue (a common failure mode on low-traffic shared hosting
where WP’s pseudo-cron never actually fires) instead of showing a false “Scheduled”
green check.
* IMPROVED: Settings API Keys now has a step-by-step “get a free Gemini key in
under a minute” guide next to the Gemini field — no credit card required, the
most accessible of the four supported AI providers.
* IMPROVED: the Dashboard now presents SEO ranking and AI citation tracking as
one pipeline (SEO first, AI citations second) instead of two unrelated charts,
with a short explanation of why the former drives the latter.
#### 1.0.6 — 2026-09-07
* FIX: removed `suppress_filters => true` from every internal content-scanning
query (business profile scan, site discovery, llms.txt generation) — it bypassed
other active plugins’ query filters (e.g. a multilingual plugin’s language filtering)
with no real benefit, and Plugin Check flags it as an error. These queries now
behave like a normal WordPress query.
#### 1.0.5 — 2026-09-07
* NEW: the Upgrade screen has a “Check current prices” button — click it to fetch
the live Amaso Pro/Starter/Agency prices from fosiarw.com instead of the numbers
bundled with the plugin. Strictly opt-in: nothing is fetched automatically, and
this remains the only page in Amaso Lite that ever contacts a Fosia server without
you first adding your own third-party API key.
#### 1.0.4 — 2026-09-07
* IMPROVED: full pass on Plugin Check’s output-escaping findings — every dynamic
value echoed in the admin UI (counts, icons, exception messages) now goes through`
esc_html()`/`absint()`/`wp_kses()` at the point of output instead of relying
on earlier, harder-to-audit escaping.
* IMPROVED: `parse_url()` `wp_parse_url()`, `strip_tags()` `wp_strip_all_tags()`(
discouraged-function warnings).
* IMPROVED: a handful of `// phpcs:ignore` comments on already-safe, hardcoded-
table-name queries were incorrectly placed (on the statement’s first line instead
of the line the linter actually flags) and were not suppressing anything — corrected.
#### 1.0.3 — 2026-09-07
* FIX: two `%s` placeholders left unnumbered in a translatable string (missed in
1.0.2’s translators-comment pass).
* IMPROVED: the Settings API Keys layout — the Google Service Account card (JSON
textarea + setup guide) is now full-width instead of being paired with a much
shorter provider card, which left an awkward empty gap next to it.
#### 1.0.2 — 2026-09-07
* FIX: Deep Scan (full-site content analysis) is now genuinely unlocked in this
build — it’s pure local computation with no external service and no cost to provide,
so it’s no longer gated behind a plan check.
* FIX: this build no longer deactivates Amaso Pro (or vice-versa) automatically—
an incompatibility notice with a one-click link is shown instead, so only the
site admin decides.
* FIX: an unrelated helper plugin used on the developer’s own site (`site/amaso-
docs-cpt`) was accidentally bundled into this ZIP — removed from the build entirely.
* FIX: two broken links in the External Services section of this readme (IndexNow/
Bing privacy policy, Perplexity terms of service) now point to the correct, live
pages.
* FIX: a manually-entered JSON-LD schema value could break out of its `