AI4Ranks SEO
| 开发者 | ai4ranks |
|---|---|
| 更新时间 | 2026年11月7日 23:44 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
AI4Ranks SEO manages local metadata safely and can link your site to AI4Ranks Cloud after you explicitly connect your account.
Features include:
- SEO audits for posts, pages, and WooCommerce products.
- AI-assisted meta title and meta description generation.
- Local SEO title, description, canonical, and robots fields that work while disconnected.
- Safe connector-only mode when another known SEO engine is active.
- Metadata revision history, audit events, optimistic conflict checks, and rollback APIs.
- Content scoring with actionable checks.
- Keyword suggestions and keyword workflow statuses.
- Content sync to the AI4RANKS dashboard.
- SEO score columns in WordPress content lists.
- Shortcodes for displaying generated SEO fields where you choose.
- Bulk sync for published content.
安装:
- Upload ZIP via Plugins > Add New > Upload Plugin
- Activate
- Go to AI4RANKS menu
- Enter email + password, click Connect
- Showing up to 50 recently published items. Click "Sync to AI4RANKS" to send content
- Use the AI4RANKS dashboard to generate and manage SEO
常见问题:
Does the plugin send data automatically?
Nothing is sent merely because the plugin is activated. Connecting sends account and site-linking information, stores the returned site token locally, provisions an optional Visitor Intelligence site key, and sends a capability manifest. Connected administrator screens may request account status or workspace summaries. Content is sent when an administrator starts a sync or AI-assisted action; a connected AI4RANKS workflow may also request the plugin's authenticated published-resource endpoint. Visitor data is sent only after an administrator enables Visitor Intelligence and the visitor gives affirmative consent.
Does the plugin store my AI4RANKS password?
No. The password is used only during connection. The plugin stores the site token returned by AI4RANKS.
Can I disconnect?
Yes. Use AI4RANKS > Settings > Disconnect. Deactivation preserves settings and history so reactivation is safe.
更新日志:
4.6.12
- Require a local WordPress administrator to review and apply each exact cloud-originated write proposal.
- Keep automatic cloud writes disabled and invalidate proposals after disconnecting or reconnecting.
- Preserve password characters by validating strings and removing WordPress slashes only.
- Check the target post's edit_post capability in both revision route permission and restoration.
- Select workspace navigation from the active page callback instead of query input.
- Cache immutable revision lookups briefly while checking current edit permissions on every restore.
- Report revision lookup database failures without caching them as missing revisions.
- Reject malformed REST metadata and invalid setup steps before writing data.
- Require successful transaction locks and byte-exact conditional solution updates.
- Preserve literal backslashes in metadata and solution titles.
- Verify AJAX request shapes, handle revision save failures, and cache revision history by version.
- Preserve WordPress 5.3 database-query compatibility and use the supported REST request attribute API.
- Exclude Python build tools and duplicate development files from the installable plugin archive.
- Sanitize and validate editor optimization plans, local SEO fields, and request paths at their input boundaries.
- Validate nested input types before storing metadata or using request values.
- Align the release ZIP directory and main plugin file with the
ai4ranks-seoslug and text domain. - Include the self-contained release builder and its used source inputs in
development/for transparent review and reproducible packaging. - Require short-lived, body-bound HMAC signatures and single-use nonces for all cloud-originated WordPress writes.
- Limit connected content creation to idempotent WordPress drafts and restrict optimization reads to published resources.
- Normalize cloud response data before it enters the admin UI and escape rendered values for their output contexts.
- Ship Visitor Intelligence browser code locally, require affirmative consent before any identifier or request, and honor excluded pages for analytics and replay.
- Document all AI4RANKS cloud and optional Visitor Intelligence connections, including consent, browser storage, and uninstall behavior.
- Escape FAQ structured data and visitor goal rules for their script contexts.
- Require WordPress 5.3 or later, matching the date functions used in scan history.
- Prevent features from loading on unsupported WordPress versions and show an administrator notice.
- Correct database table definitions for reliable activation and reactivation.
- Removed development-only source files from the distribution archive.
- Load all WordPress admin menu styles through the admin enqueue APIs.
- Use WordPress enqueue APIs for admin styles and restrict shortcode HTML tags to a fixed allowlist.
- Removed the optional image-file optimization feature from the WordPress.org distribution.
- Included the maintained source and build script with the release.
- Updated WordPress compatibility metadata and aligned the text domain with the directory slug.
- Removed the automated linking feature and all automatic outbound-link reporting from the WordPress.org distribution.
- Removed automatic post-publication sync; cloud actions require an administrator's explicit request.
- Added exact editorial previews, conditional single-field publication and restore for content, excerpts, focus keywords, schema and image alt text.
- Added five-minute HMAC write signatures with nonce replay protection.
- Added capability schema v6 for signed, idempotent approved writes.
- Cloud execution now uses a durable operation outbox with bounded reconciliation.
- Added durable idempotency receipts for approved metadata and canonical writes.
- Safe retries return the original verified receipt instead of applying a duplicate revision.
- Connector capability schema v5 advertises idempotent write support explicitly.
- Added approval-gated self-referencing canonical updates with exact revision checks, receipts, and rollback.
- Canonical capability support is advertised explicitly through connector schema v4.
- Added exact same-site 301/308 redirects for missing pages, with approval and guarded removal.
- Added approval-bound broken-link replacement and removal with exact body revision checks.
- Preserves link text, native revisions and public verification through AI4Ranks Optimization.
- Added controlled Renovation Estimator rendering with local calculations.
- Added authenticated draft-only create/update/rollback with version checks and retry deduplication.
- Prevent solution updates from replacing owner content or editing published pages.
- Added revision-bound keyword metadata updates and serialized cloud apply operations.
- Validate page and metadata versions before content writes; publish capability schema v3.
- Added revisioned, version-conflict-safe staged autofix metadata execution.
- Added authoritative full-content sync fields and SEO metadata versions.
- Added connector responses that confirm rollback support and rendered-output verification.
- Added safe SEO output ownership and competing-plugin detection.
- Added local Titles & Meta output, canonical AI4Ranks metadata keys, revisions, audit events, and rollback APIs.
- Added a versioned cloud capability manifest while preserving legacy connector compatibility.
- Changed AI metadata generation to proposal-first behavior.
- Hardened WordPress.org submission readiness.
- Enabled SSL verification for remote requests.
- Added stricter capability checks, sanitization, and escaping.
- Added external service and privacy documentation.
- Full pages, posts, and products support
- Content sync to SaaS (auto + bulk)
- Fetch and apply SEO data from SaaS
- Keyword Lab integration
- WooCommerce product support
- SEO audit, meta generation, content scoring
- Keyword suggestions
- Initial release