SEO report

SEO report for hessen.de

https://hessen.de/ · checked Sun, 01 Nov 2026 18:17 GMT

✓ 32 Passed! 6 Warnings✗ 9 FailedAI readiness 47%Built with Drupal

Fix these first

  1. Broken links (sample)high

    Checked 12 internal link(s).

    Fix: Fix or remove links that return errors, and update links that redirect.

    See the details

  2. H1 headingcritical

    4 H1 headings – one clear H1 is best practice.

    Fix: Use one H1 that states the page topic with its main keyword.

    See the details

  3. 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.

    See the details

  4. 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.

    See the details

  5. Freshness signalsmedium

    No published/updated date found.

    Fix: Show a 'last updated' date and add dateModified to your structured data.

    See the details

  6. Trust pages (E-E-A-T)medium

    No links found to about, contact or privacy pages.

    Fix: Link to About, Contact and Privacy pages from every page – they help visitors, Google and AI tools see who stands behind the content.

    See the details

  7. HTML sizemedium

    980 kB of HTML – heavy for phones (we only analysed the first 1 MB).

    Fix: Remove inline bloat, base64 images and unused markup.

    See the details

  8. Imagesmedium

    53 image(s).

    Fix: Give every image width and height, lazy-load images below the fold (but not the main image) and serve WebP/AVIF.

    See the details

Check the whole website

This report covers one page. The full-site audit crawls up to 250 pages to find broken links, duplicate titles, orphan pages and more.

Run a full-site audit

Monitor this site weekly

We'll re-check it every week and track the score, with a history graph and a list of anything that breaks.

Compare with competitors

See how this page scores against up to two competitors, side by side, and where they beat you.

Compare sites

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 hessen.de…

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 index found at https://hessen.de/sitemap.xml listing 5 sitemaps.

    Not declared in robots.txt.

    Most recent lastmod: 2026-11-01T12:47:40+01:00.

    Fix: Add a 'Sitemap:' line to robots.txt, list every indexable page and include accurate lastmod dates.

  • ✓

    Canonical URLhigh

    Canonical: https://hessen.de/

    Points to this page (self-referencing).

  • ✓

    Redirectshigh

    Loads directly with no redirects.

  • ✓

    www / non-wwwmedium

    www.hessen.de redirects to hessen.de.

  • ✓

    hreflangmedium

    1 hreflang link(s).

    All language codes are valid.

    No x-default (recommended for a language picker or fallback page).

Search snippet & sharing 83%

How the page looks in Google results and when shared.

  • ✓

    Title tagcritical

    “Startseite | HESSEN Landesregierung”

    About 339px of Google's ~580px desktop width.

  • ✓

    Meta descriptionhigh

    144 characters, ~936px of ~990px.

    Good length.

    Google sometimes rewrites descriptions to match the search; a good one is still used most often.

  • ✗

    Open Graph & social cardsmedium

    Open Graph title or image missing.

    No twitter:card tag.

    Fix: Add og:title, og:description, og:image (1200×630 PNG/JPG, absolute URL) and twitter:card=summary_large_image.

  • ✓

    Faviconlow

    Favicon linked (Google shows it next to results).

  • ✓

    Languagelow

    lang="de"

Content quality 73%

Is there enough clear, useful text that matches what the page targets?

  • ✓

    Word countmedium

    2,499 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.

  • i

    Readabilitymedium

    Reading-ease scores only work for English; this page is lang="de".

  • ✓

    Topic focushigh

    2 of 2 title keywords appear in the main content.

  • !

    H1 headingcritical

    4 H1 headings – one clear H1 is best practice.

    The H1 shares no keywords with the title.

    Fix: Use one H1 that states the page topic with its main keyword.

  • ✓

    Heading structuremedium

    19 headings for 2499 words.

    Levels are in order.

  • ✗

    Text-to-code ratiolow

    2% of the HTML is visible text.

    Fix: Trim unused markup, inline scripts and builder bloat.

AI search readiness 47%

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

    Identified as: GovernmentOrganization.

    No sameAs links to official profiles (Google Business Profile, LinkedIn, Facebook, Companies House…).

    Fix: Add Organization or LocalBusiness JSON-LD with name, url, logo, contact details and sameAs links to your official profiles.

  • ✗

    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

    No links found to about, contact or privacy pages.

    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 100%

Machine-readable facts for rich results and AI.

  • ✓

    JSON-LD present & validhigh

    1 JSON-LD block(s): GovernmentOrganization, WebSite, CollectionPage, ItemList, ListItem, NewsArticle, Article.

    All blocks parse correctly.

  • ✓

    Required propertiesmedium

    Key types include Google's required properties.

  • i

    Breadcrumbslow

    Home page – breadcrumbs not needed.

Performance 53%

Speed signals from the HTML and server. Real-user Core Web Vitals load below.

  • !

    Server response (TTFB)high

    801 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

    980 kB of HTML – heavy for phones (we only analysed the first 1 MB).

    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

    1 script tag(s); files loaded from 0 other domain(s).

  • ✗

    Imagesmedium

    53 image(s).

    10 without width/height – can cause layout shift (CLS).

    50 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: max-age=300

  • 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 100%

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, clickjacking protection.

  • ✓

    Server fingerprintlow

    No X-Powered-By header (server: cloudflare).

Mobile & accessibility 100%

Usable on phones and by everyone – Google indexes the mobile version.

  • ✓

    Mobile viewportcritical

    viewport: width=device-width, initial-scale=1.0

  • ✓

    Image alt textmedium

    All 53 images have alt text.

  • ✓

    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.

This report checks one page. Scores are a guide, not a guarantee of rankings. Check another page · Print or save as PDF

Want these fixed for you? XKey is made by IceWork, a Blackpool web studio. IceWork builds fast websites that pass every check here – a 3-page site with domain and a year's hosting is £350 all in.