# Velcomeseo (velcomeseo.fr): agent-readiness 55/100, grade D

> Rank 552 of 1000 on Qomvia (rubric v2.3.0). Last scanned 2026-09-29T00:00:16.940Z. Page: https://qomvia.com/site/velcomeseo-fr  JSON: https://qomvia.com/api/score/velcomeseo-fr

## Summary

{
  "known": false,
  "confidence": "low",
  "summary": "Velcome SEO presents itself as an SEO agency aiming to drive growth for businesses. It positions client websites as acquisition sources by improving Google rankings and converting prospects.",
  "offerings": [
    "SEO services",
    "Natural referencing",
    "SEA campaign optimization",
    "Website development and optimization",
    "UX optimization for SEO"
  ],
  "audience": "Businesses seeking to increase online visibility and convert prospects",
  "geography": "France and Europe",
  "strengths": [],
  "unknowns": [
    "Specific client results or testimonials",
    "Pricing structure details",
    "Specific methodologies or tools used",
    "Company size and team expertise",
    "Full list of services beyond what is mentioned"
  ],
  "alternatives": [],
  "business": "An SEO agency claiming to provide natural referencing, SEA optimization, and website development services for businesses in France and Europe, focused on converting prospects.",
  "competitors": []
}

## Score by group
- Machine access: 24/24
- Content legibility: 21/26
- Discovery surface: 5/20
- Identity & policy: 0/12
- Agent-facing performance: 5/8
- Agent protocols: 0/10
Failing checks:
- [blocker] No llms.txt
- [blocker] The site does not say who it is
- [blocker] No API or feed to read
- [blocker] No MCP endpoint to call
- [improvement] No stated policy for automated access

## FAQ
Q: Is Velcomeseo readable by AI agents?
A: Velcomeseo (velcomeseo.fr) scores 55 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 4 checks currently block agents outright.

Q: What stops agents from using velcomeseo.fr?
A: The heaviest problems are: No llms.txt; 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. 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 Velcomeseo agent-readiness score calculated?
A: Qomvia fetches public pages of velcomeseo.fr 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
- Score another site: https://qomvia.com/