Analysis
Website
Embotech AG
Analysis
Website
Embotech AG
Analysis
Website
Embotech AG
Summary
About
Company
Embotech AG
Overall Score of Website
32
Analysed on 2026-03-19
Description
Embotech AG is a Zürich-based Level 4 autonomous driving company founded in 2013 as an ETH Zurich spin-off by Alexander Domahidi and Juan Jerez. The company develops two certified autonomous logistics solutions: Automated Vehicle Marshalling (AVM) — deployed at BMW factories in Dingolfing, Leipzig, Regensburg, and Spartanburg (SC), driving hundreds of vehicles per day; and Autonomous Tractor Solution (ATS) — deployed at APM Terminals Rotterdam and EUROGATE Hamburg for driverless port tractor operations. Both solutions are TÜV SÜD-certified Level-4 autonomous driving systems, making Embotech the first company worldwide with two independently certified L4 solutions (AVM certified June 2024, ATS certified Jan 2026). 500,000+ vehicles driven autonomously to date. Series B: CHF 23.5M (Dec 2024), led by Emerald Technology Ventures and Yttrium; backed by BMW i Ventures, Nabtesco Technology Ventures, Sustainable Forward Capital, RKK VC. ~115 employees. CEO: Andreas Kyrtatos. CTO & Co-founder: Alexander Domahidi.
Market
Level 4 Autonomous Driving for Industrial Logistics / Automated Vehicle Marshalling (Automotive Factories) / Autonomous Terminal Tractors (Ports and Yards)
Audience
Automotive OEM production and logistics heads (BMW, VW, Stellantis); port terminal operators evaluating autonomous tractor systems; autonomous vehicle and industrial automation investors; logistics technology procurement teams; ETH Zurich and European deep-tech talent (recruiting)
HQ
Zürich, Switzerland (+ Munich, Oxford, Rotterdam, Novi Sad)
Summary
Spider Chart
Copy
18
Copy
20
Copy
32
Navigation
35
Strategy
28
Social Proof
38
Copy
40
Strategy
30
Content
36
Navigation
44
Copy
Hero Vehicle Counter Renders as '000'000' — JavaScript Animation Not Firing to Actual Number
Score
18
Severity
High
Finding
The homepage hero displays a large animated counter stat with the label 'vehicles driven autonomously to-date.' The counter value renders in the fetched DOM as the literal string '000'000' — the JavaScript counting animation has not resolved to the actual number (500,000 vehicles, per the company's own news item '500,000 Vehicles Driven Autonomously' published on the news page). This is the same class of zero-counter failure found in ANYbotics (0 Years Experience, 0 Customers, 0 Team Members) and deepki.com ('0+ buildings', '$0T+ AUM') earlier in this series. Any visitor on a slow connection, a no-JS environment, a screen reader, or a web crawler sees '000'000 vehicles driven autonomously' — a figure that reads as either zero or a placeholder error. The stat is Embotech's single most powerful proof point — 500,000 autonomous vehicle operations in production — and it is silently broken for a subset of visitors.
Recommendation
Hardcode the static fallback value in the HTML: '500,000 vehicles driven autonomously to-date.' The JavaScript counter animation can layer on top as a progressive enhancement, but the underlying DOM node must always contain the real number. This is a 5-minute Webflow fix: in the counter element settings, ensure the starting value is set to the actual number rather than zero, or add a CSS/JS fallback that populates the field if the animation library fails to load. Also evaluate updating the number now that Embotech has passed 500,000 — if the current figure is higher, display the updated count.
Copy
Hero Vehicle Counter Renders as '000'000' — JavaScript Animation Not Firing to Actual Number
Score
18
Severity
High
Finding
The homepage hero displays a large animated counter stat with the label 'vehicles driven autonomously to-date.' The counter value renders in the fetched DOM as the literal string '000'000' — the JavaScript counting animation has not resolved to the actual number (500,000 vehicles, per the company's own news item '500,000 Vehicles Driven Autonomously' published on the news page). This is the same class of zero-counter failure found in ANYbotics (0 Years Experience, 0 Customers, 0 Team Members) and deepki.com ('0+ buildings', '$0T+ AUM') earlier in this series. Any visitor on a slow connection, a no-JS environment, a screen reader, or a web crawler sees '000'000 vehicles driven autonomously' — a figure that reads as either zero or a placeholder error. The stat is Embotech's single most powerful proof point — 500,000 autonomous vehicle operations in production — and it is silently broken for a subset of visitors.
Recommendation
Hardcode the static fallback value in the HTML: '500,000 vehicles driven autonomously to-date.' The JavaScript counter animation can layer on top as a progressive enhancement, but the underlying DOM node must always contain the real number. This is a 5-minute Webflow fix: in the counter element settings, ensure the starting value is set to the actual number rather than zero, or add a CSS/JS fallback that populates the field if the animation library fails to load. Also evaluate updating the number now that Embotech has passed 500,000 — if the current figure is higher, display the updated count.
Copy
Hero Vehicle Counter Renders as '000'000' — JavaScript Animation Not Firing to Actual Number
Score
18
Severity
High
Finding
The homepage hero displays a large animated counter stat with the label 'vehicles driven autonomously to-date.' The counter value renders in the fetched DOM as the literal string '000'000' — the JavaScript counting animation has not resolved to the actual number (500,000 vehicles, per the company's own news item '500,000 Vehicles Driven Autonomously' published on the news page). This is the same class of zero-counter failure found in ANYbotics (0 Years Experience, 0 Customers, 0 Team Members) and deepki.com ('0+ buildings', '$0T+ AUM') earlier in this series. Any visitor on a slow connection, a no-JS environment, a screen reader, or a web crawler sees '000'000 vehicles driven autonomously' — a figure that reads as either zero or a placeholder error. The stat is Embotech's single most powerful proof point — 500,000 autonomous vehicle operations in production — and it is silently broken for a subset of visitors.
Recommendation
Hardcode the static fallback value in the HTML: '500,000 vehicles driven autonomously to-date.' The JavaScript counter animation can layer on top as a progressive enhancement, but the underlying DOM node must always contain the real number. This is a 5-minute Webflow fix: in the counter element settings, ensure the starting value is set to the actual number rather than zero, or add a CSS/JS fallback that populates the field if the animation library fails to load. Also evaluate updating the number now that Embotech has passed 500,000 — if the current figure is higher, display the updated count.
Copy
ATS Product Page Contains Three 'This is some text inside of a div block.' Webflow Placeholders Live in Production
Score
20
Severity
High
Finding
The Autonomous Tractor Solution (/autonomous-tractor-solution) page contains the following text, live and visible in the indexed DOM: 'This is some text inside of a div block. This is some text inside of a div block. This is some text inside of a div block.' — three consecutive Webflow default placeholder strings that were never replaced with actual content. This is the same class of error found in amilabs.xyz (2 placeholders) and iplicit.com (Lorem ipsum blocks) earlier in this series. The ATS page is one of the two primary product pages on the Embotech website and is the destination of every sales inquiry about port and yard autonomous tractors. The TÜV SÜD certification announcement, the Rotterdam port deployment, and the EUROGATE Hamburg pilot are all linked from this page — and three placeholder strings sit in the content between these sections.
Recommendation
Delete all three 'This is some text inside of a div block.' instances from the ATS page in the Webflow editor immediately. This is a 30-second fix: select each div block, identify the placeholder text, and either replace with real content or delete the block entirely. Then audit every other page on the site (AVM page, Technology page, About Us, Careers) for additional Webflow placeholder text using Webflow's built-in search or a manual page review. The site appears to have been recently migrated to or rebuilt in Webflow — placeholder text in newly published pages is a common post-migration artefact that requires systematic review before go-live.
Copy
ATS Product Page Contains Three 'This is some text inside of a div block.' Webflow Placeholders Live in Production
Score
20
Severity
High
Finding
The Autonomous Tractor Solution (/autonomous-tractor-solution) page contains the following text, live and visible in the indexed DOM: 'This is some text inside of a div block. This is some text inside of a div block. This is some text inside of a div block.' — three consecutive Webflow default placeholder strings that were never replaced with actual content. This is the same class of error found in amilabs.xyz (2 placeholders) and iplicit.com (Lorem ipsum blocks) earlier in this series. The ATS page is one of the two primary product pages on the Embotech website and is the destination of every sales inquiry about port and yard autonomous tractors. The TÜV SÜD certification announcement, the Rotterdam port deployment, and the EUROGATE Hamburg pilot are all linked from this page — and three placeholder strings sit in the content between these sections.
Recommendation
Delete all three 'This is some text inside of a div block.' instances from the ATS page in the Webflow editor immediately. This is a 30-second fix: select each div block, identify the placeholder text, and either replace with real content or delete the block entirely. Then audit every other page on the site (AVM page, Technology page, About Us, Careers) for additional Webflow placeholder text using Webflow's built-in search or a manual page review. The site appears to have been recently migrated to or rebuilt in Webflow — placeholder text in newly published pages is a common post-migration artefact that requires systematic review before go-live.
Copy
ATS Product Page Contains Three 'This is some text inside of a div block.' Webflow Placeholders Live in Production
Score
20
Severity
High
Finding
The Autonomous Tractor Solution (/autonomous-tractor-solution) page contains the following text, live and visible in the indexed DOM: 'This is some text inside of a div block. This is some text inside of a div block. This is some text inside of a div block.' — three consecutive Webflow default placeholder strings that were never replaced with actual content. This is the same class of error found in amilabs.xyz (2 placeholders) and iplicit.com (Lorem ipsum blocks) earlier in this series. The ATS page is one of the two primary product pages on the Embotech website and is the destination of every sales inquiry about port and yard autonomous tractors. The TÜV SÜD certification announcement, the Rotterdam port deployment, and the EUROGATE Hamburg pilot are all linked from this page — and three placeholder strings sit in the content between these sections.
Recommendation
Delete all three 'This is some text inside of a div block.' instances from the ATS page in the Webflow editor immediately. This is a 30-second fix: select each div block, identify the placeholder text, and either replace with real content or delete the block entirely. Then audit every other page on the site (AVM page, Technology page, About Us, Careers) for additional Webflow placeholder text using Webflow's built-in search or a manual page review. The site appears to have been recently migrated to or rebuilt in Webflow — placeholder text in newly published pages is a common post-migration artefact that requires systematic review before go-live.
Copy
Footer Copyright Reads '© 2025 embotech' — Stale in March 2026
Score
32
Severity
Medium
Finding
The homepage footer displays '© 2025 embotech' — the copyright year has not been updated for the new calendar year. As of March 2026, the footer is 3 months stale. While less severe than the 7-year stale copyright on disneyresearch.com or the 2-year stale copyright on multiple earlier sites in this series, a stale copyright year in the first quarter of a new year is the most common and most preventable web maintenance failure. For an industrial B2B company whose enterprise customers (BMW, EUROGATE, APM Terminals, VW Group) conduct vendor due diligence that includes reviewing the company's web presence, a stale copyright year is a minor but visible signal of inattention.
Recommendation
Update '© 2025 embotech' to '© 2026 embotech' in the Webflow footer component. Implement a dynamic copyright year using a Webflow CMS date field or embed code: `<script>document.write(new Date().getFullYear())</script>` so the year auto-advances without manual intervention. This is the same recommendation given to 20+ sites in this audit series — a dynamic copyright year is a zero-maintenance fix that permanently closes this issue.
Copy
Footer Copyright Reads '© 2025 embotech' — Stale in March 2026
Score
32
Severity
Medium
Finding
The homepage footer displays '© 2025 embotech' — the copyright year has not been updated for the new calendar year. As of March 2026, the footer is 3 months stale. While less severe than the 7-year stale copyright on disneyresearch.com or the 2-year stale copyright on multiple earlier sites in this series, a stale copyright year in the first quarter of a new year is the most common and most preventable web maintenance failure. For an industrial B2B company whose enterprise customers (BMW, EUROGATE, APM Terminals, VW Group) conduct vendor due diligence that includes reviewing the company's web presence, a stale copyright year is a minor but visible signal of inattention.
Recommendation
Update '© 2025 embotech' to '© 2026 embotech' in the Webflow footer component. Implement a dynamic copyright year using a Webflow CMS date field or embed code: `<script>document.write(new Date().getFullYear())</script>` so the year auto-advances without manual intervention. This is the same recommendation given to 20+ sites in this audit series — a dynamic copyright year is a zero-maintenance fix that permanently closes this issue.
Copy
Footer Copyright Reads '© 2025 embotech' — Stale in March 2026
Score
32
Severity
Medium
Finding
The homepage footer displays '© 2025 embotech' — the copyright year has not been updated for the new calendar year. As of March 2026, the footer is 3 months stale. While less severe than the 7-year stale copyright on disneyresearch.com or the 2-year stale copyright on multiple earlier sites in this series, a stale copyright year in the first quarter of a new year is the most common and most preventable web maintenance failure. For an industrial B2B company whose enterprise customers (BMW, EUROGATE, APM Terminals, VW Group) conduct vendor due diligence that includes reviewing the company's web presence, a stale copyright year is a minor but visible signal of inattention.
Recommendation
Update '© 2025 embotech' to '© 2026 embotech' in the Webflow footer component. Implement a dynamic copyright year using a Webflow CMS date field or embed code: `<script>document.write(new Date().getFullYear())</script>` so the year auto-advances without manual intervention. This is the same recommendation given to 20+ sites in this audit series — a dynamic copyright year is a zero-maintenance fix that permanently closes this issue.
Navigation
Desktop Nav Label 'NEWS' vs Mobile Nav Label 'Stories' — Inconsistent Navigation Labels for the Same Page
Score
35
Severity
Medium
Finding
The homepage navigation contains an inconsistency between the desktop and mobile versions: the desktop nav shows 'NEWS' (in all-caps) linking to /news, while the mobile/hamburger nav shows 'Stories' linking to the same destination. Two different labels for the same page create confusion — a user who navigates on desktop learns the section is called 'News,' then switches to mobile and cannot find 'News' because it has been renamed 'Stories.' The /news URL also contains a mix of news articles and what appear to be editorial/story-format posts, suggesting an incomplete rebrand of the section from 'News' to 'Stories' that was applied inconsistently across the navigation components. The footer further uses 'News' (consistent with desktop nav), making the mobile 'Stories' label the outlier.
Recommendation
Standardise the navigation label across all breakpoints. Choose one label — either 'News' (clearer for press/investors/partners) or 'Stories' (if the editorial rebrand is intentional) — and apply it consistently to the desktop nav, mobile nav, and footer. If 'Stories' is the intended direction, update the desktop nav and footer to match. If 'News' is correct, update the mobile nav to match. Also review the page title and H1 on /news — if it displays 'Stories' as the H1 but 'News' in the nav, that creates an additional inconsistency.
Navigation
Desktop Nav Label 'NEWS' vs Mobile Nav Label 'Stories' — Inconsistent Navigation Labels for the Same Page
Score
35
Severity
Medium
Finding
The homepage navigation contains an inconsistency between the desktop and mobile versions: the desktop nav shows 'NEWS' (in all-caps) linking to /news, while the mobile/hamburger nav shows 'Stories' linking to the same destination. Two different labels for the same page create confusion — a user who navigates on desktop learns the section is called 'News,' then switches to mobile and cannot find 'News' because it has been renamed 'Stories.' The /news URL also contains a mix of news articles and what appear to be editorial/story-format posts, suggesting an incomplete rebrand of the section from 'News' to 'Stories' that was applied inconsistently across the navigation components. The footer further uses 'News' (consistent with desktop nav), making the mobile 'Stories' label the outlier.
Recommendation
Standardise the navigation label across all breakpoints. Choose one label — either 'News' (clearer for press/investors/partners) or 'Stories' (if the editorial rebrand is intentional) — and apply it consistently to the desktop nav, mobile nav, and footer. If 'Stories' is the intended direction, update the desktop nav and footer to match. If 'News' is correct, update the mobile nav to match. Also review the page title and H1 on /news — if it displays 'Stories' as the H1 but 'News' in the nav, that creates an additional inconsistency.
Navigation
Desktop Nav Label 'NEWS' vs Mobile Nav Label 'Stories' — Inconsistent Navigation Labels for the Same Page
Score
35
Severity
Medium
Finding
The homepage navigation contains an inconsistency between the desktop and mobile versions: the desktop nav shows 'NEWS' (in all-caps) linking to /news, while the mobile/hamburger nav shows 'Stories' linking to the same destination. Two different labels for the same page create confusion — a user who navigates on desktop learns the section is called 'News,' then switches to mobile and cannot find 'News' because it has been renamed 'Stories.' The /news URL also contains a mix of news articles and what appear to be editorial/story-format posts, suggesting an incomplete rebrand of the section from 'News' to 'Stories' that was applied inconsistently across the navigation components. The footer further uses 'News' (consistent with desktop nav), making the mobile 'Stories' label the outlier.
Recommendation
Standardise the navigation label across all breakpoints. Choose one label — either 'News' (clearer for press/investors/partners) or 'Stories' (if the editorial rebrand is intentional) — and apply it consistently to the desktop nav, mobile nav, and footer. If 'Stories' is the intended direction, update the desktop nav and footer to match. If 'News' is correct, update the mobile nav to match. Also review the page title and H1 on /news — if it displays 'Stories' as the H1 but 'News' in the nav, that creates an additional inconsistency.
Strategy
CHF 23.5M Series B (Dec 2024) and ATS TÜV SÜD Certification (Jan 2026) Not in Hero or Above the Fold
Score
28
Severity
High
Finding
Embotech completed a CHF 23.5M (€25M) Series B round in December 2024 — led by Emerald Technology Ventures and Yttrium, with BMW i Ventures, Nabtesco Technology Ventures, Sustainable Forward Capital, and RKK VC participating. In January 2026, Embotech received TÜV SÜD EC-Type Examination Certificate for its ATS solution, becoming the first company worldwide with two TÜV SÜD-certified Level-4 autonomous driving systems. Neither milestone appears in the hero, above the fold, or in any trust bar on the homepage. The homepage's trust signals are limited to the client logo bar (BMW, APMT, Eurogate, VW, CARIAD, Terberg, Hesai, Rajant, dSPACE, NEXT G, MathWorks, MAFI Trepel). For a B2B industrial automation company competing for 8-figure multi-year contracts, the combination of a major funding round and a dual TÜV SÜD certification are the two strongest credibility signals available — both are invisible above the fold.
Recommendation
Add a homepage trust bar or announcement banner: 'CHF 23.5M Series B — backed by BMW i Ventures, Emerald Technology Ventures, and Yttrium' and 'First company worldwide with two TÜV SÜD-certified Level-4 autonomous solutions (AVM + ATS).' The TÜV SÜD dual certification claim in particular is a genuine differentiator — Embotech explicitly states it is the first company worldwide to hold two independent TÜV certifications for Level-4 autonomous driving. This claim should be in the hero, not buried in a sub-page announcement. For port operators and automotive OEMs evaluating autonomous logistics vendors, TÜV SÜD certification is the primary safety-compliance signal that unlocks procurement approval.
Strategy
CHF 23.5M Series B (Dec 2024) and ATS TÜV SÜD Certification (Jan 2026) Not in Hero or Above the Fold
Score
28
Severity
High
Finding
Embotech completed a CHF 23.5M (€25M) Series B round in December 2024 — led by Emerald Technology Ventures and Yttrium, with BMW i Ventures, Nabtesco Technology Ventures, Sustainable Forward Capital, and RKK VC participating. In January 2026, Embotech received TÜV SÜD EC-Type Examination Certificate for its ATS solution, becoming the first company worldwide with two TÜV SÜD-certified Level-4 autonomous driving systems. Neither milestone appears in the hero, above the fold, or in any trust bar on the homepage. The homepage's trust signals are limited to the client logo bar (BMW, APMT, Eurogate, VW, CARIAD, Terberg, Hesai, Rajant, dSPACE, NEXT G, MathWorks, MAFI Trepel). For a B2B industrial automation company competing for 8-figure multi-year contracts, the combination of a major funding round and a dual TÜV SÜD certification are the two strongest credibility signals available — both are invisible above the fold.
Recommendation
Add a homepage trust bar or announcement banner: 'CHF 23.5M Series B — backed by BMW i Ventures, Emerald Technology Ventures, and Yttrium' and 'First company worldwide with two TÜV SÜD-certified Level-4 autonomous solutions (AVM + ATS).' The TÜV SÜD dual certification claim in particular is a genuine differentiator — Embotech explicitly states it is the first company worldwide to hold two independent TÜV certifications for Level-4 autonomous driving. This claim should be in the hero, not buried in a sub-page announcement. For port operators and automotive OEMs evaluating autonomous logistics vendors, TÜV SÜD certification is the primary safety-compliance signal that unlocks procurement approval.
Strategy
CHF 23.5M Series B (Dec 2024) and ATS TÜV SÜD Certification (Jan 2026) Not in Hero or Above the Fold
Score
28
Severity
High
Finding
Embotech completed a CHF 23.5M (€25M) Series B round in December 2024 — led by Emerald Technology Ventures and Yttrium, with BMW i Ventures, Nabtesco Technology Ventures, Sustainable Forward Capital, and RKK VC participating. In January 2026, Embotech received TÜV SÜD EC-Type Examination Certificate for its ATS solution, becoming the first company worldwide with two TÜV SÜD-certified Level-4 autonomous driving systems. Neither milestone appears in the hero, above the fold, or in any trust bar on the homepage. The homepage's trust signals are limited to the client logo bar (BMW, APMT, Eurogate, VW, CARIAD, Terberg, Hesai, Rajant, dSPACE, NEXT G, MathWorks, MAFI Trepel). For a B2B industrial automation company competing for 8-figure multi-year contracts, the combination of a major funding round and a dual TÜV SÜD certification are the two strongest credibility signals available — both are invisible above the fold.
Recommendation
Add a homepage trust bar or announcement banner: 'CHF 23.5M Series B — backed by BMW i Ventures, Emerald Technology Ventures, and Yttrium' and 'First company worldwide with two TÜV SÜD-certified Level-4 autonomous solutions (AVM + ATS).' The TÜV SÜD dual certification claim in particular is a genuine differentiator — Embotech explicitly states it is the first company worldwide to hold two independent TÜV certifications for Level-4 autonomous driving. This claim should be in the hero, not buried in a sub-page announcement. For port operators and automotive OEMs evaluating autonomous logistics vendors, TÜV SÜD certification is the primary safety-compliance signal that unlocks procurement approval.
Social Proof
Client Logo Bar Has No Alt Text on Any of the 12 Logos — BMW, APMT, Eurogate, VW Group All Unreadable by Crawlers
Score
38
Severity
Medium
Finding
The homepage 'You are in good company' client logo bar features 12 customer and partner logos: BMW, APMT (APM Terminals), Eurogate, VW, CARIAD, Terberg Special Vehicles, Hesai, Rajant, dSPACE, NEXT G, MathWorks, and MAFI Trepel. Every logo is rendered as an image-only element with no alt text — the same zero-alt-text pattern found in a majority of sites in this series (gravisrobotics, scaile.tech, cocodelivery, neo4j, and others). For Embotech's SEO and AI search visibility, the absence of alt text means that crawlers cannot determine from the homepage that BMW and Volkswagen Group are customers. A search engine or AI assistant answering 'who are Embotech's customers?' cannot read the logo bar and must rely on external press coverage alone.
Recommendation
Add descriptive alt text to every logo image: alt='BMW logo', alt='APM Terminals logo', alt='Eurogate logo', alt='Volkswagen Group logo', etc. This is a 10-minute fix in Webflow's image settings panel. Beyond SEO, alt text is an accessibility requirement — screen readers used by procurement evaluators with visual impairments will not be able to identify the logos without it. Given that BMW and Volkswagen Group are the two most commercially significant customer relationships Embotech has, having their logos silently invisible to all text-based discovery systems is a material marketing gap.
Social Proof
Client Logo Bar Has No Alt Text on Any of the 12 Logos — BMW, APMT, Eurogate, VW Group All Unreadable by Crawlers
Score
38
Severity
Medium
Finding
The homepage 'You are in good company' client logo bar features 12 customer and partner logos: BMW, APMT (APM Terminals), Eurogate, VW, CARIAD, Terberg Special Vehicles, Hesai, Rajant, dSPACE, NEXT G, MathWorks, and MAFI Trepel. Every logo is rendered as an image-only element with no alt text — the same zero-alt-text pattern found in a majority of sites in this series (gravisrobotics, scaile.tech, cocodelivery, neo4j, and others). For Embotech's SEO and AI search visibility, the absence of alt text means that crawlers cannot determine from the homepage that BMW and Volkswagen Group are customers. A search engine or AI assistant answering 'who are Embotech's customers?' cannot read the logo bar and must rely on external press coverage alone.
Recommendation
Add descriptive alt text to every logo image: alt='BMW logo', alt='APM Terminals logo', alt='Eurogate logo', alt='Volkswagen Group logo', etc. This is a 10-minute fix in Webflow's image settings panel. Beyond SEO, alt text is an accessibility requirement — screen readers used by procurement evaluators with visual impairments will not be able to identify the logos without it. Given that BMW and Volkswagen Group are the two most commercially significant customer relationships Embotech has, having their logos silently invisible to all text-based discovery systems is a material marketing gap.
Social Proof
Client Logo Bar Has No Alt Text on Any of the 12 Logos — BMW, APMT, Eurogate, VW Group All Unreadable by Crawlers
Score
38
Severity
Medium
Finding
The homepage 'You are in good company' client logo bar features 12 customer and partner logos: BMW, APMT (APM Terminals), Eurogate, VW, CARIAD, Terberg Special Vehicles, Hesai, Rajant, dSPACE, NEXT G, MathWorks, and MAFI Trepel. Every logo is rendered as an image-only element with no alt text — the same zero-alt-text pattern found in a majority of sites in this series (gravisrobotics, scaile.tech, cocodelivery, neo4j, and others). For Embotech's SEO and AI search visibility, the absence of alt text means that crawlers cannot determine from the homepage that BMW and Volkswagen Group are customers. A search engine or AI assistant answering 'who are Embotech's customers?' cannot read the logo bar and must rely on external press coverage alone.
Recommendation
Add descriptive alt text to every logo image: alt='BMW logo', alt='APM Terminals logo', alt='Eurogate logo', alt='Volkswagen Group logo', etc. This is a 10-minute fix in Webflow's image settings panel. Beyond SEO, alt text is an accessibility requirement — screen readers used by procurement evaluators with visual impairments will not be able to identify the logos without it. Given that BMW and Volkswagen Group are the two most commercially significant customer relationships Embotech has, having their logos silently invisible to all text-based discovery systems is a material marketing gap.
Copy
About Us Page States '120 Engineers' — But PitchBook and Tracxn Show 45–115 Employees as of Mid-2024
Score
40
Severity
Medium
Finding
The About Us page (/about-us) describes Embotech as having 'a growing team of about 120 engineers, software developers and visionaries with 15 different nationalities.' PitchBook records 115 employees as of 2025, and Tracxn shows 45 employees as of July 2024. The discrepancy between the About Us claim (120) and third-party data (45–115) is significant — either the headcount has grown substantially since mid-2024 following the Series B, which would make the '120' figure current and the third-party data stale; or the About Us page is overstating the headcount. Given the CHF 23.5M Series B closed in December 2024, aggressive hiring post-funding is plausible. However, '120' is specific enough to be verifiable, and if it is inaccurate it creates a credibility risk for enterprise customers performing vendor financial due diligence.
Recommendation
Verify the current employee count and update the About Us page to reflect the accurate figure with a date qualifier: 'a growing team of over X engineers and developers (as of Q1 2026).' If 120 is accurate post-Series B hiring, add context: 'a team that has grown to 120+ following our Series B funding.' If the figure is aspirational or projected, phrase it accordingly. The '15 different nationalities' detail is a strong diversity signal that adds authenticity — keep it. Also ensure LinkedIn headcount and PitchBook/Crunchbase profiles are updated to reflect current hiring, as major discrepancies between a company's own stated headcount and third-party databases raise flags for due diligence teams.
Copy
About Us Page States '120 Engineers' — But PitchBook and Tracxn Show 45–115 Employees as of Mid-2024
Score
40
Severity
Medium
Finding
The About Us page (/about-us) describes Embotech as having 'a growing team of about 120 engineers, software developers and visionaries with 15 different nationalities.' PitchBook records 115 employees as of 2025, and Tracxn shows 45 employees as of July 2024. The discrepancy between the About Us claim (120) and third-party data (45–115) is significant — either the headcount has grown substantially since mid-2024 following the Series B, which would make the '120' figure current and the third-party data stale; or the About Us page is overstating the headcount. Given the CHF 23.5M Series B closed in December 2024, aggressive hiring post-funding is plausible. However, '120' is specific enough to be verifiable, and if it is inaccurate it creates a credibility risk for enterprise customers performing vendor financial due diligence.
Recommendation
Verify the current employee count and update the About Us page to reflect the accurate figure with a date qualifier: 'a growing team of over X engineers and developers (as of Q1 2026).' If 120 is accurate post-Series B hiring, add context: 'a team that has grown to 120+ following our Series B funding.' If the figure is aspirational or projected, phrase it accordingly. The '15 different nationalities' detail is a strong diversity signal that adds authenticity — keep it. Also ensure LinkedIn headcount and PitchBook/Crunchbase profiles are updated to reflect current hiring, as major discrepancies between a company's own stated headcount and third-party databases raise flags for due diligence teams.
Copy
About Us Page States '120 Engineers' — But PitchBook and Tracxn Show 45–115 Employees as of Mid-2024
Score
40
Severity
Medium
Finding
The About Us page (/about-us) describes Embotech as having 'a growing team of about 120 engineers, software developers and visionaries with 15 different nationalities.' PitchBook records 115 employees as of 2025, and Tracxn shows 45 employees as of July 2024. The discrepancy between the About Us claim (120) and third-party data (45–115) is significant — either the headcount has grown substantially since mid-2024 following the Series B, which would make the '120' figure current and the third-party data stale; or the About Us page is overstating the headcount. Given the CHF 23.5M Series B closed in December 2024, aggressive hiring post-funding is plausible. However, '120' is specific enough to be verifiable, and if it is inaccurate it creates a credibility risk for enterprise customers performing vendor financial due diligence.
Recommendation
Verify the current employee count and update the About Us page to reflect the accurate figure with a date qualifier: 'a growing team of over X engineers and developers (as of Q1 2026).' If 120 is accurate post-Series B hiring, add context: 'a team that has grown to 120+ following our Series B funding.' If the figure is aspirational or projected, phrase it accordingly. The '15 different nationalities' detail is a strong diversity signal that adds authenticity — keep it. Also ensure LinkedIn headcount and PitchBook/Crunchbase profiles are updated to reflect current hiring, as major discrepancies between a company's own stated headcount and third-party databases raise flags for due diligence teams.
Strategy
500,000 Autonomous Vehicles Milestone Published as a News Story — Not Featured as a Hero Stat on Homepage
Score
30
Severity
High
Finding
Embotech has driven 500,000 vehicles autonomously to date — a milestone documented in a news article titled '500,000 Vehicles Driven Autonomously: Lessons Learned and the Path Ahead' prominently linked from the homepage news section. However, the primary homepage hero displays only the counter (currently broken as '000'000' per Issue #1) and the text 'vehicles driven autonomously to-date' without the actual milestone number. The news article about the 500,000 milestone exists, but the hero counter — which should be the most impactful proof point on the page — is both broken and insufficiently contextualized. 500,000 autonomous vehicle operations in real BMW production environments is not a minor traction metric — it is extraordinary proof of production-scale deployment for any Level 4 autonomous driving company.
Recommendation
Make '500,000+ vehicles driven autonomously' a hero stat with hard numbers and context: '500,000+ vehicles driven autonomously — in BMW, VW, and port production environments.' Link the stat to the news article for visitors who want the full story. Fix the JavaScript counter animation so the number resolves correctly (per Issue #1). Consider adding two additional validated stats alongside it: e.g., '3 BMW factories deployed' and '30 ATTs rolling out at Rotterdam.' Three specific, verifiable numbers in the hero communicate traction far more effectively than product descriptions alone.
Strategy
500,000 Autonomous Vehicles Milestone Published as a News Story — Not Featured as a Hero Stat on Homepage
Score
30
Severity
High
Finding
Embotech has driven 500,000 vehicles autonomously to date — a milestone documented in a news article titled '500,000 Vehicles Driven Autonomously: Lessons Learned and the Path Ahead' prominently linked from the homepage news section. However, the primary homepage hero displays only the counter (currently broken as '000'000' per Issue #1) and the text 'vehicles driven autonomously to-date' without the actual milestone number. The news article about the 500,000 milestone exists, but the hero counter — which should be the most impactful proof point on the page — is both broken and insufficiently contextualized. 500,000 autonomous vehicle operations in real BMW production environments is not a minor traction metric — it is extraordinary proof of production-scale deployment for any Level 4 autonomous driving company.
Recommendation
Make '500,000+ vehicles driven autonomously' a hero stat with hard numbers and context: '500,000+ vehicles driven autonomously — in BMW, VW, and port production environments.' Link the stat to the news article for visitors who want the full story. Fix the JavaScript counter animation so the number resolves correctly (per Issue #1). Consider adding two additional validated stats alongside it: e.g., '3 BMW factories deployed' and '30 ATTs rolling out at Rotterdam.' Three specific, verifiable numbers in the hero communicate traction far more effectively than product descriptions alone.
Strategy
500,000 Autonomous Vehicles Milestone Published as a News Story — Not Featured as a Hero Stat on Homepage
Score
30
Severity
High
Finding
Embotech has driven 500,000 vehicles autonomously to date — a milestone documented in a news article titled '500,000 Vehicles Driven Autonomously: Lessons Learned and the Path Ahead' prominently linked from the homepage news section. However, the primary homepage hero displays only the counter (currently broken as '000'000' per Issue #1) and the text 'vehicles driven autonomously to-date' without the actual milestone number. The news article about the 500,000 milestone exists, but the hero counter — which should be the most impactful proof point on the page — is both broken and insufficiently contextualized. 500,000 autonomous vehicle operations in real BMW production environments is not a minor traction metric — it is extraordinary proof of production-scale deployment for any Level 4 autonomous driving company.
Recommendation
Make '500,000+ vehicles driven autonomously' a hero stat with hard numbers and context: '500,000+ vehicles driven autonomously — in BMW, VW, and port production environments.' Link the stat to the news article for visitors who want the full story. Fix the JavaScript counter animation so the number resolves correctly (per Issue #1). Consider adding two additional validated stats alongside it: e.g., '3 BMW factories deployed' and '30 ATTs rolling out at Rotterdam.' Three specific, verifiable numbers in the hero communicate traction far more effectively than product descriptions alone.
Content
Legacy Pages Still Indexed — /solutions/energy-management/ and /solutions/industryrobotics/ Describe Old Product Lines
Score
36
Severity
Medium
Finding
Google's search index includes two legacy embotech.com pages that describe product lines no longer prominently featured in the company's current positioning: /solutions/energy-management/ (describing optimization for electric/hybrid vehicle powertrains, including Formula E energy management with the Porsche TAG Heuer team) and /solutions/industryrobotics/ (describing industrial robot motion planning with PROBOT and FORCESPRO). Both pages use older branding ('PROBOT', 'FORCESPRO', 'PRODRIVER' as product names) and reference a broader solution scope than Embotech's current focused AVM/ATS positioning. The Formula E energy management story dates from before the company's pivot to industrial logistics autonomy. These pages receive search traffic for queries about 'embotech energy management' or 'embotech FORCESPRO' and present a potentially confusing picture of Embotech's current product focus.
Recommendation
Audit all legacy pages for alignment with current positioning. For /solutions/energy-management/ and /solutions/industryrobotics/: either (a) redirect them to the current homepage or the most relevant current product page; (b) add a banner: 'This describes a legacy Embotech solution — our current focus is [AVM/ATS]. See our current products here.'; or (c) if FORCESPRO and PROBOT are still actively marketed, update these pages to reflect current product naming and positioning. The Formula E story is a compelling credibility piece (Porsche TAG Heuer is a high-status reference) — consider repurposing it as a 'Technology Heritage' or 'Origins' section on the About Us page rather than leaving it as a legacy solutions page that confuses the current product narrative.
Content
Legacy Pages Still Indexed — /solutions/energy-management/ and /solutions/industryrobotics/ Describe Old Product Lines
Score
36
Severity
Medium
Finding
Google's search index includes two legacy embotech.com pages that describe product lines no longer prominently featured in the company's current positioning: /solutions/energy-management/ (describing optimization for electric/hybrid vehicle powertrains, including Formula E energy management with the Porsche TAG Heuer team) and /solutions/industryrobotics/ (describing industrial robot motion planning with PROBOT and FORCESPRO). Both pages use older branding ('PROBOT', 'FORCESPRO', 'PRODRIVER' as product names) and reference a broader solution scope than Embotech's current focused AVM/ATS positioning. The Formula E energy management story dates from before the company's pivot to industrial logistics autonomy. These pages receive search traffic for queries about 'embotech energy management' or 'embotech FORCESPRO' and present a potentially confusing picture of Embotech's current product focus.
Recommendation
Audit all legacy pages for alignment with current positioning. For /solutions/energy-management/ and /solutions/industryrobotics/: either (a) redirect them to the current homepage or the most relevant current product page; (b) add a banner: 'This describes a legacy Embotech solution — our current focus is [AVM/ATS]. See our current products here.'; or (c) if FORCESPRO and PROBOT are still actively marketed, update these pages to reflect current product naming and positioning. The Formula E story is a compelling credibility piece (Porsche TAG Heuer is a high-status reference) — consider repurposing it as a 'Technology Heritage' or 'Origins' section on the About Us page rather than leaving it as a legacy solutions page that confuses the current product narrative.
Content
Legacy Pages Still Indexed — /solutions/energy-management/ and /solutions/industryrobotics/ Describe Old Product Lines
Score
36
Severity
Medium
Finding
Google's search index includes two legacy embotech.com pages that describe product lines no longer prominently featured in the company's current positioning: /solutions/energy-management/ (describing optimization for electric/hybrid vehicle powertrains, including Formula E energy management with the Porsche TAG Heuer team) and /solutions/industryrobotics/ (describing industrial robot motion planning with PROBOT and FORCESPRO). Both pages use older branding ('PROBOT', 'FORCESPRO', 'PRODRIVER' as product names) and reference a broader solution scope than Embotech's current focused AVM/ATS positioning. The Formula E energy management story dates from before the company's pivot to industrial logistics autonomy. These pages receive search traffic for queries about 'embotech energy management' or 'embotech FORCESPRO' and present a potentially confusing picture of Embotech's current product focus.
Recommendation
Audit all legacy pages for alignment with current positioning. For /solutions/energy-management/ and /solutions/industryrobotics/: either (a) redirect them to the current homepage or the most relevant current product page; (b) add a banner: 'This describes a legacy Embotech solution — our current focus is [AVM/ATS]. See our current products here.'; or (c) if FORCESPRO and PROBOT are still actively marketed, update these pages to reflect current product naming and positioning. The Formula E story is a compelling credibility piece (Porsche TAG Heuer is a high-status reference) — consider repurposing it as a 'Technology Heritage' or 'Origins' section on the About Us page rather than leaving it as a legacy solutions page that confuses the current product narrative.
Navigation
Homepage Footer Privacy Policy Link Routes to /terms-and-conditions — Mislabeled Destination
Score
44
Severity
Low
Finding
The homepage contact form contains the text 'Read our privacy policy here' with the word 'here' linking to https://www.embotech.com/terms-and-conditions. The link is labeled 'privacy policy' but routes to the Terms & Conditions page, not a dedicated privacy policy page. Similarly, the footer cookie consent modal describes the Privacy Policy but links to /cookie-acceptance rather than a dedicated privacy policy URL. For a company deploying autonomous systems in BMW factories and European ports — operating under GDPR jurisdiction — having mislabeled legal links (privacy policy → T&Cs, privacy policy → cookie policy) is a compliance signal issue. Enterprise legal teams reviewing vendor data practices will notice that the privacy policy link does not go to a privacy policy.
Recommendation
Create a dedicated /privacy-policy page (or ensure the existing /terms-and-conditions page contains the full privacy policy, correctly labeled). Update all references to 'privacy policy' to link to the correct URL. Audit the cookie consent modal to ensure it links to the actual privacy policy, not the cookie policy. For GDPR compliance, a clearly accessible and correctly labeled privacy policy is a legal requirement — not just a best practice. The current structure (privacy policy → T&Cs, privacy policy → cookie policy) creates ambiguity about what information the links actually contain.
Navigation
Homepage Footer Privacy Policy Link Routes to /terms-and-conditions — Mislabeled Destination
Score
44
Severity
Low
Finding
The homepage contact form contains the text 'Read our privacy policy here' with the word 'here' linking to https://www.embotech.com/terms-and-conditions. The link is labeled 'privacy policy' but routes to the Terms & Conditions page, not a dedicated privacy policy page. Similarly, the footer cookie consent modal describes the Privacy Policy but links to /cookie-acceptance rather than a dedicated privacy policy URL. For a company deploying autonomous systems in BMW factories and European ports — operating under GDPR jurisdiction — having mislabeled legal links (privacy policy → T&Cs, privacy policy → cookie policy) is a compliance signal issue. Enterprise legal teams reviewing vendor data practices will notice that the privacy policy link does not go to a privacy policy.
Recommendation
Create a dedicated /privacy-policy page (or ensure the existing /terms-and-conditions page contains the full privacy policy, correctly labeled). Update all references to 'privacy policy' to link to the correct URL. Audit the cookie consent modal to ensure it links to the actual privacy policy, not the cookie policy. For GDPR compliance, a clearly accessible and correctly labeled privacy policy is a legal requirement — not just a best practice. The current structure (privacy policy → T&Cs, privacy policy → cookie policy) creates ambiguity about what information the links actually contain.
Navigation
Homepage Footer Privacy Policy Link Routes to /terms-and-conditions — Mislabeled Destination
Score
44
Severity
Low
Finding
The homepage contact form contains the text 'Read our privacy policy here' with the word 'here' linking to https://www.embotech.com/terms-and-conditions. The link is labeled 'privacy policy' but routes to the Terms & Conditions page, not a dedicated privacy policy page. Similarly, the footer cookie consent modal describes the Privacy Policy but links to /cookie-acceptance rather than a dedicated privacy policy URL. For a company deploying autonomous systems in BMW factories and European ports — operating under GDPR jurisdiction — having mislabeled legal links (privacy policy → T&Cs, privacy policy → cookie policy) is a compliance signal issue. Enterprise legal teams reviewing vendor data practices will notice that the privacy policy link does not go to a privacy policy.
Recommendation
Create a dedicated /privacy-policy page (or ensure the existing /terms-and-conditions page contains the full privacy policy, correctly labeled). Update all references to 'privacy policy' to link to the correct URL. Audit the cookie consent modal to ensure it links to the actual privacy policy, not the cookie policy. For GDPR compliance, a clearly accessible and correctly labeled privacy policy is a legal requirement — not just a best practice. The current structure (privacy policy → T&Cs, privacy policy → cookie policy) creates ambiguity about what information the links actually contain.