SEOriva SEO Audit Tool: Features, MCP Server and Pricing

The SEOriva SEO audit tool checks every page on a website for on-page, technical, security and WordPress problems, then connects that audit to real Google Search Console data and, if you want it, to an AI assistant through an MCP server. This guide covers what it does, how each part works, what it costs and who it suits. Disclosure: I built SEOriva, and I use it to run the SEO routines on this blog.

What is SEOriva?

Most SEO tools give you a score and a wall of data. SEOriva is built around a different question: what should I fix next, and did the last fix work? It scans every URL in your sitemap, scores each page, turns the failures into a prioritised fix list, and then layers your Search Console numbers on top so you can see which problems matter on pages that actually get traffic.

It was built for freelancers, small business owners and agencies who want the checklist run automatically, and for developers who want to hand the results straight to a coding agent. Sign-in is Google OAuth only, so there are no passwords to leak. Billing runs through Stripe, so card details never touch SEOriva. There are no advertising or analytics trackers on the site.

What the audit checks

Each scan runs a large set of checks across categories, and every check has a plain-English explanation of why it matters. Here is what is covered.

On-page SEO

• Title tag present and a sensible length (ideally 50 to 60 characters).
• Meta description present and a sensible length (ideally 150 to 160 characters).
• Exactly one H1, and an H1 that is not empty.
• Image alt attributes, canonical tags and Open Graph tags.
• Indexability: it warns if a page is accidentally set to noindex, the most common reason a page silently disappears from search.
• Viewport meta tag, favicon, and published and last-modified dates, which help freshness signals.

The full list is on the on-page SEO checks page.

Technical checks

HTTPS, a clean 200 response, a reachable robots.txt, document size, Time to First Byte, the status of your canonical URL, mobile viewport settings and loading hints such as lazy loading and preconnect. It also checks for an llms.txt file, the emerging convention that gives AI crawlers a curated summary of your site. See the technical checks for the details.

Security headers and TLS

Content-Security-Policy, Strict-Transport-Security, X-Frame-Options, X-Content-Type-Options, Referrer-Policy and Permissions-Policy. Beyond headers it looks for server and PHP version disclosure, cookie security flags, mixed content, outdated JavaScript libraries, CORS misconfiguration and the presence of a web application firewall. It also checks certificate validity, expiry, hostname match and signature algorithm, plus DNS CAA records. It probes for exposed sensitive files such as .env, .git/config and wp-config.php. The security checks page lists them all.

WordPress security

SEOriva detects WordPress, compares your core version against the latest release from WordPress.org, and flags an exposed xmlrpc.php, plugin paths and theme slugs in your page source. Those details let attackers fingerprint your stack, so hiding them is cheap protection. More on the WordPress security checks.

HTML validation, sitemap and links

HTML checks cover the doctype, the lang attribute, character encoding, deprecated elements, duplicate IDs and empty links. The sitemap and link checks confirm the sitemap exists, is valid XML and uses the right host, and look at internal link counts, broken links and redirect chains. See HTML validation and sitemap and links.

Scans, scores and history

SEOriva discovers your pages from your sitemap and audits each one. Scans are throttled with a sliding window of about five seconds between page requests, so auditing your site never looks like an attack and does not trigger false alarms from your firewall. Paid plans re-scan the whole sitemap automatically on the first of each month, so you can see whether your score is trending the right way, and you can re-run any URL whenever you like.

Each page gets a score from 0 to 100 and a good, moderate or poor rating. Score history is kept per URL, which means a regression shows up as a line going down, not as something you notice three months later.

Search Console insights

Connect Google Search Console with read-only OAuth and SEOriva matches the right property to your project, including www, non-www and domain property variations. For every audited page you then see clicks, impressions, click-through rate, average position and the top keywords driving traffic. You can filter by publish date to compare new posts with older ones. Disconnecting deletes the stored tokens and synced metrics immediately. Details are on the Search Console page.

Putting audit scores next to search data is where it gets useful. A page with a poor score and thousands of impressions is a priority. A page with a poor score and no traffic can wait.

Opportunities and revision tracking

This part is plain arithmetic on your own Search Console data, with no AI involved. SEOriva highlights:

• Ranking quick wins: pages sitting around positions 11 to 17 with real impressions, where a small improvement could reach page one.
• Click-through quick wins: pages ranking in the top 12 but getting under 0.5 percent of clicks, where a better title and description can lift traffic without changing rank.
• Best pages to refresh next: your top pages by impressions that either rank poorly or rank well but get few clicks, each tagged with the type of fix needed.
• Top 50 movers: who moved up, who dropped, who entered and who left since the last sync.

Noindexed pages, the homepage and anything you have already revised are left out, so the lists stay worth reading. When you update a page, log it, and SEOriva freezes its current numbers as a baseline. After 28 days it marks the revision as improving, flat or worse. Search Console uses a rolling 90-day window, so a verdict on one page is approximate and it is better to judge a batch of edits together. The honest labels are the point: the tool will say too early or no data when that is the truth. See the opportunities page.

AI suggestions on your own key

SEOriva can draft title and description rewrites, explain why a page is underperforming, and suggest focus keywords picked from the page’s own search queries. It runs on your own Anthropic or OpenAI API key, which is checked with a small test call and stored encrypted. Nothing runs in the background: a suggestion is only generated when you click, and you can set a monthly token cap.

Rewrites are written as natural copy, checked for length and keyword use, and fed back so that a suggestion you dismiss is not offered again. Page content is treated as untrusted data and never as instructions, and nothing is published to your site. Anthropic has said that Claude Max, Ultra and Team subscribers receive monthly API credits that work with an API key, so suggestions can cost nothing extra, though you should check the current terms on your own plan. More on the AI suggestions page.

WordPress content planning

For WordPress sites, SEOriva can connect read-only using an Application Password. It mirrors your posts, categories and, where Rank Math or Yoast expose them, the SEO fields. From that it builds a weekly workflow:

• Metadata audit: scores every indexed post on title, description and focus keyword and shows what improved or slipped since last week.
• Pillar analysis: maps your top pages to topic areas and splits the week’s draft slots by what earns clicks, not by what you publish most.
• Trend research and gap analysis: live web search for what is new, checked strictly against everything published, scheduled, earmarked or rejected. A topic is only a gap if nothing already covers it.
• Topic backlog and series: ideas land in a backlog, series are proposed from proven demand, and rejected ideas are never proposed twice.
• Weekly drafts and diagnosed revisions: ready-to-paste Gutenberg blocks with slug, excerpt, categories and SEO fields, and for pages that already earn impressions, a diagnosis plus a revised draft that keeps the slug.

Crucially, nothing is published for you. Every draft and revision is a recommendation to review. Counts, scores and comparisons are plain code, and AI is used only for judgement and writing. This is the same approach I use on this blog. The content planning page has the full description.

The SEOriva MCP server

MCP, the Model Context Protocol, is an open standard that lets AI assistants call tools exposed by a service, with your explicit authorisation. SEOriva runs an MCP server so Claude, ChatGPT or any MCP-compatible client can read your live audit results and Search Console data and answer questions about them, instead of you copying data into a chat window. The server is available on the Pro and Agency plans.

Connect in under a minute

In Claude Code, add the server with one command and then authorise with your SEOriva account. It uses standard OAuth with an mcp:use scope, so there are no API keys to copy around.

claude mcp add --transport http seoriva https://seoriva.com/mcp

For Claude Desktop and other clients, add a remote server in the settings with the same URL.

The 13 tools

• list_sites: list your projects. Almost every conversation starts here.
• get_site_pages: every audited page with its score and rating.
• get_page_results: the full pass, fail and warn breakdown for one audit.
• get_urls_by_filter: every URL failing a specific check, such as missing meta descriptions or broken links.
• get_fix_plan: a complete fix-everything Markdown document with every failure, why it matters, how to fix it and every affected URL.
• get_site_performance: rank pages by clicks, impressions, CTR or position, optionally filtered by publish date.
• get_page_keywords: the search queries driving traffic to one page.
• set_focus_keywords: set or clear focus keywords for many pages in one batch.
• rescan_pages: queue fresh audits for up to 50 pages after you fix something.
• get_opportunities: ranking and click-through quick wins plus refresh candidates.
• get_top_movers: rank changes between the last two Search Console syncs.
• log_revision: freeze a page’s current numbers as a baseline.
• get_revision_results: compare revised pages with their baselines and get a verdict.

What you can ask

• “Which pages are missing meta descriptions?”
• “What are my five posts with the fewest clicks published this year?”
• “What keywords is my technical SEO checklist post ranking for?”
• “What are my easiest SEO wins this month?”
• “Did my content revisions help?”
• “Fix everything wrong with my site.”

The last one is the powerful one. get_fix_plan returns every issue with its affected URLs in a single document, which a coding agent can work through from top to bottom. After it fixes things, it calls rescan_pages and checks the new scores. Browsing, fixing one issue everywhere, fixing a whole site and understanding search performance each have a natural tool chain, and there are worked examples with sample responses on the MCP tools page.

Reports for clients and fix lists for agents

Agencies can send clients a branded report link with their scores, checks and every page that passes or fails. The link needs no login and is protected by a PIN, so it is never publicly crawlable. For developers, every failure and warning is available as one Markdown fix-it list, either as a download or over MCP, ready to hand to Claude, Cursor or any coding agent.

Launch checklist and free scan

A lot of launch-day problems are the same: a forgotten noindex tag, robots.txt still blocking crawlers from staging, no SSL redirect, canonical tags pointing at the staging domain, or broken links left over from a migration. SEOriva turns that into an automated day-one checklist. There is a free scan that needs no card, and a website launch checklist you can work through before you point DNS at a new site.

It also tracks your domain authority using the OpenPageRank 0 to 10 score. Every refresh is stored, so you can see whether a link-building or content campaign is moving the number.

Pricing

Every paid plan starts with a 14-day free trial and can be cancelled from the billing portal.

• Starter, £9 a month: one project, up to 100 URLs, all SEO checks, HTML validation, WordPress and security checks, sitemap scanning and monthly auto-scans.
• Pro, £29 a month: up to 10 projects with up to 1,000 URLs each, PDF reports, and the MCP server.
• Agency, £99 a month: unlimited projects and URLs, unlimited refreshes and the MCP server.

AI suggestions and WordPress content planning are included on every paid plan, with AI usage billed to your own provider key.

Who SEOriva is for

• Bloggers and publishers who want to know which old posts to refresh and which titles to rewrite.
• WordPress site owners who want security and metadata problems caught early.
• Agencies and freelancers who need repeatable audits and client-ready reports.
• Developers using AI coding agents who want a machine-readable list of everything wrong with a site.

How I use it on this blog

Each week the same loop runs against this blog: pull the top pages by clicks and impressions, look for ranking and click-through quick wins, diagnose a few underperforming posts from their real queries, draft the revisions, and then check weeks later whether they helped. SEOriva’s MCP server makes that loop something an assistant can do in conversation, and the revision baselines mean I find out whether an edit worked instead of guessing.

Get started

The quickest way in is the free scan: enter a URL and see the results with no card. If you like it, the plans above start with a 14-day trial. Questions can go to hi@seoriva.com, which goes to a real inbox. Visit SEOriva to try it.