A catalogue of grouped web pages connected to a question panel and analytics chart.
Blog

Q&A, analytics and SEO: managing more of the site

The plugin started with internal links and grew into an editorial pipeline. The latest work widens the scope again: it is becoming a tool for managing more of the site around the articles, including questions, search data, metadata and related collections.

Questions as a content workflow

The Q&A module adds its own storage, administration, front-end routing and rendering, as well as publishing and sitemap behaviour. It also connects to the Journal and automated publishing work. Questions and answers have different structures from a conventional article, so they need their own workflow rather than being treated as ordinary posts with a different title.

I added Q&A statistics and cost tracking as well. These help make activity and model usage visible, although a count or a cost figure cannot tell me whether an answer is correct or useful.

Data and metadata

The analytics module connects to Google Search Console and Google Analytics, with Bing Webmaster support added alongside them. Dashboards bring those external measurements into WordPress. A connection gives me a way to inspect the data; it does not demonstrate that any particular plugin feature improved traffic or rankings.

The SEO suite adds metadata editing, analysis and bulk workflows, including AI-assisted metadata generation. It also includes controls for content types and Qdrant indexing. Those controls matter because the semantic features depend on knowing which content should be indexed and whether it is available for matching.

Collections and relationships

Collections provide structured groupings of content that can be selected and displayed together. They sit alongside the developing vector and internal-linking work: both deal with relationships between pieces of a site, but a curated grouping and a semantic match are different kinds of relationship.

There has been a good deal of interface and technical-debt work around these modules. The aim is to make the separate parts usable as a coherent site-management toolkit, while keeping the limits of the data and automation visible.