| 开发者 | abdsseo |
|---|---|
| 更新时间 | 2026年9月3日 07:07 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
No. Everything in this free plugin — the technical audit, rule-based content analysis, migration, and snippet preview — works with no key and no third-party service. The optional integrations that use your own API keys (AI, SERP, DataForSEO, Google Search Console) are part of the separate ABDS SEO Pro add-on, not this free plugin (see "External services").
Nothing is deleted automatically. The plugin offers to import your data via the migration wizard and only deactivates the old plugin after you confirm.
Only in one narrow, anonymous way, as of 0.9.0: opening the plugin's own Plans screen (Settings before 0.10.0) fetches the current subscription prices from the ABDS license server, so the upgrade options it shows are accurate. That request carries no license key, no site URL, and nothing else about your site — it's the same public price list anyone could load in a browser — and it's cached, so it doesn't repeat on every visit; if it ever fails, Plans just falls back to the plugin's built-in prices instead of breaking. Every OTHER third-party call — the actual license check — still only happens after you enter a license key. A free install that never opens Plans and never enters a key makes no license-related contact at all. The paid integrations that would send data elsewhere live in the separate ABDS SEO Pro add-on, not here (see "External services").
Buy a plan, then install the separate ABDS SEO Pro add-on (downloaded from your ABDS account) and activate your license key. The paid features live entirely in that add-on — this free plugin ships none of them. This free plugin always updates from WordPress.org like any other plugin; the Pro add-on delivers its own updates from the ABDS license server once activated.
Sitemap: line to robots.txt — previously it trusted that the address was registered, which was usually but not always the same thing as the address working. This does not check that the sitemap's contents are complete, only that the address itself responds correctly./sitemap.xml returned a 404, and WordPress's own built-in sitemap stayed switched off because this plugin had already told it to stand down. The sitemap now repairs itself automatically the next time an admin opens any wp-admin page, and WordPress's own sitemap is never switched off unless this plugin's sitemap is confirmed to actually be working — a site should never end up with no sitemap at all.robots.txt didn't declare where the sitemap lives. It now does, once the sitemap above is confirmed working./sitemap.xml that honors every Search Appearance setting (a page or archive you mark Noindex is excluded), with a status view and a manual regenerate button; and a read-only Robots.txt tab showing your site's live file plus three checks (sitemap declared, /wp-admin/ disallowed, no site-wide blanket block). When another SEO plugin is active, this plugin's own sitemap and robots.txt checks step aside automatically, the same way its other frontend output already does.<title> tag and canonical URL now use the same Search Appearance template settings as the meta description/Open Graph tags already did (previously the title tag itself didn't pick up a configured title template).<h1> tag inside the post body, which standard WordPress themes never put there (the theme renders the post title as H1), so it could never pass; and the URL-slug check didn't understand how WordPress stores non-Latin (e.g. Ukrainian) slugs, so it always failed on Cyrillic content. Both are fixed, check weights were rebalanced (title and heading placement count for more than the URL slug), and three checks were added that Yoast/Rank Math already had and we didn't: image alt text, internal + outbound links, and content length. The result now lands within about 10 points of Yoast on weak, medium, and strong test content — the same corridor established Yoast/Rank Math already agree with each other on.includes/license/class-abds-seo-pricing.php (a new file added by that release, missed at commit time) — every site running 0.9.0 hit a fatal error on update. 0.9.1 is 0.9.0 with the missing file included. No other changes.