Novasira – AI SEO Automation, AEO, Schema and MCP for ChatGPT and Claude

Apraksts

Rank better with AI SEO automation. Connect ChatGPT or Claude to WordPress and let it audit your site, then fix titles, meta descriptions and image alt text for you.

Novasira is an AI SEO plugin built around MCP, the open standard that lets an
AI assistant work inside your site. Connect Claude, ChatGPT, Claude Code,
Cursor, VS Code, GitHub Copilot, Windsurf, Codex, Gemini CLI or any other MCP
client, and ask it to do your SEO. It sees what a crawler cannot, including
drafts, private pages and every image’s alt text, finds what is holding your
pages back, lists the fixes in order of importance, and makes the changes when
you say go.

No API key. No account. No monthly fee. No data leaves your site.

An honest note

No plugin can promise rankings, AI citations or traffic, and Novasira does not.
What it does is find and fix the on-site problems that keep good pages from
ranking: missing titles and descriptions, images with no alt text, orphaned
pages, broken canonicals, weak structure for AI answers. It will not invent
traffic numbers, keyword volumes or a “citation score”.

Works alongside Yoast SEO, Rank Math and SEOPress

Keep the SEO plugin you already use. Novasira reads the titles and descriptions
that Yoast SEO, Rank Math and SEOPress store, so its report matches what your
site really outputs. It does not replace them, convert between them or change
their settings, and it adds nothing to your pages: no front-end scripts, styles
or markup.

AI SEO audit with a ranked fix list

• Site health score across every area it can scan on your site.
• What to fix first, worst problem first, with the cheapest wins on top.
• Twenty-six SEO areas with written guidance and a prompt you can copy:
  full audit, action plan, single page, content quality, content briefs,
  topic clusters, internal links, programmatic pages, technical SEO, sitemaps,
  schema, languages, images, alt text, search experience, AI search, agent
  readability, drift, products and local SEO.

Fix titles, meta descriptions and alt text with ChatGPT or Claude

• Ask your AI to find every image with no alt text and write good ones.
• Ask which pages have a missing, duplicate or weak title or meta description.
• Ask it to rewrite a page’s title, description, canonical URL or slug, and
  show you the change before it saves.
• Every write needs an explicit call naming the post or image, a connection you
  gave the write permission, and a user who could edit that item by hand.

AEO and GEO: be the answer AI search quotes

Answer Engine Optimization (AEO) and Generative Engine Optimization (GEO) are
the same fundamentals applied to ChatGPT, Claude, Perplexity, Gemini and Google
AI Overviews. Novasira checks what WordPress can see:

• Whether a page opens with a direct answer and uses question-style headings.
• Self-contained answer blocks, lists and tables, bylines, and published and
  modified dates.
• Whether author profiles are filled in.
• Your robots rules for AI crawlers, and whether an llms.txt file exists.
• Whether an agent can actually read your pages, or whether the content is
  assembled in the browser and invisible to it.

Schema, sitemap and internal link checks

• Read the schema markup on a page and spot what is missing or inconsistent.
• See which pages your sitemap leaves out.
• Find orphaned pages that nothing links to, and pages that deserve more links.

Connect any AI tool over MCP

Novasira → Connect walks you through it in a few steps and gives you
ready-made setup for each tool. Sign in with WordPress (OAuth 2.1) with
per-connection permissions, or use an application password limited to
Novasira’s own endpoint. Nine MCP tools are exposed: scan an area, read the
method, read a site overview, read a page’s SEO, list images with no alt text,
check internal links, read schema, and write SEO fields or alt text.

Safe by design

• The endpoint carries Novasira’s own tools and nothing else. No tool installs
  or changes plugins, themes, users or site settings.
• The agent can write only SEO fields (titles, meta descriptions, canonical
  URLs, slugs, robots flags) and image alt text.
• You choose the permissions on the sign-in screen and can revoke any
  connection at any time.
• No outbound requests, no telemetry, no licence server.

Twenty-six areas

The plugin organises its work into twenty-six SEO areas. Twenty of them are
live: WordPress holds the data, so the area can be scanned against this
site. Six are advisory: the answer lives outside your site, so the area
ships the method and the prompt and says so plainly.

Live areas: full audit, action plan, single page, content quality, content
brief, topic clusters, internal links, programmatic pages, technical, sitemaps,
schema, languages, images, alt text, search experience, AI search, agent
readability, drift, products, local.

Advisory areas: Search Console, backlinks, competitors, keyword data, maps
listing, and the orchestrator page that says which area answers which question.

The advisory split is deliberate. Impressions, rankings, referring domains and
keyword volumes are not stored anywhere in WordPress. Novasira ships no
API key, no crawler and no bundled data service, so for those areas it gives you
the method and the prompt rather than a number it would have had to invent.

Guidance, not a score

Every area carries a written guidance document, which an agent reads through an
MCP tool. Each one answers the same five questions: what the area is about, what
Novasira can actually see from inside WordPress, how to tell a real problem from
a number that merely looks bad, what to do about it cheapest-first, and how you
would know you were wrong.

In the admin, each area has a card naming what it covers, whether it is live or
advisory, and a prompt you can copy and hand to your agent.

That last question is the point. A finding without a falsifiability check is a
guess with a chart next to it.

The agent side

Novasira registers its tools as WordPress abilities and serves them over a
single MCP endpoint on your own site, using the bundled wordpress/mcp-adapter
(GPL-2.0-or-later). You connect your agent to your site; nothing is brokered
through a third party.

Only an authenticated user with the required capability can reach the endpoint.
Novasira → Connect walks through it in a few steps: switch the MCP server
on, pick your AI tool (Claude, ChatGPT, Claude Code, Cursor, VS Code, GitHub
Copilot, Windsurf, Codex, Gemini CLI and more), choose how it signs in, and copy
the ready-made connection for that tool. An agent can sign in in either of two
ways:

• Sign in with WordPress (OAuth 2.1). Clients that support MCP
  authorization, such as Claude, discover the sign-in automatically. An
  administrator approves each connection on a consent screen, choosing which
  permissions it gets (read, write, manage), and can revoke it at any time from
  Novasira → Connect. This uses dynamic client registration, so any client
  can ask to connect; nothing is granted until an administrator approves.
• Application password. Works with every client and every host. The Connect
  screen can create one for you through WordPress core’s own application
  password API, named “Novasira…”, and puts it straight into a prompt and a
  config snippet for the tool you picked. The password is shown once, in that
  page view only; Novasira never stores it (WordPress keeps only its hash, as it
  does for any application password). A key created here is accepted only on
  Novasira’s MCP endpoint: WordPress refuses it on every other REST route and
  on XML-RPC. Keys created here are listed, and can be revoked, under
  Manage connections and keys.

Either way, the agent reaches Novasira’s own tools and nothing else. They read
your content and SEO data, and write only SEO fields: titles, meta
descriptions, canonical URLs, slugs and image alt text. The endpoint does not
carry the MCP adapter’s generic tools for running other plugins’ abilities, and
no tool installs or changes plugins, themes, users or site settings. There is no
Novasira server: the agent you choose connects straight to your site.

For OAuth connections Novasira stores, on your own site: the registered
client’s name and redirect addresses, and for each approved connection a hash
of its access and refresh tokens (never the tokens themselves), the permissions
granted, timestamps, and the IP address it last connected from. Access tokens
last 30 days and renew while in use; an unused connection expires after 180
days. A token is accepted only on Novasira’s own MCP endpoint, never on the
rest of the REST API.

Everything the agent can read, that user could already read in wp-admin, and a
tool that edits a post refuses anybody who could not edit that post by hand.

Credits

• wordpress/mcp-adapter and wordpress/php-mcp-schema by the WordPress AI
  Team (GPL-2.0-or-later), bundled unmodified in vendor/. Sources:
  https://github.com/WordPress/mcp-adapter and
  https://github.com/WordPress/php-mcp-schema

External services

Novasira makes no outbound requests at all. It contacts no API, no licence
server, no update service, no analytics endpoint and no CDN, and sends nothing
anywhere. There is no account to create and no key to enter. The only personal
data it stores is described under “The agent side” above (the last IP address of
each OAuth connection), kept on your own site; suggested privacy-policy text
is added under Settings → Privacy.

The Connect screen has two buttons that open a third-party website in a new
tab, only when you click them. Nothing is sent automatically:

• Add the connector to Claude.ai opens claude.ai’s connector settings, with this site’s MCP
  endpoint address and site name in the link so you do not have to type them.
  Provided by Anthropic. Terms: https://www.anthropic.com/legal/consumer-terms ·
  Privacy: https://www.anthropic.com/legal/privacy
• Open ChatGPT connectors opens chatgpt.com’s connector settings. Provided by OpenAI.
  Terms: https://openai.com/policies/terms-of-use · Privacy:
  https://openai.com/policies/privacy-policy

The plugin bundles wordpress/mcp-adapter (GPL-2.0-or-later, by the WordPress
AI Team) and wordpress/php-mcp-schema. The adapter’s role is to serve an
MCP endpoint on this site — an inbound route under this site’s own REST API. It
does not call out either. Reaching that endpoint requires authenticating as a
user with the capability described above; an unauthenticated request gets
nothing.

The application-password connection snippets tell your AI client to start
@automattic/mcp-wordpress-remote with npx. That is an open-source npm
package (MIT licence, by Automattic) which your own computer downloads from
the npm registry when the client starts it; Novasira does not download, bundle
or run it. It connects only to this site’s MCP endpoint, using the credentials
in the snippet. Source: https://github.com/Automattic/mcp-wordpress-remote ·
npm terms: https://docs.npmjs.com/policies/terms · npm privacy:
https://docs.npmjs.com/policies/privacy

If you connect an AI agent to that endpoint, the agent is software you chose and
run, and whatever it reads from your site travels wherever you have configured
it to travel. That is a property of your agent and your MCP client, not of this
plugin. Novasira itself never initiates a connection.