| 开发者 | kapybara |
|---|---|
| 更新时间 | 2026年8月25日 13:02 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
src/), the PHP that ships with the plugin, and BUILD.md with the exact steps to reproduce the compiled build/ assets distributed here (npm install && npm run build). Every release is tagged there, for example v1.3.9.
External service: SnowSEO
This plugin requires an account at SnowSEO (https://snowseo.com) and communicates with the SnowSEO API at https://api.snowseo.com/v3 to function. Except for the public health check described below, communication begins only after a WordPress administrator connects the plugin with a SnowSEO site token. By connecting the plugin, you authorize the following data exchange:
Data sent from your WordPress site to SnowSEO:
/integrations/wordpress/validate-plugin-key) - the plugin API key (site token) you paste into Settings, your site URL, site title, site tagline, WordPress version, plugin version, and a flag indicating that the connection should be saved./integrations/wordpress/plugin-disconnect) - the plugin API key as an authentication header only./cms/publish) - the selected article slug, requested WordPress status, provider name, and plugin API key./cms/articles*) - pagination and status filters or the selected article slug, plus the plugin API key. SnowSEO returns the requested SnowSEO article data for display in the WordPress admin./integrations/wordpress/settings) - the plugin API key only./wp-json/snowseo/v1/posts-status, authenticated with the site token) - the site returns WordPress post IDs, statuses, publication dates, and permalinks. SnowSEO can request specific post IDs or, when no IDs are supplied, up to the 100 most recently modified posts./wp-json/snowseo/v1/posts/by-url, authenticated with the site token) - SnowSEO sends the selected public page URL, and the site returns the matching WordPress post or page ID, title, full content, status, and supported SnowSEO, Yoast, Rank Math, or SEOPress title, description, and canonical metadata. SnowSEO uses this data to prepare and apply the requested fix./wp-json/snowseo/v1/ping) - the site returns whether the plugin is reachable and its installed version. This endpoint does not return site content or credentials./wp-json/snowseo/v1/receive-publish, authenticated with your site token) - article title, HTML content (sanitized via wp_kses), excerpt, target status, scheduled date, SnowSEO article ID, featured-image URL and caption, and SEO meta fields. These are written as a standard WordPress post./wp-json/snowseo/v1/posts/{id}/update, authenticated with your site token) - an updated title, HTML content, or supported SEO metadata is written to the post or page selected for the fix./wp-json/snowseo/v1/posts/{id}, authenticated with your site token) - the requested post ID is sent to WordPress. The plugin permanently deletes the post only if it was originally created by SnowSEO./wp-json/snowseo/v1/invalidate, authenticated with the previous site token) - SnowSEO can instruct the plugin to remove its stored site token and connection metadata. An optional SnowSEO team ID may be sent as a secondary connection check./wp-json/snowseo/v1/perf/apply and /perf/revert, authenticated with your site token) - SnowSEO sends only an identifier naming one fix from a fixed list. No file content is ever sent or accepted: everything written is fixed text built into this plugin. These endpoints do nothing at all unless an administrator has first enabled Allow SnowSEO to apply performance fixes under SnowSEO > Performance or Settings > Reading. Applying "text compression" adds a marker-delimited compression block to this site's .htaccess; applying "robots.txt" turns on a filter that removes invalid lines from the robots.txt WordPress generates. Both are reversible from the same screen, and both are removed when the plugin is uninstalled./wp-json/snowseo/v1/perf, authenticated with your site token) - the site returns its web server type, whether .htaccess is writable, whether a robots.txt file exists on disk, and which caching or optimisation plugins are active. No site content or credentials are returned.snowseo folder to the /wp-content/plugins/ directory, or install through the WordPress Plugins screen.Yes. This plugin is the WordPress receiver for the SnowSEO platform. Without an account at https://snowseo.com you have no way to obtain the site token required for the connection. The plugin will not function in isolation.
The WordPress plugin itself is free and GPL-licensed. The SnowSEO service it connects to is a paid subscription. A 7-day free trial is available on the Pro plan; other plans are billed from the start of the subscription. Current plans and pricing are listed at https://snowseo.com/pricing.
Yes. Signing up for any SnowSEO plan, including the 7-day free trial, requires a valid payment method. You are not charged until a trial ends and converts to a paid plan, and you can cancel during the trial to avoid being billed. The cancellation policy and pricing are at https://snowseo.com/pricing.
See the External service: SnowSEO section above. In short, the plugin can send connection metadata, the site token, publishing request details, post status and permalink data, and the content and SEO metadata of a post or page selected for an audit autofix. It does not send visitor analytics, IP addresses, cookies, or WordPress user account data.
Open SnowSEO → Settings in the WordPress admin and click Disconnect. The stored API key and connection metadata are deleted locally and the SnowSEO backend is notified to deactivate the integration.
When SnowSEO sends a post with status scheduled and a future date, the plugin creates the post with status future and the supplied post_date. WordPress will publish it automatically at the scheduled time using its built-in cron.
When SnowSEO publishes a post via server-to-server call (authenticated with the site token rather than a WordPress login), the post is assigned to the first administrator on the site. If you want a specific user as the author of incoming posts, ensure that user is an administrator and has the lowest user ID among administrators.
.htaccess with WordPress's site root helper instead of assuming it sits next to WordPress. On sites where WordPress lives in a subdirectory, leftover SnowSEO blocks are now cleaned out of the right file, and if the site root cannot be determined nothing is touched at all..htaccess between clearly marked comments, and can be removed from the same screen, by hand, or by uninstalling the plugin.snowseo-perf-off file in wp-content that works when you cannot reach wp-admin at all. If a fatal error ever happens while it is running, the plugin notices on the same request and serves the next one unoptimized./robots.txt is being blocked by a firewall or when compression is already handled upstream.