Is companyformationbahrain.bh AI agent ready? C · 58/100

companyformationbahrain.bh

Lovable · 70% confidence
https://companyformationbahrain.bh/business-consultant-bahrain
C58 / 100
Grade C · Level 3GovernedFair — agents can find you, but a lot is left on the table.
Why we think this is Lovable (1 signals)
  • · gpteng.co loader script

Scan history · 2 public scans of companyformationbahrain.bh

WhenScoreGradeSnapshot
13 Sept 2026, 2:39 UTC9e0136a558/100CView →
1 Sept 2026, 11:41 UTC698f498e48/100DView →
4 checks need fixing

4 failed out of 13 that apply to your site.

See top fixes

Fix automatically with AIScan

4 open checks (4 failing) can be handed to an AI agent: B2, P1, P4, E2. Pick one route — each returns the full, check-by-check instructions.

Option A — Agent Skill (any runtime)
npx add-skill https://aiscan.site/aiscan-skill.json

Then ask your agent: “Fix the failing AI readiness checks for https://companyformationbahrain.bh/business-consultant-bahrain.

Option B — Claude Code (CLAUDE.md)
curl -o CLAUDE.md https://aiscan.site/CLAUDE.md

Drop it in your project root, then ask Claude Code to fix the failing AIScan checks.

Option C — MCP client
https://aiscan.site/api/mcp

Tools: scan_website, get_fixes, get_grade. Call get_fixes { "url": "https://companyformationbahrain.bh/business-consultant-bahrain" }.

Option D — REST API
curl -s 'https://aiscan.site/api/public/scan?url=https%3A%2F%2Fcompanyformationbahrain.bh%2Fbusiness-consultant-bahrain'

Returns every check with its complete fix guide.

Verify: Re-scan at https://aiscan.site after applying fixes, or run npx aiscan-cli https://companyformationbahrain.bh/business-consultant-bahrain. Individual checks that need a specific probe list it in their own guide.

Quick Wins

Top 3 fixes ranked by score impact

  • 01Fail

    Explicit AI bot rules

    +5 pts if fixed

    Add explicit allow/deny rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc.

    See full details
  • 02Fail

    API Catalog (RFC 9727)

    +4 pts if fixed

    Publish /.well-known/api-catalog linking to your OpenAPI descriptions.

    See full details
  • 03Fail

    OAuth discovery metadata

    +4 pts if fixed

    Publish RFC 8414 / RFC 9728 metadata at the /.well-known/oauth-* endpoints.

    See full details
Hand-off prompt for your coding agent4 issues
You are helping me raise my AIScan.site agent-readiness score.

Site: https://companyformationbahrain.bh/business-consultant-bahrain
Platform: lovable (70% confidence)
AIScan score: 58/100 — Level 3 (Governed)
Rubric: v2026.08.2

Please implement the fixes below. Where a file already exists (e.g. `public/robots.txt`, `public/llms.txt`), edit it; otherwise create it. After each change, briefly explain what you did so I can verify in the next scan.

### Failing checks
- **[B2] Explicit AI bot rules** — FAIL
  - Evidence: 0 known AI agent(s) addressed in robots.txt
  - Fix: Add explicit allow/deny rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc.
- **[P1] API Catalog (RFC 9727)** — FAIL
  - Evidence: 404 at /.well-known/api-catalog
  - Fix: Publish /.well-known/api-catalog linking to your OpenAPI descriptions.
- **[P4] OAuth discovery metadata** — FAIL
  - Evidence: auth-server: 404, protected-resource: 404
  - Fix: Publish RFC 8414 / RFC 9728 metadata at the /.well-known/oauth-* endpoints.
- **[E2] Machine-readable API description** — FAIL
  - Evidence: no /openapi.json, /api/openapi.json or swagger document found
  - Fix: Publish an OpenAPI 3.1 document at /openapi.json and reference it from /.well-known/api-catalog as a service-desc link.

### Constraints
- Do not change visible UI or copy.
- Keep changes additive and reversible.
- Prefer static files in `public/` over server routes when possible.
- For `llms.txt`, generate a real index of the site's most important pages.

How this score is calculated

Every check earns points against a weight. We divide the points you earned by the points that actually apply to a Lovable — so checks that don't apply never drag you down.

Essential
26 / 31 pts

Baseline every site should meet.

Recommended
17 / 28 pts

Strong signals most sites benefit from.

Bonus earned
0 signals

Emerging standards. Can only add points.

Not counted (5): B1, B3, P2, P3, E5 — either not applicable to this site profile or optional and not yet adopted. Expand any check to see the exact evidence we based it on.

Discoverability

100

Can agents find your pages? robots, sitemaps, llms.txt.

5

Content

100

Can agents read your content cleanly? Markdown, structured data.

4

Bot Access

0

Are AI crawlers explicitly allowed or blocked?

1
  • Your site is missing this right now, so AI agents can't use it. The fix below is what to change.

    ID · B2

    What we found

    0 known AI agent(s) addressed in robots.txt

    How to fix it

    Add explicit allow/deny rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc.

    This is a Lovable project

    Edit files directly in the Lovable editor, or ask Lovable AI to apply these changes. Static files like robots.txt, llms.txt, and .well-known/* belong in the public/ folder — they're served from the site root automatically.

    Add explicit User-agent blocks

    Don't rely on User-agent: * alone. Address each major AI crawler so your policy is unambiguous.

    Recommended block

    User-agent: GPTBot
    Allow: /
    
    User-agent: ClaudeBot
    Allow: /
    
    User-agent: PerplexityBot
    Allow: /
    
    User-agent: Google-Extended
    Allow: /
    
    User-agent: Applebot-Extended
    Allow: /

Capabilities

0

Can agents do things? APIs, auth, MCP, Agent Skills.

3
  • Your site is missing this right now, so AI agents can't use it. The fix below is what to change.

    ID · P1

    What we found

    404 at /.well-known/api-catalog

    How to fix it

    Publish /.well-known/api-catalog linking to your OpenAPI descriptions.

    This is a Lovable project

    Edit files directly in the Lovable editor, or ask Lovable AI to apply these changes. Static files like robots.txt, llms.txt, and .well-known/* belong in the public/ folder — they're served from the site root automatically.

    Publish an API catalog (RFC 9727)

    # Add to your homepage HTTP response headers
    Link: </.well-known/api-catalog>; rel="api-catalog"
    
    # And serve a JSON document at /.well-known/api-catalog:
    {
      "links": [
        { "href": "/openapi.json", "rel": "service-desc", "type": "application/openapi+json" }
      ]
    }
  • Your site is missing this right now, so AI agents can't use it. The fix below is what to change.

    ID · P4

    What we found

    auth-server: 404, protected-resource: 404

    How to fix it

    Publish RFC 8414 / RFC 9728 metadata at the /.well-known/oauth-* endpoints.

    This is a Lovable project

    Edit files directly in the Lovable editor, or ask Lovable AI to apply these changes. Static files like robots.txt, llms.txt, and .well-known/* belong in the public/ folder — they're served from the site root automatically.

    Publish OAuth discovery metadata

    If your API supports OAuth, serve RFC 8414 metadata at /.well-known/oauth-authorization-server and/or RFC 9728 at /.well-known/oauth-protected-resource.

  • Your site is missing this right now, so AI agents can't use it. The fix below is what to change.

    ID · E2

    What we found

    no /openapi.json, /api/openapi.json or swagger document found

    How to fix it

    Publish an OpenAPI 3.1 document at /openapi.json and reference it from /.well-known/api-catalog as a service-desc link.

    This is a Lovable project

    Edit files directly in the Lovable editor, or ask Lovable AI to apply these changes. Static files like robots.txt, llms.txt, and .well-known/* belong in the public/ folder — they're served from the site root automatically.

    Publish an OpenAPI 3.1 description

    Serve it at /openapi.json (or /openapi.yaml). Describe every public endpoint, its parameters, and its response schema.

    Advertise it

    Reference it from /.well-known/api-catalog as a service-desc link and from a Link response header.

    Link: </openapi.json>; rel="service-desc"; type="application/json"

    Content sites can skip this

    If you expose no programmatic API, this check is informational and costs you nothing.

Share the result

Share as a social image

Download a 1200×630 social card or post straight to X, LinkedIn or Facebook — sized for every feed.

AIScan share card — companyformationbahrain.bh graded C

Tip: for X and LinkedIn, upload the downloaded PNG with your post so the card shows in the feed. Posts that include just the link will still preview AIScan.site.

Showcase your grade

Embed your AIScan badge

Drop this badge into your site footer, GitHub README, or docs. It links back to a fresh scan of companyformationbahrain.bh on AIScan.site.

AIScan.site grade C
HTML
<!-- AIScan.site agent-readiness badge -->
<a href="https://aiscan.site/?u=https%3A%2F%2Fcompanyformationbahrain.bh%2Fbusiness-consultant-bahrain" target="_blank" rel="noopener" title="Agent-Readiness Grade C (58/100) — AIScan.site">
  <img src="https://aiscan.site/api/public/badge.svg?score=58&grade=C&host=companyformationbahrain.bh" alt="AIScan.site Grade C — 58/100" width="240" height="64" loading="lazy" />
</a>
Markdown
[![AIScan.site Grade C — 58/100](https://aiscan.site/api/public/badge.svg?score=58&grade=C&host=companyformationbahrain.bh)](https://aiscan.site/?u=https%3A%2F%2Fcompanyformationbahrain.bh%2Fbusiness-consultant-bahrain)

Create a free account to track this site over time

  • Save scan history
  • See score trends
  • Re-scan anytime

Dig deeper

Scan any site from Telegram
Open in Telegram

companyformationbahrain.bh is built on Lovable. AI-agent readiness for Lovable apps walks through the same checks on that platform.

Scan any site from Telegram
Open in Telegram

This page always shows the most recent public scan for companyformationbahrain.bh.