Two New Features Make LexBlog Content More Findable, Shareable and Citable

We just shipped two features that work at different layers but serve the same goal: making every piece of content in the LexBlog Library easier to find, easier to reference and correctly attributed—whether the reader is a person, a search engine or an AI system.

Here’s what changed and why it matters.

Share the Addressable Headings and Optional Table of Contents (TOC) sectionAddressable Headings and Optional Table of Contents (TOC)

Long-form legal commentary is one of the things that makes LexBlog content valuable. But until now, if you wanted to share a specific section of a post—say, the key takeaway or a particular case analysis—you had to link to the top of the page and hope the reader scrolled down far enough.

That’s no longer the case. Every subheading in a post now gets a stable anchor link, so you can deep-link directly to the section that matters. We’ve also added an optional table of contents that renders at the top of a post with jump links to each section.

A few things worth noting:

• It’s automatic. When an author uses proper heading levels, the system generates anchor links. No manual work required.
• The TOC is opt-in. It’s controlled at the theme level via the WordPress Customizer. Turn it on when it makes sense for your blog; leave it off when it doesn’t.
• Smooth scrolling is built in. Clicking a TOC link scrolls the reader to the section rather than jumping instantly, so it’s clear they’ve moved to a different part of the page.
• It degrades gracefully. No headings in a post? No TOC appears. Post displayed as an excerpt on a homepage? TOC is suppressed.

The feature is live on Stoddard and Apple Fritter.

Share the JSON-LD Structured Data Improvements sectionJSON-LD Structured Data Improvements

This one is invisible to the reader, but it changes how search engines and AI systems understand LexBlog content.

We deployed eight to nine improvements to our structured data output across the entire platform. The highlights:

• Correct schema type. Posts now output as BlogPosting instead of the generic ItemPage. This tells search engines and AI crawlers exactly what the content is.
• Proper multi-author attribution. Co-authored posts now output multiple distinct author nodes in JSON-LD instead of concatenating names into a single string. This is a meaningful differentiator—Yoast and Co-Authors+ don’t do this out of the box, and very few publishers are this thoughtful about structured co-author data.
• Accurate author metadata. Author archive pages now surface the author’s actual portrait image (not a recent post thumbnail) and include a meta description where one was missing.
• Cleaned up social profile URLs. Malformed X/Twitter URLs in author metadata have been corrected.

We deployed the full set of fixes across our banner bear integration, Yoast, Co-Authors+, Apple Fritter and Stoddard—and validated the results with two different structured data testing tools.

Share the Why This Matters sectionWhy This Matters

These aren’t flashy features. One adds navigation and deep links. The other fixes metadata most readers will never see. But together, they move LexBlog content toward being structured for the way legal research and discovery are heading—where AI systems, research platforms and search engines need content that’s not just published, but organized, attributed and citable at the section level.

That’s a meaningful step for the Library. And we’re just getting started.