About this plugin
Can ChatGPT, Claude, Perplexity and Google’s AI features reach, read and
cite your site? Aetos SEO Audit answers that from inside WordPress, together
with the classic technical SEO defects that stop a page from being indexed or
quoted in the first place.
txt blocks the AI crawlers you actually want
(GPTBot, ClaudeBot, PerplexityBot, Google-Extended and others), whether
txt exists and says something useful, whether your structured data
names the entity behind the site, and whether your pages are built in passages
an answer engine can lift. Then it ranks every finding by severity so you know
what to fix first.
What it never does: it does not write meta tags, redirects, schema or
sitemaps, needs no account or API key, and sends nothing to an outside service.
It reads and reports, so it runs beside Rank Math, Yoast, AIOSEO or SEOPress
without conflict.
What the free edition checks
- AI readiness – AI crawler access in robots.txt, llms.txt, JSON-LD entity
coverage (Organization, sameAs, author, publisher), FAQ and HowTo schema,
heading structure for answer extraction and Open Graph completeness.
- Technical SEO – indexability, canonicals, robots directives, sitemaps,
redirects, broken links and HTTP error pages.
- On-page – titles, meta descriptions, headings, duplicates, and lang and
dir correctness for Arabic and RTL sites.
- Mobile, media and performance – viewport, alt text, oversized images,
lazy loading, cache headers and heavy assets.
- Analytics and security basics – GA4, Tag Manager, Clarity and Meta Pixel
detection, HTTPS, mixed content and exposed endpoints.
Every finding shows a severity (High, Medium, Low or Info), the pages where it
was found, why it matters, the fix steps and how to confirm the fix. You can
mark it done and follow its status from one audit to the next.
The admin interface is available in English and Arabic. Pick the language in
Settings.
Free and Pro
org edition is a complete local audit. It shows every finding it
computes in full, and you choose the scan depth in Settings (50 pages by
default, or 0 for every page).
com and
uploaded by you. It adds 22 deeper audit modules (answer-engine and AI Overview
patterns, question coverage, E-E-A-T, entity and GEO signals, e-commerce,
local, news and content depth), a redacted JSON bundle you can hand to ChatGPT
or Claude for a site-specific fix plan, a ranked list of the top open actions,
and client reports as printable HTML (save as PDF), Markdown and CSV. Pro also
runs inside WordPress and does not connect your site to any external SEO,
analytics or AI service.
External services
The free edition does not automatically contact any third-party
service. 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
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
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
com,
io,
js,
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.