Google Privacy Policy<\/a><\/p>\n\nChart.js<\/strong> 4.4.0 - charting library, MIT license.\nFile: assets\/js\/chart.umd.min.js<\/code>\nLicense: licenses\/chartjs-MIT.txt<\/code>\nSource: https:\/\/github.com\/chartjs\/Chart.js<\/p>\n\nVazirmatn font<\/strong> 33.0.3 (variable, weights 100-900) - SIL Open Font License 1.1.\nFile: assets\/fonts\/Vazirmatn-Variable.woff2<\/code> - full license: assets\/fonts\/LICENSE.txt<\/code>\nSource: https:\/\/github.com\/rastikerdar\/vazirmatn<\/p>\n\n\n\n- Upload the
palette-data-analyzer<\/code> folder to wp-content\/plugins\/<\/code>, or install the .zip from Plugins - Add New - Upload Plugin.<\/li>\n- Activate the plugin.<\/li>\n
- Open the Palette Data Analyzer menu and upload a Search Console export.<\/li>\n<\/ol>\n\n
Your server needs the standard PHP zip<\/code> and xml<\/code> extensions, which are enabled on almost all WordPress hosts. No Composer packages are required - .xlsx files are parsed directly.<\/p>\n\n\n\nDo I need a Google API connection?<\/h3><\/dt>\nNo. The free plugin analyses uploaded files. Direct API connection is an optional capability of the separately distributed Palette Data Analyzer Pro add-on.<\/p><\/dd>\n
Which date range should I export?<\/h3><\/dt>\nAny range works, and the plugin scales its thresholds to match. A 28-day window is the best default because it is exactly four weeks, so each period contains the same number of Saturdays, Sundays and so on, and day-of-week seasonality cancels out of the comparison. A calendar-month comparison does not have that property.<\/p><\/dd>\n
Is my data sent anywhere?<\/h3><\/dt>\nNot unless you ask for it. File uploads are processed on your own server. The Google Search Status feed is contacted only after you explicitly enable it on the upload screen. The separately distributed Pro add-on contacts Google only after you start its connection flow, and contacts an AI service only after you configure a key and request a summary. See the External services section below.<\/p><\/dd>\n
Does the AI layer change the numbers?<\/h3><\/dt>\nNo. In the separately distributed Pro add-on, it receives already-calculated figures and writes prose about them. Turning it off changes nothing about the analysis.<\/p><\/dd>\n
Why is a section of the report empty?<\/h3><\/dt>\nSome modules need history. Ranking volatility, for example, is measured as the standard deviation of a page's position across at least three archived reports, because volatility cannot be defined from two data points. The section explains what it still needs.<\/p><\/dd>\n\n<\/dl>\n\n\n
Older releases are listed in changelog.txt<\/code> inside the plugin folder.<\/p>\n\n4.20.4<\/h4>\n\n\n- Added the dedicated plugin page as the Plugin URI.<\/li>\n<\/ul>\n\n
4.20.3<\/h4>\n\n\n- Removed the redundant Plugin URI header so the plugin and author URIs are not identical.<\/li>\n<\/ul>\n\n
4.20.2<\/h4>\n\n\n- Clarified which capabilities belong to the free plugin and which require the separately distributed Pro add-on.<\/li>\n
- Connection and relay tests now run only after an administrator explicitly clicks a nonce-protected test link; opening Settings never makes a network request.<\/li>\n
- Removed Pro upgrade cards from the free plugin dashboard; the single contextual add-on notice remains on the Settings page.<\/li>\n<\/ul>\n\n
4.20.1<\/h4>\n\n\n- Google Search Status updates are now strictly opt-in. The upload screen explains the network request and the feed does not include the site URL in its User-Agent.<\/li>\n
- Removed code that suppressed other plugins' admin notices.<\/li>\n
- Added the bundled Chart.js MIT license and moved the WordPress minimum version into the main plugin header.<\/li>\n<\/ul>\n\n
4.20.0<\/h4>\n\n\n- The Action Plan is now ordered by estimated impact inside each priority level, instead of by the order the modules happen to run in. Previously every item of one module came out in a block, so a report with ten page-two queries opened with ten near-identical lines while a single low-CTR page worth several times the traffic sat further down. Each action is now scored in one common unit - the clicks it would gain or recover, using your own site's CTR curve for the target position - and ties are broken by title so the same file still produces the same report twice.<\/li>\n<\/ul>\n\n
4.19.0<\/h4>\n\n\n- A query or page that did not exist in the previous period no longer shows a position drop. With no earlier rank, its \"position change\" was computed as zero minus the current rank, so a brand-new query at position 15.3 was reported as having fallen 15.30 places. Those rows are now labelled \"new\".<\/li>\n
- The dashboard said \"19 analysis modules\" in both editions. It now states the real count for the edition you are running.<\/li>\n<\/ul>\n\n
4.18.0<\/h4>\n\n\n- Search Console reports the same page once per anchor link, so
\/page\/<\/code>, \/page\/#h-1<\/code> and \/page\/#h-2<\/code> arrived as three separate rows. On a real site 376 of 585 page rows were anchors and a single page was split across eleven of them, which meant no row carried that page's real weight and one page could fill most of the action plan. Anchors are now merged: clicks and impressions are summed, position becomes an impression-weighted average, and CTR is recalculated from the totals rather than averaged.<\/li>\n<\/ul>\n\n4.17.0<\/h4>\n\n\n- Saving a report now returns its archive ID, so anything referring back to that exact report \u2014 such as a shareable link \u2014 can name the right row.<\/li>\n
- Setup guide updated for Google's new console: \"Publishing status\" and \"Test users\" both moved to the Audience page, and the wizard links there directly.<\/li>\n<\/ul>\n\n
4.16.0<\/h4>\n\n\n- Fixed a slowdown on servers that cannot reach Google. The Google Search Status feed is fetched while building a report, but a failed fetch was never cached \u2014 so every single report waited out the full 15-second timeout, again and again. Failures are now remembered for an hour, the timeout is 5 seconds, and the previous data is kept rather than discarded.<\/li>\n
- That feed can now go through the relay. It was missing from the allowlist, so a configured relay did not help it. Added to both the PHP list and the sample Cloudflare Worker.<\/li>\n<\/ul>\n\n
4.15.0<\/h4>\n\n\n- The setup guide now covers the \"Access blocked \/ Error 403: access_denied\" screen people hit when connecting their Google account, and adds a step for publishing the OAuth app. That step matters more than it looks: while the app stays in Testing, Google expires the connection after seven days, so the plugin silently loses access about once a week and scheduled reports stop. Publishing removes that limit and needs no Google review.<\/li>\n<\/ul>\n\n
4.14.1<\/h4>\n\n\n- Bot setup instructions no longer print bare @handles, which some marketplace scanners flag as personal contact details. The instructions name the official BotFather bot instead.<\/li>\n<\/ul>\n\n
4.14.0<\/h4>\n\n\n- The settings page no longer probes Google on load. It only checks connectivity once you have entered a Client ID or a property address \u2014 before that there is nothing to connect to, and probing meant an outbound request just for opening a page.<\/li>\n
- Sections that need a direct API connection now say so instead of showing a \"Pro\" upsell. Those sections have no data when the report comes from a file upload, and telling a customer who already owns Pro to buy Pro was confusing.<\/li>\n
- Added a
PALDA_DISTRIBUTION<\/code> constant so a vendor-neutral build can be produced from the same source, without maintaining a second copy of the plugin.<\/li>\n<\/ul>\n\n4.13.0<\/h4>\n\n\n- A fresh install no longer makes any outbound request until you generate your first report. The Google Search Status feed was fetched on a daily cron that scheduled itself five minutes after the first admin page view \u2014 before the user had done anything, and while its output had nothing to label yet. It is now scheduled only once a report exists. Existing installs keep their schedule.<\/li>\n<\/ul>\n\n
4.12.0<\/h4>\n\n\n- Fixed \"jump to section\", which had been broken in Persian.<\/strong> Section IDs were built from the section number \u2014 a translated<\/em> string. In English it stayed \"1\" and worked; in Persian it became \"\u06f1\", every non-ASCII character was stripped, and all twenty sections ended up with the identical id
pda-sec-<\/code>. So getElementById<\/code> always returned the first section (every jump went to the top of the report) and the active-section highlight had nothing to map to. IDs are now derived from section order and are language-independent.<\/li>\n- Pro teaser sections had the same bug and were also missing from the jump bar entirely, so free users could not jump to them. Both section builders now share one ID source.<\/li>\n
- The jump offset was hardcoded at 120px while the real sticky-bar height is around 230px, so the target landed hidden underneath the bar. It is now measured, which also covers RTL, mobile and a hidden admin bar.<\/li>\n
- Jumping now survives environments that ignore smooth scrolling (reduced-motion settings), re-checks its position once the scroll settles \u2014 charts change height as they load \u2014 and cancels a pending correction when you click another section.<\/li>\n
- Bidirectional text is now derived from content, not assumed.<\/strong> Every link was forced to
direction: ltr<\/code>, which is right for a URL but wrong for links whose text is Persian, whose trailing punctuation jumped to the wrong side. Links and inline code now use unicode-bidi: plaintext<\/code>, so each element takes its direction from its own first strong character. Standalone URLs stay explicitly LTR so a Persian slug cannot flip them.<\/li>\n- Multi-line URLs in tables were right-aligned line by line, breaking their left-to-right reading order. They are block-level now, so the box follows the page direction while the text inside stays left-aligned.<\/li>\n
- Free dashboard: the \"Get started\" link pointed at the settings page, which without a licence is only a Pro pitch \u2014 a free user clicking it landed on a sales page instead of somewhere they could work. It now points at the file upload, and the main button carries a \"Start here\" badge until the first report exists.<\/li>\n<\/ul>\n\n
4.11.0<\/h4>\n\n\n- Plugin Check compliance: zero errors and zero warnings against the official WordPress plugin-check tool.<\/li>\n
- readme.txt is now in English, as the plugin directory requires. The full Persian history moved to
changelog.txt<\/code>.<\/li>\n- File operations in the uninstaller and the ZIP-signature check now use WP_Filesystem, so they work on hosts where WordPress writes over FTP or SSH.<\/li>\n
- Dropped
wp_set_option_autoload()<\/code>, which needs WordPress 6.4 while this plugin supports 5.8. The same result is achieved with functions available in every supported version.<\/li>\n- Removed the manual
load_plugin_textdomain()<\/code> call; WordPress has loaded translations automatically since 4.6. Verified that Persian still loads without it.<\/li>\n<\/ul>\n\n4.10.0<\/h4>\n\n\n- The
palda_settings_sections<\/code> seam is now live, so the Pro add-on can render its own settings block without any of its code living in the free plugin.<\/li>\nPALDA_Connectivity::rewrite_google()<\/code> renamed to rewrite_if_allowed()<\/code>; the relay allowlist is no longer Google-only. The old name is kept as an alias.<\/li>\n- Sample Cloudflare Worker:
api.telegram.org<\/code> added to the allowlist.<\/li>\n<\/ul>\n\n4.9.0<\/h4>\n\n\n- Report thresholds now scale with the length of the exported window. Minimum-impression gates were tuned for 28 days, so on a 3-month export they were roughly three times too loose and on a 7-day export three times too strict.<\/li>\n<\/ul>\n\n
4.8.0<\/h4>\n\n\n- Comparison exports now work with any date range, not just 28 days. Previously the column detection matched the literal text \"Last 28 days\"; every other range silently produced a report where all numbers were zero, alongside a misleading \"your file is single-period\" message.<\/li>\n
- Added a guard against that silent failure: if a sheet has rows but no numbers could be read, the plugin says so and names the sheet.<\/li>\n
- Re-running the same report no longer clutters the archive. Each run used to insert a new row, which put duplicate points into the time series and dragged volatility toward zero.<\/li>\n<\/ul>\n\n
4.7.0<\/h4>\n\n\n- Rewrote the ranking-volatility module. It previously measured the absolute difference between two periods, which is not volatility and duplicated the \"biggest movers\" module. It now uses the standard deviation of position across at least three archived reports.<\/li>\n
- Each report now stores a snapshot of the top 50 pages so per-page time series can be built.<\/li>\n<\/ul>\n\n
4.6.1<\/h4>\n\n\n- Property selection in the report archive is now correctly limited to the Pro add-on.<\/li>\n
- Fixed archive rows saved under an inconsistent property format, with a one-time migration.<\/li>\n<\/ul>","raw_excerpt":"Turn a Google Search Console export into a prioritised SEO action plan with formula-based analysis.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/tw.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/352917","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/tw.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/tw.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/tw.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=352917"}],"author":[{"embeddable":true,"href":"https:\/\/tw.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/paletteagencyy"}],"wp:attachment":[{"href":"https:\/\/tw.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=352917"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/tw.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=352917"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/tw.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=352917"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/tw.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=352917"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/tw.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=352917"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/tw.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=352917"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}