Agent-readiness report, Professional services
Is Digitalwerk agent-ready?
No class of agent can use Digitalwerk today: they cannot call it as a tool.
digitalwerk.at, last scanned yesterday, on 29.09.2026
Agent classes working
0/3
Score history
▲ 45 scans since 19.09.2026
- 3
- Blocking agents
- 12
- Weak spots
- 11/26
- Checks passed
What costs Digitalwerk the most
0 of 3 agent classes work
- !Answer engines & research agents
- ✕MCP tool-callers
- !Summarisers & knowledge agents
- ✕
The site does not say who it is
A model cannot tell that this domain is the brand it was asked about.
Blocker - ✕
No API or feed to read
Every integration has to scrape HTML, which most integrators will not do.
Blocker - ✕
No MCP endpoint to call
Tool-calling assistants have no function to call, so they can only scrape.
Blocker - ✕
No stated policy for automated access
Cautious platforms will not act on the site without an explicit permission signal.
Improvement - ✕
No machine-readable contact
When something breaks, an agent operator has no documented way to reach you.
Improvement
✓11 checks passed · 10 more to fix+−
Free dashboard
Track digitalwerk.at and watch it climb.
Weekly re-scans, the fix for every gap above, and the rank moves of your rivals.
- 15 optimization suggestions, ready today
- Weekly re-scan with alerts on every change
- Rank and rival moves in one view
Your dashboard
We email you a sign-in link and add digitalwerk.at to your dashboard.
- Re-scan weekly
- Fixes listed
- Rivals tracked
Check a rival
5 domains free, unlimited with a plan.
Machine interfaces
Digitalwerk exposes 4 of 8 interfaces agents look for: AI crawler access, Bot user-agent handling, Server-rendered content, llms.txt.
Locked
All 8 interfaces and 26 checks for digitalwerk.at
See which interface is missing, what each check looked for, and what to change to pass it. Free account, no card.
View detailed signalsThe seal
Agent-Readable
Agents can read the site, but acting on it still breaks. Paste this line where you want the seal: it is drawn at runtime, so it upgrades itself when you improve and removes itself if a deploy closes the site to agents.
<script src="https://qomvia.com/badge.js" data-slug="digitalwerk-at" async></script>There is no image URL and no static version. The seal exists only as markup we serve per request, which is what makes it worth displaying.
- Agent-Ready Champion90+
- Agent-Ready75+
- Agent-Readable60+
- In Progress40+, dashboard only
Digitalwerk and AI agents: common questions
Is Digitalwerk readable by AI agents?+−
Digitalwerk (digitalwerk.at) scores 63 out of 100 for agent readiness, grade C, measured yesterday, on 29.09.2026. 0 of 3 agent classes we test can use the site, and 3 checks currently block agents outright.
What stops agents from using digitalwerk.at?+−
The heaviest problems are: The site does not say who it is; No API or feed to read; No MCP endpoint to call; No stated policy for automated access; No machine-readable contact. Each one is scored from a public HTTP response, and the fix for each is listed in the signed-in report.
How is the Digitalwerk agent-readiness score calculated?+−
Qomvia fetches public pages of digitalwerk.at as an AI agent would and runs the core checks every site gets across 6 groups: Machine access, Content legibility, Discovery surface, Identity & policy, Agent-facing performance, Agent protocols. Checks are weighted by how much an agent loses when they fail, and the score is expressed out of 100.
How often is this score updated?+−
Public scores are re-checked when the site is re-scanned; tracked domains are re-scanned weekly and their owners are alerted when a check regresses. This page shows the scan from yesterday, on 29.09.2026.
Compare and keep reading
Scores are computed from public HTTP responses only. We never submit forms, never attempt a purchase and never bypass a bot challenge. Disagree with a result? Request a correction or opt this domain out.