Public Audit Report

b3rgel.com

https://www.b3rgel.com/
Scanned on April 13, 2026
55
Overall
D
70
SEO
69/99 passed
48
AEO
25/52 passed
30
GEO
17/57 passed
111
Passed
97
Failed
208
Total Checks
Poor
Rating

Quick Wins — Top 5 Issues to Fix

SEO — 70/100 (30 issues)

Failed Checks (30)

  • ✗Title length: 66 characters (too long, keep under 60)meta
  • ✗Title-H1 alignment: 0% word overlap — title and H1 should share key termscontent
  • ✗1 images missing width/height — causes layout shift (CLS)content
  • ✗1 of 1 images use legacy formats (JPG/PNG/GIF) — convert to WebP/AVIF for 25-50% smaller filescontent
  • ✗Only 0 internal links — add more for better crawlingcontent
  • ✗No hreflang tags — add if targeting multiple languagestechnical
  • ✗Text-to-HTML ratio: 3.0% — too code-heavy, add more contenttechnical
  • ✗Inline CSS: 56.3 KB — too much, move to external stylesheetperformance
  • ✗No font preload/preconnect — add for faster renderingperformance
  • ✗Missing X-Content-Type-Options headersecurity
  • ✗No Content-Security-Policy header — XSS risksecurity
  • ✗No Privacy Policy link — required by GDPR and improves trusttrust
  • ✗No Terms of Service link — add for legal compliance and trusttrust
  • ✗No author byline — add "By [Name]" for E-E-A-T trusttrust
  • ✗No Web App Manifest — add for installability and modern web signalstechnical
  • ✗No dns-prefetch or preconnect hints — add for faster third-party loadingperformance
  • ✗Only 0 first-person pronouns — add personal experience (E-E-A-T)content
  • ✗0% sentences use transition words — aim for 20%+content
  • ✗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
  • ✗1 paragraph(s) exceed 150 words — break up for readabilitycontent
  • ✗1 image(s) with generic filenames — use descriptive names for image SEOcontent
  • ✗H1 length: 10 characters — too short, aim for 20-70content
  • ✗1 render-blocking script(s) in head — add defer or asyncperformance
  • ✗Missing ARIA landmarks — add <main>, <nav>, and skip-to-content link for accessibilityaccessibility
  • ✗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
  • ✗2 of 5 H2 sections have < 50 words — add more content or merge thin sectionscontent

Passed Checks (69)

  • ✓Title tag found: "Максим Бергель (B3RGEL) — Фулстек-разработчик · React, Node...."meta
  • ✓Meta description found (162 chars)meta
  • ✓Description length: 162 chars (too long)meta
  • ✓Viewport meta tag found (mobile-friendly)meta
  • ✓UTF-8 charset declaredmeta
  • ✓Language attribute set on HTML tagmeta
  • ✓Theme color set: #090909meta
  • ✓No meta refresh redirect (good)meta
  • ✓Robots: "index, follow"meta
  • ✓meta keywords tag found — deprecated since 2009, Google ignores it. Remove to keep HTML cleanmeta
  • ✓Single H1 tag foundcontent
  • ✓5 H2 tags foundcontent
  • ✓Heading hierarchy is correctcontent
  • ✓407 words on page (good content depth)content
  • ✓Readability: 100 (easy to read)content
  • ✓11% long sentences (>20 words) — good readabilitycontent
  • ✓All 1 images have ALT textcontent
  • ✓No below-fold images to lazy loadcontent
  • ✓2 external links foundcontent
  • ✓No empty href attributes foundcontent
  • ✓Open Graph title foundsocial
  • ✓Open Graph description foundsocial
  • ✓Open Graph image foundsocial
  • ✓Open Graph URL foundsocial
  • ✓og:type set to "website"social
  • ✓og:site_name: "B3RGEL"social
  • ✓Twitter Card: "summary_large_image"social
  • ✓Twitter title foundsocial
  • ✓Twitter description foundsocial
  • ✓Twitter image foundsocial
  • ✓HTTPS enabledtechnical
  • ✓Canonical tag foundtechnical
  • ✓Canonical points to different URL: https://b3rgel.com/ — verify this is intentionaltechnical
  • ✓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
  • ✓Inline JS: 0.7 KB (acceptable)performance
  • ✓All 1 external scripts use defer/asyncperformance
  • ✓Cache-Control: public, max-age=0, must-revalidateperformance
  • ✓HSTS header present — enforces HTTPSsecurity
  • ✓About page link found — builds trust and E-E-A-Ttrust
  • ✓Contact page/email link foundtrust
  • ✓1 JSON-LD schema block(s) foundschema
  • ✓Schema types: Personschema
  • ✓<!DOCTYPE html> declaredtechnical
  • ✓No mixed content — all resources use HTTPStechnical
  • ✓All 1 JSON-LD block(s) have valid syntaxschema
  • ✓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 1 URL(s)technical
  • ✓OG image uses absolute URL (correct)social
  • ✓All 3 target="_blank" links have rel="noopener"security
  • ✓All schema types have required propertiesschema
  • ✓Title and meta description are different (good)meta
  • ✓OG URL matches canonical URL (consistent)social
  • ✓Viewport allows zoom (good for accessibility)accessibility
  • ✓16 links on page (within limit)content
  • ✓DOM size: ~513 elements (good)performance
  • ✓No snippet blocking detected (good — content is fully accessible)technical
  • ✓0 third-party script domain(s) (acceptable)performance
  • ✓All 2 form input(s) have labels or aria-labelsaccessibility
  • ✓No duplicate IDs found (9 unique IDs)accessibility
  • ✓No iframes on pagesecurity
AEO — 48/100 (27 issues)

Failed Checks (27)

  • ✗Few internal links — AI values interconnected contentdiscoverability
  • ✗No definition lists (<dl>) — great for term/value pairsdiscoverability
  • ✗No code blocks — add <code>/<pre> for technical contentdiscoverability
  • ✗No FAQ section found — add Q&A content for AI citationstructure
  • ✗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
  • ✗No numbered steps or ordered lists — add for "how to" AI answersstructure
  • ✗Few key-value patterns — use "**Label:** value" format for AIstructure
  • ✗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
  • ✗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 /llms.txt found — add one to guide AI crawlers (emerging standard)discoverability
  • ✗No sameAs links in schema — add social profiles for brand recognitioncitation
  • ✗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 (25)

  • ✓Structured data found — AI can understand your contentdiscoverability
  • ✓407 words in HTML — good content for AI parsingdiscoverability
  • ✓Clean URL structurediscoverability
  • ✓3 semantic HTML5 elements founddiscoverability
  • ✓6 content sections — well-structured for AIdiscoverability
  • ✓Description + OG description both present — clear topic signalsdiscoverability
  • ✓11 named entities found — helps AI understand contextdiscoverability
  • ✓3 lists found — structured content for AIstructure
  • ✓89% short sentences — easy for AI to extractstructure
  • ✓95% concise paragraphs — scannable for AIstructure
  • ✓Avg 295 words/section — sufficient depthstructure
  • ✓Author information found — builds E-E-A-Tcitation
  • ✓Statistics and data found in content — highly citablecitation
  • ✓2 external links — references authoritative sourcescitation
  • ✓Content references 2026/2025 — fresh contentcitation
  • ✓Topic focus: 100% — title keywords found in contentcitation
  • ✓Avg 12 words/sentence — easy reading levelvoice
  • ✓Active voice dominant (0% passive) — AI-friendlyvoice
  • ✓9 H2/H3 headings — good content structure for AIvoice
  • ✓No AI-blocking robots directives — AI crawlers can access contentdiscoverability
  • ✓Freshness signal found (Last-Modified header or dateModified)citation
  • ✓AI crawlers allowed in robots.txt (0/4 explicitly listed)discoverability
  • ✓Brand name consistent across 2/3 signals (title, OG, schema)citation
  • ✓Content updated within 90 days — fresh content gets 3.2x more AI citationscitation
  • ✓Brand "B3RGEL" used consistently (4 mentions)citation
GEO — 30/100 (40 issues)

Failed Checks (40)

  • ✗No clear definitions — add "X is..." patterns for AI Overviewoverview
  • ✗Few question headings — add Q&A headings for AI Overviewoverview
  • ✗Content may be too thin for AI Overview (407 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
  • ✗5% 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 0/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 FAQ Schema — add for Google rich results + AI Overviewformat
  • ✗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 2/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
  • ✗3/14 semantic elements — add <article>, <figure>, <time>, etc.semantic
  • ✗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
  • ✗Only 1 Schema type(s) — add more for AI contexttechnical
  • ✗Few ARIA landmarks — add <main>, <nav>, <footer> or role attributestechnical
  • ✗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 (17)

  • ✓Content freshness signals detectedoverview
  • ✓2-level heading hierarchy — deep content structureoverview
  • ✓1 images all with ALT text — AI can understand visualsformat
  • ✓Data visualization elements found (tables/charts)format
  • ✓1 entity types in Schema — AI can classify contentsemantic
  • ✓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
  • ✓Page size: 90 KB — reasonabletechnical
  • ✓Open Graph fully configured (title, description, image)technical
  • ✓Canonical URL set — prevents AI from citing duplicatestechnical
  • ✓Page allows AI indexing (no noindex/nosnippet)technical
  • ✓Language + OG locale set — clear language signaltechnical
  • ✓All image ALT texts are descriptive (>5 chars)format
  • ✓407 words — sufficient depth for AI analysisoverview
  • ✓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
Scan This Site Again Request Report Removal