www.noybern.ch
https://www.noybern.ch/
Scanned on April 23, 2026
Quick Wins — Top 5 Issues to Fix
- ✗Title length: 26 characters (too short, aim for 30-60)meta
- ✗Description length: 486 chars (too long)meta
- ✗No theme-color meta tag — improves mobile browser appearancemeta
- ✗No H1 tag foundcontent
- ✗Heading hierarchy has gaps (e.g. H1 to H3 without H2)content
SEO — 68/100 (31 issues)
Failed Checks (31)
- ✗Title length: 26 characters (too short, aim for 30-60)meta
- ✗Description length: 486 chars (too long)meta
- ✗No theme-color meta tag — improves mobile browser appearancemeta
- ✗No H1 tag foundcontent
- ✗Heading hierarchy has gaps (e.g. H1 to H3 without H2)content
- ✗Only 158 words — thin content may rank poorlycontent
- ✗7 of 7 images use legacy formats (JPG/PNG/GIF) — convert to WebP/AVIF for 25-50% smaller filescontent
- ✗Missing og:image — social shares will lack visualssocial
- ✗Missing twitter:imagesocial
- ✗No hreflang tags — add if targeting multiple languagestechnical
- ✗Text-to-HTML ratio: 0.1% — too code-heavy, add more contenttechnical
- ✗Inline CSS: 174.3 KB — too much, move to external stylesheetperformance
- ✗Inline JS: 483.8 KB — too much, use external scriptsperformance
- ✗3 render-blocking scripts — add defer or async attributeperformance
- ✗No font preload/preconnect — add for faster renderingperformance
- ✗No Content-Security-Policy header — XSS risksecurity
- ✗No Privacy Policy link — required by GDPR and improves trusttrust
- ✗No author byline — add "By [Name]" for E-E-A-T trusttrust
- ✗2 target="_blank" links missing rel="noopener" — security risksecurity
- ✗No Web App Manifest — add for installability and modern web signalstechnical
- ✗No dns-prefetch or preconnect hints — add for faster third-party loadingperformance
- ✗No max-image-preview:large — add to robots meta for Google Discovermeta
- ✗Missing X-Frame-Options — clickjacking risksecurity
- ✗No Referrer-Policy header — may leak URL datasecurity
- ✗No Permissions-Policy — restrict camera/mic/geo accesssecurity
- ✗2 render-blocking script(s) in head — add defer or asyncperformance
- ✗49 duplicate ID(s) found: "soapAfterPagesContainer" (10x), "CONTROLLER_COMP_CUSTOM_ID" (5x), "SOSP_CONTAINER_CUSTOM_ID" (2x) — must be unique per HTML specaccessibility
- ✗3 iframe(s) without sandbox attribute — security risksecurity
- ✗No RSS/Atom feed in <head> — add for content discovery by aggregators and AItechnical
- ✗No IndexNow integration — add for instant Bing/Yandex indexing on content changestechnical
- ✗5 of 5 H2 sections have < 50 words — add more content or merge thin sectionscontent
Passed Checks (66)
- ✓Title tag found: "noy | bar&caffè | bern"meta
- ✓Meta description found (486 chars)meta
- ✓Viewport meta tag found (mobile-friendly)meta
- ✓UTF-8 charset declaredmeta
- ✓Language attribute set on HTML tagmeta
- ✓No meta refresh redirect (good)meta
- ✓No robots meta tag (default: index, follow)meta
- ✓5 H2 tags foundcontent
- ✓Readability: 70 (easy to read)content
- ✓23% long sentences (>20 words) — good readabilitycontent
- ✓All 7 images have ALT textcontent
- ✓All 7 images have width/height attributes (prevents CLS)content
- ✓JS-based lazy loading detectedcontent
- ✓10 internal links foundcontent
- ✓2 external links foundcontent
- ✓No empty href attributes foundcontent
- ✓All link texts are descriptive (no "click here" or "read more")content
- ✓Open Graph title foundsocial
- ✓Open Graph description foundsocial
- ✓Open Graph URL foundsocial
- ✓og:type set to "website"social
- ✓og:site_name: "noy"social
- ✓Twitter Card: "summary_large_image"social
- ✓Twitter title foundsocial
- ✓Twitter description foundsocial
- ✓HTTPS enabledtechnical
- ✓Canonical tag foundtechnical
- ✓Canonical tag is self-referencing (correct)technical
- ✓Favicon foundtechnical
- ✓Apple touch icon foundtechnical
- ✓Compression: brtechnical
- ✓URL length: 23 chars (good)technical
- ✓URL uses hyphens or no separators (good)technical
- ✓No deprecated HTML tags foundtechnical
- ✓Cache-Control: private,max-age=0,must-revalidateperformance
- ✓HSTS header present — enforces HTTPSsecurity
- ✓X-Content-Type-Options: nosniffsecurity
- ✓About page link found — builds trust and E-E-A-Ttrust
- ✓Contact page/email link foundtrust
- ✓Terms of Service link foundtrust
- ✓1 JSON-LD schema block(s) foundschema
- ✓Schema types: WebSiteschema
- ✓<!DOCTYPE html> declaredtechnical
- ✓No mixed content — all resources use HTTPStechnical
- ✓All 1 JSON-LD block(s) have valid syntaxschema
- ✓font-display: swap detected — prevents invisible textperformance
- ✓Viewport includes width=device-width (responsive)meta
- ✓robots.txt found and allows crawlingtechnical
- ✓robots.txt includes Sitemap referencetechnical
- ✓No AI crawlers blocked in robots.txt — AI search and training can access contenttechnical
- ✓sitemap.xml found with valid formattechnical
- ✓Sitemap contains 3 URL(s)technical
- ✓All 4 checked internal links are workingcontent
- ✓0% nofollow links (0/13) — good link equity flowcontent
- ✓All schema types have required propertiesschema
- ✓Only 43% responsive images — add srcset for mobilecontent
- ✓Title uses "|" separator — Google may rewrite it; consider using "—" insteadmeta
- ✓Title and meta description are different (good)meta
- ✓OG URL matches canonical URL (consistent)social
- ✓Viewport allows zoom (good for accessibility)accessibility
- ✓13 links on page (within limit)content
- ✓DOM size: ~495 elements (good)performance
- ✓No snippet blocking detected (good — content is fully accessible)technical
- ✓2 third-party script domain(s) (acceptable)performance
- ✓ARIA landmarks present: main, navaccessibility
- ✓All 1 form input(s) have labels or aria-labelsaccessibility
AEO — 46/100 (28 issues)
Failed Checks (28)
- ✗No definition lists (<dl>) — great for term/value pairsdiscoverability
- ✗No code blocks — add <code>/<pre> for technical contentdiscoverability
- ✗No question-style headings — try "How to...", "What is..."structure
- ✗No data tables — tables help AI compare and cite datastructure
- ✗No concise answer paragraphs detected — add short summaries after headingsstructure
- ✗Few key-value patterns — use "**Label:** value" format for AIstructure
- ✗No author information — AI values attributed contentcitation
- ✗No date information — AI prefers fresh, dated contentcitation
- ✗No Organization schema — AI may not recognize your brandcitation
- ✗Only 2/5 E-E-A-T signals — add about, contact, author infocitation
- ✗No source citations — reference studies and data for authoritycitation
- ✗No recent year mentioned — AI prefers up-to-date contentcitation
- ✗Only 0 concise answer paragraph(s) after headings — add 2+ short summaries (40-200 chars) right after H2/H3 tagscitation
- ✗No Speakable schema — add for voice assistant optimizationvoice
- ✗Formal tone — use more "you", "your", "we" for AI readabilityvoice
- ✗First paragraph too short for AI snippetsvoice
- ✗No SearchAction schema — add for enhanced search presencevoice
- ✗Pronoun density: 0.0% — add more "you/your" for engagementvoice
- ✗No summary section — add Key Takeaways for AI extractionvoice
- ✗Few Q&A blocks — add question headings followed by answer paragraphsvoice
- ✗No Last-Modified header or dateModified — AI prefers content with freshness signalscitation
- ✗robots.txt does not explicitly allow AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended)discoverability
- ✗No sameAs links in schema — add social profiles for brand recognitioncitation
- ✗Content not updated in 90+ days — stale content loses AI visibilitycitation
- ✗No Table of Contents — add jump links for AI content navigationstructure
- ✗No video content — multimedia increases AI engagement and citation ratediscoverability
- ✗Statistics lack source references — attribute data to boost AI trustcitation
- ✗No <details>/<summary> elements — use for expandable Q&A contentstructure
Passed Checks (24)
- ✓Structured data found — AI can understand your contentdiscoverability
- ✓158 words in HTML — good content for AI parsingdiscoverability
- ✓Clean URL structurediscoverability
- ✓5 semantic HTML5 elements founddiscoverability
- ✓11 content sections — well-structured for AIdiscoverability
- ✓Description + OG description both present — clear topic signalsdiscoverability
- ✓3 named entities found — helps AI understand contextdiscoverability
- ✓10 internal links — good topic cluster signaldiscoverability
- ✓FAQ content detected — great for AI answers (Note: FAQ rich results limited to gov/health sites since Aug 2023)structure
- ✓3 lists found — structured content for AIstructure
- ✓Step-by-step content detected — AI loves procedural answersstructure
- ✓77% short sentences — easy for AI to extractstructure
- ✓100% concise paragraphs — scannable for AIstructure
- ✓Avg 438 words/section — sufficient depthstructure
- ✓Statistics and data found in content — highly citablecitation
- ✓2 external links — references authoritative sourcescitation
- ✓Topic focus: 100% — title keywords found in contentcitation
- ✓Avg 13 words/sentence — easy reading levelvoice
- ✓Active voice dominant (0% passive) — AI-friendlyvoice
- ✓5 H2/H3 headings — good content structure for AIvoice
- ✓No AI-blocking robots directives — AI crawlers can access contentdiscoverability
- ✓/llms.txt found — AI crawlers can discover your content guidelinesdiscoverability
- ✓Brand name consistent across 2/3 signals (title, OG, schema)citation
- ✓Brand "noy" used consistently (9 mentions)citation
GEO — 25/100 (43 issues)
Failed Checks (43)
- ✗No clear definitions — add "X is..." patterns for AI Overviewoverview
- ✗Few question headings — add Q&A headings for AI Overviewoverview
- ✗No freshness signals — add dates, update timestampsoverview
- ✗Content may be too thin for AI Overview (158 words, 5 sections)overview
- ✗Title and H1 don't align — confusing for AI topic matchingoverview
- ✗No step-by-step content — add numbered guides for AIoverview
- ✗Flat heading structure — add H3/H4 subheadings for depthoverview
- ✗20% optimal paragraphs — aim for 20-80 words per paragraphoverview
- ✗No author schema — add for AI trust signalsauthority
- ✗No source citations — reference studies and data for authorityauthority
- ✗Only 1/5 trust signals — add reviews, certificationsauthority
- ✗Incomplete brand identity — add og:site_name + Organization schemaauthority
- ✗No original data signals — "our research shows..." boosts AI citationauthority
- ✗No expert quotes — add professional opinions for credibilityauthority
- ✗No examples or case studies — add real-world examplesauthority
- ✗Few industry terms — use relevant jargon for topical authorityauthority
- ✗No links to authoritative sources — cite Google, Schema.org, etc.authority
- ✗Few external source domains — diversify your referencesauthority
- ✗No HowTo Schema — add for step-by-step rich resultsformat
- ✗No comparison content — add vs. sections for AI recommendationsformat
- ✗No summary section — add Key Takeaways or TL;DR for AIformat
- ✗No BreadcrumbList schema — add for better AI contextformat
- ✗Only one list type — use both <ul> and <ol> for content varietyformat
- ✗Only 1/6 formatting types — use bold, lists, tables, quotes, codeformat
- ✗Single-perspective content — add "on the other hand..." for balanceformat
- ✗No actionable content — add "you should...", "try...", tipsformat
- ✗No conclusion — add recommendations or a verdict sectionformat
- ✗No entity Schema types — add Person, Product, or Organization schemasemantic
- ✗No <time> elements — wrap dates in <time datetime="...">semantic
- ✗Few data points with units — add specific numbers (e.g., "300+ users")semantic
- ✗Few contextual links — interlink related contentsemantic
- ✗Few sections have subtopics — add H3 subheadings for depthsemantic
- ✗Page size: 715 KB — very large, may slow AI crawlingtechnical
- ✗Incomplete Open Graph tags — AI uses these for contexttechnical
- ✗Only 1 Schema type(s) — add more for AI contexttechnical
- ✗Only 158 words — AI systems prefer content with 300+ words for comprehensive analysisoverview
- ✗First 200 words lack topic keywords — AI may skip your content for extractionoverview
- ✗Missing definition or list format — combine "X is..." with lists for snippetsoverview
- ✗Only 0 data points — add 5+ statistics for +30-40% AI visibility (Princeton study)authority
- ✗Author lacks credentials — anonymous content is a GEO penaltyauthority
- ✗Only 0/6 question types — add What, Why, How headingsoverview
- ✗No <figure>/<figcaption> — wrap images with descriptive captions for AIformat
- ✗No authoritative sameAs links — add Wikipedia/Wikidata/LinkedIn URIs to schema for Knowledge Graph alignmentauthority
Passed Checks (14)
- ✓FAQ Schema (FAQPage) foundformat
- ✓7 images all with ALT text — AI can understand visualsformat
- ✓Data visualization elements found (tables/charts)format
- ✓5/14 semantic HTML5 elements — deep semantic structuresemantic
- ✓100% title keywords in first 200 words — good prominencesemantic
- ✓Content categorization found — clear topic classificationsemantic
- ✓Mobile-friendly (viewport set)technical
- ✓HTTPS secure — trusted by AI systemstechnical
- ✓Canonical URL set — prevents AI from citing duplicatestechnical
- ✓Page allows AI indexing (no noindex/nosnippet)technical
- ✓HTML lang="de" set (add og:locale for completeness)technical
- ✓3 ARIA landmarks found — good accessibility for AItechnical
- ✓All image ALT texts are descriptive (>5 chars)format
- ✓No snippet restrictions — AI can freely extract content (good)technical
Fix These Issues Automatically
Using WordPress? Install SEO Autopilot for one-click auto-fixes on 65+ issues — with full undo support.
Get SEO Autopilot Plugin