AIScan.site

Is vuteem.com AI agent ready? B · 69/100

Re-test this site

vuteem.com

Next.js · 99% confidence
https://vuteem.com/
B69 / 100
Grade B · Level 3GovernedGood — solid foundations, with room to polish.
Discoverability
81Content
50Bot Access
100Capabilities
64Commerce
—
Why we think this is Next.js (3 signals)
  • · x-powered-by: Next.js
  • · hosted on Vercel
  • · /_next/static/ asset

Scan history · 3 public scans of vuteem.com

WhenScoreGradeSnapshot
19 Sept 2026, 18:01 UTC2f530e2969/100BView →
17 Sept 2026, 19:57 UTC2e3cba8b69/100BView →
17 Sept 2026, 19:00 UTC131bed5440/100DView →
6 checks need fixing

3 failed · 3 partial out of 13 that apply to your site.

See top fixes

Fix automatically with AIScan

6 open checks (3 failing) can be handed to an AI agent: D3, C1, C3, P4, E3, E4. 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://vuteem.com/”.

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://vuteem.com/" }.

Option D — REST API
curl -s 'https://aiscan.site/api/public/scan?url=https%3A%2F%2Fvuteem.com%2F'

Returns every check with its complete fix guide.

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

Quick Wins

Top 3 fixes ranked by score impact

  • 01Fail

    Markdown content negotiation

    +8 pts if fixed

    Serve text/markdown when the client sends Accept: text/markdown, or publish /index.md.

    See full details
  • 02Fail

    OAuth discovery metadata

    +4 pts if fixed

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

    See full details
  • 03Fail

    Link header for discovery

    +3 pts if fixed

    Add a Link response header or HTML <link rel="api-catalog"|"describedby"> tag.

    See full details
Hand-off prompt for your coding agent6 issues
# Agent-readiness remediation brief

Site: https://vuteem.com/
Platform: nextjs (99% confidence)
AIScan score: 69/100 — Level 3 (Governed)
Rubric: v2026.08.2

## Failing checks (sorted by weight)
- **[C1] Markdown content negotiation** — FAIL
  - Evidence: Accept: text/markdown → 200 (text/html; charset=utf-8)
  - Fix: Serve text/markdown when the client sends Accept: text/markdown, or publish /index.md.
- **[C3] Structured HTML (title, meta, JSON-LD, single H1)** — PARTIAL
  - Evidence: h1: 2, title: true, meta description: true, JSON-LD: true
  - Fix: Ensure a single <h1>, <title>, meta description, and schema.org JSON-LD.
- **[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.
- **[E3] Heading hierarchy & server-rendered text** — PARTIAL
  - Evidence: 34 words of server-rendered text, 3 <h2>, 0 <h3>
  - Fix: Server-render your main copy and break it into a real heading outline (one h1, then descriptive h2/h3 sections). Agents that don't execute JavaScript only see the HTML you ship.
- **[E4] HTTPS & canonical host** — PARTIAL
  - Evidence: final origin https://vuteem.com · http:// upgrades to https · www.vuteem.com serves its own copy (duplicate origin) · HSTS set
  - Fix: Serve the site over HTTPS, 301-redirect http:// to https://, and redirect the www/apex variant to a single canonical host so agents don't index two copies of every URL.
- **[D3] Link header for discovery** — FAIL
  - Evidence: no Link header or <link> tag
  - Fix: Add a Link response header or HTML <link rel="api-catalog"|"describedby"> tag.

## General guidance
- Static-first: `robots.txt`, `llms.txt`, `/.well-known/*` JSON cards.
- Markdown negotiation: serve `text/markdown` when requested via `Accept` header or `?format=md`.
- Bot access: explicit allow/deny per AI user-agent (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, Applebot-Extended, Bytespider, Amazonbot, CCBot, meta-externalagent, cohere-ai, Diffbot).
- Capabilities: publish an MCP server card and (optionally) an Agent Skills manifest even if the runtime isn't live — discovery first.
- Re-scan at aiscan.site after deploying.

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 Next.js — so checks that don't apply never drag you down.

Essential
27 / 31 pts

Baseline every site should meet.

Recommended
13 / 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

81

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

311

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

    ID · D3

    What we found

    no Link header or <link> tag

    How to fix it

    Add a Link response header or HTML <link rel="api-catalog"|"describedby"> tag.

    Add a Link response header

    Set this header on your homepage and/or root document. Most CDNs (Cloudflare, Vercel, Netlify) support response-header rules.

    Example

    Link: </.well-known/api-catalog>; rel="api-catalog"
    Fix in ChatGPT Fix in Claude

Content

50

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

121

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

    ID · C1

    What we found

    Accept: text/markdown → 200 (text/html; charset=utf-8)

    How to fix it

    Serve text/markdown when the client sends Accept: text/markdown, or publish /index.md.

    Serve text/markdown on Accept negotiation

    When a client sends Accept: text/markdown, return a markdown rendering of the same content. The simplest path is to publish parallel .md files (e.g. /about → /about.md) and rewrite based on the Accept header.

    Test it

    curl -H "Accept: text/markdown" https://yoursite.com/
    Fix in ChatGPT Fix in Claude

Bot Access

100

Are AI crawlers explicitly allowed or blocked?

1

Capabilities

64

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

21

  • 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.

    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.

    Fix in ChatGPT Fix in Claude
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 — vuteem.com graded B
Post on X Share on LinkedIn Share on Facebook

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 vuteem.com on AIScan.site.

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

Create a free account to track this site over time

  • Save scan history
  • See score trends
  • Re-scan anytime
Sign up free Already have an account? Sign in →

Dig deeper

Scan any site from Telegram
Open in Telegram

vuteem.com is built on Next.js. AI-agent readiness for Next.js 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 vuteem.com.

Browse all public scansScan your site