aeocontent

When someone asks ChatGPT, Perplexity, Claude, Gemini, or Google AI Overview a question your website can answer, do they cite you or someone else? Most websites never show up in AI-generated answers because their pages are not structured for extraction, trust, and citation.
AEO Content AI Studio helps WordPress teams understand what AI engines see, what they ignore, and what to fix first. The scoring methodology is built on published research into how large language models select sources, not on SEO heuristics or opinions.
It connects your site to <a href="https://www.aeocontent.ai" rel="nofollow ugc">aeocontent.ai</a> for site audits, AI Visibility tracking, prioritized rewrite opportunities, and WordPress publishing.
<h4>Know Your Score</h4>
The plugin audits your entire site against 48 criteria developed from research into how large language models choose which sources to cite. Every page gets a score from 0 to 100 and a letter grade (A through F) so you know exactly where you stand.
The audit looks at what actually matters for AI citation: whether your content says something original, whether it can be cleanly extracted as an answer, whether it carries enough entities and data to be trustworthy, and whether it is structured in a way AI engines can parse. Content that just restates what ten other sites say gets penalized. Content with original insights, named frameworks, and clear answer patterns gets rewarded.
<h4>See Who Is Getting Cited Instead of You</h4>
The AI Visibility stage monitors your most important queries across five engines every day. You see exactly which prompts return your pages, which ones cite a competitor, and how your visibility changes over time. No more guessing whether your optimization work is paying off.
<h4>Fix What Matters First</h4>
The audit does not just tell you what is wrong. It ranks every opportunity by impact so you know which pages to fix first. Rewrite candidates show the weakest pillar for each page. Opportunities show the highest-leverage fixes across your site. You focus your time where it moves the needle the most.
<h4>Publish Optimized Content</h4>
The platform can read your existing posts, optimize them for AI citation readiness, and publish the updated content back to WordPress. Categories, tags, featured images, and FAQ schema are handled automatically.
<h4>Features</h4>
<ul>
<li>One-click Google sign-in to create your account and connect your site</li>
<li>48-criteria site audit with per-page scoring and letter grades</li>
<li>AI Visibility tracking across ChatGPT, Perplexity, Claude, Gemini, and Google AI Overviews</li>
<li>Daily visibility monitoring with citation tracking and competitor comparison</li>
<li>Rewrite candidates ranked by priority with weakest-pillar breakdown</li>
<li>Opportunity list with impact scores and fix guidance</li>
<li>Full page inventory with AEO Rank, word count, and inbound links</li>
<li>Run site audits from WordPress admin with real-time progress</li>
<li>Content publishing with AI optimization back to WordPress</li>
<li>Zero frontend footprint. Nothing added to your public pages</li>
</ul>
<h4>How It Works</h4>
<ol>
<li>Install the plugin and click Continue with Google</li>
<li>Your account and site connection are created in one click</li>
<li>The platform crawls your site and scores every page against the full criteria set</li>
<li>Review your audit, fix the highest-impact issues, and track visibility improvements</li>
<li>Optimized content can be published back to WordPress directly from the platform</li>
</ol>
<h4>Onboarding</h4>
Start from AEO Content in your WordPress admin sidebar:
<ol>
<li>Click Continue with Google to sign in or create an account</li>
<li>The popup closes automatically and your site is connected</li>
<li>Or use Create Account Manually / I Already Have an Account for email-based setup</li>
</ol>
You can also start from AEO Content AI Studio, enter your site URL, and finish the connection from WordPress admin.
<h4>External Service</h4>
This plugin connects to the AEO Content platform at <code>aeocontent.ai</code> for the following purposes:
<ul>
<li>Registration (on initial setup): When you connect your site from WordPress admin, the plugin sends your site URL to <code>https://www.aeocontent.ai/api/v1/plugin/register</code> to register the connection. No content or personal data is transmitted.</li>
<li>Heartbeat (periodic): The plugin sends your site URL, plugin version, WordPress version, PHP version, and enabled features to <code>https://www.aeocontent.ai/api/v1/plugin/heartbeat</code>. This keeps the platform in sync and delivers any pending updates. No personal data or site content is transmitted.</li>
<li>Audit Report (on demand): When you view the Audit Report page, the plugin fetches your site’s audit data from <code>https://www.aeocontent.ai/api/v1/audits/{site-slug}</code>. This returns scoring data and recommendations generated by the platform. Audit results are cached locally for 1 hour.</li>
<li>AI Visibility (on demand): When you open the AI Visibility stage, the plugin fetches your site’s visibility snapshot from <code>https://www.aeocontent.ai/api/v1/visibility/{site-slug}?include=timeline</code>. This returns citations, engine coverage, competitors, alerts, and score trend history. The plugin prefers this dedicated visibility report over stale audit-embedded visibility data.</li>
</ul>
All communication uses HTTPS and authenticated platform credentials. The platform’s <a href="https://www.aeocontent.ai/terms" rel="nofollow ugc">Terms of Service</a> and <a href="https://www.aeocontent.ai/privacy" rel="nofollow ugc">Privacy Policy</a> apply to data processed on the platform side.
<h3>Privacy</h3>
This plugin connects to the external service at aeocontent.ai. See the “External Service” section in the Description for full details on what data is transmitted and when.
The plugin stores the IP address of incoming API requests in the activity log for security and diagnostic purposes. Log entries are automatically deleted after 90 days. No cookies are set, no users are tracked, and no analytics are collected on the frontend.
Local logging remains available for secure platform-to-plugin diagnostics, but user-facing operational logs are no longer rendered inside the WordPress admin UI.

AEO Content AI Studio

Track AI citations, audit your site for answer-engine readiness, and publish optimized drafts back to WordPress.

Esteban

Aipatch Security Scanner is a modular security audit engine built for site owners, developers, and AI-powered agents who need deep visibility into WordPress security posture — without the bloat of all-in-one security suites.
<h4>Why Aipatch Security Scanner?</h4>
Most WordPress security plugins are either too simple to be useful or too heavy to be practical. Aipatch takes a different approach:
<ul>
<li>Audit-first architecture. Every check is a standalone, testable module that returns structured findings with severity, confidence, evidence, and fingerprints.</li>
<li>Built for automation. 23 MCP abilities expose the full audit, scanning, and remediation surface to external AI agents — making Aipatch the first WordPress security plugin designed for agentic workflows.</li>
<li>Zero external dependencies. Everything runs locally. No accounts, no cloud services, no API keys required.</li>
<li>Reversible by design. Every automated remediation stores rollback data so you can undo any change with one click.</li>
</ul>
<h4>Core Capabilities</h4>
36-Point Security Audit
Aipatch runs 36 automated checks across 8 categories — core, plugins, themes, users, configuration, server, access control, and malware surface:
<ul>
<li>Outdated WordPress core, plugins, and themes</li>
<li>Default admin username, excessive admin accounts, inactive admin users, user ID 1 exposure</li>
<li>XML-RPC, file editor, debug mode, debug log, REST API exposure, directory listing</li>
<li>PHP version, HTTPS, file permissions, security headers (X-Frame-Options, CSP, etc.)</li>
<li>Database prefix, sensitive files, PHP execution in uploads, auto-update configuration</li>
<li>Salt key strength, cron health, cookie security flags, CORS, application passwords</li>
<li>Exposed backup files, phpinfo files, uploads directory indexing, default login URL</li>
<li>Database credential security, file installation permissions</li>
</ul>
Every finding includes a severity (critical / high / medium / low / info), confidence score, human-readable explanation, and actionable recommendation.
Weighted Security Score (0–100)
A logarithmic scoring engine computes an overall security score and per-area breakdown across six risk dimensions: software, access control, configuration, infrastructure, malware surface, and vulnerability exposure. Severity weights and confidence multipliers ensure the score reflects actual risk, not just issue count.
Multi-Layer Malware File Scanner
A three-layer file scanner (content 55%, context 25%, integrity 20%) with 27 detection signatures, Shannon entropy analysis, and malware family classification detects:
<ul>
<li>Code execution patterns: eval(), assert(), create_function(), preg_replace /e</li>
<li>System command functions: shell_exec, exec, passthru, backtick operators</li>
<li>Obfuscation techniques: base64 encoding, hex encoding, str_rot13, gzinflate chains, chr() concatenation, variable variables, suspiciously long lines</li>
<li>Network/exfiltration: cURL execution, fsockopen, remote file_get_contents</li>
<li>Known backdoor signatures: c99, r57, WSO, b374k, weevely, FilesMan</li>
<li>WordPress-specific threats: unauthorized admin creation, critical option injection, security function removal</li>
</ul>
Scanning runs in batches via an async job system with configurable batch sizes — safe for shared hosting.
Files are classified into 11 malware families (web shell, obfuscated loader, dropper, persistence backdoor, cloaked PHP, code injector, and more) with confidence scores and remediation hints.
WordPress Core Integrity Verification
Verifies every core file against official checksums from api.wordpress.org. Detects modified core files (checksum mismatch), missing core files, and unexpected files planted in wp-admin/ or wp-includes/. Core tampering findings are automatically escalated to critical severity with zero false-positive likelihood.
File Integrity Baseline
Build a known-good hash baseline of all PHP files in your installation. Diff against it at any time to detect modified, deleted, or newly added files. Origin detection distinguishes core, plugin, theme, and upload files.
Vulnerability Intelligence
A local knowledge base of known plugin, theme, and core vulnerabilities with a database-backed caching layer for fast lookups. Provider architecture allows extending with external feeds.
One-Click Remediation with Rollback
Apply fixes directly from findings — change WordPress options, delete suspicious files, rename files, patch file contents, or add .htaccess rules. Every automated action stores a full rollback payload so you can reverse any change. Manual remediations can be logged for audit trails.
Six supported action types: <code>wp_option</code>, <code>delete_file</code>, <code>rename_file</code>, <code>file_patch</code>, <code>htaccess_rule</code>, <code>manual</code>.
Hardening Module
Five toggleable hardening rules with clear explanations and compatibility warnings:
<ul>
<li>Disable XML-RPC — blocks external XML-RPC requests and removes X-Pingback header</li>
<li>Hide WordPress Version — removes version leaks from source, RSS feeds, scripts, and styles</li>
<li>Restrict REST API — limits sensitive endpoints to authenticated users</li>
<li>Block Author Scanning — prevents user enumeration via author archives</li>
<li>Login Brute-Force Protection — rate-limits login attempts per IP with configurable thresholds and lockout duration</li>
</ul>
Persistent Findings Store
All audit findings persist in a dedicated database table with automatic deduplication by fingerprint. Track findings over time — dismissed findings stay dismissed across scans; resolved findings reopen if the issue reappears.
Security Event Logging
Every scan, hardening change, remediation, and significant event is logged to a dedicated table. Logs are filterable by severity and exportable as CSV.
WordPress Site Health Integration
Adds 6 security tests to the built-in Site Health screen: file editor, debug mode, XML-RPC, admin username, SSL, and overall security score.
Performance Diagnostics
Built-in performance profiling to identify slow queries, high memory usage, and resource bottlenecks related to security operations.
REST API
10 authenticated endpoints under the <code>aipatch-security-scanner/v1</code> namespace for triggering scans, retrieving summaries, toggling hardening, exporting logs, and running performance diagnostics.
<h4>MCP Surface for AI Agents (23 Abilities)</h4>
Aipatch exposes 23 structured abilities via the WordPress Abilities API — making your site’s security surface fully accessible to external AI agents, coding assistants, and orchestration tools:
By default, only aipatch/audit-site is enabled. You can enable additional abilities from Aipatch Security Scanner -> Settings -> MCP Abilities.
Audit & Scanning
<ul>
<li>aipatch/audit-site — Run a full 36-check security audit with scored findings</li>
<li>aipatch/audit-suspicious — Quick heuristic scan for suspicious files</li>
<li>aipatch/start-file-scan — Launch an async multi-layer malware scan job</li>
<li>aipatch/process-file-scan-batch — Process next batch of files in a running scan</li>
<li>aipatch/file-scan-progress — Check file scan progress</li>
<li>aipatch/file-scan-results — Retrieve enriched scan results with family, reasons, layer scores</li>
<li>aipatch/get-scan-summary — Comprehensive latest scan summary with classification breakdown</li>
<li>aipatch/list-suspicious-files — List suspicious files from latest scan (no job_id needed)</li>
</ul>
Integrity & Baseline
<ul>
<li>aipatch/verify-core-integrity — Verify WP core files against official api.wordpress.org checksums</li>
<li>aipatch/baseline-build — Build or refresh the known-good file hash baseline</li>
<li>aipatch/baseline-diff — Compare current filesystem against stored baseline</li>
<li>aipatch/baseline-stats — Baseline statistics by origin type</li>
<li>aipatch/get-baseline-drift — Combined baseline drift + core integrity report</li>
</ul>
Findings & Monitoring
<ul>
<li>aipatch/list-findings — Query persistent findings with status/severity/category filters</li>
<li>aipatch/findings-stats — Aggregate finding statistics</li>
<li>aipatch/findings-diff — New and resolved findings since a point in time</li>
<li>aipatch/get-file-finding-detail — Single finding with decoded metadata, layer scores, family</li>
<li>aipatch/dismiss-finding — Dismiss a finding as accepted risk</li>
</ul>
Remediation
<ul>
<li>aipatch/apply-remediation — Apply a security fix with rollback support</li>
<li>aipatch/rollback-remediation — Undo a previously applied fix</li>
<li>aipatch/list-remediations — List remediation history with filters</li>
</ul>
Jobs & Status
<ul>
<li>aipatch/list-jobs — List scan/audit jobs with filters</li>
<li>aipatch/get-async-job-status — Check async job status and retrieve results</li>
</ul>
20 abilities are read-only; only 3 (dismiss, apply-remediation, rollback) modify site state. All abilities include typed input/output schemas, permission checks (<code>manage_options</code>), and structured error responses.
<h4>What Aipatch Does NOT Do</h4>
<ul>
<li>It is NOT a firewall or WAF — it does not filter incoming traffic.</li>
<li>It does NOT intercept frontend requests or affect page load performance.</li>
<li>It does NOT phone home, require an account, or send data externally.</li>
<li>It does NOT inject ads, upsells, or nag notices.</li>
</ul>

Aipatch Security Scanner

WordPress security scanner with 36 checks, malware scanning, core integrity verification, remediation, and 23 MCP abilities.

AEO Content AI Studio vs Aipatch Security Scanner