Local on Windows · Developed by CoreWeb Studio
Obserya audits a site on your own machine and ties every finding to the affected page and the value found there. The result is an action plan for the client and for the people doing the work.
The application interface is currently in German. Screenshots on this page show it as it is.
Obserya is website audit software built by CoreWeb Studio for Windows. It crawls a site locally, scores technical SEO and AI readiness on two separate axes, and backs every finding with the affected page and the value found there. From that it produces a prioritised action plan, a PDF client report and technical exports.
Why Obserya exists
An audit score describes a state but assigns nobody any work. Which page is affected and who tackles what first is settled by hand after the crawl. Obserya pulls that into the analysis.
Metric
A number with no address
The value moves. The pages behind it stay invisible.
Finding
The finding gets its pages
The displayed count opens the URLs behind it.
Evidence
The value found is attached
For a broken link, the target and anchor text as found.
Action
With an owner and a first step
Ranked by effort and impact, ready to hand over.
Obserya replaces neither an enterprise crawler nor keyword research. It covers the stretch in between, where signals turn into ranked work packages.
How Obserya works
Each step carries the previous step’s data forward — so any finding traces back to its source.
The site is captured on your own machine.
Obserya fetches and parses pages while following internal links. The result is a page inventory with HTML, metadata and status codes.
A legal notice is not judged like a service page.
Every page is assigned a role. A missing meta description weighs differently on a utility page than on a service page.
Two axes, scored separately.
Technical SEO and on-page on one side, AI readiness and GEO signals on the other — with no third number blending the two.
Every finding carries its proof.
A finding consists of the affected page, the issue and the value found. Where no location can be established, the report says so.
Order comes from effort, impact and evidence.
What can be tackled straight away is kept apart from what needs verifying — each with an owner and a first step.
Results leave the tool in a usable form.
The client report explains the state without SEO vocabulary; the exports pass the same data to the implementation team.
Detail from “How Obserya Works” — the view follows the step on the left.
Tap a step.
Full workflow
How Obserya Works: six steps from the local crawl through to reports and exports, with the local-first architecture and optional LLM path below.
Tap a step.
What Obserya checks
Technical SEO describes the foundation for classic search, AI readiness how well the same page reads as an answer source.
Why there is no third score
A page can be technically sound and still be hard to use as an answer source. An average would hide that difference.
Visibility foundation for classic search
Local SEOOptional
Local signals run as an optional block at project level; a full area is still ahead.
Usability as an answer source
Findings and evidence
Six findings from a demo audit. The technical key appears the same way in the exports.
Select a finding
Finding types and actions match the application; quantities come from the demo audit.
Technical SEO · Internal linking
Links lead nowhere: an empty target, a bare hash, or a script call.
Evidence quality and urgency are two different things
A finding whose evidence only partly holds up is filed under “verify first” rather than in the immediate list.
Prioritisation and drilldowns
Obserya ranks findings by impact, effort and evidence quality, and shows its working.
Score class
Where the measured value sits on the scale.
A project scoring 91 falls into the “Good” class.
Action status
Whether evidenced findings are still open.
That same project can still carry confirmed work.
Both appear separately in the report and are easily confused.
The labels come from the report and describe how quickly something can be picked up — not deadlines.
Low effort
This week
Well evidenced and actionable without further checks.
More effort
This month
Clear in substance, heavier to implement.
Check before acting
Verify first
Evidenced, but worth confirming manually once.
Bar width matches the value range: “Very good” covers five points, “Significant work needed” covers sixty-one.
Both scores, all areas, the overall count.
One analysis area with its value and findings.
The issue with its cause, action and affected pages.
The specific URL with the value found there.
Every level stays navigable.
Local-first architecture
Crawl, analysis, scoring and report generation all run locally; audit data sits in a database on the device.
Only the crawl of the target site needs network access.
Leaves the device only when triggered
The whole chain stays on the device
From page capture through to the finished report.
Audit data stays on the device
Crawl and page data, findings, evidence and project settings.
No service in between
The core workflow needs no account and no API key.
Sending data out is a decision
Whether anything leaves is decided by the user, per task.
Everything inside the large block runs in the application. Only the dashed path at the bottom right leaves the device.
Full view
Obserya System Architecture: input signals, the local application with its ingestion, analysis and decision layers, local audit data, outputs and the optional LLM path.
Select a section.
Optional AI assistance
Crawl, analysis and scoring are rule-based. No language model contributes to scores or core findings, which keeps results reproducible in a client meeting.
This is why Obserya is not positioned as an AI tool.
Three stages run locally, only the last one leaves the device.
Off by default
Audits, reports and startup all work without a language model.
One task, one prompt
A selected task produces a structured prompt with context.
The user triggers it
A call happens only when it is initiated.
Additive, never scoring
A result may add suggestions. Scores and core findings stay untouched.
Client reports and exports
The client report explains the state in plain language and separates confirmed work from open checks.
Audit state
Pages, findings, evidence and scores.
Prioritisation
Impact, effort and evidence quality set the order.
Report pages
Summary judgement, status and action plan.
Output
PDF for the client, CSV and JSON for the work ahead.
Swipe · tap for the full page
The same findings, keys and evidence — once as a report, once as a file.
For the client
For the implementation team
Where it fits
A working tool for recurring audits. Six situations from practice.
Taking on a new client site
A new site arrives, and a proposal depends on that first assessment.
Create the project, crawl locally, run the audit.
A PDF for the client meeting, a CSV for the estimate.
Built for
The focus is on small and mid-sized agencies with recurring audit work.
Development status
Obserya is developed at CoreWeb Studio as an in-house audit tool, tested against real client projects.
Planned, and not available today.
No reliable statement can be made about release date, pricing or distribution.
Common questions
These answers describe the current development status.
Website audit software built by CoreWeb Studio for Windows. It crawls locally, scores technical SEO and AI readiness separately, and backs every finding with the affected page and the value found. Output: an action plan, a PDF client report and technical exports.
Yes. Crawl, analysis, scoring and report generation run in the desktop application, and audit data stays in a local database. Only the crawl needs network access.
No, those three steps are rule-based. Optional LLM assistance applies only to a selected task and changes neither scores nor core findings.
Technical SEO covers seven core areas: indexing and crawlability, document structure, meta and snippet basics, content basics, internal linking, structured data, and images and page elements; Local SEO runs alongside as an option. AI readiness scores six dimensions on its own axis, from answer clarity through to context density.
A finding names the affected pages and the value found — for a broken link, the target and anchor text. Where evidence only partly holds up, Obserya flags it for verification.
A client report as PDF, plus HTML as a shareable report, CSV for working data, JSON as a raw export, Markdown, and an Obsidian-compatible export.
Primarily small and mid-sized web, SEO and digital agencies handing audit results to clients and implementation teams. Freelancers and in-house teams too.
Obserya is developed and used internally at CoreWeb Studio. The audit core, reports and exports are built; the installer, full JavaScript rendering and a standalone Local SEO area are in progress. There is no public access, sign-up or download.
Obserya comes out of day-to-day audit work at CoreWeb Studio — where crawl data has to turn into something a client will read and a team can work through.