

Dashboard: overall score, latest run, plugin / theme stack detection.
Aetos SEO is an audit plugin, not another meta-writer. It runs alongside
your existing SEO plugin (Rank Math, Yoast, AIOSEO, SEOPress, or any other)
and tells you what is actually broken, missing, or risky across technical SEO
and AI-readiness, then shows you a prioritized list of what to fix first.
Think of it as a second opinion that does not touch your meta titles, your
schema output, or your sitemap. It only reads, diagnoses, and reports.
Every SEO plugin tells you it is doing a great job. None of them tell you
when something is wrong outside of their own scope: a noindex left from
staging, a canonical pointing at the wrong domain, a schema that is valid
but does not list the right entity, an <h1> that does not match the
title, a robots.txt that blocks an AI crawler you actually want to be in,
or a sitemap that omits half your category pages.
Aetos SEO does that read across the whole rendered page, then ranks the
findings by severity so you can fix the highest-impact issues first.
dir correctness for Arabic / RTL sites.Every finding includes: a plain-language title, a severity badge (High /
Medium / Low / Info), the pages where it was detected, an “Open” / “Fixed”
status, guidance on how to verify the fix, and a “why this matters”
explanation. Results are shown directly in the Findings screen.
The plugin auto-detects RTL sites and switches the admin interface to
Arabic. Finding titles, severity levels, and “why this matters” copy are
all translated.
Pro is sold separately at aetosseo.com and is
uploaded to your site by you, like a separate premium add-on. The
WordPress.org edition is a complete local audit tool: it shows every finding it
computes in full, and you set the scan depth yourself in Settings (the default
is 50 pages, or set 0 to analyze every page on your site).
The WordPress.org edition diagnoses your technical SEO and AI-readiness.
Pro is for acting on what it finds and going deeper: advanced
answer-engine modules, industry modules, deeper content analysis, internal
page-opportunity prioritization, AI handoff reports with copy-paste prompts
for any AI assistant, and agency-style HTML / PDF / CSV reports. Pro audits
from inside WordPress too, and it does not connect your site to any external
SEO, analytics, or AI service.
The free edition does not automatically contact any third-party
service. Updates ship through WordPress.org like any other free plugin
(handled by WordPress core, not by this plugin).
During an audit, the plugin performs HTTP requests against your own
WordPress site to inspect your public pages, robots.txt, sitemaps, and
internal links. These are same-site requests; no page content leaves your
server. To run audits in the background it may also trigger WordPress cron
through a same-site loopback request to this same WordPress installation
(the standard WP-Cron mechanism); this never contacts Aetos servers or any
third-party API in the free edition. The admin interface also contains a few
user-clicked links to documentation, pricing, changelog, and support on
aetosseo.com — those open only when you click them; the plugin never
requests those pages itself.
Some checks look for analytics or tag-manager fingerprints already present in
your site’s rendered HTML. The plugin may recognize strings such as
googletagmanager.com, google-analytics.com, analytics.google.com,
connect.facebook.net, clarity.ms, clarity.microsoft, plausible.io,
cdn.plausible.io, cdn.segment.com, segment.com, posthog.com, matomo.js,
matomo.php, and piwik.js, plus the matching client-side API names these tools
place in page scripts (for example gtag, fbq, and _paq). These are
detection strings only: Aetos SEO does not contact those providers, does
not send them data, and does not load their scripts. If your public pages
already include one of those scripts, the plugin records that it was detected
so the audit can avoid false “analytics missing” findings.
To put findings in context, the audit also detects which SEO, performance,
caching, security, and page-builder plugins or themes are active on your site
and reads their settings from your local WordPress database through the
standard options API. This information is shown only inside your own WordPress
admin, to explain a finding (for example, that a caching plugin controls a
header the audit flagged). It is never transmitted anywhere, and the plugin
never contacts those plugins’ vendors.