We measure 5,125 publishers against a 17-signal AI readiness framework. Here is our own score — every signal, honest status, and what we are still building. We should be the best example of what we teach.
Overall score
95
out of 100
Top 1% globally against our own framework
Global average
4.4
out of 100
5,125 publishers, 99 countries
AI Policy
100
out of 100
Editorial Transparency
96
out of 100
Technical Infrastructure
91
out of 100
Score methodology follows our global publisher framework: AI Policy (crawler declaration, llms.txt, ai.txt, tdmrep), Editorial Transparency (named editor, editorial policy, AI use disclosure, AI Act readiness), and Technical Infrastructure (JSON-LD, speakable, canonical, OG, sitemap, NewsArticle schema). Same framework, same weights, applied to ourselves.
AI Policy
robots.txt — AI crawlers explicitly allowed
GPTBot, ClaudeBot, PerplexityBot, Google-Extended, Applebot all explicitly permitted
llms.txt — structured guidance for AI systems
Full context: who we are, what we cover, founder details, citation guidance
ai.txt — formal AI access declaration
Access policy: crawling and citation allowed, training requires license
tdmrep.json — text and data mining rights
Mining and citation permitted, training requires licensing agreement
Editorial Transparency
Named editor — publicly visible and attributed
Susanne Sperling named on About, in JSON-LD Person schema, and in llms.txt
Editorial policy page — published and machine-readable
Covers responsibility, AI use, research standards, corrections, independence
AI use disclosure — how AI is used in content production
Documented in editorial policy. AI-assisted, human-reviewed, human-approved.
AI access policy — formal institutional position
Open for citation, closed for training without license. Documented in ai.txt.
EU AI Act readiness — transparency provisions
Three content types disclosed: AI-assisted (blog/analysis), AI-conducted (Firechat interviews), AI-generated under editorial direction (Moltbook). See editorial policy.
Technical Infrastructure
JSON-LD structured data — all public pages
WebPage, Article, Person, Dataset, FAQPage, SoftwareApplication on relevant pages
Speakable markup — AI reading and citation signals
SpeakableSpecification on all 21 public pages — one of very few publishers with full coverage
Schema.org Organisation + founder identity
Organisation and Person schema with name, URL, contact, sameAs references
Canonical URLs — consistent across all pages
stratechmedia.com canonical on all pages, corrected from legacy publisherpact.com refs
OpenGraph — social and AI preview metadata
Title, description, image, type set globally and per-page
XML Sitemap — dynamic, all public routes
Generated by Next.js sitemap.ts, submitted to search engines and referenced in robots.txt
NewsArticle schema on article pages
Set on research articles and blog posts. Not yet on all content types.
ethicsPolicy — editorial policy referenced in JSON-LD
Organisation JSON-LD references stratechmedia.com/editorial-policy as ethicsPolicy
Why this page exists
Every publisher we work with gets audited against this framework. It would be absurd to hold clients to a standard we do not hold ourselves to. This page is updated whenever our own configuration changes.
The global average across 5,125 publishers is 4.4 out of 100. The gap between 4.4 and 92 is not expensive to close. It is just deliberate.