SEO report for www.stanford.edu
https://www.stanford.edu/ · checked Sun, 01 Nov 2026 15:13 GMT
Fix these first
- Entity clarityhigh
No Organization / LocalBusiness structured data – search engines and AI have to guess who runs this site.
Fix: Add Organization or LocalBusiness JSON-LD with name, url, logo, contact details and sameAs links to your official profiles.
- JSON-LD present & validhigh
No JSON-LD structured data.
Fix: Add JSON-LD describing the business and the page (Organization/LocalBusiness, WebSite, WebPage or Article, BreadcrumbList).
- Title tagcritical
“Stanford University”
Fix: Write a unique title of roughly 50–60 characters with the main search phrase first.
- HTML sizemedium
769 kB of HTML – heavy for phones.
Fix: Remove inline bloat, base64 images and unused markup.
- Scripts & third partiesmedium
105 script tag(s); files loaded from 5 other domain(s): t.contentsquare.net, googletagmanager.com, a-us.storyblok.com, a2-us.storyblok.com, youtube.com.
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.
- Canonical URLhigh
Canonical: https://www.stanford.edu/home
Fix: Add <link rel="canonical" href="(this page's full URL)"> – only point it elsewhere for true duplicates.
- Meta descriptionhigh
364 characters, ~2210px of ~990px.
Fix: Write a 140–155 character description that answers the searcher's question and invites the click.
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 stanford.edu…
Indexing & crawling 94%
Can search engines reach, read and index this page?
- ✓
Status codecritical
The page returned HTTP 200.
- ✓
Indexablecritical
No noindex instruction – the page can appear in search.
- ✓
robots.txthigh
robots.txt found.
Googlebot is allowed to crawl this page.
- ✓
XML sitemaphigh
Sitemap found at https://www.stanford.edu/sitemap.xml with 27 URLs.
Declared in robots.txt.
This page is listed in it.
Most recent lastmod: 2026-10-30T20:10:32.205Z.
- !
Canonical URLhigh
Canonical: https://www.stanford.edu/home
Points to a DIFFERENT address – Google will probably index that one instead of this page.
Fix: Add <link rel="canonical" href="(this page's full URL)"> – only point it elsewhere for true duplicates.
- ✓
Redirectshigh
1 redirect before the page loaded.
https://stanford.edu/ → https://www.stanford.edu/
A single redirect to your preferred address is normal; just make sure your own links use the final address.
- ✓
www / non-wwwmedium
stanford.edu redirects to www.stanford.edu.
Search snippet & sharing 67%
How the page looks in Google results and when shared.
- !
Title tagcritical
“Stanford University”
About 169px of Google's ~580px desktop width – short; use the space.
Fix: Write a unique title of roughly 50–60 characters with the main search phrase first.
- !
Meta descriptionhigh
364 characters, ~2210px of ~990px.
Long – Google will probably truncate it.
Google sometimes rewrites descriptions to match the search; a good one is still used most often.
Fix: Write a 140–155 character description that answers the searcher's question and invites the click.
- ✓
Faviconlow
Favicon linked (Google shows it next to results).
- ✓
Languagelow
lang="en"
Content quality 80%
Is there enough clear, useful text that matches what the page targets?
- ✓
Word countmedium
1,019 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 33 (fairly difficult), about 22 words per sentence.
Fix: Use shorter sentences and everyday words – aim for a score of 50+ for customer-facing pages.
- ✓
Topic focushigh
1 of 1 title keywords appear in the main content.
- ✓
H1 headingcritical
“Stanford University”
- !
Heading structuremedium
52 headings for 1019 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
1% of the HTML is visible text.
Fix: Trim unused markup, inline scripts and builder bloat.
AI search readiness 69%
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
2 heading(s) phrased as questions, e.g. “Why democracy may be our best defense against collapse”.
Fix: Add headings that match real questions ("How much does…?") followed by a direct one- or two-sentence answer – an easy format for search and AI answers to quote.
- ✗
Entity clarityhigh
No Organization / LocalBusiness structured data – search engines and AI have to guess who runs this site.
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 0%
Machine-readable facts for rich results and AI.
- ✗
JSON-LD present & validhigh
No JSON-LD structured data.
Fix: Add JSON-LD describing the business and the page (Organization/LocalBusiness, WebSite, WebPage or Article, BreadcrumbList).
Links 100%
Internal linking, anchor text and broken links.
- ✓
Internal linkinghigh
50 internal and 97 external links.
- ✓
Anchor text qualitymedium
No link text points to two different pages.
- ✓
Broken links (sample)high
Checked 12 internal link(s).
No broken links found.
Performance 53%
Speed signals from the HTML and server. Real-user Core Web Vitals load below.
- ✓
Server response (TTFB)high
301 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
769 kB of HTML – heavy for phones.
Fix: Remove inline bloat, base64 images and unused markup.
- ✓
Compressionmedium
Compressed with gzip.
- !
Render-blocking resourceshigh
1 blocking script(s) and 4 stylesheet(s) in <head>.
Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.
- ✗
Scripts & third partiesmedium
105 script tag(s); files loaded from 5 other domain(s): t.contentsquare.net, googletagmanager.com, a-us.storyblok.com, a2-us.storyblok.com, youtube.com.
Fix: Remove unused tracking and widget scripts; every third party adds connection time.
- !
Imagesmedium
23 image(s).
2 without width/height – can cause layout shift (CLS).
The first image is lazy-loaded – if it's the main (LCP) image, that delays it. Don't lazy-load images visible on arrival.
0 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=0,must-revalidate
Fix: Set Cache-Control so browsers and CDNs can reuse the page.
- i
HTTP/3low
Couldn't be confirmed from our server – the alt-svc header that advertises HTTP/3 isn't always visible to it. Your site is on Cloudflare, which offers HTTP/3 under Network settings.
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=31536000; includeSubDomains; preload
- ✓
Security headerslow
Present: CSP, nosniff, Referrer-Policy, Permissions-Policy, clickjacking protection.
- ✗
Server fingerprintlow
X-Powered-By reveals “Next.js”.
Fix: Remove X-Powered-By so attackers can't see your software versions.
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 23 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.