SEO report for www.cfr.org
https://www.cfr.org/ · checked Sun, 01 Nov 2026 15:01 GMT
Fix these first
- Indexablecritical
The page tells search engines not to index it (noindex).
Fix: Remove the noindex meta tag or X-Robots-Tag header if this page should be found.
- H1 headingcritical
“Informing U.S. engagement with the world”
Fix: Use one H1 that states the page topic with its main keyword.
- HTML sizemedium
935 kB of HTML – heavy for phones.
Fix: Remove inline bloat, base64 images and unused markup.
- Scripts & third partiesmedium
28 script tag(s); files loaded from 0 other domain(s).
Fix: Remove unused tracking and widget scripts; every third party adds connection time.
- Tap-to-contactmedium
No tel: or mailto: links.
Fix: Add a tap-to-call or tap-to-email button so phone visitors can contact you instantly.
- Entity clarityhigh
Identified as: Organization.
Fix: Add Organization or LocalBusiness JSON-LD with name, url, logo, contact details and sameAs links to your official profiles.
- Render-blocking resourceshigh
1 blocking script(s) and 2 stylesheet(s) in <head>.
Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.
- Readabilitymedium
Flesch reading ease 30 (fairly difficult), about 13 words per sentence.
Fix: Use shorter sentences and everyday words – aim for a score of 50+ for customer-facing pages.
Real-world speed Google PageSpeed
Loading Core Web Vitals from Google… this can take up to 30 seconds.
Authority & backlinks
Looking up which websites link to cfr.org…
Indexing & crawling 79%
Can search engines reach, read and index this page?
- ✓
Status codecritical
The page returned HTTP 200.
- ✗
Indexablecritical
The page tells search engines not to index it (noindex).
Fix: Remove the noindex meta tag or X-Robots-Tag header if this page should be found.
- ✓
robots.txthigh
robots.txt found.
Googlebot is allowed to crawl this page.
- ✓
XML sitemaphigh
Sitemap index found at https://www.cfr.org/sitemap.xml listing 6,516 sitemaps.
Declared in robots.txt.
Most recent lastmod: 2026-10-30T15:54:12-04:00.
- ✓
Canonical URLhigh
Canonical: https://www.cfr.org/
Points to this page (self-referencing).
- ✓
Redirectshigh
1 redirect before the page loaded.
https://cfr.org/ → https://www.cfr.org/
A single redirect to your preferred address is normal; just make sure your own links use the final address.
- ✓
www / non-wwwmedium
cfr.org redirects to www.cfr.org.
Search snippet & sharing 100%
How the page looks in Google results and when shared.
- ✓
Title tagcritical
“Council on Foreign Relations”
About 257px of Google's ~580px desktop width.
- ✓
Meta descriptionhigh
117 characters, ~744px of ~990px.
Good length.
Google sometimes rewrites descriptions to match the search; a good one is still used most often.
- ✓
Faviconlow
Favicon linked (Google shows it next to results).
- ✓
Languagelow
lang="en"
Content quality 63%
Is there enough clear, useful text that matches what the page targets?
- ✓
Word countmedium
2,544 words of main content (inside <main>).
Google has no minimum word count – this is a rough guide to whether the page answers the question in full.
- !
Readabilitymedium
Flesch reading ease 30 (fairly difficult), about 13 words per sentence.
Fix: Use shorter sentences and everyday words – aim for a score of 50+ for customer-facing pages.
- ✓
Topic focushigh
3 of 3 title keywords appear in the main content.
- !
H1 headingcritical
“Informing U.S. engagement with the world”
The H1 shares no keywords with the title.
Fix: Use one H1 that states the page topic with its main keyword.
- !
Heading structuremedium
113 headings for 2544 words – a lot for the amount of text.
1 skipped level(s), e.g. H2 → H4.
Fix: Use H2s for main sections and H3s inside them, without skipping levels.
- ✗
Text-to-code ratiolow
2% of the HTML is visible text.
Fix: Trim unused markup, inline scripts and builder bloat.
AI search readiness 84%
Can ChatGPT, Claude, Perplexity and Google AI Overviews read, understand and cite this site?
- ✓
AI crawler accesshigh
Search and AI-search crawlers (Googlebot, Bingbot, OAI-SearchBot, Claude-SearchBot, PerplexityBot…) can read this page.
- ✓
Snippet controlshigh
No snippet restrictions – search and AI answers can quote this page.
- ✗
llms.txtlow
No /llms.txt file. It's an optional, emerging convention – few AI tools are confirmed to read it yet, so this is low priority.
Fix: Optionally add /llms.txt: a short Markdown summary of who you are with links to your key pages.
- ✓
Question-led contentmedium
20 heading(s) phrased as questions, e.g. “Can the United States Lead Through Transactional Foreign Policy?”.
- !
Entity clarityhigh
Identified as: Organization.
No sameAs links to official profiles (Google Business Profile, LinkedIn, Facebook, Companies House…).
Fix: Add Organization or LocalBusiness JSON-LD with name, url, logo, contact details and sameAs links to your official profiles.
- ✓
Freshness signalsmedium
The page shows when it was published or last updated.
- ✓
Trust pages (E-E-A-T)medium
Links found to all three: about, contact and privacy.
Structured data 100%
Machine-readable facts for rich results and AI.
- ✓
JSON-LD present & validhigh
1 JSON-LD block(s): WebSite, Organization, SearchAction.
All blocks parse correctly.
- ✓
Required propertiesmedium
Key types include Google's required properties.
Links 88%
Internal linking, anchor text and broken links.
- ✓
Internal linkinghigh
121 internal and 15 external links.
- !
Anchor text qualitymedium
Same text used for different pages: “can the united states lead through transactional foreign policy?”, “war in ukraine”, “read more”, “view all”.
2 vague link(s) like “click here” or “read more”.
Fix: Make every link text describe its destination, e.g. “logo design prices” instead of “click here”.
- ✓
Broken links (sample)high
Checked 12 internal link(s).
No broken links found.
2 link(s) point to a redirect – link to the final address instead.
Performance 54%
Speed signals from the HTML and server. Real-user Core Web Vitals load below.
- ✓
Server response (TTFB)high
137 ms until the first response from our checker, including connection setup (Google rates TTFB good under 0.8 s, poor over 1.8 s).
- ✗
HTML sizemedium
935 kB of HTML – heavy for phones.
Fix: Remove inline bloat, base64 images and unused markup.
- i
Compressionmedium
Couldn't be measured from our server (our fetch decodes compressed pages before we see them). Check in your browser's developer tools that HTML is sent with br or gzip.
- !
Render-blocking resourceshigh
1 blocking script(s) and 2 stylesheet(s) in <head>.
Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.
- ✗
Scripts & third partiesmedium
28 script tag(s); files loaded from 0 other domain(s).
Fix: Remove unused tracking and widget scripts; every third party adds connection time.
- !
Imagesmedium
111 image(s).
1 without width/height – can cause layout shift (CLS).
1 image(s) after the first three aren't lazy-loaded.
110 use WebP/AVIF or responsive srcset.
Fix: Give every image width and height, lazy-load images below the fold (but not the main image) and serve WebP/AVIF.
- ✓
Cachinglow
Cache-Control: public, max-age=3600, stale-while-revalidate=3600, stale-if-error=86400
- ✓
HTTP/3low
Server advertises HTTP/3 (faster on mobile networks).
Security 92%
Visitor safety signals that browsers and Google check.
- ✓
HTTPScritical
Secure HTTPS with no mixed content.
- ✓
HTTP → HTTPS redirecthigh
http:// redirects to https://.
- ✓
HSTSmedium
HSTS: max-age=15552000; includeSubDomains; preload
- ✗
Security headerslow
Present: nosniff.
Fix: Add X-Content-Type-Options, Referrer-Policy, Permissions-Policy and X-Frame-Options (or a CSP).
- ✓
Server fingerprintlow
No X-Powered-By header (server: cloudflare).
Mobile & accessibility 83%
Usable on phones and by everyone – Google indexes the mobile version.
- ✓
Mobile viewportcritical
viewport: width=device-width, initial-scale=1
- ✓
Image alt textmedium
All 111 images have alt text.
- ✓
Form labelsmedium
All 1 form fields are labelled.
- ✓
Link nameslow
Every link has a readable name.
- ✗
Tap-to-contactmedium
No tel: or mailto: links.
Fix: Add a tap-to-call or tap-to-email button so phone visitors can contact you instantly.
Local SEO not scored
This site doesn't look like a local business, so these checks are shown for information and not scored.
- i
LocalBusiness markuphigh
No LocalBusiness structured data.
- i
Contact details on pagemedium
No phone number found.
No postcode found (fine for service-area businesses).
- i
Map & directionslow
No map or directions link.