PluginProbe
ThinkRank AI SEO – AI SEO Plugin for WordPress: Schema, XML Sitemaps, Meta Tags, Search Console & Local SEO / 2.14.0
ThinkRank AI SEO – AI SEO Plugin for WordPress: Schema, XML Sitemaps, Meta Tags, Search Console & Local SEO v2.14.0
2.14.0 2.13.0 2.12.0 2.11.0 2.10.0 2.9.0 2.8.0 2.7.0 2.6.0 2.5.0 2.4.0 2.3.0 2.2.0 2.1.1 2.1.0 2.0.2 2.0.1 2.0.0 1.32.0 1.31.0 1.30.0 1.29.0 1.28.0 1.27.0 1.26.0 All 55 releases
← All changes | includes/api/class-seo-score-endpoint.php +53 -8 2.0.0 → 2.14.0 View file →
@@ -286,16 +286,36 @@
286 286 $metadata,
287 287 $score_options
288 288 );
289 289
290 - // Add readability_score and content_quality from frontend if provided
291 - if (!empty($readability_score)) {
292 - $score_data['readability_score'] = $readability_score;
293 - }
294 - if (!empty($content_quality)) {
295 - $score_data['content_quality'] = $content_quality;
296 - }
290 + // The browser's own readability_score and content_quality are no
291 + // longer applied. They used to be written over the labels this
292 + // request had just computed, and then persisted, so the saved
293 + // Readability and Content Quality described the editor text alone
294 + // (#829).
295 + //
296 + // That is wrong whenever the two see different content, which is
297 + // exactly when it matters: `analyze_live_content()` resolves what
298 + // the editor sent AND whatever `thinkrank_analyzable_content`
299 + // contributes on top, so a post with 2 words in the editor and 615
300 + // added by a filter scored 617 words server-side and saved
301 + // "Too short" / "Needs improvement" from the browser's 2.
302 + //
303 + // Nothing is lost by ignoring them: when `live_content` is non-empty
304 + // the server analysed the very text the editor measured, so its
305 + // labels cover the live case too. The parameters stay accepted so an
306 + // older cached bundle still gets a successful response, and they
307 + // stay documented in the route args; they simply no longer win.
308 + //
309 + // The panel keeps computing them in the browser for instant feedback
310 + // between calculations. What it must not do is persist them.
311 + unset($readability_score, $content_quality);
297 312
313 + // The resolved word count, so the panel can show the number this
314 + // score was actually calculated from rather than its own count of
315 + // the editor text (#829).
316 + $score_data['word_count'] = (int) ($content_data['word_count'] ?? 0);
317 +
298 318 // Save score if requested
299 319 if ($save_score) {
300 320 $user_id = get_current_user_id();
301 321 $score_id = $this->calculator->save_score($post_id, $user_id, $score_data);
@@ -332,8 +352,10 @@
332 352 // Get existing score data from database
333 353 $existing_data = $this->calculator->get_existing_score_data($post_id);
334 354
335 355 if ($existing_data) {
356 + $existing_data['keywords'] = $this->keyword_placements((int) $post_id);
357 +
336 358 return new WP_REST_Response([
337 359 'success' => true,
338 360 'data' => $existing_data,
339 361 'message' => __('Existing SEO score retrieved successfully', 'thinkrank')
@@ -351,8 +373,27 @@
351 373 }
352 374 }
353 375
354 376 /**
377 + * Where each focus keyword sits (#729), for a stored score. A stored score
378 + * predates the editor's current keywords and content, so this is read
379 + * from the post as saved now — a text pass, no request, no AI.
380 + *
381 + * @param int $post_id Post ID.
382 + * @return array<int, array<string, mixed>>
383 + */
384 + private function keyword_placements(int $post_id): array {
385 + return $this->calculator->keyword_placements(
386 + $this->calculator->analyze_post_content($post_id),
387 + [
388 + 'title' => \ThinkRank\SEO\Pattern_Resolver::effective_title($post_id),
389 + 'description' => \ThinkRank\SEO\Pattern_Resolver::effective_description($post_id),
390 + ],
391 + \ThinkRank\SEO\Focus_Keywords::get($post_id)
392 + );
393 + }
394 +
395 + /**
355 396 * Get score history for a post
356 397 *
357 398 * @param WP_REST_Request $request Request object
358 399 * @return WP_REST_Response|WP_Error Response object
@@ -387,10 +428,14 @@
387 428 public function get_latest_score(WP_REST_Request $request) {
388 429 try {
389 430 $post_id = $request->get_param('post_id');
390 431
432 + // The stored row only — no keyword gauges (#729). The dashboard
433 + // asks for five posts at once and reads overall_score; a gauge
434 + // pass would analyse and render each whole post for nothing. The
435 + // editor reads its gauges from /seo-score/get.
391 436 $latest_score = $this->calculator->get_latest_score($post_id);
392 -
437 +
393 438 return new WP_REST_Response([
394 439 'success' => true,
395 440 'data' => $latest_score,
396 441 ], 200);