SEO report for www.unizar.es
https://www.unizar.es/ · checked Sun, 01 Nov 2026 20:13 GMT
Fix these first
- H1 headingcritical
No H1 heading.
Fix: Use one H1 that states the page topic with its main keyword.
- XML sitemaphigh
No XML sitemap found at /sitemap.xml or in robots.txt.
Fix: Create an XML sitemap listing every page and submit it in Google Search Console.
- Meta descriptionhigh
No meta description – Google will pick text from the page.
Fix: Write a 140–155 character description that answers the searcher's question and invites the click.
- 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).
- Render-blocking resourceshigh
9 blocking script(s) and 99 stylesheet(s) in <head>.
Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.
- Title tagcritical
“Universidad de Zaragoza | Universidad de Zaragoza”
Fix: Write a unique title of roughly 50–60 characters with the main search phrase first.
- Open Graph & social cardsmedium
Open Graph title or image missing.
Fix: Add og:title, og:description, og:image (1200×630 PNG/JPG, absolute URL) and twitter:card=summary_large_image.
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 unizar.es…
Indexing & crawling 88%
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
No XML sitemap found at /sitemap.xml or in robots.txt.
Fix: Create an XML sitemap listing every page and submit it in Google Search Console.
- ✓
Canonical URLhigh
Canonical: https://www.unizar.es/
Points to this page (self-referencing).
- ✓
Redirectshigh
1 redirect before the page loaded.
https://unizar.es/ → https://www.unizar.es/
A single redirect to your preferred address is normal; just make sure your own links use the final address.
- ✓
www / non-wwwmedium
unizar.es redirects to www.unizar.es.
- ✓
hreflangmedium
1 hreflang link(s).
All language codes are valid.
No x-default (recommended for a language picker or fallback page).
Search snippet & sharing 38%
How the page looks in Google results and when shared.
- !
Title tagcritical
“Universidad de Zaragoza | Universidad de Zaragoza”
About 463px of Google's ~580px desktop width.
Repeated words: universidad, zaragoza.
Fix: Write a unique title of roughly 50–60 characters with the main search phrase first.
- ✗
Meta descriptionhigh
No meta description – Google will pick text from the page.
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="es"
Content quality 42%
Is there enough clear, useful text that matches what the page targets?
- !
Word countmedium
331 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.
Fix: Add genuinely useful content: key service pages usually need 400+ words to answer what customers ask.
- i
Readabilitymedium
Reading-ease scores only work for English; this page is lang="es".
- ✓
Topic focushigh
2 of 2 title keywords appear in the main content.
- ✗
H1 headingcritical
No H1 heading.
Fix: Use one H1 that states the page topic with its main keyword.
- !
Heading structuremedium
16 headings for 331 words – a lot for the amount of text.
Levels are in order.
Fix: Use H2s for main sections and H3s inside them, without skipping levels.
- !
Text-to-code ratiolow
7% of the HTML is visible text.
Fix: Trim unused markup, inline scripts and builder bloat.
AI search readiness 50%
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
No headings phrased as questions.
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 contact; missing about and privacy.
Fix: Link to About, Contact and Privacy pages from every page – they help visitors, Google and AI tools see who stands behind the content.
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 90%
Internal linking, anchor text and broken links.
- ✓
Internal linkinghigh
137 internal and 302 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.
- !
Internal links to http://medium
7 internal link(s) use http:// – each one goes through a redirect.
Fix: Update internal links to use https:// (or relative links).
Performance 40%
Speed signals from the HTML and server. Real-user Core Web Vitals load below.
- !
Server response (TTFB)high
944 ms until the first response from our checker, including connection setup (Google rates TTFB good under 0.8 s, poor over 1.8 s).
Fix: Use page caching or a CDN (e.g. Cloudflare) so HTML is served from the edge.
- !
HTML sizemedium
197 kB of HTML.
Fix: Remove inline bloat, base64 images and unused markup.
- ✓
Compressionmedium
Compressed with gzip.
- ✗
Render-blocking resourceshigh
9 blocking script(s) and 99 stylesheet(s) in <head>.
Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.
- ✗
Scripts & third partiesmedium
81 script tag(s); files loaded from 5 other domain(s): fonts.googleapis.com, tag.oniad.com, cdn-eu.readspeaker.com, static.addtoany.com, code.jquery.com.
Fix: Remove unused tracking and widget scripts; every third party adds connection time.
- !
Imagesmedium
42 image(s).
2 without width/height – can cause layout shift (CLS).
28 image(s) after the first three aren't lazy-loaded.
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: must-revalidate, no-cache, private
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 75%
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=300
max-age is under 6 months – browsers will forget it quickly.
Fix: Add Strict-Transport-Security: max-age=63072000; includeSubDomains.
- ✗
Security headerslow
Present: nosniff, clickjacking protection.
Fix: Add X-Content-Type-Options, Referrer-Policy, Permissions-Policy and X-Frame-Options (or a CSP).
- ✗
Server fingerprintlow
X-Powered-By reveals “PHP/8.2.35”.
Fix: Remove X-Powered-By so attackers can't see your software versions.
Mobile & accessibility 67%
Usable on phones and by everyone – Google indexes the mobile version.
- ✓
Mobile viewportcritical
viewport: width=device-width, initial-scale=1
- ✗
Image alt textmedium
8 of 42 images have no alt attribute.
Fix: Describe each meaningful image in its alt attribute (use alt="" for decorative ones).
- ✗
Form labelsmedium
1 of 1 form field(s) have no label.
Fix: Give every form field a <label> or aria-label (a placeholder isn't a label).
- ✓
Link nameslow
Every link has a readable name.
- ✓
Tap-to-contactmedium
One-tap contact: email.
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.
- ✓
Contact details on pagemedium
No phone number found.
No postcode found (fine for service-area businesses).
An email link is shown.
- i
Map & directionslow
No map or directions link.