orcid.org

Readiness by lane

Green: orcid.org. Thin bar: Literary & Knowledge peer median.

Priority fixes for orcid.org

Ordered by impact and by how common each practice is among peers.

1. Priority 1 · Enable

   Meta description written

   Observed: The homepage had no meta description.

   Why it matters: Search engines often use it for the snippet under your link, so a clear description can improve click-through.

   What to do: Write a short, specific description of the page for people, not a list of keywords.

   88% of Literary & Knowledge peers do this. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.

   Guide: Meta Titles and Descriptions That Match Search Intent

2. Priority 2 · Harden

   HSTS kept for at least a year

   Observed: The homepage response did not include a Strict-Transport-Security header.

   What to do: Send Strict-Transport-Security on HTTPS responses. Start with a short max-age (for example 300 seconds), confirm every subdomain works over HTTPS, then raise it in steps to 31536000. Add includeSubDomains only when all subdomains are HTTPS. HSTS preload is optional and hard to undo; hstspreload.org itself does not recommend it by default.

   On Cloudflare: Enable HSTS under SSL/TLS > Edge Certificates > HTTP Strict Transport Security and raise max-age gradually.

   28% of Literary & Knowledge peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 2 external scripts without async or defer.

   What to do: Add defer to scripts that need the DOM, async to independent ones such as analytics, or move them to the end of the body.

   48% of Literary & Knowledge peers do this.

   Guide: Control Third-Party Scripts Before They Control Your Page

4. Priority 4 · Enable

   Canonical URL declared

   Observed: The homepage did not declare a canonical URL.

   What to do: Add a self-referencing canonical link to every indexable page, using the final https:// URL.

   67% of Literary & Knowledge peers do this.

   Guide: Canonical Tags: A Decision Guide for Duplicate URLs

What orcid.org already does well

Practices fewer than half of Literary & Knowledge peers use.

• CAA records limit who can issue certificatesCAA limits issuance to amazon.com, comodoca.com, digicert.com and others.13% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=quarantine.22% of peers
• Framing restrictedFraming controls present.37% of peers

What we saw

Homepage checked

https://orcid.org/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Sectigo, 198-day validity, expiring 2026-12-31

CDN or edge

Cloudflare

DNS operators

Cloudflare

DMARC policy

p=quarantine

Homepage HTML

66 KB, gzip

Images on homepage

0

Limits: homepage only, one location, one moment. Header checks reflect the homepage response; other pages may differ.

Stack and providers

Seen in the homepage response, certificate and DNS. Provider pages compare how their customers configure the same checks.

All 31 checks

Select a gap for the method and fix. How each check works

Compare with other Literary & Knowledge sites

• manhwaden.com63
• nettruyen13s.com63
• odbm.org63
• rcsb.org63
• roman-one1.com63

Literary & Knowledge readiness benchmark