Public Audit Report

www.honhai.com

https://www.honhai.com/zh-tw/CSR/focus-employees?category=labor-pro
Scanned on May 5, 2026
41
Overall
F
55
SEO
51/93 passed
29
AEO
15/51 passed
24
GEO
14/58 passed
80
Passed
122
Failed
202
Total Checks
Poor
Rating

Quick Wins — Top 5 Issues to Fix

SEO — 55/100 (42 issues)

Failed Checks (42)

  • ✗Title length: 28 characters (too short, aim for 30-60)meta
  • ✗Description length: 451 chars (too long)meta
  • ✗Missing language attribute on HTML tagmeta
  • ✗No theme-color meta tag — improves mobile browser appearancemeta
  • ✗No H1 tag foundcontent
  • ✗No H2 tags foundcontent
  • ✗Only 266 words — thin content may rank poorlycontent
  • ✗Readability: 0 (difficult — simplify language)content
  • ✗100% long sentences (>20 words) — break up for readabilitycontent
  • ✗16 of 21 images missing ALT text (24% have it)content
  • ✗18 images missing width/height — causes layout shift (CLS)content
  • ✗20 images could use loading="lazy" for better performancecontent
  • ✗Missing og:site_name — helps brand recognition in sharessocial
  • ✗Missing canonical tag — risk of duplicate contenttechnical
  • ✗No favicon detectedtechnical
  • ✗No apple-touch-icon — iOS home screen will lack custom icontechnical
  • ✗URL contains uppercase characters — use lowercase for consistency and to avoid duplicate contenttechnical
  • ✗No hreflang tags — add if targeting multiple languagestechnical
  • ✗Text-to-HTML ratio: 0.2% — too code-heavy, add more contenttechnical
  • ✗Inline CSS: 750.8 KB — too much, move to external stylesheetperformance
  • ✗Inline JS: 64.2 KB — too much, use external scriptsperformance
  • ✗No font preload/preconnect — add for faster renderingperformance
  • ✗No Terms of Service link — add for legal compliance and trusttrust
  • ✗No author byline — add "By [Name]" for E-E-A-T trusttrust
  • ✗No JSON-LD structured data foundschema
  • ✗Web fonts without font-display: swap — may cause FOITperformance
  • ✗robots.txt does not reference Sitemap — add Sitemap: URLtechnical
  • ✗sitemap.xml found but not valid XML formattechnical
  • ✗2 of 5 internal links are brokencontent
  • ✗URL lacks title keywords — use a descriptive URL slugtechnical
  • ✗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% responsive images — add srcset for mobilecontent
  • ✗Possible hidden text detected (font-size:0 or same-color text) — Google spam violationtechnical
  • ✗No max-image-preview:large — add to robots meta for Google Discovermeta
  • ✗173 links on page — exceeds 100 limit, may dilute link equitycontent
  • ✗DOM size: ~1600 elements — exceeds 1500, may slow renderingperformance
  • ✗1 render-blocking script(s) in head — add defer or asyncperformance
  • ✗Missing ARIA landmarks — add <main>, <nav>, and skip-to-content link for accessibilityaccessibility
  • ✗4 duplicate ID(s) found: "a" (22x), "b" (2x), "c" (2x) — must be unique per HTML specaccessibility
  • ✗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

Passed Checks (51)

  • ✓Title tag found: "「 焦點面向 - 員工照護 」勞權維護 - 鴻海科技集團"meta
  • ✓Meta description found (451 chars)meta
  • ✓Viewport meta tag found (mobile-friendly)meta
  • ✓UTF-8 charset declaredmeta
  • ✓No meta refresh redirect (good)meta
  • ✓No robots meta tag (default: index, follow)meta
  • ✓meta keywords tag found — deprecated since 2009, Google ignores it. Remove to keep HTML cleanmeta
  • ✓Heading hierarchy is correctcontent
  • ✓6 of 21 images use legacy formats (JPG/PNG/GIF) — convert to WebP/AVIF for 25-50% smaller filescontent
  • ✓151 internal links foundcontent
  • ✓22 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
  • ✓Open Graph URL foundsocial
  • ✓og:type set to "website"social
  • ✓Twitter Card: "summary_large_image"social
  • ✓Twitter title foundsocial
  • ✓Twitter description foundsocial
  • ✓Twitter image foundsocial
  • ✓HTTPS enabledtechnical
  • ✓Compression: brtechnical
  • ✓URL length: 67 chars (good)technical
  • ✓URL uses hyphens or no separators (good)technical
  • ✓No deprecated HTML tags foundtechnical
  • ✓All 1 external scripts use defer/asyncperformance
  • ✓Cache-Control: max-age=31536000,publicperformance
  • ✓HSTS header present — enforces HTTPSsecurity
  • ✓X-Content-Type-Options: nosniffsecurity
  • ✓Content-Security-Policy header presentsecurity
  • ✓About page link found — builds trust and E-E-A-Ttrust
  • ✓Contact page/email link foundtrust
  • ✓Privacy Policy link foundtrust
  • ✓<!DOCTYPE html> declaredtechnical
  • ✓No mixed content — all resources use HTTPStechnical
  • ✓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/173) — good link equity flowcontent
  • ✓OG image uses absolute URL (correct)social
  • ✓All 25 target="_blank" links have rel="noopener"security
  • ✓Referrer-Policy: strict-origin-when-cross-originsecurity
  • ✓Permissions-Policy header presentsecurity
  • ✓Title and meta description are different (good)meta
  • ✓Viewport allows zoom (good for accessibility)accessibility
  • ✓No snippet blocking detected (good — content is fully accessible)technical
  • ✓0 third-party script domain(s) (acceptable)performance
  • ✓All 0 form input(s) have labels or aria-labelsaccessibility
  • ✓No iframes on pagesecurity
AEO — 29/100 (36 issues)

Failed Checks (36)

  • ✗No structured data — AI systems struggle to categorize your pagediscoverability
  • ✗Only 1 content sections — segment your content betterdiscoverability
  • ✗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
  • ✗Few or no lists — add bullet/numbered lists for better AI parsingstructure
  • ✗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
  • ✗0% short sentences — shorten sentences for better AI parsingstructure
  • ✗Few key-value patterns — use "**Label:** value" format for AIstructure
  • ✗Avg 0 words/section — expand sections for AI comprehensionstructure
  • ✗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
  • ✗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
  • ✗Avg 266 words/sentence — simplify for AI and voicevoice
  • ✗Pronoun density: 0.0% — add more "you/your" for engagementvoice
  • ✗No summary section — add Key Takeaways for AI extractionvoice
  • ✗Only 0 H2/H3 headings — add more to structure your contentvoice
  • ✗Few Q&A blocks — add question headings followed by answer paragraphsvoice
  • ✗No Last-Modified header or dateModified — AI prefers content with freshness signalscitation
  • ✗No sameAs links in schema — add social profiles for brand recognitioncitation
  • ✗Brand name inconsistent — align site name across title, og:site_name, Organization schemacitation
  • ✗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 (15)

  • ✓266 words in HTML — good content for AI parsingdiscoverability
  • ✓Clean URL structurediscoverability
  • ✓4 semantic HTML5 elements founddiscoverability
  • ✓Description + OG description both present — clear topic signalsdiscoverability
  • ✓4 named entities found — helps AI understand contextdiscoverability
  • ✓151 internal links — good topic cluster signaldiscoverability
  • ✓100% concise paragraphs — scannable for AIstructure
  • ✓Statistics and data found in content — highly citablecitation
  • ✓22 external links — references authoritative sourcescitation
  • ✓Content references 2026/2025 — fresh contentcitation
  • ✓Topic focus: 100% — title keywords found in contentcitation
  • ✓Active voice dominant (0% passive) — AI-friendlyvoice
  • ✓No AI-blocking robots directives — AI crawlers can access contentdiscoverability
  • ✓/llms.txt found — AI crawlers can discover your content guidelinesdiscoverability
  • ✓AI crawlers allowed in robots.txt (0/4 explicitly listed)discoverability
GEO — 24/100 (44 issues)

Failed Checks (44)

  • ✗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 (266 words, 0 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
  • ✗0% 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
  • ✗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
  • ✗16 images missing ALT textformat
  • ✗No BreadcrumbList schema — add for better AI contextformat
  • ✗No lists found — add lists for structured contentformat
  • ✗Only 0/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
  • ✗4/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 sections have subtopics — add H3 subheadings for depthsemantic
  • ✗Page size: 901 KB — very large, may slow AI crawlingtechnical
  • ✗No canonical URL — AI may index duplicate versionstechnical
  • ✗Only 0 Schema type(s) — add more for AI contexttechnical
  • ✗No HTML lang attribute — AI needs language contexttechnical
  • ✗Only 266 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)

  • ✓Content freshness signals detectedoverview
  • ✓14 unique external domains — diverse sourcesauthority
  • ✓Data visualization elements found (tables/charts)format
  • ✓100% title keywords in first 200 words — good prominencesemantic
  • ✓6 contextual links — good cross-referencingsemantic
  • ✓Content categorization found — clear topic classificationsemantic
  • ✓Mobile-friendly (viewport set)technical
  • ✓HTTPS secure — trusted by AI systemstechnical
  • ✓Open Graph fully configured (title, description, image)technical
  • ✓Page allows AI indexing (no noindex/nosnippet)technical
  • ✓2 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
  • ✓Link anchor texts are descriptive — good AI context signalsemantic

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