GeoChecker.Umbraco 1.1.1

GEO Checker for Umbraco

An AI Readiness dashboard inside the Umbraco backoffice. One button: it scores how ready the site is to be found and cited by AI engines, explains every finding, and links out to the full report.

Free, and intended to stay free.

What it checks

Exactly what the browser extension and the web scanner check, because it is the same engine: llms.txt, llms-full.txt, robots.txt AI-bot rules, sitemap, Schema.org JSON-LD, title & meta description, canonical, Open Graph, indexability, plus the two informational signals (ai.txt, Content-Signal).

It scores nothing itself. See "How it is wired" below — that is the whole design.

Install

dotnet add package GeoChecker.Umbraco

The dashboard appears in Content → AI Readiness. No Startup.cs change: the IComposer is discovered when the assembly is referenced.

The same NuGet supports both backoffice generations: Umbraco 13 reads package.manifest and loads the AngularJS dashboard; Umbraco 14-17 read umbraco-package.json and load the web-component dashboard.

Configuration

Everything is optional.

{
  "GeoChecker": {
    // Point at your own geo-web instance to keep scans inside your infrastructure.
    "ApiBaseUrl": "https://www.geochecker.app",

    // The public URL to scan. Set this when editors work on a staging hostname —
    // otherwise you will be scoring the staging site, not production.
    "SiteUrl": "https://www.example.com",

    "TimeoutSeconds": 30
  }
}

When SiteUrl is empty the package uses the public address Umbraco reports for the site, falling back to the host of the backoffice request. The dashboard always shows which of the three it used, so a scan of the wrong host is visible rather than mysterious.

ApiBaseUrl defaults to the production scanner (https://www.geochecker.app), so a fresh install talks to production with no configuration.

How it is wired

backoffice dashboard (wwwroot/dashboard.js)
        │  fetch (AllowAnonymous — public data only)
        ▼
GeoCheckerApiController        /umbraco/backoffice/GeoChecker/GeoCheckerApi/{site,scan}
        │  server-side HTTP
        ▼
GEO Checker scan API           POST {ApiBaseUrl}/api/scan
        │
        ▼
geo-scan engine                the one implementation of what we check

Three deliberate choices:

1. No checks are re-implemented in C#. The engine is the single source of truth for what is checked and how it is scored. This package is a thin client over it.
2. The scan is proxied server-side, not called from the dashboard's JavaScript. That avoids CORS and does not open the public scan endpoint to every backoffice origin on the internet.
3. The what/why/fix copy is a generated file, wwwroot/checks.json, so the plugin cannot quietly start telling people something different from the report.
4. Version handling lives at the shell only. Umbraco 13 gets a small AngularJS dashboard; Umbraco 14-17 get the existing web component. Both call the same C# controller and the same GEO Checker scan API.

Licence

MIT — see the LICENSE file in this package. Copyright (c) 2026 4SPACES Sp. z o.o. (dba Startup Island).