| 开发者 | ngofeed |
|---|---|
| 更新时间 | 2026年8月27日 04:07 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
Yes. A CrawlSage account is required to use the connected CrawlSage service and cloud-powered SEO features.
Supported SEO changes are applied through an authorized workflow. Administrators can review recommendations before applying supported optimizations.
CrawlSage opens the CrawlSage web application for authentication. The browser returns a short-lived authorization code and state value. WordPress then exchanges that authorization code directly with the CrawlSage API. Long-lived authentication tokens are not sent through browser URLs.
The plugin does not initiate CrawlSage service requests before an administrator starts the connection process.
Depending on the detected issue and supported WordPress configuration, CrawlSage can provide workflows for SEO titles, meta descriptions, focus keywords, image alt text, and other supported SEO audit recommendations.
Yes. CrawlSage is designed around a review and authorization workflow for supported optimizations.
CrawlSage maintains fix history for supported deployments and can roll back supported changes when rollback information is available and the current WordPress state permits it.
No. CrawlSage does not require or transmit your WordPress account password.
No. Payment processing and billing are handled by the CrawlSage service. Payment-card details are not stored by this WordPress plugin.
Plugin data and connection information are preserved so CrawlSage can resume after reactivation. Scheduled CrawlSage events are cleared according to the plugin lifecycle.
Plugin credentials, settings, security transients, and options are removed. CrawlSage custom tables are retained by default unless Delete CrawlSage data on uninstall is enabled before uninstalling.