Fix guides ยท Emerging standards

Publish OAuth protected resource metadata

Optional, for protected APIs: serve JSON at /.well-known/oauth-protected-resource with a resource field.

Proposal or draft, no proven ranking benefit

What we check

We fetch the well-known path and require valid JSON with a resource field.

5%

of 198 sites we could read pass this.

Why it matters

RFC 9728 is a Proposed Standard. Its only required field is resource, which must match the identifier used to fetch it. Others, like authorization_servers, are optional.

It's only relevant if you run OAuth-protected resources.

How to fix it

  1. Create the JSON document.
  2. Serve it at the well-known path as application/json.
{
  "resource": "https://api.yoursite.com/",
  "authorization_servers": ["https://auth.yoursite.com/"]
}

Fix it yourself with AI

Small fixes shouldn't sit in a queue. Give your AI agent one prompt, and it fixes and deploys for you.

PromptShip is made by the team behind this checker.

Sources

Fixed it?

Run your site through the checker, and re-check after you ship to see what improved.

Check my site

Related guides