The free version is open source. All of it.

Vantage SEO Free is released under the MIT license. You can read the code, run it, change it and ship it. The output is plain HTML you can check in your page source.

License

MIT

Use it on any number of sites, for yourself or for clients. Keep the copyright notice. That is the whole rule.

Repository

Mariomarquezt/vantage-seo

The free plugin source: server, admin screens, editor panel, build scripts and the LICENSE file.

Checks

2,750 tests

Every release runs the full test suite. The free build is also checked so that no Pro code ships inside it.

Where the line is, and why.

One rule decides what is free: if a site is broken or invisible to crawlers without it, it is in the free version.

That covers titles and meta, Open Graph tags, the core schema graph, the sitemap, IndexNow and llms.txt. A site with only the free version is complete in search.

Pro is the work that comes after: monitoring, automation, third-party integrations, features that cost money each time they run, and agent access through the MCP server. Pro lives in a separate private repository and is sold under a commercial license.

The free version shows no ads. Pro features appear locked in place, each with one line that says what it does. Nothing more.

Check the output yourself.

You do not need to trust a score. Open any published page and look.

  1. Publish a page, then open it and view the page source.
  2. Find the block between <!--seo:start--> and <!--seo:end--> in the <head>. Every tag Vantage writes is in that block.
  3. Open the sitemap and llms.txt. The docs list their addresses.
  4. Run a Lighthouse SEO audit on the page. On our test site the published output scores 100.

The optional page-view counter adds one small deferred script. It does nothing unless you turn the counter on. See Privacy and data.

Report a bug or suggest a change.

Open an issue on GitHub. Say what you did, what you expected and what happened. Include your Instatic version and the plugin version from the admin.

For a security problem, do not open a public issue. Write to the security contact instead: [Security contact — set before launch].

Open an issue on GitHub