archive.org
Internet Archive: Digital Library of Free & Borrowable Texts, Movies, Music & Wayback Machine
5 failed · 7 warnings · 15 passed
Audited Sat, 11 Jul 2026 20:00:21 GMT · https://archive.org/
Meta & Head
13.9/25
Title, description, canonical, social tags — what search engines read first.
Meta descriptionhigh impactlow effort
No meta description found
The meta description is your ad copy in search results; without one, engines pull an arbitrary snippet from the page, which usually reads poorly and costs you clicks. Add <meta name="description" content="..."> with 70–160 characters that summarize the page and give a concrete reason to click — what the visitor gets plus a differentiator (free, instant, no signup). Write a unique description per page: one duplicated across the site is treated much like a missing one.
Open Graph tagsmedium impactlow effort
No Open Graph tags found
Open Graph tags control how your page looks when shared on Facebook, LinkedIn, Slack, WhatsApp, and most chat apps; without them, links render as a bare URL or with guessed text, and far fewer people click through. Add four meta tags to <head>: og:title, og:description, og:url, and og:image — an image around 1200x630 pixels works well across platforms. Use absolute https:// URLs for og:image and og:url; relative paths are the most common reason preview images silently fail to appear.
Title taghigh impactlow effort
<title> is "Internet Archive: Digital Library of Free & Borrowable Texts, Movies, Music & Wayback Machine" (101 characters)
Search engines truncate titles past roughly 60 characters and often rewrite very short or vague ones, so the message you wrote may never actually be shown. Rewrite the title to 30–60 characters that lead with the primary keyword and end with your brand, e.g. "Merge PDF Files Online Free | YourBrand". Front-load the important words, since truncation always cuts from the end. Don't pad a short title with repeated keywords just to hit the range — clarity wins clicks, not length.
Canonical URLmedium impactlow effort
No <link rel="canonical"> found
When the same page is reachable at several URLs — tracking parameters, trailing-slash variants, http vs https — search engines may split ranking signals across the duplicates. A canonical tag names the one version that should get all the credit. Add <link rel="canonical" href="https://www.example.com/page/"> to the <head>, pointing at the page's preferred absolute URL. Double-check it's self-referencing on the primary version: a canonical that points at the wrong page can quietly de-index the right one.
Twitter card taglow impactlow effort
No twitter:card meta tag found
X (Twitter) layers its own card markup on top of Open Graph, and without a twitter:card tag your shared links may render as plain text instead of a large image preview. Add <meta name="twitter:card" content="summary_large_image"> alongside your Open Graph tags; X will fill in the title, description, and picture from og:title, og:description, and og:image. Keep og:image an absolute URL — a relative or missing image is the usual reason cards show up without a picture.
4 passing checks
- Viewport meta tagViewport is "width=device-width, initial-scale=1"
- Character encoding declaredCharacter encoding is declared
- FaviconA <link rel="icon"> is present
- Page allows indexingNo restrictive robots meta tag
Content & Structure
7.7/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
29 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.
Internal linkingmedium impactmedium effort
0 internal, 0 external links
Search engines discover and rank your pages by following internal links; a page with none is a dead end for crawlers and visitors alike. Add contextual links to related pages on your own site — navigation, related-content sections, and in-body links all count. Aim for at least a handful of relevant internal links per page.
Structured data (JSON-LD)medium impactmedium effort
No JSON-LD structured data blocks found
Structured data makes your listing eligible for rich results — star ratings, FAQs, breadcrumbs, product prices — which occupy more space on the results page and draw more clicks than plain blue links. Add a <script type="application/ld+json"> block with a schema.org type that matches the page: Organization or WebSite for a homepage, Article for posts, Product for product pages. Only mark up content actually visible on the page — markup for invisible content violates Google's guidelines and can earn a manual action.
2 passing checks
- HTML lang attribute<html lang="en">
- JavaScript-dependent contentvisible text ~294 chars in the initial HTML
Technical
22.2/25
HTTPS, redirects, robots, sitemap, speed, crawlability.
HTTP redirects to HTTPSmedium impactlow effort
http:// version serves content without redirecting
Your http:// URLs serve content instead of redirecting, so search engines can crawl and index two parallel copies of every page and split ranking signals between them. Add a permanent 301 redirect from http to https at the server or CDN level — in nginx, "return 301 https://$host$request_uri;" in the port-80 server block; in Apache, a RewriteRule in .htaccess; on Cloudflare, enable "Always Use HTTPS". Use a 301, not a 302 — temporary redirects don't consolidate ranking signals — and preserve the full path in the redirect target.
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.
9 passing checks
- Served over HTTPSfinal URL uses https://
- No mixed content0 http:// subresource references
- Short redirect chainno redirects; URL resolves directly
- robots.txt present and permissiverobots.txt exists and allows crawling
- Fast time to first byte81 ms
- Reasonable HTML size1.8 KB
- 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.