v1.4.0

Added

• New "Exclude Selector" setting under Content Extraction — strip decorative or non-content elements (e.g. carousels, [data-nosnippet]) from the HTML before Markdown conversion (#3)
• "Description Field" now supports dot notation for traversing nested fields and sub-objects (e.g. seo.seoDescription inside a ContentBlock field, or seo.description for an Ether SEO field), () method-call syntax (e.g. metaData.getMetaDescription() for SEO Fields), and Generated Field handles (#4)
• Native SEOmatic resolver: set Description Field to seomatic:description (or seomatic:og-description, seomatic:twitter-description) to use SEOmatic's full resolution chain — per-entry override → section default → global default, with Twig token parsing. No Generated Field required
• New "Title Field" front-matter setting — point at any field handle/path to override the front-matter title: value, with the same syntax as Description Field. Falls back to the entry's native title when unresolved (#6)
• New "Author Override" front-matter setting — write a single authoritative author name (e.g., an editorial team) to every entry's front matter instead of leaking individual editor names (#6)
• New CP dashboard widget — compact summary of last-30-day analytics for the current site (total requests, top bot, top page) with a click-through to the full dashboard. Hidden when analytics are disabled or the user lacks the llm-ready:viewAnalytics permission (#5)
• New "Auto-inject Link Header" setting (default on) — adds an HTTP Link response header (RFC 8288) pointing at the Markdown alternate, alongside the existing <link rel="alternate"> HTML tag. Useful for crawlers that inspect headers without parsing HTML (#7)
• New SEO-PLUGINS.md documenting how to wire LLM Ready into SEOmatic, Ether SEO, SEOmate, and Studio Espresso SEO Fields
• New user permissions under "LLM Ready": "View the analytics dashboard" and the nested "Purge analytics data". Admins have both by default

Changed

• When "Description Field" is explicitly configured but resolves to an empty value, the entry's description is now omitted rather than silently falling back to auto-extraction from other fields (#4)

Security

• Analytics dashboard, JSON data endpoint, and purge action now require the corresponding permission. Previously any CP user could view analytics and trigger a purge. Existing non-admin users will lose access until granted the new permissions