SEO report for www.gosh.nhs.uk
https://www.gosh.nhs.uk/ · checked Sun, 01 Nov 2026 15:43 GMT
Fix these first
- Render-blocking resourceshigh
2 blocking script(s) and 1 stylesheet(s) in <head>.
Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.
- LocalBusiness markuphigh
No LocalBusiness structured data.
Fix: Add LocalBusiness JSON-LD with address or areaServed, telephone, geo, opening hours and url.
- Title tagcritical
“Great Ormond Street Hospital | Great Ormond Street Hospital”
Fix: Write a unique title of roughly 50–60 characters with the main search phrase first.
- H1 headingcritical
“Home”
Fix: Use one H1 that states the page topic with its main keyword.
- Freshness signalsmedium
No published/updated date found.
Fix: Show a 'last updated' date and add dateModified to your structured data.
- 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.
- XML sitemaphigh
Sitemap found at https://www.gosh.nhs.uk/sitemap.xml with 4,253 URLs.
Fix: Add a 'Sitemap:' line to robots.txt, list every indexable page and include accurate lastmod dates.
- Meta descriptionhigh
258 characters, ~1566px 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 gosh.nhs.uk…
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.gosh.nhs.uk/sitemap.xml with 4,253 URLs.
Not declared in robots.txt.
This page is listed in it.
Most recent lastmod: 2026-10-29.
Fix: Add a 'Sitemap:' line to robots.txt, list every indexable page and include accurate lastmod dates.
- ✓
Canonical URLhigh
Canonical: https://www.gosh.nhs.uk/
Points to this page (self-referencing).
- ✓
Redirectshigh
1 redirect before the page loaded.
https://gosh.nhs.uk/ → https://www.gosh.nhs.uk/
A single redirect to your preferred address is normal; just make sure your own links use the final address.
- ✓
www / non-wwwmedium
gosh.nhs.uk redirects to www.gosh.nhs.uk.
Search snippet & sharing 67%
How the page looks in Google results and when shared.
- !
Title tagcritical
“Great Ormond Street Hospital | Great Ormond Street Hospital”
About 545px of Google's ~580px desktop width.
Repeated words: great, ormond, street, hospital.
Fix: Write a unique title of roughly 50–60 characters with the main search phrase first.
- !
Meta descriptionhigh
258 characters, ~1566px 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-GB"
Content quality 73%
Is there enough clear, useful text that matches what the page targets?
- ✓
Word countmedium
440 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 56 (fairly easy), about 7 words per sentence.
- ✓
Topic focushigh
4 of 4 title keywords appear in the main content.
- !
H1 headingcritical
“Home”
The H1 shares no keywords with the title.
Fix: Use one H1 that states the page topic with its main keyword.
- !
Heading structuremedium
16 headings for 440 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
6% of the HTML is visible text.
Fix: Trim unused markup, inline scripts and builder bloat.
AI search readiness 75%
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
1 heading(s) phrased as questions, e.g. “What's going on around GOSH”.
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
Identified as: Organization.
2 official profile link(s) (sameAs).
- ✗
Freshness signalsmedium
No published/updated date found.
Fix: Show a 'last updated' date and add dateModified to your structured data.
- ✓
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
2 JSON-LD block(s): Organization, ImageObject, Thing.
All blocks parse correctly.
- ✓
Required propertiesmedium
Key types include Google's required properties.
Links 88%
Internal linking, anchor text and broken links.
- ✓
Internal linkinghigh
123 internal and 15 external links.
- !
Anchor text qualitymedium
Same text used for different pages: “careers”, “research and innovation”, “read more”.
6 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.
Performance 63%
Speed signals from the HTML and server. Real-user Core Web Vitals load below.
- !
Server response (TTFB)high
945 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
93 kB of HTML.
- ✓
Compressionmedium
Compressed with br.
- ✗
Render-blocking resourceshigh
2 blocking script(s) and 1 stylesheet(s) in <head>.
Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.
- ✓
Scripts & third partiesmedium
6 script tag(s); files loaded from 2 other domain(s): cdn-ukwest.onetrust.com, googletagmanager.com.
- !
Imagesmedium
20 image(s).
All images reserve their space.
17 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: s-maxage=1800, stale-while-revalidate=30, public
- 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 96%
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=63072000
- !
Security headerslow
Present: nosniff, Referrer-Policy, clickjacking protection.
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 20 images have alt text.
- ✓
Form labelsmedium
All 2 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 33%
Signals that help you appear in Google Maps and 'near me' searches.
- ✗
LocalBusiness markuphigh
No LocalBusiness structured data.
Fix: Add LocalBusiness JSON-LD with address or areaServed, telephone, geo, opening hours and url.
- ✓
Contact details on pagemedium
No phone number found.
A UK postcode is shown.
- ✗
Map & directionslow
No map or directions link.
Fix: Add a Google Maps directions link so customers can find you.