WWB SEO Master is developed by [Wild Web Builder] Aleksander Auset B\u00e6kkelund (https:\/\/www.wildwebbuilder.com\/).\nVisit our website for more information about our WordPress tools and services like WebDesign and Plugin automation.<\/p>\n\n
WWB SEO Master provides technical and editorial SEO tools without advertising,\nlicense checks or telemetry:<\/p>\n\n
\/llms.txt<\/code>.<\/li>\n- Migration from WWB SEO V3, Yoast SEO, Rank Math, SEOPress and AIOSEO.<\/li>\n
- Optional read-only Google Search Console reports and URL inspection.<\/li>\n
- Optional AI Optimization Assistant and manual backlink candidate research.<\/li>\n<\/ul>\n\n
AI features are disabled by default and run only after an authorized user clicks\nthe relevant action. WordPress 7.0 or newer uses the built-in, provider-agnostic\nWordPress AI Client when a compatible connector supports the request. On older\nWordPress versions, or when the native client cannot support the request, an\nadministrator can configure the backward-compatible OpenAI fallback. The plugin\nstill requires only WordPress 6.0 and does not require WordPress 7.0.<\/p>\n\n
AI output is sanitized, bounded and review-only. It is never published, posted,\nemailed or adopted automatically. Deactivation preserves all data. Deletion also\npreserves data unless permanent cleanup is explicitly enabled in Settings.<\/p>\n\n
External Services<\/h3>\n\n
This plugin has no licensing, update-check, advertising, analytics or telemetry\nservice. The following optional services are used only when a site administrator\nconfigures and invokes their associated features.<\/p>\n\n
WordPress AI Client and configured AI provider<\/h4>\n\n
On WordPress 7.0 or newer, the plugin first calls wp_ai_client_prompt()<\/code>. The\nWordPress AI Client selects a compatible AI provider from connectors installed\nand configured by the site owner. WWB SEO does not install a connector and does\nnot control which provider the owner selects.<\/p>\n\nWhen an authorized editor manually requests page optimization, the prompt may\ncontain the site name, locale, saved page title, saved SEO\/social metadata,\nschema type and a bounded plain-text copy of the saved page content. When an\nadministrator manually requests backlink candidates, it may contain the site\nname and URL, business goal, audience, location and up to eight recent public\npage titles and URLs. That second request also asks a capable provider to use web\nsearch. No prompt is sent automatically or in the background.<\/p>\n\n
Data handling, retention, billing, terms and privacy are determined by the AI\nconnector and provider configured by the site owner. See the\nWordPress AI Client documentation<\/a>\nand the selected connector\/provider documentation before enabling this feature.<\/p>\n\nOpenAI fallback<\/h4>\n\n
The optional backward-compatible fallback sends manual AI requests to\n https:\/\/api.openai.com\/v1\/responses. It is used only when the WordPress AI\nClient is unavailable or cannot support the requested capability and a site\nadministrator has saved an OpenAI API key.<\/p>\n\n
Page-optimization and backlink-candidate requests contain the same bounded data\ndescribed above. A pseudonymous HMAC identifier derived from the current local\nuser ID can also be sent for abuse prevention; it is not the WordPress username,\nemail address or raw user ID. Requests set store: false<\/code>. Backlink research may\nenable OpenAI web search. The encrypted API key remains on the WordPress site and\nis transmitted only in the authorization header for the request. Nothing is sent\nuntil an authorized user explicitly runs an AI action.<\/p>\n\nOpenAI API use is subject to OpenAI's\nterms<\/a> and\nprivacy policy<\/a>. API usage may be\nbilled to the key owner.<\/p>\n\nGoogle OAuth and Search Console<\/h4>\n\n
The optional Search Console module communicates with these Google endpoints:<\/p>\n\n
\nhttps:\/\/accounts.google.com\/o\/oauth2\/v2\/auth<\/code> for administrator-initiated OAuth consent.<\/li>\nhttps:\/\/oauth2.googleapis.com\/token<\/code> to exchange and refresh OAuth tokens.<\/li>\nhttps:\/\/www.googleapis.com\/webmasters\/v3\/<\/code> for verified properties and read-only performance reports.<\/li>\nhttps:\/\/searchconsole.googleapis.com\/v1\/urlInspection\/index:inspect<\/code> for administrator-requested URL inspection.<\/li>\n<\/ul>\n\nThe OAuth client ID, authorization code, encrypted client secret and encrypted\ntokens are used for authentication. Selected property, date ranges, report\ndimensions and administrator-entered inspection URLs are sent as needed. The\nmodule requests the read-only webmasters.readonly<\/code> scope. Performance results\nare cached locally for one hour and inspection results for six hours. Disconnect\nremoves stored tokens and the selected property. Google use is subject to the\nGoogle Terms of Service<\/a> and\nGoogle Privacy Policy<\/a>.<\/p>\n\n\n\n- Upload the plugin ZIP in Plugins > Add New > Upload Plugin.<\/li>\n
- Activate WWB SEO Master.<\/li>\n
- Open WWB SEO > Settings and enable only the modules you need.<\/li>\n
- Set the public identity used by the schema graph.<\/li>\n
- Edit content or public taxonomy terms to configure SEO fields.<\/li>\n
- Back up the site before using migration or permanent uninstall cleanup.<\/li>\n<\/ol>\n\n\n
\nIs a license key required?<\/h3><\/dt>\nNo. There is no license-key system, advertising or telemetry.<\/p><\/dd>\n
Is WordPress 7.0 required?<\/h3><\/dt>\nNo. The minimum remains WordPress 6.0. WordPress 7.0 or newer can use the native\nAI Client; older versions can use the optional direct OpenAI fallback.<\/p><\/dd>\n
Does AI publish or change content automatically?<\/h3><\/dt>\nNo. AI runs only on an authorized manual action. Suggestions must be selected,\nreviewed and saved by the user. Backlink candidates also require manual adoption\nand outreach.<\/p><\/dd>\n
Does deactivation delete SEO data?<\/h3><\/dt>\nNo. Deactivation never deletes data. Optional permanent cleanup applies only\nwhen the plugin itself is deleted and the setting was enabled beforehand.<\/p><\/dd>\n
Does it replace the WordPress sitemap?<\/h3><\/dt>\nIt controls and extends the sitemap system built into WordPress. The sitemap\nindex remains available at \/wp-sitemap.xml<\/code>.<\/p><\/dd>\n\n<\/dl>\n\n\n5.6.2<\/h4>\n\n\n- Moved settings-page CSS to a local stylesheet loaded with
admin_enqueue_scripts<\/code>.<\/li>\n- Passed Smart Finisher data through
wp_add_inline_script()<\/code> instead of printing a script element in admin markup.<\/li>\n- Changed the answer-helper shortcodes to the unique
wwbseo_answer<\/code>, wwbseo_faq<\/code> and wwbseo_howto<\/code> names before the public directory release.<\/li>\n- Removed the global PHP compatibility notice and kept the permalink-change confirmation inside the relevant post-editing form.<\/li>\n
- Corrected the WordPress.org contributor username and replaced the short internal namespace and constant prefixes with unique plugin-specific names.<\/li>\n
- Retained WordPress AI Client priority with the documented OpenAI compatibility fallback for older WordPress versions.<\/li>\n<\/ul>\n\n
5.6.1<\/h4>\n\n\n- Added a persistent, accessible saved, unsaved, saving and save-failed status inside the page SEO panel.<\/li>\n
- Added reliable save confirmation for both the classic editor and block editor workflows.<\/li>\n
- Clarified that Smart Finisher and AI actions add recommendations to the editor but do not store them until WordPress confirms Update or Publish.<\/li>\n
- Highlighted modified SEO and schema fields and guided users to the WordPress save button.<\/li>\n
- Completed the four-step AI progress indicator only after a successful WordPress save.<\/li>\n
- Added selection counts, duplicate-click protection, busy states and clearer undo and restore feedback.<\/li>\n<\/ul>\n\n
5.6.0<\/h4>\n\n\n- Added WordPress AI Client support with capability checks, structured output, model preference, token limits and optional web search.<\/li>\n
- Kept a safe direct OpenAI fallback for WordPress 6.x and unsupported native requests without making WordPress 7.0 a requirement.<\/li>\n
- Prevented duplicate provider calls when a native AI request fails after execution starts.<\/li>\n
- Hardened external requests with safe URL validation, disabled redirects and bounded responses.<\/li>\n
- Improved OAuth property-boundary validation, AI lock cleanup and provider-aware settings guidance.<\/li>\n
- Completed uninstall cleanup for Smart Finisher snapshots and removed unused custom update metadata.<\/li>\n
- Expanded External Services, privacy, compatibility and data-flow documentation.<\/li>\n
- Updated the translation template, compatibility declarations and release checks.<\/li>\n<\/ul>\n\n
5.5.1<\/h4>\n\n\n- Added manual AI web search for relevant backlink and recognition candidates.<\/li>\n
- Added reviewable candidate details, selection controls and strict URL\/output validation.<\/li>\n
- Kept discovery manual with no automatic outreach or posting.<\/li>\n<\/ul>\n\n
5.5.0<\/h4>\n\n\n- Added the local Backlink Center planning workflow and quality scoring.<\/li>\n<\/ul>\n\n
5.4.1<\/h4>\n\n\n- Protected populated or changed metadata from unintended AI overwrite.<\/li>\n
- Unified title and description limits across the editor, server and AI output.<\/li>\n<\/ul>\n\n
5.0.0<\/h4>\n\n\n- Rebuilt the plugin around consistent indexability, connected entities, crawler controls and visible answer helpers.<\/li>\n<\/ul>","raw_excerpt":"Fast, modular and privacy-first WordPress SEO with optional, manual AI assistance.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/361923","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=361923"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/aleksa64"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=361923"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=361923"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=361923"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=361923"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=361923"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=361923"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}