Flowblinq AI Boost

Changelog

1.3.6

• Human-facing URLs in the readme and the admin settings page now point to www.flowblinq.com instead of geo.flowblinq.com. The sign-up link goes to /free-audit; the credentials link goes to /login. API endpoints (llms.txt proxy, OAuth tokens, audit submission) continue to be served from geo.flowblinq.com as before. No behaviour change for end users.
• Plugin URI updated to https://www.flowblinq.com.

1.3.5

• WordPress.org Plugin Check fix. Renamed three plugin classes to use the same prefix as the rest of the plugin namespace: Flowblinq_Proxy to Fqgeo_Proxy, Flowblinq_API_Client to Fqgeo_API_Client, Flowblinq_Admin_Page to Fqgeo_Admin_Page. Behaviour unchanged.

1.3.4

• readme.txt Installation, Screenshots, FAQ, External Services, and Privacy sections rewritten in the Flowblinq voice. Plugin functionality unchanged.
• Description block corrected: Flowblinq hosts the AI assets. The plugin serves them at your domain via WordPress rewrite rules. Previous wording implied the assets were hosted on the customer site.
• Em-dashes in prose replaced with periods, colons, or commas.
• AI-marker phrasing stripped (Typically, actionable, automatically, etc.).
• Shorter sentences and direct imperatives in operational instructions.

1.3.3

• readme.txt rewritten in the Flowblinq brand voice. Plugin functionality unchanged.
• New short description and Tags line position the plugin as performance automation for AI-specific web pages, away from the saturated “llms.txt generator” category.
• Description block follows the brand-book copy structure: urgency stat, direction, position, action. Includes the audit/fix/maintain loop and two anonymized client deployment results.

1.3.2

• Internal hardening pass before WordPress.org resubmission.
• AJAX handlers now bail out cleanly after a failed permission check (defence-in-depth: wp_send_json_error normally exits via wp_die(), but a custom wp_die handler could otherwise let execution continue past the rejection).
• Schema JSON-LD output is now restricted to singular and front-page contexts. Previously it was emitted on search-result pages, archives, 404 pages, and feeds, where business-profile schema is not appropriate.
• Site slug option (fqgeo_site_slug) now has a register_setting() sanitize callback enforcing the same lowercase-alphanumeric-hyphen format the audit handler validates. Defends against direct option writes via WP-CLI or settings-import plugins.
• OAuth credential sanitize callbacks now use a base64url charset whitelist instead of a deny-list of newlines and angle brackets. Tab characters and other unexpected bytes are rejected.
• Plugin boot moved into a plugins_loaded hook so plugin-conflict tooling can inspect the load order.
• Referrer cookie is no longer trusted blindly when already present — the existing value must be a well-formed cross-site URL or it is overwritten.
• Documented as single-site only — in WordPress multisite installations the OAuth credentials must be entered per network site.
• uninstall.php now removes the _fqgeo_stale_schema_json option used for stale-while-revalidate, plus the _fqgeo_lock_schema_json refresh lock transient.

1.3.1

• WordPress.org plugin review compliance fixes.
• Renamed all 2-character fq_ prefix identifiers to the 4+ character fqgeo_ prefix per WP.org naming-collision guidelines: every option key (fqgeo_client_id, fqgeo_client_secret, fqgeo_site_slug, fqgeo_active_audit_id), every transient (fqgeo_access_token, fqgeo_proxy_*), the rewrite query variable (fqgeo_serve), and all matching HTML form field IDs/names.
• register_setting() sanitize callbacks for fqgeo_client_id and fqgeo_client_secret now preserve raw OAuth credential bytes — sanitize_text_field() was stripping control characters and collapsing whitespace, which could mangle valid OAuth secrets. New callbacks reject newlines + HTML brackets, enforce a 1024-character cap, and surface settings errors on invalid input. Placeholder-preservation logic for the masked secret display unchanged.
• Contributors line in readme.txt corrected to the registered WordPress.org username.

1.3.0

• Renamed plugin from “Flowblinq GEO” to “Flowblinq AI Boost” for clarity. New display name in the WordPress admin sidebar and on the plugin listing.
• Plugin slug changed from flowblinq-geo to flowblinq-ai-boost (the folder under wp-content/plugins/).
• All internal identifiers (option keys, transient keys, AJAX action names, version constant) are unchanged. No database migration is required when upgrading from 1.2.x.
• Settings menu item now reads “Flowblinq AI Boost”. Re-bookmark Settings > Flowblinq AI Boost if you had a direct link.

1.2.1

• WordPress.org Plugin Check (PCP) compliance — production code now reports zero errors and zero warnings against PCP severity 4.
• Tested up to: 6.7 → 6.9.
• Removed manual load_plugin_textdomain call (auto-loaded by WordPress core since 4.6 for WordPress.org-hosted plugins).
• error_log calls in the proxy are now wrapped in WP_DEBUG checks (production-safe).
• Added wp_unslash() before sanitize_text_field on POST inputs (correctness improvement).
• Added i18n translators-comments above all \%s placeholder strings.
• Inline phpcs:ignore comments with justifications on the proxy pass-through and nonce-via-helper false positives.

1.2.0

• Added explicit External Services disclosure and Privacy section to readme (WordPress.org compliance).
• Added screenshot descriptions for the WordPress.org listing.
• GPL v2 Copyright line added to LICENSE.
• Internal: Docker integration test infrastructure for staging (ES-044), .htaccess seed + canonical redirect handling.

1.1.0

• Server-side referrer capture — sets _geo_ref first-party cookie on every page load so LinkedIn, Twitter, email, and Slack referrals are correctly attributed in GEO analytics. No configuration required.

1.0.0

• Proxy architecture — serves GEO files via WordPress rewrite rules
• Schema JSON-LD injection with stale-while-revalidate caching
• AI crawler robots.txt directives (GPTBot, ClaudeBot, PerplexityBot)
• Admin settings page with test connection and cache management
• Security hardening (17 findings resolved across 3 adversarial reviews)

0.1.0

• Initial release.