Public Audit Report

bipeye.com

https://bipeye.com/
Scanned on July 9, 2026
70
Overall
B
68
SEO
64/94 passed
76
AEO
35/46 passed
66
GEO
38/60 passed
136
Passed
63
Failed
199
Total Checks
Needs Work
Rating

Quick Wins — Top 5 Issues to Fix

SEO — 68/100 (30 issues)

Failed Checks (30)

  • Title length: 67 characters (too long, keep under 60)meta
  • Title-H1 alignment: 14% word overlap — title and H1 should share key termscontent
  • 32% long sentences (>20 words) — break up for readabilitycontent
  • 20 images missing width/height — causes layout shift (CLS)content
  • 20 of 20 images use legacy formats (JPG/PNG/GIF) — convert to WebP/AVIF for 25-50% smaller filescontent
  • Missing og:url — social platforms may use wrong URLsocial
  • Missing og:site_name — helps brand recognition in sharessocial
  • Missing twitter:titlesocial
  • Missing twitter:descriptionsocial
  • Missing twitter:imagesocial
  • Missing canonical tag — risk of duplicate contenttechnical
  • No hreflang tags — add if targeting multiple languagestechnical
  • 3 render-blocking scripts — add defer or async attributeperformance
  • No Content-Security-Policy header — XSS risksecurity
  • No Contact page link detected — add for trust signalstrust
  • robots.txt does not reference Sitemap — add Sitemap: URLtechnical
  • sitemap.xml found but not valid XML formattechnical
  • 1 of 5 internal links are brokencontent
  • 13 target="_blank" links missing rel="noopener" — security risksecurity
  • No Web App Manifest — add for installability and modern web signalstechnical
  • Only 0% responsive images — add srcset for mobilecontent
  • No max-image-preview:large — add to robots meta for Google Discovermeta
  • Event content found but no Event schema — add for event rich resultsschema
  • No Permissions-Policy — restrict camera/mic/geo accesssecurity
  • 1 render-blocking script(s) in head — add defer or asyncperformance
  • Missing ARIA landmarks — add <main>, <nav>, and skip-to-content link for accessibilityaccessibility
  • 2 duplicate ID(s) found: "features" (2x), "developers" (2x) — must be unique per HTML specaccessibility
  • 1 iframe(s) without sandbox attribute — security risksecurity
  • No RSS/Atom feed in <head> — add for content discovery by aggregators and AItechnical
  • 3 of 12 H2 sections have < 50 words — add more content or merge thin sectionscontent

Passed Checks (64)

  • Title tag found: "BI.P.EYE – Connect to any datasource. Transform data into in..."meta
  • Meta description found (152 chars)meta
  • Description length: 152 chars (optimal)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
  • Single H1 tag foundcontent
  • 12 H2 tags foundcontent
  • Heading hierarchy is correctcontent
  • 1858 words on page (good content depth)content
  • Readability: 51 (moderate — aim for 60+)content
  • All 20 images have ALT textcontent
  • JS-based lazy loading detectedcontent
  • 16 internal links foundcontent
  • 8 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 image foundsocial
  • og:type set to "website"social
  • Twitter Card: "summary_large_image"social
  • HTTPS enabledtechnical
  • Favicon foundtechnical
  • Compression: enabled (vary: accept-encoding)technical
  • URL length: 19 chars (good)technical
  • URL uses hyphens or no separators (good)technical
  • No deprecated HTML tags foundtechnical
  • Text-to-HTML ratio: 15.8% (good)technical
  • Inline CSS: 0.0 KB (acceptable)performance
  • Inline JS: 1.3 KB (acceptable)performance
  • Font preload/preconnect found — faster font loadingperformance
  • Cache-Control: public, max-age=0performance
  • HSTS header present — enforces HTTPSsecurity
  • X-Content-Type-Options: nosniffsecurity
  • About page link found — builds trust and E-E-A-Ttrust
  • Privacy Policy link foundtrust
  • Terms of Service link foundtrust
  • Author byline foundtrust
  • 1 JSON-LD schema block(s) foundschema
  • Schema types: SoftwareApplicationschema
  • <!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
  • No AI crawlers blocked in robots.txt — AI search and training can access contenttechnical
  • 0% nofollow links (0/24) — good link equity flowcontent
  • OG image uses absolute URL (correct)social
  • 2 resource hint(s) (dns-prefetch/preconnect) — faster loadingperformance
  • All schema types have required propertiesschema
  • 30 first-person pronouns — strong personal experiencecontent
  • Referrer-Policy: no-referrersecurity
  • H1 length: 24 characters (optimal)content
  • Title and meta description are different (good)meta
  • Viewport allows zoom (good for accessibility)accessibility
  • 48 links on page (within limit)content
  • DOM size: ~553 elements (good)performance
  • No snippet blocking detected (good — content is fully accessible)technical
  • 1 third-party script domain(s) (acceptable)performance
  • All 0 form input(s) have labels or aria-labelsaccessibility
AEO — 76/100 (11 issues)

Failed Checks (11)

  • No definition lists (<dl>) — great for term/value pairsdiscoverability
  • No data tables — tables help AI compare and cite datastructure
  • 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
  • First paragraph too short for AI snippetsvoice
  • No summary section — add Key Takeaways for AI extractionvoice
  • Few Q&A blocks — add question headings followed by answer paragraphsvoice
  • robots.txt blocks AI search crawlers (8/8 blocked) — blocked bots (GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot etc.) cannot cite your contentdiscoverability
  • Statistics lack source references — attribute data to boost AI trustcitation

Passed Checks (34)

  • Structured data found — AI can understand your contentdiscoverability
  • 1858 words in HTML — good content for AI parsingdiscoverability
  • Clean URL structurediscoverability
  • 4 semantic HTML5 elements founddiscoverability
  • 14 content sections — well-structured for AIdiscoverability
  • Description + OG description both present — clear topic signalsdiscoverability
  • 36 named entities found — helps AI understand contextdiscoverability
  • 16 internal links — good topic cluster signaldiscoverability
  • Q&A/FAQ content detected — useful for AI answers (note: Google retired FAQ rich results in May 2026; the schema itself no longer produces SERP features)structure
  • Question-style headings found — ideal for AI snippetsstructure
  • 7 lists found — structured content for AIstructure
  • Concise answer paragraphs after headings — great for AI citationstructure
  • 68% short sentences — easy for AI to extractstructure
  • 100% concise paragraphs — scannable for AIstructure
  • Avg 149 words/section — sufficient depthstructure
  • Author information found — builds E-E-A-Tcitation
  • Statistics and data found in content — highly citablecitation
  • 3/5 E-E-A-T signals presentcitation
  • Source citations found — increases AI trustcitation
  • 8 external links — references authoritative sourcescitation
  • Content references 2026/2025 — fresh contentcitation
  • Topic focus: 100% — title keywords found in contentcitation
  • 14 answer-box-ready paragraphs found after headingscitation
  • 97 conversational words — good for AI summariesvoice
  • Avg 17 words/sentence — easy reading levelvoice
  • Active voice dominant (10% passive) — AI-friendlyvoice
  • Pronoun density: 3.6% — engaging, user-focusedvoice
  • 27 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
  • Content updated within 90 days — AI engines strongly prefer fresh contentcitation
  • Table of Contents detected — helps AI navigate long contentstructure
  • Video found but no VideoObject schema — add for AI video discoverydiscoverability
  • 12 collapsible section(s) (<details>) — interactive AI-friendly contentstructure
GEO — 66/100 (22 issues)

Failed Checks (22)

  • Few question headings — add Q&A headings for AI Overviewoverview
  • Title and H1 don't align — confusing for AI topic matchingoverview
  • No step-by-step content — add numbered guides for AIoverview
  • 47% optimal paragraphs — aim for 20-80 words per paragraphoverview
  • No author schema — add for AI trust signalsauthority
  • Incomplete brand identity — add og:site_name + Organization schemaauthority
  • No examples or case studies — add real-world examplesauthority
  • No comparison content — add vs. sections for AI recommendationsformat
  • 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 <time> elements — wrap dates in <time datetime="...">semantic
  • No canonical URL — AI may index duplicate versionstechnical
  • Only 1 Schema type(s) — add more for AI contexttechnical
  • 2 image(s) with generic/short ALT text — use descriptive textformat
  • First 200 words lack topic keywords — AI may skip your content for extractionoverview
  • Only 1 data points — adding statistics measurably boosts generative-engine visibility (GEO study, arXiv:2311.09735)authority
  • Author lacks credentials — anonymous content is a GEO penaltyauthority
  • No authoritative sameAs links — add Wikipedia/Wikidata/LinkedIn URIs to schema for entity disambiguationauthority
  • Hidden text detected (~49 words in display:none/visibility:hidden) — AI crawlers read it and may flag cloaking; render it or remove ittrust
  • Video without VideoObject schema — add name, description, thumbnailUrl, uploadDate (+ captions/transcript)semantic

Passed Checks (38)

  • Definition-style content found — featured snippet candidateoverview
  • Content freshness signals detectedoverview
  • Comprehensive content (1858 words, 12 sections)overview
  • 2-level heading hierarchy — deep content structureoverview
  • Source citations found — increases AI trustauthority
  • 3/5 trust signals foundauthority
  • Original research/data signals foundauthority
  • Expert quotes or testimonials found — authority signalauthority
  • 5 industry terms used — domain expertise signalauthority
  • 5 links to authoritative sources — boosts credibilityauthority
  • 4 unique external domains — diverse sourcesauthority
  • Summary/conclusion section foundformat
  • 20 images all with ALT text — AI can understand visualsformat
  • Data visualization elements found (tables/charts)format
  • Actionable advice found — AI prefers practical contentformat
  • Conclusion/recommendation found — helps AI provide answersformat
  • 1 entity types in Schema — AI can classify contentsemantic
  • 8/14 semantic HTML5 elements — deep semantic structuresemantic
  • 100% title keywords in first 200 words — good prominencesemantic
  • 18 contextual links — good cross-referencingsemantic
  • Content categorization found — clear topic classificationsemantic
  • 5 sections have subtopics (H3) — deep coveragesemantic
  • Mobile-friendly (viewport set)technical
  • HTTPS secure — trusted by AI systemstechnical
  • Page size: 73 KB — reasonabletechnical
  • Open Graph fully configured (title, description, image)technical
  • Page allows AI indexing (no noindex/nosnippet)technical
  • HTML lang="en" set (add og:locale for completeness)technical
  • 2 ARIA landmarks found — good accessibility for AItechnical
  • 1858 words — sufficient depth for AI analysisoverview
  • Definition + list combo — strong featured snippet candidateoverview
  • No snippet restrictions — AI can freely extract content (good)technical
  • 4/6 question types (5W1H) in headings — comprehensiveoverview
  • Link anchor texts are descriptive — good AI context signalsemantic
  • 3 image caption(s) found — helps AI understand visual contentformat
  • No keyword-stuffing detectedauthority
  • Healthy content-to-chrome ratio (~3% boilerplate)overview
  • All tested AI crawlers can access the page (GPTBot, ClaudeBot, PerplexityBot)authority

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