Analysis
Website
Ardoq
Analysis
Website
Ardoq
Analysis
Website
Ardoq
Summary
About
Company
Ardoq
Overall Score of Website
42
Analysed on 2026-03-19
Description
Ardoq is the leading AI-powered Enterprise Architecture (EA) platform for data-driven business transformation. Provides application rationalization, portfolio management, risk management, business capability modeling, strategy to execution, ERP transformation, technical debt management, AI governance, and process modeling (via ShiftX acquisition). Founded 2013 by Erik Bakstad and Magnulf Pilskog. $159M raised (Series D, March 2022, led by EQT Growth and One Peak, valuation >$300M). 284 employees. ~$35.5M ARR (2024). Gartner Magic Quadrant Leader 5th consecutive year (2025). G2 4.7 stars. 99% CSAT. Customers: ExxonMobil, MUFG, Stanley Black & Decker, Riot Games, Asda, Stihl, US FCC, Carlsberg, Condé Nast. Integrations: Celonis, Lucid Software.
Market
Enterprise Architecture Software / IT Portfolio Management / Business Capability Management / Digital Transformation Platform
Audience
Enterprise Architects, CIOs, IT Leaders, Solution Architects, Security Architects, CISOs, and Enterprise PMOs at mid-market and enterprise organisations managing complex IT landscapes, digital transformation, M&A integrations, and AI governance
HQ
Oslo, Norway (offices in New York, London, and globally)
Summary
Spider Chart
Copy
40
Copy
34
Copy
36
Social Proof
42
Performance
38
Social Proof
44
Navigation
46
Brand
48
Copy
44
SEO
50
Copy
H1 'A Smarter Way To EA' — Five-Word Acronym That Excludes Any Non-EA Audience
Score
40
Severity
High
Finding
The homepage H1 is 'A Smarter Way To EA.' This headline communicates nothing to any visitor who does not already know what 'EA' stands for. Enterprise Architecture as a discipline is understood by practitioners but not by the CIO, CFO, or business leader who controls the buying decision. 'A smarter way to EA' tells a non-practitioner nothing about what the product does, why they need it, or what problem it solves. The sub-head 'Intelligent, Connected, Data-Driven Architecture' adds three adjectives but still no concrete problem statement. Ardoq's own role-based navigation (Enterprise Architects, CIO, Business Leaders, CISO) acknowledges that the buyer audience extends beyond EA practitioners — yet the H1 speaks exclusively to insiders. Competitors like LeanIX (acquired by SAP) and iServer use H1s that name outcomes: 'Reduce IT costs', 'Accelerate digital transformation.'
Recommendation
Rewrite the H1 to lead with a specific outcome that resonates with both EA practitioners and the CIO/CFO buyers who control procurement: 'See Every App, Risk, and Cost Across Your IT Estate — In One Platform.' Or: 'Map Your Entire Technology Landscape. Cut Costs. Enable Change.' The sub-head should then name the product category for context: 'The AI-powered Enterprise Architecture platform for data-driven transformation.' The current H1 is a practitioner tagline, not a buying trigger. Given that Ardoq has invested in role-specific pages for CIO, CISO, Enterprise PMO, and Business Leaders, the homepage H1 should bridge the discipline-specific insider language with the executive-level outcome language that unlocks budget.
Copy
H1 'A Smarter Way To EA' — Five-Word Acronym That Excludes Any Non-EA Audience
Score
40
Severity
High
Finding
The homepage H1 is 'A Smarter Way To EA.' This headline communicates nothing to any visitor who does not already know what 'EA' stands for. Enterprise Architecture as a discipline is understood by practitioners but not by the CIO, CFO, or business leader who controls the buying decision. 'A smarter way to EA' tells a non-practitioner nothing about what the product does, why they need it, or what problem it solves. The sub-head 'Intelligent, Connected, Data-Driven Architecture' adds three adjectives but still no concrete problem statement. Ardoq's own role-based navigation (Enterprise Architects, CIO, Business Leaders, CISO) acknowledges that the buyer audience extends beyond EA practitioners — yet the H1 speaks exclusively to insiders. Competitors like LeanIX (acquired by SAP) and iServer use H1s that name outcomes: 'Reduce IT costs', 'Accelerate digital transformation.'
Recommendation
Rewrite the H1 to lead with a specific outcome that resonates with both EA practitioners and the CIO/CFO buyers who control procurement: 'See Every App, Risk, and Cost Across Your IT Estate — In One Platform.' Or: 'Map Your Entire Technology Landscape. Cut Costs. Enable Change.' The sub-head should then name the product category for context: 'The AI-powered Enterprise Architecture platform for data-driven transformation.' The current H1 is a practitioner tagline, not a buying trigger. Given that Ardoq has invested in role-specific pages for CIO, CISO, Enterprise PMO, and Business Leaders, the homepage H1 should bridge the discipline-specific insider language with the executive-level outcome language that unlocks budget.
Copy
H1 'A Smarter Way To EA' — Five-Word Acronym That Excludes Any Non-EA Audience
Score
40
Severity
High
Finding
The homepage H1 is 'A Smarter Way To EA.' This headline communicates nothing to any visitor who does not already know what 'EA' stands for. Enterprise Architecture as a discipline is understood by practitioners but not by the CIO, CFO, or business leader who controls the buying decision. 'A smarter way to EA' tells a non-practitioner nothing about what the product does, why they need it, or what problem it solves. The sub-head 'Intelligent, Connected, Data-Driven Architecture' adds three adjectives but still no concrete problem statement. Ardoq's own role-based navigation (Enterprise Architects, CIO, Business Leaders, CISO) acknowledges that the buyer audience extends beyond EA practitioners — yet the H1 speaks exclusively to insiders. Competitors like LeanIX (acquired by SAP) and iServer use H1s that name outcomes: 'Reduce IT costs', 'Accelerate digital transformation.'
Recommendation
Rewrite the H1 to lead with a specific outcome that resonates with both EA practitioners and the CIO/CFO buyers who control procurement: 'See Every App, Risk, and Cost Across Your IT Estate — In One Platform.' Or: 'Map Your Entire Technology Landscape. Cut Costs. Enable Change.' The sub-head should then name the product category for context: 'The AI-powered Enterprise Architecture platform for data-driven transformation.' The current H1 is a practitioner tagline, not a buying trigger. Given that Ardoq has invested in role-specific pages for CIO, CISO, Enterprise PMO, and Business Leaders, the homepage H1 should bridge the discipline-specific insider language with the executive-level outcome language that unlocks budget.
Copy
Typo: 'interwined' in Asda Case Study Card (Should Be 'intertwined')
Score
34
Severity
High
Finding
The homepage Asda case study card contains a typo: 'Asda identified over 1,200 applications interwined with complex dependencies.' The word 'interwined' is missing a 't' — the correct spelling is 'intertwined.' This appears twice in the Asda section: first in the stat block ('1200 Apps Mapped — Identified over 1,200 applications intertwined with complex dependencies') where it is correctly spelled 'intertwined', and then in the 'See How' descriptive paragraph where it is misspelled 'interwined.' The inconsistency between the correct spelling in the stat and the misspelling in the paragraph confirms this is a copy error in the paragraph text specifically.
Recommendation
Fix 'interwined' to 'intertwined' in the Asda case study card paragraph. This is a one-word CMS edit. Search the full site for other instances of 'interwined' that may have been introduced from the same copy source. The Asda divestiture story is one of Ardoq's most compelling enterprise proof points (Europe's largest divestiture from Walmart, 1,200 apps mapped) — the case study paragraph deserves proofread copy that matches the quality of the outcome it's describing.
Copy
Typo: 'interwined' in Asda Case Study Card (Should Be 'intertwined')
Score
34
Severity
High
Finding
The homepage Asda case study card contains a typo: 'Asda identified over 1,200 applications interwined with complex dependencies.' The word 'interwined' is missing a 't' — the correct spelling is 'intertwined.' This appears twice in the Asda section: first in the stat block ('1200 Apps Mapped — Identified over 1,200 applications intertwined with complex dependencies') where it is correctly spelled 'intertwined', and then in the 'See How' descriptive paragraph where it is misspelled 'interwined.' The inconsistency between the correct spelling in the stat and the misspelling in the paragraph confirms this is a copy error in the paragraph text specifically.
Recommendation
Fix 'interwined' to 'intertwined' in the Asda case study card paragraph. This is a one-word CMS edit. Search the full site for other instances of 'interwined' that may have been introduced from the same copy source. The Asda divestiture story is one of Ardoq's most compelling enterprise proof points (Europe's largest divestiture from Walmart, 1,200 apps mapped) — the case study paragraph deserves proofread copy that matches the quality of the outcome it's describing.
Copy
Typo: 'interwined' in Asda Case Study Card (Should Be 'intertwined')
Score
34
Severity
High
Finding
The homepage Asda case study card contains a typo: 'Asda identified over 1,200 applications interwined with complex dependencies.' The word 'interwined' is missing a 't' — the correct spelling is 'intertwined.' This appears twice in the Asda section: first in the stat block ('1200 Apps Mapped — Identified over 1,200 applications intertwined with complex dependencies') where it is correctly spelled 'intertwined', and then in the 'See How' descriptive paragraph where it is misspelled 'interwined.' The inconsistency between the correct spelling in the stat and the misspelling in the paragraph confirms this is a copy error in the paragraph text specifically.
Recommendation
Fix 'interwined' to 'intertwined' in the Asda case study card paragraph. This is a one-word CMS edit. Search the full site for other instances of 'interwined' that may have been introduced from the same copy source. The Asda divestiture story is one of Ardoq's most compelling enterprise proof points (Europe's largest divestiture from Walmart, 1,200 apps mapped) — the case study paragraph deserves proofread copy that matches the quality of the outcome it's describing.
Copy
Typo: 'dependancies' in Integration & Cloud Architects Flip Card (Should Be 'dependencies')
Score
36
Severity
High
Finding
The 'Integrations & Cloud Architects' flip card on the homepage lists three benefits including 'Visualize cloud dependancies.' The correct spelling is 'dependencies' — 'dependancies' is a misspelling. This is a role-specific card visible to a technically sophisticated audience (cloud architects) who are particularly likely to notice spelling errors in technical terminology. The word 'dependencies' appears correctly elsewhere on the page (in the Security Architects section: 'map vulnerabilities across apps'), making this a single-instance inconsistency that likely reflects a copy-paste error during card creation.
Recommendation
Fix 'dependancies' to 'dependencies' in the Integrations & Cloud Architects flip card. Run a global search for 'dependancies' across all ardoq.com pages to catch any other instances. This is the same class of single-character misspelling seen in the Asda case study — both suggest the homepage copy received insufficient proofreading before publication. A role-specific card targeting cloud architects should use precise technical terminology.
Copy
Typo: 'dependancies' in Integration & Cloud Architects Flip Card (Should Be 'dependencies')
Score
36
Severity
High
Finding
The 'Integrations & Cloud Architects' flip card on the homepage lists three benefits including 'Visualize cloud dependancies.' The correct spelling is 'dependencies' — 'dependancies' is a misspelling. This is a role-specific card visible to a technically sophisticated audience (cloud architects) who are particularly likely to notice spelling errors in technical terminology. The word 'dependencies' appears correctly elsewhere on the page (in the Security Architects section: 'map vulnerabilities across apps'), making this a single-instance inconsistency that likely reflects a copy-paste error during card creation.
Recommendation
Fix 'dependancies' to 'dependencies' in the Integrations & Cloud Architects flip card. Run a global search for 'dependancies' across all ardoq.com pages to catch any other instances. This is the same class of single-character misspelling seen in the Asda case study — both suggest the homepage copy received insufficient proofreading before publication. A role-specific card targeting cloud architects should use precise technical terminology.
Copy
Typo: 'dependancies' in Integration & Cloud Architects Flip Card (Should Be 'dependencies')
Score
36
Severity
High
Finding
The 'Integrations & Cloud Architects' flip card on the homepage lists three benefits including 'Visualize cloud dependancies.' The correct spelling is 'dependencies' — 'dependancies' is a misspelling. This is a role-specific card visible to a technically sophisticated audience (cloud architects) who are particularly likely to notice spelling errors in technical terminology. The word 'dependencies' appears correctly elsewhere on the page (in the Security Architects section: 'map vulnerabilities across apps'), making this a single-instance inconsistency that likely reflects a copy-paste error during card creation.
Recommendation
Fix 'dependancies' to 'dependencies' in the Integrations & Cloud Architects flip card. Run a global search for 'dependancies' across all ardoq.com pages to catch any other instances. This is the same class of single-character misspelling seen in the Asda case study — both suggest the homepage copy received insufficient proofreading before publication. A role-specific card targeting cloud architects should use precise technical terminology.
Social Proof
G2 Badges Shown Are Winter 2025 — Three Seasons Out of Date in March 2026
Score
42
Severity
Medium
Finding
The homepage awards section displays three G2 badges: 'Winter 2025 Momentum Leader', 'Winter 2025 Best Support', and 'Winter 2025 High Performer.' In March 2026, Winter 2025 is four G2 seasons out of date (Spring 2025, Summer 2025, Fall 2025, Winter 2026 have all been published since). G2 publishes seasonal reports quarterly — Winter 2026 badges would have been available since approximately December 2025. For a platform that self-describes as 'The Undisputed Leader in Enterprise Architecture' immediately above the badge row, displaying badges that are three seasons old undermines the currency of the leadership claim. G2 leadership in EA is a genuine competitive differentiator that Ardoq actively earns — the stale badge presentation is a maintenance failure, not a reflection of the product's actual G2 standing.
Recommendation
Update all three G2 badges to the most current season earned (Winter 2026 or Fall 2025). G2 provides updated badge assets in the vendor portal after each report cycle — this is a three-image swap in HubSpot. Check whether Ardoq earned additional G2 badges in the Winter 2026 cycle (Leader placement, not just Momentum/High Performer) and add them. Given Ardoq's 4.7 G2 rating and 99% CSAT score displayed on the same page, the platform is almost certainly earning strong G2 placements every cycle — they should be current.
Social Proof
G2 Badges Shown Are Winter 2025 — Three Seasons Out of Date in March 2026
Score
42
Severity
Medium
Finding
The homepage awards section displays three G2 badges: 'Winter 2025 Momentum Leader', 'Winter 2025 Best Support', and 'Winter 2025 High Performer.' In March 2026, Winter 2025 is four G2 seasons out of date (Spring 2025, Summer 2025, Fall 2025, Winter 2026 have all been published since). G2 publishes seasonal reports quarterly — Winter 2026 badges would have been available since approximately December 2025. For a platform that self-describes as 'The Undisputed Leader in Enterprise Architecture' immediately above the badge row, displaying badges that are three seasons old undermines the currency of the leadership claim. G2 leadership in EA is a genuine competitive differentiator that Ardoq actively earns — the stale badge presentation is a maintenance failure, not a reflection of the product's actual G2 standing.
Recommendation
Update all three G2 badges to the most current season earned (Winter 2026 or Fall 2025). G2 provides updated badge assets in the vendor portal after each report cycle — this is a three-image swap in HubSpot. Check whether Ardoq earned additional G2 badges in the Winter 2026 cycle (Leader placement, not just Momentum/High Performer) and add them. Given Ardoq's 4.7 G2 rating and 99% CSAT score displayed on the same page, the platform is almost certainly earning strong G2 placements every cycle — they should be current.
Social Proof
G2 Badges Shown Are Winter 2025 — Three Seasons Out of Date in March 2026
Score
42
Severity
Medium
Finding
The homepage awards section displays three G2 badges: 'Winter 2025 Momentum Leader', 'Winter 2025 Best Support', and 'Winter 2025 High Performer.' In March 2026, Winter 2025 is four G2 seasons out of date (Spring 2025, Summer 2025, Fall 2025, Winter 2026 have all been published since). G2 publishes seasonal reports quarterly — Winter 2026 badges would have been available since approximately December 2025. For a platform that self-describes as 'The Undisputed Leader in Enterprise Architecture' immediately above the badge row, displaying badges that are three seasons old undermines the currency of the leadership claim. G2 leadership in EA is a genuine competitive differentiator that Ardoq actively earns — the stale badge presentation is a maintenance failure, not a reflection of the product's actual G2 standing.
Recommendation
Update all three G2 badges to the most current season earned (Winter 2026 or Fall 2025). G2 provides updated badge assets in the vendor portal after each report cycle — this is a three-image swap in HubSpot. Check whether Ardoq earned additional G2 badges in the Winter 2026 cycle (Leader placement, not just Momentum/High Performer) and add them. Given Ardoq's 4.7 G2 rating and 99% CSAT score displayed on the same page, the platform is almost certainly earning strong G2 placements every cycle — they should be current.
Performance
Video Requires Form Fill to Watch — 'Please Fill Out Your Details to Watch Videos' Blocks Hero Video
Score
38
Severity
Medium
Finding
The homepage hero section contains a 'Watch Product Videos' CTA. When clicked, it displays a gate: 'Please Fill Out Your Details to Watch Videos' — a lead capture form that must be completed before any product video plays. Gating a homepage hero product video behind a lead capture form is a significant conversion friction pattern: a visitor who clicks 'Watch Product Videos' from the hero expecting to see a 30-second product overview is instead presented with a form requesting their name, email, and company. For a product whose technical complexity (Enterprise Architecture) benefits enormously from visual demonstration, blocking the hero video behind a gate removes the primary tool for converting a curious prospect into an informed one. The 'Request Demo' CTA already handles lead capture for demo-intent visitors.
Recommendation
Remove the form gate from the homepage hero product video. The hero video should play immediately — its purpose is to show what the product does and create desire, not to capture leads. Lead capture should happen at higher-intent touchpoints: the demo request flow, the white paper download, the webinar registration. A gated homepage video is a conversion antipattern: it introduces friction at the exact moment when a prospect is most curious (after clicking a CTA from the hero) and most likely to bounce if friction is encountered. If analytics are needed, use HubSpot video tracking (Vidyard, Wistia) that records views without requiring form completion.
Performance
Video Requires Form Fill to Watch — 'Please Fill Out Your Details to Watch Videos' Blocks Hero Video
Score
38
Severity
Medium
Finding
The homepage hero section contains a 'Watch Product Videos' CTA. When clicked, it displays a gate: 'Please Fill Out Your Details to Watch Videos' — a lead capture form that must be completed before any product video plays. Gating a homepage hero product video behind a lead capture form is a significant conversion friction pattern: a visitor who clicks 'Watch Product Videos' from the hero expecting to see a 30-second product overview is instead presented with a form requesting their name, email, and company. For a product whose technical complexity (Enterprise Architecture) benefits enormously from visual demonstration, blocking the hero video behind a gate removes the primary tool for converting a curious prospect into an informed one. The 'Request Demo' CTA already handles lead capture for demo-intent visitors.
Recommendation
Remove the form gate from the homepage hero product video. The hero video should play immediately — its purpose is to show what the product does and create desire, not to capture leads. Lead capture should happen at higher-intent touchpoints: the demo request flow, the white paper download, the webinar registration. A gated homepage video is a conversion antipattern: it introduces friction at the exact moment when a prospect is most curious (after clicking a CTA from the hero) and most likely to bounce if friction is encountered. If analytics are needed, use HubSpot video tracking (Vidyard, Wistia) that records views without requiring form completion.
Performance
Video Requires Form Fill to Watch — 'Please Fill Out Your Details to Watch Videos' Blocks Hero Video
Score
38
Severity
Medium
Finding
The homepage hero section contains a 'Watch Product Videos' CTA. When clicked, it displays a gate: 'Please Fill Out Your Details to Watch Videos' — a lead capture form that must be completed before any product video plays. Gating a homepage hero product video behind a lead capture form is a significant conversion friction pattern: a visitor who clicks 'Watch Product Videos' from the hero expecting to see a 30-second product overview is instead presented with a form requesting their name, email, and company. For a product whose technical complexity (Enterprise Architecture) benefits enormously from visual demonstration, blocking the hero video behind a gate removes the primary tool for converting a curious prospect into an informed one. The 'Request Demo' CTA already handles lead capture for demo-intent visitors.
Recommendation
Remove the form gate from the homepage hero product video. The hero video should play immediately — its purpose is to show what the product does and create desire, not to capture leads. Lead capture should happen at higher-intent touchpoints: the demo request flow, the white paper download, the webinar registration. A gated homepage video is a conversion antipattern: it introduces friction at the exact moment when a prospect is most curious (after clicking a CTA from the hero) and most likely to bounce if friction is encountered. If analytics are needed, use HubSpot video tracking (Vidyard, Wistia) that records views without requiring form completion.
Social Proof
Gartner Magic Quadrant 5x Leader (2025) — Badge Visible but No Customer Count or ARR Signal on Homepage
Score
44
Severity
Medium
Finding
The homepage prominently displays the Gartner Magic Quadrant 2025 Leader badge (5th consecutive year) — this is a genuine and powerful enterprise procurement signal. However, the homepage contains no customer count, no ARR figure, and no 'X enterprises trust Ardoq' scale metric. Third-party sources cite ~$35.5M ARR (2024), 284 employees (Feb 2026), and customers including ExxonMobil, MUFG, Stanley Black & Decker, Riot Games, Asda, Stihl, and the US FCC. The customer logos in the hero carousel are strong (ExxonMobil, MUFG, Stanley Black & Decker are Fortune 500 names), but no aggregate scale figure grounds the breadth of deployment. For an enterprise EA platform competing against SAP LeanIX (which serves 1,000+ enterprises) and iServer, deployment scale is a procurement criterion.
Recommendation
Add a scale stat to the homepage: '500+ enterprises trust Ardoq for data-driven EA' (or the accurate current count). If the exact customer count cannot be disclosed, use a qualifier: 'Trusted by leading enterprises across 40+ countries.' The customer logos in the hero carousel (ExxonMobil, MUFG, Stanley Black & Decker, Riot Games) are excellent — add an aggregate claim to contextualise their presence: 'Join 500+ enterprise architects and CIOs who rely on Ardoq for complete visibility into their IT landscape.'
Social Proof
Gartner Magic Quadrant 5x Leader (2025) — Badge Visible but No Customer Count or ARR Signal on Homepage
Score
44
Severity
Medium
Finding
The homepage prominently displays the Gartner Magic Quadrant 2025 Leader badge (5th consecutive year) — this is a genuine and powerful enterprise procurement signal. However, the homepage contains no customer count, no ARR figure, and no 'X enterprises trust Ardoq' scale metric. Third-party sources cite ~$35.5M ARR (2024), 284 employees (Feb 2026), and customers including ExxonMobil, MUFG, Stanley Black & Decker, Riot Games, Asda, Stihl, and the US FCC. The customer logos in the hero carousel are strong (ExxonMobil, MUFG, Stanley Black & Decker are Fortune 500 names), but no aggregate scale figure grounds the breadth of deployment. For an enterprise EA platform competing against SAP LeanIX (which serves 1,000+ enterprises) and iServer, deployment scale is a procurement criterion.
Recommendation
Add a scale stat to the homepage: '500+ enterprises trust Ardoq for data-driven EA' (or the accurate current count). If the exact customer count cannot be disclosed, use a qualifier: 'Trusted by leading enterprises across 40+ countries.' The customer logos in the hero carousel (ExxonMobil, MUFG, Stanley Black & Decker, Riot Games) are excellent — add an aggregate claim to contextualise their presence: 'Join 500+ enterprise architects and CIOs who rely on Ardoq for complete visibility into their IT landscape.'
Social Proof
Gartner Magic Quadrant 5x Leader (2025) — Badge Visible but No Customer Count or ARR Signal on Homepage
Score
44
Severity
Medium
Finding
The homepage prominently displays the Gartner Magic Quadrant 2025 Leader badge (5th consecutive year) — this is a genuine and powerful enterprise procurement signal. However, the homepage contains no customer count, no ARR figure, and no 'X enterprises trust Ardoq' scale metric. Third-party sources cite ~$35.5M ARR (2024), 284 employees (Feb 2026), and customers including ExxonMobil, MUFG, Stanley Black & Decker, Riot Games, Asda, Stihl, and the US FCC. The customer logos in the hero carousel are strong (ExxonMobil, MUFG, Stanley Black & Decker are Fortune 500 names), but no aggregate scale figure grounds the breadth of deployment. For an enterprise EA platform competing against SAP LeanIX (which serves 1,000+ enterprises) and iServer, deployment scale is a procurement criterion.
Recommendation
Add a scale stat to the homepage: '500+ enterprises trust Ardoq for data-driven EA' (or the accurate current count). If the exact customer count cannot be disclosed, use a qualifier: 'Trusted by leading enterprises across 40+ countries.' The customer logos in the hero carousel (ExxonMobil, MUFG, Stanley Black & Decker, Riot Games) are excellent — add an aggregate claim to contextualise their presence: 'Join 500+ enterprise architects and CIOs who rely on Ardoq for complete visibility into their IT landscape.'
Navigation
Footer 'PRODUCT' and 'COMPANY' Nav Use 'javascript:;' — Non-Functional Top-Level Links
Score
46
Severity
Medium
Finding
The footer navigation labels 'PRODUCT' and 'COMPANY' both use 'javascript:;' as their href values — they are non-functional top-level labels rather than linked destinations. This is the same pattern flagged in the emnify.com audit (Issue 5) — top-level nav items that cannot be navigated to directly, right-clicked to open in a new tab, or crawled by search engines as meaningful page destinations. The 'BEST PRACTICE GUIDES' and 'RESOURCES' footer sections correctly link to real destination URLs (/solutions and /resources). The inconsistency between two clickable footer section headers and two non-clickable ones creates a confusing UX pattern.
Recommendation
Replace the 'javascript:;' href values on the PRODUCT and COMPANY footer headers with meaningful destination URLs: PRODUCT → /platform-overview or /plans, COMPANY → /about-ardoq. This gives crawlers a clear signal about the site's navigation architecture and allows visitors who right-click or hover to see where they're going. If these sections are intentionally non-linking (pure labels), remove the anchor tag entirely and use a non-clickable heading element (<h3> or <p>) instead — a heading that looks clickable but isn't is a UX failure.
Navigation
Footer 'PRODUCT' and 'COMPANY' Nav Use 'javascript:;' — Non-Functional Top-Level Links
Score
46
Severity
Medium
Finding
The footer navigation labels 'PRODUCT' and 'COMPANY' both use 'javascript:;' as their href values — they are non-functional top-level labels rather than linked destinations. This is the same pattern flagged in the emnify.com audit (Issue 5) — top-level nav items that cannot be navigated to directly, right-clicked to open in a new tab, or crawled by search engines as meaningful page destinations. The 'BEST PRACTICE GUIDES' and 'RESOURCES' footer sections correctly link to real destination URLs (/solutions and /resources). The inconsistency between two clickable footer section headers and two non-clickable ones creates a confusing UX pattern.
Recommendation
Replace the 'javascript:;' href values on the PRODUCT and COMPANY footer headers with meaningful destination URLs: PRODUCT → /platform-overview or /plans, COMPANY → /about-ardoq. This gives crawlers a clear signal about the site's navigation architecture and allows visitors who right-click or hover to see where they're going. If these sections are intentionally non-linking (pure labels), remove the anchor tag entirely and use a non-clickable heading element (<h3> or <p>) instead — a heading that looks clickable but isn't is a UX failure.
Navigation
Footer 'PRODUCT' and 'COMPANY' Nav Use 'javascript:;' — Non-Functional Top-Level Links
Score
46
Severity
Medium
Finding
The footer navigation labels 'PRODUCT' and 'COMPANY' both use 'javascript:;' as their href values — they are non-functional top-level labels rather than linked destinations. This is the same pattern flagged in the emnify.com audit (Issue 5) — top-level nav items that cannot be navigated to directly, right-clicked to open in a new tab, or crawled by search engines as meaningful page destinations. The 'BEST PRACTICE GUIDES' and 'RESOURCES' footer sections correctly link to real destination URLs (/solutions and /resources). The inconsistency between two clickable footer section headers and two non-clickable ones creates a confusing UX pattern.
Recommendation
Replace the 'javascript:;' href values on the PRODUCT and COMPANY footer headers with meaningful destination URLs: PRODUCT → /platform-overview or /plans, COMPANY → /about-ardoq. This gives crawlers a clear signal about the site's navigation architecture and allows visitors who right-click or hover to see where they're going. If these sections are intentionally non-linking (pure labels), remove the anchor tag entirely and use a non-clickable heading element (<h3> or <p>) instead — a heading that looks clickable but isn't is a UX failure.
Brand
Celonis Joint Solution (September 2024) and Lucid Software Integration (June 2025) — Not on Homepage
Score
48
Severity
Medium
Finding
Tracxn confirms two significant partnership announcements in 2024–2025: the Celonis + Ardoq joint solution for business transformation (September 2024) and the Ardoq + Lucid Software integration (June 2025). Both are category-expanding integrations: Celonis is the market leader in process mining, and Lucid is the leading visual collaboration platform. The Celonis integration specifically creates an 'unparalleled visibility and control' joint capability for CIOs — directly addressing Ardoq's CIO audience. Neither integration appears on the homepage despite being announced in the last 12 months. The homepage Integrations & APIs nav item points to /integrations but the hero and body content do not reference either strategic partnership.
Recommendation
Add a 'Powerful integrations' or 'Works with your existing tools' section to the homepage highlighting the Celonis and Lucid Software partnerships as headline integrations — these are not commodity connectors, they are strategic alliances with category leaders. The Celonis angle ('process mining + enterprise architecture for CIO-level visibility') is particularly compelling for the CIO persona Ardoq explicitly targets. A section showing: 'Ardoq + Celonis for end-to-end transformation visibility' and 'Ardoq + Lucid for architecture that comes to life' adds conversion value for buyers who are already using either platform.
Brand
Celonis Joint Solution (September 2024) and Lucid Software Integration (June 2025) — Not on Homepage
Score
48
Severity
Medium
Finding
Tracxn confirms two significant partnership announcements in 2024–2025: the Celonis + Ardoq joint solution for business transformation (September 2024) and the Ardoq + Lucid Software integration (June 2025). Both are category-expanding integrations: Celonis is the market leader in process mining, and Lucid is the leading visual collaboration platform. The Celonis integration specifically creates an 'unparalleled visibility and control' joint capability for CIOs — directly addressing Ardoq's CIO audience. Neither integration appears on the homepage despite being announced in the last 12 months. The homepage Integrations & APIs nav item points to /integrations but the hero and body content do not reference either strategic partnership.
Recommendation
Add a 'Powerful integrations' or 'Works with your existing tools' section to the homepage highlighting the Celonis and Lucid Software partnerships as headline integrations — these are not commodity connectors, they are strategic alliances with category leaders. The Celonis angle ('process mining + enterprise architecture for CIO-level visibility') is particularly compelling for the CIO persona Ardoq explicitly targets. A section showing: 'Ardoq + Celonis for end-to-end transformation visibility' and 'Ardoq + Lucid for architecture that comes to life' adds conversion value for buyers who are already using either platform.
Brand
Celonis Joint Solution (September 2024) and Lucid Software Integration (June 2025) — Not on Homepage
Score
48
Severity
Medium
Finding
Tracxn confirms two significant partnership announcements in 2024–2025: the Celonis + Ardoq joint solution for business transformation (September 2024) and the Ardoq + Lucid Software integration (June 2025). Both are category-expanding integrations: Celonis is the market leader in process mining, and Lucid is the leading visual collaboration platform. The Celonis integration specifically creates an 'unparalleled visibility and control' joint capability for CIOs — directly addressing Ardoq's CIO audience. Neither integration appears on the homepage despite being announced in the last 12 months. The homepage Integrations & APIs nav item points to /integrations but the hero and body content do not reference either strategic partnership.
Recommendation
Add a 'Powerful integrations' or 'Works with your existing tools' section to the homepage highlighting the Celonis and Lucid Software partnerships as headline integrations — these are not commodity connectors, they are strategic alliances with category leaders. The Celonis angle ('process mining + enterprise architecture for CIO-level visibility') is particularly compelling for the CIO persona Ardoq explicitly targets. A section showing: 'Ardoq + Celonis for end-to-end transformation visibility' and 'Ardoq + Lucid for architecture that comes to life' adds conversion value for buyers who are already using either platform.
Copy
Security Section Copy: 'Review Ardoq's comprehensive approach to information security for the Ardoq Cloud platform..' — Double Period
Score
44
Severity
Low
Finding
The Platform nav mega-menu Security & Governance item reads: 'Review Ardoq's comprehensive approach to information security for the Ardoq Cloud platform..' — with a double period at the end ('platform..'). This is a minor typographic error in the navigation dropdown. It is visible on every page of the site to any visitor who opens the Platform menu. While low-severity on its own, it is notable because: (1) it appears in the security-related navigation item — the one context where attention to detail is most critically signalled; (2) it has been present long enough to be indexed by search engines in the nav structure.
Recommendation
Remove the duplicate period from the Security & Governance nav description. Change 'Ardoq Cloud platform..' to 'Ardoq Cloud platform.' This is a one-character fix in the HubSpot navigation module. While trivial, a typo in the security navigation item of a platform competing for enterprise IT governance contracts is the kind of detail that technically-oriented security architecture buyers notice. Fix alongside any other copy cleanup pass on the nav.
Copy
Security Section Copy: 'Review Ardoq's comprehensive approach to information security for the Ardoq Cloud platform..' — Double Period
Score
44
Severity
Low
Finding
The Platform nav mega-menu Security & Governance item reads: 'Review Ardoq's comprehensive approach to information security for the Ardoq Cloud platform..' — with a double period at the end ('platform..'). This is a minor typographic error in the navigation dropdown. It is visible on every page of the site to any visitor who opens the Platform menu. While low-severity on its own, it is notable because: (1) it appears in the security-related navigation item — the one context where attention to detail is most critically signalled; (2) it has been present long enough to be indexed by search engines in the nav structure.
Recommendation
Remove the duplicate period from the Security & Governance nav description. Change 'Ardoq Cloud platform..' to 'Ardoq Cloud platform.' This is a one-character fix in the HubSpot navigation module. While trivial, a typo in the security navigation item of a platform competing for enterprise IT governance contracts is the kind of detail that technically-oriented security architecture buyers notice. Fix alongside any other copy cleanup pass on the nav.
Copy
Security Section Copy: 'Review Ardoq's comprehensive approach to information security for the Ardoq Cloud platform..' — Double Period
Score
44
Severity
Low
Finding
The Platform nav mega-menu Security & Governance item reads: 'Review Ardoq's comprehensive approach to information security for the Ardoq Cloud platform..' — with a double period at the end ('platform..'). This is a minor typographic error in the navigation dropdown. It is visible on every page of the site to any visitor who opens the Platform menu. While low-severity on its own, it is notable because: (1) it appears in the security-related navigation item — the one context where attention to detail is most critically signalled; (2) it has been present long enough to be indexed by search engines in the nav structure.
Recommendation
Remove the duplicate period from the Security & Governance nav description. Change 'Ardoq Cloud platform..' to 'Ardoq Cloud platform.' This is a one-character fix in the HubSpot navigation module. While trivial, a typo in the security navigation item of a platform competing for enterprise IT governance contracts is the kind of detail that technically-oriented security architecture buyers notice. Fix alongside any other copy cleanup pass on the nav.
SEO
ShiftX Acquisition (Process Modeling Feature) — Not Mentioned in Homepage or Navigation Context
Score
50
Severity
Low
Finding
PitchBook records 'Ardoq's most recent deal was a Merger/Acquisition with ShiftX.' The homepage navigation includes 'Process Modeling — AI-driven process modeling and real-time collaboration to align IT and business in one platform' linking to /features/shiftx — confirming ShiftX technology was absorbed into Ardoq as a feature. However, the ShiftX acquisition is not mentioned in any homepage section, and the /features/shiftx URL still surfaces the ShiftX brand name in the path. For CIOs and enterprise architects evaluating Ardoq's roadmap, an acquisition that added process modeling capability (a historically separate market from EA) is a significant product expansion story. It broadens Ardoq's TAM from EA tools into business process management — a decision-relevant fact for buyers.
Recommendation
Add the ShiftX process modeling capability to the homepage as a distinct feature highlight: 'Now includes process modeling — AI-driven workflow design integrated directly with your architecture data.' If ShiftX has been fully absorbed with no separate brand, update the URL from /features/shiftx to /features/process-modeling or /features/workflow and set a 301 redirect. The acquisition story can be mentioned in the 'What's New' section or a dedicated changelog entry that explains how process modeling became part of the Ardoq platform.
SEO
ShiftX Acquisition (Process Modeling Feature) — Not Mentioned in Homepage or Navigation Context
Score
50
Severity
Low
Finding
PitchBook records 'Ardoq's most recent deal was a Merger/Acquisition with ShiftX.' The homepage navigation includes 'Process Modeling — AI-driven process modeling and real-time collaboration to align IT and business in one platform' linking to /features/shiftx — confirming ShiftX technology was absorbed into Ardoq as a feature. However, the ShiftX acquisition is not mentioned in any homepage section, and the /features/shiftx URL still surfaces the ShiftX brand name in the path. For CIOs and enterprise architects evaluating Ardoq's roadmap, an acquisition that added process modeling capability (a historically separate market from EA) is a significant product expansion story. It broadens Ardoq's TAM from EA tools into business process management — a decision-relevant fact for buyers.
Recommendation
Add the ShiftX process modeling capability to the homepage as a distinct feature highlight: 'Now includes process modeling — AI-driven workflow design integrated directly with your architecture data.' If ShiftX has been fully absorbed with no separate brand, update the URL from /features/shiftx to /features/process-modeling or /features/workflow and set a 301 redirect. The acquisition story can be mentioned in the 'What's New' section or a dedicated changelog entry that explains how process modeling became part of the Ardoq platform.
SEO
ShiftX Acquisition (Process Modeling Feature) — Not Mentioned in Homepage or Navigation Context
Score
50
Severity
Low
Finding
PitchBook records 'Ardoq's most recent deal was a Merger/Acquisition with ShiftX.' The homepage navigation includes 'Process Modeling — AI-driven process modeling and real-time collaboration to align IT and business in one platform' linking to /features/shiftx — confirming ShiftX technology was absorbed into Ardoq as a feature. However, the ShiftX acquisition is not mentioned in any homepage section, and the /features/shiftx URL still surfaces the ShiftX brand name in the path. For CIOs and enterprise architects evaluating Ardoq's roadmap, an acquisition that added process modeling capability (a historically separate market from EA) is a significant product expansion story. It broadens Ardoq's TAM from EA tools into business process management — a decision-relevant fact for buyers.
Recommendation
Add the ShiftX process modeling capability to the homepage as a distinct feature highlight: 'Now includes process modeling — AI-driven workflow design integrated directly with your architecture data.' If ShiftX has been fully absorbed with no separate brand, update the URL from /features/shiftx to /features/process-modeling or /features/workflow and set a 301 redirect. The acquisition story can be mentioned in the 'What's New' section or a dedicated changelog entry that explains how process modeling became part of the Ardoq platform.