cnn.com
Breaking News, Latest News and Videos | CNN
3 failed · 4 warnings · 23 passed
Audited Sat, 11 Jul 2026 20:30:52 GMT · https://www.cnn.com/
Meta & Head
23.6/25
Title, description, canonical, social tags — what search engines read first.
Open Graph tagsmedium impactlow effort
Missing Open Graph tags: og:description
Your Open Graph markup is incomplete, so social platforms fall back to guessed text or drop the preview image entirely when this page is shared — a broken card gets far fewer clicks than a complete one. Add the missing og:description tag to <head>. For og:image, use an absolute https:// URL to an image around 1200x630 pixels; relative paths are the usual reason previews break. Re-check with a platform's sharing debugger afterwards, since preview cards are cached.
8 passing checks
- Title tag<title> is "Breaking News, Latest News and Videos | CNN" (43 characters)
- Meta descriptionMeta description is "View the latest news and breaking news today for U.S., world, weather, entertainment, politics and health at CNN.com." (117 characters)
- Canonical URLCanonical href is "https://www.cnn.com"
- Viewport meta tagViewport is "width=device-width,initial-scale=1,shrink-to-fit=no"
- Character encoding declaredCharacter encoding is declared
- FaviconA <link rel="icon"> is present
- Twitter card tagtwitter:card is "summary_large_image"
- Page allows indexingNo restrictive robots meta tag
Content & Structure
16.2/25
Headings, copy depth, images, structured data, internal linking.
Single H1 headinghigh impactlow effort
0 h1 headings found
The h1 is the visible headline of the page and one of the clearest signals to search engines of what it's about; with none present, engines lean on surrounding text and may misread the topic. Add exactly one h1 near the top that states the main topic in plain language and includes the primary keyword, e.g. <h1>Merge PDF Files Online</h1>. Don't fake it with a styled <div> — the semantic tag itself is what crawlers and screen readers actually read.
Word counthigh impactlow effort
261 words of visible text
Under 300 words, search engines typically classify a page as thin content, and thin pages rarely rank for anything competitive. Decide which query this page should answer, then write substantive copy — aim for 600+ words covering what it is, how it works, common questions, and concrete examples. If the page genuinely has nothing more to say, merge it into a stronger related page with a 301 redirect rather than padding it with filler that helps no one.
7 passing checks
- Heading hierarchy13 headings in order without skipped levels
- Image alt text33 of 33 images have alt text
- Structured data (JSON-LD)JSON-LD types found: WebPage
- Hreflang annotations4 valid hreflang link(s) including x-default
- HTML lang attribute<html lang="en">
- JavaScript-dependent contentvisible text ~61446 chars in the initial HTML
- Internal linking385 internal, 48 external links
Technical
21/25
HTTPS, redirects, robots, sitemap, speed, crawlability.
Reasonable HTML sizelow impactmedium effort
4.8 MB
A very large HTML document slows parsing on every visit and risks exceeding the portion of a file crawlers are willing to fetch — content past the cutoff may simply never be indexed. Slim it down: move large inline <script> and <style> blocks into external cacheable files, strip embedded JSON data blobs and base64-encoded images, and paginate or lazy-load very long listings. Check the most common culprit first: a framework serializing the entire page state or dataset into the document itself.
Short redirect chainmedium impactlow effort
https://cnn.com/ (301) → https://www.cnn.com/
Every redirect hop adds a round-trip before the visitor sees anything, each hop can leak a little link equity, and crawlers abandon long chains — which can leave the destination page undiscovered. Trace the chain above and point the first URL directly at the final destination in a single 301; commonly this means merging separate http-to-https and non-www-to-www rules into one combined redirect. Also update internal links to reference the final URL directly, so most visitors never enter the chain at all.
XML sitemap availablemedium impactlow effort
no sitemap.xml found
Without an XML sitemap, search engines discover pages only by following links, so new, deep, or weakly linked pages get found slowly or not at all. Generate one at /sitemap.xml — most frameworks and CMSs have a generator built in or as a plugin — listing every canonical, indexable URL, then add "Sitemap: https://www.example.com/sitemap.xml" to robots.txt and submit it in Google Search Console. Keep it clean: listing redirected, noindexed, or 404 URLs erodes crawler trust in the whole file.
Response compression enabledlow impactlow effort
no content-encoding header
This HTML is served uncompressed, so every visitor downloads far more bytes than necessary — text compresses extremely well, and the savings directly speed up first render on slow connections. Enable Brotli or gzip on your server or CDN: in nginx it's "gzip on;" (or the brotli module), in Apache it's mod_deflate via .htaccess, and on most CDNs it's a single toggle. Make sure compression covers all text types (HTML, CSS, JS, JSON, SVG), but skip already-compressed images — recompressing them wastes CPU for no gain.
8 passing checks
- Served over HTTPSfinal URL uses https://
- HTTP redirects to HTTPShttp:// redirects to https://
- No mixed content0 http:// subresource references
- robots.txt present and permissiverobots.txt exists and allows crawling
- Fast time to first byte305 ms
- Missing pages return 404missing paths return HTTP 404/410
- www and non-www resolve consistentlywww and non-www converge on the same host
- HTML5 doctype<!DOCTYPE html> present
Performance
Core Web Vitals scoring via Google PageSpeed is coming soon.
Share your score
Embed this live badge on your site — it updates whenever the audit is re-run.