Dragon Content Decay

Search Console figures are now added up across www/non-www addresses and matched to posts regardless of trailing slashes, so the Search Clicks column no longer under-reports.

What's fixed in 1.0.12

• Pages with more than one address are counted once, in full. A Domain property reports the same page under https://example.com/a/ and https://www.example.com/a/ (and http/https). Previously whichever row came last won, so a page with 10 + 5 clicks could show 5. Clicks and impressions are now summed across all of a page's addresses, and the average position is weighted by impressions.

• Only your own domain is counted. Rows for other subdomains in a Domain property (a shop or docs subdomain, say) no longer leak into your figures. www. and non-www. both count as your site.

• Trailing slashes and encoding no longer break the match. GA4 might report /about while Search Console reports /about/, or one side percent-encodes a character the other does not. The Search Clicks column showed 0 for such pages even though they had clicks. Both sources are now matched on the same normalised path, and GA4 rows that only differ in this way are added together.

• A sync that could not save every score says so. If the database refuses to write some decay scores, the sync was still reported as complete. The dashboard and the Sync Now button now report how many posts could not be saved, and the sync is recorded as partial or failed.

Run a sync after updating to refresh the stored figures. No settings changes.

Dragon Content Decay 1.0.11 is a documentation-only update that fully describes the Google Analytics and optional Search Console connections - no behaviour changes.

= 1.0.11 =

• Readme: the external services section now also covers the optional Google Search Console API calls (when they happen and what is sent), states that syncs run once a day, and lists the bundled Google client libraries and their licences. No code changes.

New: optional Google Search Console integration — see search clicks and impressions alongside your GA4 traffic decline.

= 1.0.10 =

• New: Google Search Console integration. Turn on "Search Console" under Settings, reconnect to Google to grant read-only access, and pick your verified property — the plugin then pulls per-page search clicks and impressions (current vs previous period) alongside GA4 pageviews, and the decaying-content dashboard gains a Search Clicks column. GA4 remains the decay driver; this is an additional signal, and existing GA4-only setups are untouched until you opt in.
• Note: this needs the Search Console API enabled in your Google Cloud project, and a reconnect to grant the new scope. GA4-only users are never prompted to reconnect.

Small fix: a clearer message when a sync is already running.

= 1.0.9 =

• Fixed: clicking "Sync Now" while a sync is already in progress (for example during the daily run) now shows a clear "already running" message instead of a misleading "Sync complete. Analyzed 0 posts."

Large-site reliability: the analysis sync is now time-bounded and can't overlap itself, and the digest email's links point to the right place.

= 1.0.8 =

• Improved: the analysis sync now runs within a time budget and works through your content across runs, so very large sites no longer risk the sync timing out mid-way.
• Improved: overlapping syncs (the daily job and a manual sync) can no longer run at the same time.
• Fixed: the "View Dashboard" and "Manage notification settings" links in the digest email now open the correct page.
• Housekeeping: removed an unused internal database table.

Security & reliability: adds CSRF protection to the Google connection, encrypts the client secret, and speeds up sync on large properties.

= 1.0.7 =

• Security: the Google OAuth flow now uses a state token (CSRF protection) and the client secret is encrypted at rest and masked in the UI.
• Fixed: corrected the OAuth redirect URI so connecting to Google works reliably.
• Performance: the decay sync resolves URLs in bulk instead of one query per URL, so it no longer times out on large properties.

Tested and verified on WordPress 7.1.

• Compatibility: tested up to WordPress 7.1.
• Fix: the first-run guidance panel now shows its intended styling.

Documents the Google Analytics connection in full, adds a Delete-data-on-uninstall setting, and stops writing debug noise to your server log unless WP_DEBUG is on.

Fixed Google Analytics connection errors, and a 90% smaller plugin.

This release bundles the Google Analytics data client correctly — previously, connecting a property or running a report could fail with a fatal error. The bundled Google libraries are also slimmed from about 170MB to 17MB, so installs and updates are much faster, and HTTP/JWT dependencies were updated to close published security advisories. Reconnect is not required; existing connections pick up automatically.

A cleaner, consistent look: the Dragon design system arrives.

This release brings Dragon Core's design system to every screen: a consistent header with the Dragon mark, cleaner tables, and unified status colours across the whole plugin family. Purely visual — everything behaves exactly as before.

• Initial release
• GA4 integration
• Decay detection