CiteWP AI Search Optimizer – Get Cited by ChatGPT, Perplexity & Claude

0.7.14

• Fix: Restored the correct text domain (citewp-ai-search-optimizer) after a 0.7.13 regression. No functional change.

0.7.13

• Fix: FAQ schema nested inside article schema (Rank Math’s standard BlogPosting → subjectOf → FAQPage structure) is now correctly detected and credited — affected pages no longer cap at 5/8 for the FAQ Structure signal despite having valid FAQ schema.
• Fix: Recalculate no longer downgrades the Cite Score when the self-request loopback returns a non-200 response or an implausibly small body (blocked loopback, CDN challenge page, security plugin filtering the CiteWP UA). The existing cached detection result is preserved in those cases instead of being overwritten.

0.7.12

• Improvement: Schema insertion in the Classic Editor and page-builder meta box now injects into the page head — matching the block-editor sidebar — instead of copy-paste into content.
• Fix: Inserting schema via either the meta box or block-editor sidebar now correctly updates the Cite Score on Recalculate, including on sites where the self-request loopback is unavailable.
• Improvement: Category rows (Structure, Citability, Authority) in the meta box are now expandable — click any row to see individual signal scores and recommendations.
• Fix: Bot Visits panel in the Classic/page-builder meta box now correctly shows AI crawler activity for the current post (query was referencing columns that don’t exist in the crawler log table).

0.7.11

• New: Schema scoring now credits authority-entity types — SoftwareApplication, Organization, Person, Product, LocalBusiness, and more — so product, landing, and service pages no longer score 0 for schema just because they aren’t Articles.
• New: “Detected on this page” readout in the Schema Suggestions panel and editor meta box shows the schema types found on each post or page.
• New: AI crawler detection expanded from 43 to 86 verified bots (DeepSeek, Brave, PetalBot, Semrush, Ahrefs, social link-preview bots, and more).
• New: AI Blind Spots card on the Crawler Logs page surfaces published content that AI crawlers have not yet visited.
• New: “Hide excluded” toggle on the Post & Page Cite Scores table.
• Improvement: Top Crawled Pages now focuses on your posts and pages (site files stay in the full log and CSV export).
• Fix: Schema scoring message now names what schema was found instead of a misleading “no schema markup detected.”
• Fix: Needs Attention card and AI Recommendation cards always reference the same top gap on large sites.
• Fix: Admin styles now cache-bust correctly so design updates appear immediately.
• Fix: Removed a broken tooltip on the Crawler Logs page.

0.7.10

• Improvement: AI Recommendations cards now group by signal and post type — Posts and Pages are shown as separate, targeted cards.
• Improvement: Cards ranked by recoverable Cite Score points so the highest-impact fixes surface first.
• Fix: “View N Posts/Pages” button now opens a curated list showing exactly those N affected items — not the full dashboard.
• Fix: Card count, button count, and filter-banner count now always agree (count-match contract restored).
• Fix: Recommendation filter correctly scopes to published content only, excluding llms.txt-opted-out posts.
• Improvement: Empty state shows a positive message when all content is fully optimized.
• Improvement: Statistics density scoring uses a raw-count floor for more consistent scoring across content lengths.
• Improvement: Named entity detection extended to CamelCase brand names (ChatGPT, WordPress, SEMrush, etc.).

0.7.9

• Schema detection now reads rendered page output, crediting FAQPage and Article schema from any emitter (Rank Math, Yoast, AIOSEO, hand-rolled JSON-LD) equally.
• Schema generation moved from post content insertion to head injection (wp_head), eliminating wpautop corruption and improving compatibility with caching plugins.
• FAQ and Article signals now score independently — Article signal credits validated Article schema only, not generic SEO-plugin presence.
• FAQ extractor fixes: CSS leak in text extraction, br-tag word-fusion, and whitespace handling.
• Tolerant JSON-LD parsing handles hand-crafted schema with embedded line breaks.
• Unicode handling fix — em-dashes and other escaped Unicode characters now render correctly in injected schema.
• Removed block-label as a schema-generation trigger to prevent overwriting existing user-authored schema.
• New REST endpoint POST /citewp/aiso/v1/schema/[id]/inject for Insert/Remove with conflict guard.
• AI Recommendations card on the Cite Score page now excludes llms.txt-opted-out posts from per-signal counts and card visibility, matching the rest of the dashboard’s exclusion behavior.

0.7.8

• Schema detection — emitter-agnostic rendered-output detection via template_redirect full-page cache and sync self-request on Recalculate. Credits schema from Rank Math, Yoast, AIOSEO, and hand-rolled wp:html blocks equally.
• FAQ/Article signal independence — Article/Schema signal gates on Article-type validation, not presence of any schema type; FAQPage-only detections credit the FAQ signal only. Schema detection cache survives content edits and clears on post status transitions only (not every save).
• json_decode_tolerant — hand-crafted JSON-LD with literal CR/LF in string values (accepted by Google Rich Results, rejected by PHP’s strict parser) now parsed correctly.
• Flag-don’t-inject — CiteWP no longer offers to insert FAQPage schema when a valid FAQPage already exists on the rendered page, preventing Rich Result clobbering. Removes the Kadence block-label auto-generation trigger that caused duplicate FAQPage schema insertion.
• FAQ extraction fix — inline CSS from Kadence accordion blocks no longer leaks into acceptedAnswer.text; clean_text() strips style/script noise nodes before extracting text content.
• Head injection — Schema Suggestions Insert/Remove now stores generated schema in post meta and emits via wp_head, replacing block-editor insertion. Eliminates wpautop corruption of JSON-LD in post_content. Insert and Remove buttons backed by REST endpoint with detect-before-inject conflict guard.
• Schema storage — injected schema stored as serialized PHP array instead of JSON string, preventing wp_unslash from corrupting Unicode escapes (e.g. em-dash rendered as ‘u2014’).
• FAQ word-fusion fix — clean_text() replaces br elements with a space text node before reading textContent, preventing adjacent words from fusing at line breaks.

0.7.7

• Cite Score page — ‘Excluded from llms.txt’ pill on per-post table rows for posts excluded from llms.txt generation.
• Cite Score Over Time chart — sparse-data state shown when the selected window has fewer than 3 recorded data points.
• Left rail — ‘Request a Feature’ link below the Pro card.

0.7.6

First public release on WordPress.org.

• Cite Score — transparent 100-point AI citation readiness score across 17 signals in three categories (Structure, Citability, Authority). Full rubric published at https://citewp.com/cite-score with research citations for every weight.
• AI Crawler Tracking — log and filter visits from GPTBot, ClaudeBot, PerplexityBot, and 40+ other AI bots across 19 vendors. Bot-type and date-range filters, summary stats, CSV export.
• llms.txt Generation — automatic llms.txt and llms-full.txt with cornerstone content prioritization. Integrates with Yoast SEO, Rank Math, SEOPress, and AIOSEO.
• Cite Score in every editor — Gutenberg sidebar with per-signal drilldown and on-demand recalculation; universal meta box brings the Cite Score and schema suggestions to Classic Editor, Elementor, Divi, Beaver Builder, and Bricks.
• Schema Suggestions — one-click Article and FAQPage JSON-LD generation with per-post schema type selection. FAQ detection recognizes accordions from Kadence, Elementor, Divi, Beaver Builder, Bricks, Spectra, and HTML5 details/summary.
• Cite Score dashboard — site-wide score, score-over-time trend, per-post score table, AI recommendations, and schema coverage.
• Crawler Logs page — Bot Visits Over Time and Top Crawled Pages, with date-range-aware KPIs.
• Per-post llms.txt control — exclude individual posts or pages from llms.txt; excluded content is also dropped from aggregate score metrics.
• Dashboard widget — average Cite Score, top crawled pages, and AI bot activity at a glance.