Skip to content
  • AI visibility
  • Integrations
  • MCP
  • Pricing
  • Documentation

Research, write, optimise, publish and measure — with every number telling you where it came from.

© Copyright 2026 Noverva. All Rights Reserved.

Platform
  • AI visibility
  • Integrations
  • MCP
  • Pricing
Resources
  • Documentation
  • Blog
  • Changelog
  • FAQ
  • Contact
Legal
  • Terms of Service
  • Privacy Policy
  • Cookie Policy
  • AI visibility
  • Integrations
  • MCP
  • Pricing
  • Documentation
  • Changelog
    Sep 5, 2026

    Your own API keys, and an audit that explains itself

    Programmatic access with scoped keys, a command centre that opens with the last crawl, filters that survive a shared link, and searchable documentation.

    Two weeks of work on the parts you touch every day.

    API keys, from the product. Create a key, scope it, revoke it. The key is shown once and never again, because only a hash of it is stored — there is no version of "show me that key again" that we can honestly offer.

    A versioned API. Ask Noverva to crawl a site over HTTP behind a write scope. The API describes itself at /api/v1/openapi, so a client can be generated rather than hand-written.

    Agent access carries the rules with it. Noverva's MCP server gained prompts and resources. The prompts include the honesty rules, so a model reading opportunity scores is told, in the same breath, that they are not search demand. An agent inherits your authorisation exactly — anything you could not do in the application fails in MCP with the same error.

    The command centre opens with what happened. Pages read, findings that need attention, opportunities scored, and the three highest, from the most recent crawl.

    Filters that survive being shared. Findings and opportunities can be filtered and sorted, and that state lives in the URL. Send someone the view you are looking at and they see the same one. A finding also links to the page it is about, which sounds small until you have read forty of them.

    The audit reports your internal link graph. Orphaned pages, pages reachable from only one place, and how densely the site links to itself.

    Better terms, from better reading. Pages are now read from their main content region, so navigation and footer text no longer read as things the site is about. Four separate faults that invented phrases nobody had written are fixed — the one that produced "continue withsign" came from words welded together across two HTML elements.

    Documentation you can search, grouped by category, with the search field appearing once there are enough pages to need one.

    Smaller things. Every footer link now meets the minimum target size; nine of thirteen were under it, the smallest at 17 pixels. Transactional emails carry Noverva's own design rather than a framework's default.

    Previous

    Connect a site, and it gets crawled

    Aug 26, 2026
    Next

    Plans, pricing, and a 14-day trial

    Sep 6, 2026