AIUNSEEN AI Readability & SEO

Before you install

This plugin connects WordPress to AIUNSEEN Studio's hosted audit service. Crawling, AI review, report generation and paid file generation run there, not on your WordPress host. It is not an offline crawler or a self-hosted backend.

• WordPress 6.9+ and PHP 8.2+. Declared Tested up to WordPress 7.1. Use current security-patched versions. WooCommerce is optional.
• Administrator access and a supported site layout: single-site WordPress installed at the domain root, public HTTPS on the default port with no explicit port in the site URL, and the standard /wp-admin/tools.php location.
• Reachable public REST verification without stale caching or firewall interference, plus outbound verified HTTPS to the hosted service. Multisite, subdirectory installations and private/local domain layouts are unsupported.
• For automatic publication: PHP ZipArchive, readable directory checks, database capacity for the bundle and one previous revision, and working same-site HTTPS loopback requests with valid TLS certificates.
• Two independent limits: 10 MiB for ZIP archive downloads and 10 MiB for total declared expanded/decoded publication content. Both must pass. Host memory, database, request time, routing or caching limits can still prevent publication.

No shell access, Node.js, WordPress password sharing or customer-supplied OpenAI/Stripe API keys are required. Hosted availability is required for connection, audits, report/ZIP retrieval and checkout. Compatibility with every host, cache, firewall or later release is not guaranteed.

Quickstart

1. Install. Open Plugins > Add New > Upload Plugin, select the installable plugin ZIP, install and activate AIUNSEEN AI Readability & SEO. Do not install a documentation or screenshot ZIP as a plugin. Alternatively, upload the aiunseen-audit folder into wp-content/plugins and activate it.
2. Open the dashboard. Select AIUNSEEN AI Readability & SEO in the administrator sidebar. Existing Tools links remain available.
3. Connect deliberately. Read the external-service and privacy disclosures, then choose Connect my site. Activation alone sends no data. Connection sends the public site address, site-scoped credential and temporary verification challenge over HTTPS; the service checks a temporary public REST response. Connecting does not start an audit.
4. Choose a plan. Start a free audit or separately buy a matching hosted credit when checkout is available. The service fetches public pages; do not submit private content.
5. Choose email, or leave it off. If available, select Email me when this audit finishes, type an address and choose Yes in the local Yes/Edit review. Edit returns to the field without starting the audit. Blank or unchecked means no email; invalid addresses must be corrected or cleared. No account or Administration Email Address is used automatically.
6. Review the result. Return to the dashboard for status and open the ready report. Review severity, evidence, coverage and recommended actions. For a paid audit, download its unexpired verified ZIP or preview optional publication. A preview alone publishes nothing.

The hosted mail server sends optional completion email, not WordPress. No WordPress SMTP keys, mail plugin or inbox verification is needed. If hosted email is unavailable, use the dashboard; there is no WordPress-mail fallback. Sender acceptance is not guaranteed inbox delivery. Sidebar status depends on WordPress scheduled tasks and navigation/refresh, not instant cross-page updates.

Hosted audit options

Paid credits are one-off Stripe purchases, not subscriptions, available only when hosted checkout is enabled. They pay for hosted processing, not unlocking locally included code. Credits must match the selected paid tier.

The free allowance is two accepted jobs per registrable domain per UTC day, shared across subdomains and including failed jobs. It resets at midnight UTC and is separate from the public website's allowance. Only one audit per installation may be queued or running at a time.

Page limits are maxima, not promised coverage. Discovery, permissions, fetch failures and resource limits affect results; additional resource/link checks are bounded. Reports display the fields supplied by the service without a separate local paid-feature filter.

A matching paid credit is reserved when an audit starts. Paid delivery requires both report and verified ZIP. After at most two attempts, terminal failure returns the credit on hold for support review, not immediate reuse or an automatic cash refund. Each credit has a limited lifetime AI allowance; retries and support review do not reset it or guarantee another attempt.

Publish or install manually

Option A: Manual installation

1. Open a ready paid audit and download its verified ZIP before expiry. Unzip it locally and read READ-ME.txt.
2. In your hosting File Manager, open the website root and enable hidden-folder visibility.
3. Upload only the contents of website-root, including hidden .well-known and its contents, into the website root. Do not upload the enclosing website-root folder.
4. If any destination already exists, stop. Review the conflict, take a backup and approve any replacement separately. Ask your website administrator to handle it when appropriate.

Manual file changes require your own backups and are not covered by plugin rollback.

Option B: Automatic virtual publication

1. For a ready paid audit with an unexpired verified ZIP, select Check & Preview Publishing under Auto Publish AEO files.
2. Review the checked public-file preview. Approval is bound to the exact archive, audit, site and current local publication.
3. Explicitly approve publication. Opening the preview does not publish. Check the resulting live status and public responses.

The fixed checked routes are /agents.md, /llms.txt, /llms-full.txt, /ai-sitemap.json, /services.json, /products.json, /packages.json, /pricing.json, /actions.json, /page-inventory.json and /.well-known/agent.json.

Existing files, symbolic links, occupied routes, unreadable directories and unverifiable responses block publication. Redirects block it except supported WordPress trailing-slash normalization. The plugin does not overwrite or merge existing files, edit posts or write files to the web root. Approved content is served virtually from the WordPress database only on exact, query-free GET/HEAD routes where WordPress would otherwise return 404.

After switching, live response types and checksums are verified. Failure attempts recovery only if that publication is still current; failed content may briefly be public. One previous managed revision is retained. Use Restore previous local publication when available, or Remove local publication if none exists, and review/approve the action. Restoration requires fresh checks. External caches and later routing changes can affect visibility; removal does not guarantee a 404 everywhere. Neither action restores physical files changed manually.

Expiry & retention

• Free reports: five days after completion.
• Paid reports: 30 days after completion.
• ZIP downloads: seven days after completion, independently of reports.

For reports, creation time is the fallback if completion time is unavailable. ZIP expiry is based on completion time. Save needed files before expiry. Expired content becomes unavailable immediately; stored-content cleanup runs at service startup and hourly. Structured audit diagnostics are pruned after 30 days.

Expiry is not deletion of all records. Installation records, audit metadata, credit/payment history, lifetime AI allowances, logs, backups and provider records do not share these expiry periods. Downloaded copies and local publications do not expire with hosted reports. Ask support separately about hosted deletion or credential revocation.

Troubleshooting

Connection verification fails

Read the orange error notice inside the connection panel. Distinct problems appear in separate boxes. Localhost and private or IP-literal addresses cannot connect: use a publicly accessible HTTPS domain. Confirm the root single-site public HTTPS layout, no explicit port and standard administrator path. Ask your host to check public REST reachability, valid TLS, outbound HTTPS, security rules and stale caching. Do not share WordPress credentials or disable TLS verification.

Other action errors or an interrupted request

Read the orange notice beside the relevant controls. Audit-specific errors stay with their report. Activity shows up to ten recent locally observed updates and safe error references; action errors are visible to the administrator who encountered them. It is not a complete payment or server history. If an audit submission or checkout is interrupted, refresh and check its current status before trying again. A connection or status error does not prove that an audit or payment failed.

Free allowance reached or audit already running

The two-job limit includes failures and subdomains. Wait for midnight UTC or choose a separately purchased matching paid tier. Wait for an existing queued/running installation job to finish; repeated submissions do not bypass limits.

Paid credit returned but unavailable

A terminal failure can leave a returned credit held for support review. Contact support with the audit reference. A hold is not a cash refund or a promise of another attempt.

No ZIP or an expired download

Free audits are report-only. Paid delivery requires a ready verified package, and its seven-day expiry can precede the report's 30-day expiry. Use a previously downloaded copy if you have one; report availability does not extend the ZIP deadline.

Publishing preview or live verification fails

Check ZipArchive, both 10 MiB limits, readable directories, database capacity and same-site HTTPS loopback with valid TLS. Review existing route/file conflicts. For routing failures, open Settings > Permalinks and Save Changes without changing the selected structure, then retry preview. This is not a guaranteed fix. Ask the host about redirects, caching and routing if it persists. Do not overwrite occupied paths or disable TLS; consider reviewed manual installation instead.

No email or delayed sidebar status

Use the dashboard. Email must be offered, selected, typed and approved for that audit. Check spam folders; sender acceptance does not prove inbox delivery. WordPress SMTP setup will not repair hosted mail. Ask your host about scheduled tasks if dashboard/sidebar tracking is delayed.

Interface reference

Open the individual landscape illustrations below. Synthetic demonstration data and balances are not customer reports or credits included with purchase. The approval illustration shows the review step, not proof that files have been published. These local image links work offline when the guide and its images folder are kept together.

1. Connection onboarding
2. Free and paid hosted audit plans
3. Report summary
4. Categorized findings and evidence
5. Download and publication choices
6. Public-file preview
7. Explicit publication approval controls

Included files

The installable ZIP contains these files under aiunseen-audit/:

• aiunseen-audit.php
• connection.php
• lifecycle.php
• notifications.php
• feedback.php
• publication.php
• uninstall.php
• assets/aeo-mark.svg
• assets/dashboard.css
• assets/dashboard.js
• languages/aiunseen-audit.pot
• readme.txt
• LICENSE.txt

License: GPL-2.0-or-later, with the complete GNU GPL v2 text included. The public documentation is supplied separately. Hosted backend, crawler, AI/payment infrastructure, provider credentials and paid credits are not included. Reports and generated paid ZIPs are produced separately by the service. Test fixtures and internal developer documentation are not runtime-package contents.

Privacy & limitations

External processing

Starting an audit authorizes remote fetching and processing of public URLs, page content and resources. The crawler does not sign in to WordPress. The service processes findings, audit identifiers, installation and credit/payment history and generated files. Connected dashboard visits check connection; audit, status, report, ZIP and checkout requests contact the service as needed. Protect the site-scoped credential stored in your WordPress database and backups. Do not submit private content.

Paid AI review uses OpenAI through the hosted service. Selected finding titles, numeric identifiers, priorities and observation counts are sent, not raw page text, URLs or extracted evidence. Response storage is disabled for these requests, but provider policies still apply; zero provider retention is not promised.

Separate credit purchases redirect to Stripe Checkout. Enter payment details at Stripe, not in the plugin. The service retains payment references and credit, refund and dispute history. Only a completion-email address explicitly typed and approved for an audit is sent privately over verified HTTPS; it is not put in URLs, analytics, browser storage, public reports or publication files.

• AIUNSEEN privacy information and service terms
• OpenAI privacy, services agreement and API data controls
• Stripe privacy and services agreement

Languages and evidence

The interface, report headings, controls, local errors and publishing instructions are translation-ready using the aiunseen-audit text domain and included POT template. Complete language packs are not included. Generated findings, evidence and hosted-service narratives remain English; interface catalogs do not translate hosted completion emails or generated AEO files. Full RTL verification or multilingual report generation is not promised.

AI review prioritizes selected findings, not every page or claim. Evidence checks recheck up to five detected price conflicts and five sampled broken same-site links; blocking results prevent AI review for that attempt. A verified ZIP has passed implemented checks against observed evidence, not certification of every fact. Review findings and generated content before acting. No guarantees of full accuracy, coverage, rankings, traffic, AI visibility, citations, delivery time or uninterrupted availability.

Disconnect, deactivate or delete

Disconnect withdraws local connection consent but does not revoke hosted credentials, cancel hosted audits/email, delete hosted history, refund payments or remove publications. Local publication management remains available while disconnected. Deactivation stops virtual serving and retains publication state; it may serve again after reactivation, while hosted connection requires renewed consent. Deleting the plugin through WordPress removes its local single-site data, not hosted history or physical website files, and does not issue refunds. Arrange hosted deletion/revocation separately with support.

Support & changelog

Use Contact support in the plugin or the AIUNSEEN contact page. Include the audit reference, relevant version, symptoms and a redacted error message. Never send passwords, credentials or private customer data. No response time is guaranteed. External support and policy links require internet access; this guide itself does not.

0.1.15

• Display connection failures inside the connection panel with accessible, prominent orange notices, including clear public HTTPS requirements for unsupported local environments.
• Stack distinct errors without replacing earlier messages; show audit, checkout, report, download and publication failures beside the relevant controls.
• Translate known hosted error codes locally, use safe fallback messages, and keep uncertain submission/payment outcomes explicit.
• Add bounded, administrator-scoped action error history to the latest-ten Activity view without storing error bodies or email addresses.
• Keep authorization, ownership, nonce, TLS and package validation checks unchanged.

Audit-specific error notices remain attached to the selected report, including publication errors. This separate documentation was synchronized on 10 November 2026; the audited plugin ZIP is unchanged.

0.1.14 (previous release)

Documentation-only resubmission: consolidate requirements, included files, setup, hosted costs, publication prerequisites and retention in the public listing; add an offline quickstart and clearer interface-preview coverage. No new runtime features or changes to hosted tiers, charges, limits or publication behavior.

0.1.13

Made PHP/JavaScript interface strings and the report framework translation-ready; included a POT template and standard WordPress script translation loading. Generated findings and evidence remain English.