Introducing the LibreCrawl Plugin Workshop: Community-Driven SEO Extensions

Two days ago we shipped LibreCrawl's plugin system. Today we're shipping the other half of the idea: the Plugin Workshop, a free community marketplace where you can browse plugins other people have built, download them, and share your own. If the plugin system gave you the ability to extend your crawler, the Workshop gives you a reason to.

Why a Marketplace at All

Here's the honest version of how this happened. When we built the plugin system, the first question from users wasn't "how do I write a plugin?" It was "where do I find plugins someone else already wrote?" That's a reasonable question, and we didn't have a good answer. Plugins were scattered across GitHub gists, Discord messages, and a couple of forum threads. If you wanted an hreflang validator or a content quality scorer, you had to know it existed and know where to look.

The deeper problem is one every crawler faces: no tool can ship every analysis. We can build solid core features (crawling, link analysis, issue detection, exports), but we cannot anticipate the compliance check a healthcare SEO needs, the reporting format a specific agency's clients expect, or the scoring model one team has refined over five years of audits. Paid tools handle this by adding features to a roadmap and shipping the popular ones eventually. That works for the majority use case and leaves everyone else waiting.

An open source tool can do better. The people who need niche analyses are often the same people capable of building them, especially when a plugin is just a JavaScript file. What was missing was distribution. The Workshop is that distribution layer: a single place where the community's work accumulates instead of evaporating into chat history.

What the Workshop Is

The Plugin Workshop lives at workshop.librecrawl.com. It's a catalog of community-built LibreCrawl plugins that you can browse, download, and contribute to. Three things you can do there:

• Browse - See what other people have built, read plugin descriptions, and look through the source before you commit to anything.
• Download - Every plugin is a plain .js file. Grab it and it's yours, no license fees, no per-seat pricing, no account required to download.
• Share - Upload your own plugins so other people can benefit from the analysis you already built for yourself.

Everything on the Workshop is free and MIT licensed, same as LibreCrawl itself. There is no paid tier, no featured-listing fee, and no plan to add either. The Workshop exists to make the plugin ecosystem useful, not to monetize it.

Installing a Plugin Takes About Thirty Seconds

We were careful not to build a package manager. There's no CLI tool to learn, no dependency resolution, no version lockfile. Installing a plugin from the Workshop works like this:

1. Download the plugin's .js file from the Workshop
2. Drop it into web/static/plugins/ in your LibreCrawl install
3. Refresh your browser

That's the whole process. LibreCrawl picks up every file in that directory automatically, and each plugin registers itself as a new tab in the interface. Run a crawl and the plugin's tab fills with its analysis alongside the built-in tabs. Uninstalling is the same operation in reverse: delete the file, refresh, gone.

If you've used LibreCrawl's example plugins, you've already done this. LibreCrawl ships with several, including the E-E-A-T analyzer (e-e-a-t.js), which scores pages on experience, expertise, authoritativeness, and trust signals. The examples live in the same directory Workshop downloads go into, which means they double as reference implementations. If you're wondering how a Workshop plugin is structured, open e-e-a-t.js in a text editor and read it.

How Plugins Work Under the Hood

We covered the plugin architecture in depth in LibreCrawl's Plugin System: The Future of Extensible SEO Tools, so here's the short version for context.

A plugin is plain JavaScript that calls LibreCrawlPlugin.register() with a name, a tab definition, and the functions that render its analysis. No build step, no framework, no backend code. When a crawl runs, the plugin receives the live crawl data: the URLs discovered, the link graph, the issues LibreCrawl flagged, and the running stats. What the plugin does with that data is entirely up to its author. Aggregate it, score it, chart it, cross-reference it, or format it into the exact table your client wants to see.

Because plugins consume the same data structures LibreCrawl's own tabs use, a community plugin isn't a second-class citizen. It sits in the same tab bar, updates from the same crawl, and has access to everything the built-in analyses do. The difference between a core feature and a plugin is who wrote it, not what it can see.

What We Expect People to Build

We seeded the Workshop with our own example plugins, but the point of a community marketplace is that the community outgrows the seed. Based on what people have already asked for or started building, here's where we think the gaps get filled first:

• Content quality scorers - Every team has its own definition of thin content. A plugin can encode yours: word counts weighted by template type, readability scores, keyword coverage, whatever your model says matters.
• Niche compliance checks - Accessibility statements on every page, required legal disclosures for financial content, cookie consent verification. These are critical for some sites and irrelevant for most, which is exactly why they'll never be core features in any crawler.
• Custom reporting tabs - Agencies repeat the same transformation after every crawl: filter the data, group it, format it the way the client expects. A plugin does that once and then it's a tab.
• Whatever you need - The honest catch-all. The best plugins will be things we didn't predict, built by someone solving their own specific problem.

If you're working through something like our technical SEO audit checklist, you can probably spot two or three checks in your own workflow that LibreCrawl doesn't automate yet. Those are plugin candidates. If you build one, someone else has the same gap.

Sharing Your Own Plugins

Uploading to the Workshop requires an account, and we reused the existing LibreCrawl account system rather than building a new one: verify your email address and you're in. No separate registration, no developer program application, no review queue to wait in.

Once you're signed in, sharing a plugin means uploading your .js file with a name and a description of what it does. That's it. We deliberately kept the bar low because the failure mode we're most worried about isn't low-quality plugins, it's useful plugins that never get shared because publishing felt like a chore.

A Straight Answer on Security

We should be direct about the trade-off in this design, because it matters.

LibreCrawl plugins run entirely client-side, in your own browser, inside your own LibreCrawl install. Nothing executes on our servers, and there is no central runtime we control. The upside is that there's no code review bottleneck between an author publishing a plugin and you using it. We don't gatekeep, and the ecosystem can move as fast as its contributors do.

The downside is the same fact viewed from the other side: we are not reviewing every line of every upload, and you should not treat a Workshop listing as a security guarantee. Before you install a plugin, read its source. Every plugin is a plain, unminified JavaScript file, so this is genuinely practical: open the file and check what it does before you drop it into web/static/plugins/. This is the same discipline anyone running userscripts already practices, and it applies here for the same reasons. Code you run in your browser deserves a look first, whoever wrote it.

We think this is the right trade for an open source tool. A closed review pipeline would make us the bottleneck for a community that exists precisely because we couldn't build everything ourselves. Transparency plus an informed user beats a rubber stamp.

Where This Fits in LibreCrawl's Direction

The last few weeks have been about turning LibreCrawl from a crawler into a platform: the plugin system on November 19, and now the Workshop to give that system a community around it. The pattern behind both is the same one that's guided the project from the start. The core stays focused and free, and the edges stay open so you can shape the tool around your work instead of shaping your work around the tool.

Paid crawlers have real strengths, and we've said so in our comparisons. What they can't offer is this: an extension model where the community owns the catalog, every extension is readable source, and the price of the whole ecosystem is zero. That's the thing an MIT-licensed tool can do that a commercial roadmap structurally can't.

The Workshop is young. The catalog is small today, and it will stay small unless people who build useful plugins decide to share them. If that's you, we'd genuinely like to see what you've made.

Conclusion

The Plugin Workshop is live now at workshop.librecrawl.com. Browsing and downloading require nothing, sharing requires only a verified email, and installing a plugin is a file copy and a refresh. The plugins are plain JavaScript against the LibreCrawlPlugin.register() API, they see your live crawl data, and they run in your own browser under your own inspection.

Key takeaways:

• The Plugin Workshop is a free, MIT-licensed marketplace for community LibreCrawl plugins
• Install any plugin by dropping its .js file into web/static/plugins/ and refreshing
• Plugins receive live crawl data (urls, links, issues, stats) and appear as new tabs automatically
• Sharing requires only the same email-verified account as the hosted service
• Plugins run client-side with no central review, so read the source before installing, same as any userscript