# Mediaplanning (mediaplanning.io): agent-readiness 43/100, grade D

> Rank 809 of 1000 on Qomvia (rubric v2.3.0). Last scanned 2026-09-29T16:30:39.903Z. Page: https://qomvia.com/site/mediaplanning-io  JSON: https://qomvia.com/api/score/mediaplanning-io

## Summary
Category: Software and SaaS
{
  "known": false,
  "confidence": "low",
  "summary": "I do not have specific pre-existing knowledge about mediaplanning.io from my training data. Therefore, I cannot provide details about its operations or offerings.",
  "offerings": [],
  "audience": null,
  "geography": null,
  "strengths": [],
  "unknowns": [
    "Specific product features and capabilities",
    "Target customer segments and typical use cases",
    "Current market position and competitive landscape",
    "Pricing structures and business model details",
    "Company history, founding team, and funding status"
  ],
  "alternatives": [],
  "business": null,
  "competitors": []
}

## Score by group
- Machine access: 18/24
- Content legibility: 9/26
- Discovery surface: 5/20
- Identity & policy: 3/12
- Agent-facing performance: 8/8
- Agent protocols: 0/10
Failing checks:
- [blocker] No llms.txt
- [blocker] Content is buried in boilerplate
- [blocker] No API or feed to read
- [blocker] No heading hierarchy
- [blocker] Pages are empty without JavaScript

## FAQ
Q: Is Mediaplanning readable by AI agents?
A: Mediaplanning (mediaplanning.io) scores 43 out of 100 for agent readiness, grade D, measured yesterday, on 29.09.2026. 0 of 3 agent classes we test can use the site, and 6 checks currently block agents outright.

Q: What stops agents from using mediaplanning.io?
A: The heaviest problems are: No llms.txt; Content is buried in boilerplate; No API or feed to read; No heading hierarchy; Pages are empty without JavaScript. Each one is scored from a public HTTP response, and the fix for each is listed in the signed-in report.

Q: How is the Mediaplanning agent-readiness score calculated?
A: Qomvia fetches public pages of mediaplanning.io 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.

Q: How often is this score updated?
A: 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.

## Related
- Leaderboard: https://qomvia.com/leaderboard — category ranking: https://qomvia.com/leaderboard/saas-software
- Score another site: https://qomvia.com/