Nova-Core v0.1.64

Stops phantom Plausible visitors inflating every site's visitor count.

• tracking.js bails out entirely when navigator.webdriver is true (honest automation)
• All event wiring (IntersectionObserver, click, form, menu listeners) now only arms once the document has been visible, matching Plausible script.js pageview behaviour
• A page that is never visible (headless crawlers, background loads) now sends zero custom events, so events and pageviews stay consistent per visitor
• No event names, props, or visible-page behaviour changed; historical data stays comparable
• tracking.js cache-buster bumped to 1.0.2

Full Changelog: v0.1.63...v0.1.64

Nova-Core v0.1.63

Changes

• Removes manual Q&A pair repeater from Nova Schema metabox — FAQ schema is now auto-extracted from Bricks Builder accordions only
• Add nova-faq CSS class to your FAQ accordion in Bricks to disambiguate when multiple accordions exist on a page
• Updated FAQ checkbox description text for clarity

Full Changelog: v0.1.62...v0.1.63

Nova-Core v0.1.62

Bug fix

The FAQ auto-extraction from Bricks accordion was returning empty results on all live sites. Root cause was three incorrect assumptions about Bricks' internal data format, diagnosed by inspecting _bricks_data directly via WP-CLI.

What was wrong

	Was	Now
Meta key	_bricks_data	_bricks_page_content_2 (falls back to _bricks_data)
Items key	settings.items	settings.accordions (falls back to settings.items)
CSS class storage	settings._cssClasses string	settings._cssGlobalClasses ID array, resolved via bricks_global_classes option

Result

All six FAQ pairs are now extracted correctly and the FAQPage schema node appears in the page's JSON-LD output.

Full Changelog: v0.1.61...v0.1.62

Nova-Core v0.1.61

What's new

Bricks accordion FAQ extraction diagnostic

When Auto-extract from Bricks accordion is checked in the Nova Schema metabox, an Extraction status panel now appears showing exactly what was found in _bricks_data:

• Total element count
• Element types present on the page
• For each accordion: its ID, _cssClasses value, item count, and the key names on the first item

This makes it possible to diagnose extraction failures immediately from the page editor, without needing database access. Once the cause is identified the diagnostic will be removed in the next release.

Full Changelog: v0.1.60...v0.1.61

Nova-Core v0.1.60

What's new

Nova Schema module

Replaces SEOPress structured data with a custom JSON-LD @graph implementation. Every page now emits WebSite + Organization nodes plus a template-specific node (WebPage, BlogPosting, Article/CaseStudy, Service, Review, CollectionPage, FAQPage) — all cross-referenced by @id fragments.

Configure organisation details (name, type, logo, address, geo, sameAs) under Nova Core → Schema.

Bricks accordion FAQ auto-extraction

The per-page Nova Schema sidebar now includes a checkbox: Auto-extract FAQ from Bricks accordion. When checked, the plugin reads _bricks_data and extracts Q/A pairs from the accordion element on that page — no manual entry required.

If a page has multiple accordions, add the CSS class nova-faq to the FAQ accordion in Bricks Builder and that one will be used.

The manual Q/A repeater is still available when auto-extract is off, for pages without Bricks.

Settings page improvements

• New Schema tab
• Shared toggle CSS so all tabs render consistently
• Feature toggle callbacks refactored to a shared renderer

Full Changelog: v0.1.58...v0.1.60

Nova-Core v0.1.58

Full Changelog: v0.1.57...v0.1.58

Nova-Core v0.1.57

Full Changelog: v0.1.56...v0.1.57

Nova-Core v0.1.56

Full Changelog: v0.1.55...v0.1.56

Nova-Core v0.1.55

Full Changelog: v0.1.54...v0.1.55

Nova-Core v0.1.54

Full Changelog: v0.1.53...v0.1.54