Composing Scores: From Codesheet to Rehearsal

,
3 minutes
Orchestra rehearsal inside a concert hall.

This post is part of the Composing Scores series:

In Movement I of this series, we laid out the design for an optimization strategy. The goal was to find a unified way to handle the overlapping requirements of modern visibility: SEO, SMO, AEO, LLMO, and AIO.

Up until now, these optimizations were already running quietly backstage on this site. They lived as a collection of isolated custom functions and hooks. While that setup provided great benchmarks and handled about 75% of the heavy lifting directly inside the editor, managing multiple fragmented pieces of code is not sustainable for the long haul.

The goal of this initiative was to take those proven, isolated efforts and package them into a single, cohesive engine. Today, that work is complete, and the project has officially moved into the open.

Table of Contents

The Source Code is on GitHub

The foundational mechanics are now fully assembled, unified, and public.

You can review, and inspect the entire code and the logic over at the Gregius Optimizer repository on GitHub.

Consolidating these features meant translating our existing site configurations into lightweight, structured PHP and JavaScript. By bundling the code into a unified plugin, it ensures your content does not just speak to traditional search indexers, but routes cleanly through language models, answer engines, and semantic crawlers without the code bloat.

Submitted to the WordPress Plugin Directory

While the raw code lives on GitHub for developers to audit and test, a smooth rollout requires an accessible home. To make deployment seamless for those who prefer to keep things simple rather than diving into the code, we have officially submitted the plugin to the WordPress Plugin Directory. At the moment, the project is under review.

What Happens Next?

Consider this the final technical rehearsal. The foundational work is unified, and complete.

Once the WordPress review team gives the green light, we will publish the third post in this series. That will mark the official premiere, complete with the live WordPress.org directory link, an overview of the dashboard interface, and a quick setup guide to help you automate your optimization scores.

Until then, feel free to check out the Gregius Optimizer repository on GitHub.

Now Available on WordPress.org. Install the plugin directly from the official WordPress Plugin Directory.

Frequently Asked Questions

The Gregius Optimizer is a unified WordPress plugin that consolidates five optimization dimensions — SEO, SMO, AEO, LLMO, and AIO — into a single, lightweight engine. It bundles sitemap generation, robots.txt directives, Open Graph and Schema.org structured data, and /llms.txt context provisioning into editor-native controls, replacing the fragmented custom functions that power the optimizations described in Movement I.

Movement I described the manual approach — custom PHP action filters, individual inspector control components, and postmeta fields built directly into the theme. The Gregius Optimizer packages those same strategies into a standalone, portable plugin that can be installed on any WordPress site without touching the theme code.

The plugin is currently under review. WordPress.org review timelines vary based on queue volume and the complexity of the submission. The third post in this series will announce the live directory link as soon as the review concludes.

Yes. The complete source code is available at the Gregius Optimizer repository on GitHub. You can audit the logic, review the architecture, and test it locally before it appears in the WordPress directory.

Stay tuned.

Next Steps

Gregius Optimizer is fully open-source, transparent, and built for modern development workflows.

Available on WordPress.org: Install the plugin directly from the official in the WordPress Plugin Directory.

View on GitHub: You can review, fork, and inspect the entire codebase and core logic over at the repository on GitHub.

Documentation: Read the setup guides and technical documentation below to get started.

  • Sitemap – Control which content appears in your XML sitemap
  • Robots.txt – Configure crawl directives for search engines and AI bots
  • Schema – Add structured data markup to help search engines understand your content
  • Social Card – Control how your content appears when shared on social media and in search results.
  • LLMs – Optimize your site for AI agents and large language models with an /llms.txt file

Photo credit Manuel Nägeli • Culture Casino Bern, Bern, Switzerland

Hector Jarquin Avatar

Sign up for the newsletter

Practical insights on how real-world AI adoption is reshaping the open web.