justified.gg

Publish a discoverable agent-skills index so AI agents can find and load your structured skill bundles.

Agent Skills index exists but does not list any SKILL.md paths

Publish a skills discovery index at /.well-known/agent-skills/index.json (per the Agent Skills Discovery RFC v0.2.0) with a `$schema` field and a `skills` array. Each entry should have `name`, `type`, `description`, `url`, and a `sha256` digest of the SKILL.md so agents can verify integrity. Make sure each `url` resolves to a reachable SKILL.md.

Publish an A2A Agent Card so other agents can discover your agent-to-agent capabilities and supported interfaces.

No agent-to-agent surface was detected, so A2A agent-card discovery may not apply

Publish /.well-known/agent-card.json describing your agent: `name`, `description`, `endpoints`, `version`, and a complete `supportedInterfaces` array with the protocols and message types you accept. Include a `capabilities` block so calling agents can negotiate, and keep the URL stable across deploys — agents cache discovery responses.

Expose in-page tools to AI agents via the WebMCP browser API so agents can act on your site directly.

No in-page agent tool surface was detected, so WebMCP may not apply

Implement the WebMCP API by calling `navigator.modelContext.provideContext()` with tool definitions exposing your site's key actions to AI agents. Each tool needs `name`, `description`, `inputSchema` (JSON Schema), and an `execute` callback. Register tools at the points an agent could meaningfully use them — after page hydration, on route changes, or when permission state changes.

Each indexable page carries enough unique, substantive content to merit indexing on its own without overlapping siblings.

2 page(s) are under 100 words; 3 page(s) are between 100 and 300 words; 0 duplicate-content fingerprint group(s) were detected.

Audit indexable pages for substantive, unique content — at minimum a few hundred words of original copy that delivers on the title and description. Consolidate near-duplicate pages with canonical tags or merge them into a single richer page. Don't ship placeholder "Coming soon" pages to production indexable URLs.

• /changelog/gmod/darkrp
• /gallery
• justified.gg
• /rules/discord
• /streamers

Robots meta tags and X-Robots-Tag headers align with which pages should actually be crawled and ranked.

1 sampled public page(s) are marked noindex.

Audit `<meta name="robots">` tags and `X-Robots-Tag` response headers across the site. Remove `noindex` and `nofollow` from any page meant to appear in search, especially on staging templates that leaked into production. For pages that genuinely should be excluded (admin, internal tools), keep the directive but verify the URL isn't also linked from a sitemap.

• /changelog/gmod/darkrp

Each page has a clear heading hierarchy with one h1 and properly nested h2/h3 sections so structure conveys meaning to readers and crawlers.

1 H1 issue(s) and 0 skipped heading hierarchy warning(s) were detected.

Use exactly one `<h1>` per page that conveys the page's subject, then nest `<h2>` sections beneath it and `<h3>` for sub-sections — never skip levels (h1 → h3) or wrap headings in `<div>` for styling. Headings communicate document structure to assistive tech and crawlers; write them as outline entries, not as styled text.

• justified.gg

Internal links use descriptive anchor text and form a reachable graph so crawlers, readers, and AI agents can navigate context.

51 link crawlability or anchor-text warning(s) were detected.

Use real `<a href="...">` elements for navigation — never `<div onclick>` or button-styled spans, which crawlers can't follow. Write descriptive anchor text that summarizes the destination (avoid "click here", "read more", or naked URLs). Keep important pages within ~3 clicks of the homepage so crawl depth doesn't starve them.

• justified.gg
• /changelog/gmod/darkrp
• /gallery
• /guides/gmod/basics/change-playermodel
• /privacy

Article-like and substantial pages expose reliable freshness signals so answer engines know whether the content is current.

8 content page(s) have no reliable date signal and 0 have a newest signal older than six months.

Add truthful freshness metadata only where it reflects a real content update: JSON-LD dateModified/datePublished, article modified-time meta tags, a visible updated or reviewed date, or sitemap lastmod. Do not stamp every page with build time unless the visible content actually changed.

• justified.gg
• /privacy
• /ranks
• /rules/discord
• /store

Content pages with factual claims link out to credible external primary sources so readers and answer engines can verify context.

5 content page(s) have fewer than two contextual external citation links.

For articles, guides, and research-like pages, cite official docs, standards, primary research, or authoritative sources where claims need support. Do not add arbitrary outbound links to transactional pages, and avoid vague anchors like "click here".

• /guides/gmod/basics/change-playermodel
• /ranks
• /store
• /wiki/casino/coinflip
• /rules/gmod/darkrp/actions

Every indexable page has a single meta description (50-160 chars) that previews the page accurately for search and social.

0 sampled page(s) have missing or multiple meta descriptions; 1 description quality warning(s) were detected.

Add one `<meta name="description">` tag to each important indexable page — 50–180 characters of distinct, human-readable copy that previews the page accurately. Avoid copying the title, padding with keywords, or duplicating descriptions across pages; search engines either rewrite duplicates or skip them entirely.

• /changelog/gmod/darkrp

Each indexable page declares one canonical URL pointing to itself or the definitive original, so search engines consolidate ranking signals.

0 canonical error(s) and 1 canonical warning(s) were detected in the sample.

Add exactly one `<link rel="canonical" href="...">` per indexable page in the document head, with an absolute URL pointing to the preferred version (after redirects, with the right protocol and trailing-slash policy). Self-canonical is fine for the original; cross-canonical only when consolidating duplicates. Never canonicalize to a noindexed or 404 page.

• /changelog/gmod/darkrp

No visible FAQ-style questions or FAQPage JSON-LD were detected.

Add visible question-and-answer sections only where they genuinely help users make a decision or complete a task.

Pages declare language and region alternates with hreflang annotations when content varies by locale, so search engines route the right version to the right reader.

No hreflang annotations were detected in the sampled pages.

On each localized page, add `<link rel="alternate" hreflang="...">` tags pointing to every language/region variant (including a self-reference). Use valid IANA language-region codes (e.g. `en-US`, `fr-FR`), absolute `href` URLs, and one `hreflang="x-default"` entry pointing to the version for unspecified locales. Each variant must reciprocally link back.

Lightweight server and document metrics from the sampled homepage are captured every scan so drift in HTML size, server stack, or DOM complexity is observable across reports.

Captured lightweight server and document metrics from the sampled homepage.

Content-Security-Policy is missing

Publish a baseline Content-Security-Policy for the site shell.

HTTP Observatory grade C with score 55.

Tighten response headers and HTTP posture where Observatory reports gaps.

Identify your own bot traffic with Web Bot Auth signed requests so receiving sites can verify and trust them.

Web Bot Auth HTTP Message Signatures directory is missing

Publish a JWKS at /.well-known/http-message-signatures-directory containing the public keys you use to sign outgoing bot requests, so receiving sites can verify those requests via HTTP Message Signatures (RFC 9421). Rotate keys on a regular cadence and keep the previous key in the JWKS until in-flight requests have aged out.

No Cloudflare Challenge Page marker was detected on the homepage response.

Domain registration data is temporarily unavailable.

PSI mobile performance score is 85.

Improve mobile Lighthouse performance issues highlighted by PageSpeed Insights.

Publish Agentic Commerce Protocol discovery so agents can transact with your commerce surfaces without scraping.

No ACP discovery markers were detected

Serve /.well-known/acp.json at the origin root with `protocol.name` set to `"acp"`, the `protocol.version`, `api_base_url`, supported transports, and `capabilities.services`. Agents can then discover your ACP implementation without first creating a checkout session.

Publish Machine Payment Protocol metadata so agents can discover paid endpoints in your API.

No MPP discovery markers were detected

Publish an OpenAPI document at /openapi.json with `x-payment-info` extensions on payable operations. Each operation should declare `intent` (charge or session), `method` (tempo, stripe, lightning, card), `amount`, and `currency`. Use the MPP SDK (`mppx` for TypeScript, `pympp` for Python) with framework middleware for Hono, Express, Next.js, or Elysia to handle the payment flow.

Expose Universal Commerce Protocol metadata so agents can transact for content or services through a standard interface.

No UCP discovery markers were detected

Serve /.well-known/ucp with your protocol version, declared `services`, supported `capabilities`, and reachable `endpoints`. Make sure any spec URLs and referenced JSON Schemas resolve so agents can validate against them at discovery time.

Support x402-style HTTP 402 payment flows so agents can pay for API access machine-to-machine.

No x402 discovery markers were detected

Add x402 payment middleware to your API routes so AI agents can pay for access via HTTP. Use `@x402/express`, `@x402/hono`, or `@x402/next` middleware with a facilitator URL and wallet address. Protected routes will return HTTP 402 with payment requirements that agents can fulfill automatically.

Scanned 12 representative pages out of 202.

No Cloudflare-generated error diagnostics were detected on the homepage response.

No Cloudflare product beacons were detected in the homepage response.

Detected 2 public DNS/service signal(s).

HTML validation is temporarily unavailable.