Egaki Review: strong foundations, weak readability (71/100)

Fact	Value
Domain	egaki.ai
Category	AI discovery platform for marketing, content, and product teams
Pricing	Unknown; price range not provided
Pages crawled	17
Crawl date	2026-09-28

Egaki presents a clear B2B SaaS position around AI discovery, with a 75/100 score for first impressions and 85/100 for usability. Design execution is strong, with clear hierarchy and strong mobile presentation, but some lighter text treatments are inconsistently applied. Technical SEO also scores 82/100: the crawled pages returned HTTP 200 with valid TLS 1.3 and HSTS headers, and robots.txt declares a sitemap.

The main constraint is content structure. Writing quality scores 32/100 and editorial QA scores 35/100 because pages are rendered as single massive paragraphs, which makes them hard to scan. Messaging scores 65/100: the likely audience is understood from the site, but is not explicitly named, and pricing answers are partial. Performance is mixed rather than uniformly strong: desktop records a 1.5s LCP and 180ms TBT, while mobile reaches 5.2s LCP.

Egaki presents a clear AI-discovery proposition, but the homepage does not name Egaki in its hero. The headline, "Turn AI Discovery Into Growth," is easy to understand, while "The OS for Personalized AI Discovery" introduces a less familiar category without supporting proof of category creation. The audience is implied through references to AI startups, SaaS companies, DTC brands, eCommerce teams, and marketing agencies, but the hero does not identify roles or company sizes. A logo wall for supported LLMs and the claim "Trusted by forward-thinking AI startups" provide context, yet no named customer outcome or specific metric is visible. Add the brand name to the hero and pair the category claim with one named customer result or measurable outcome.

Egaki signals a B2B audience, but its messaging stops short of naming the specific roles and company sizes it serves. AI startups, SaaS companies, DTC brands, eCommerce teams, and marketing agencies appear as broad segments, while the hero remains at L3 specificity. Pricing is also only partially answered: the site presents Starter, Team, and Enterprise tiers, but the homepage shows no price points or trial information. Trust rests on "Trusted by forward-thinking AI startups" and a supported-LLM logo wall, without a named customer testimonial or outcome. The Book A Demo CTA indicates how to begin, but does not explain the demo length or process. Name the primary buyer in the hero, publish a clear pricing signal, and add brief process detail beside the CTA.

Egaki is generally easy to navigate, but a high-value pricing path is unnecessarily long. The homepage Book A Demo CTA leads to contact, and solution pages do not link directly to pricing; users must reach a footer link labeled "AI visibility pricing plans." The documented path can take three clicks from the homepage to the relevant pricing page. The contact form adds seven required fields—first name, last name, business email address, company name, job title, country, and a textarea—for an initial inquiry. These choices do not block completion, but they add friction at moments when prospects are still deciding whether to engage. Put Pricing in the main navigation and solution pages, and require only business email and company name at first contact.

Egaki’s visual system is strong: the sampled experience has clear hierarchy, no horizontal scroll, no tap-target failures, and WCAG AA contrast checks pass. The light blue primary color is reported at #5aa1e6 against white, while other text treatments use #9CA3AF and darker translucent values with inconsistent application. Minor spacing and type differences interrupt an otherwise coherent system: pricing cards use 16px between Starter and Growth but 24px between Growth and Pro, and FAQ question titles vary between 14px and 16px. These are refinement issues rather than structural failures. Define shared text-color and spacing tokens, then standardize the pricing-card gaps and FAQ type scale.

Egaki’s desktop homepage is responsive, but mobile loading is the material performance weakness. Desktop records a 1.5s LCP, while mobile reaches 5.2s. The mobile LCP element is the hero image, served at 21.8KB and rendered at 144px wide from a natural 1920×640 image; the image has no explicit dimensions, lazy-loading attribute, preload, or high fetch priority in the evidence. The network log also records 9 blocking homepage requests, including Google Tag Manager and Clarity loaded synchronously. TBT is 180ms in the reported desktop result. Set image dimensions, prioritize the critical image appropriately, and defer non-critical third-party scripts to reduce mobile rendering delay.

Writing quality is constrained by structure: the homepage contains 2,806 words in one paragraph, and every sampled page has paragraph_count: 1. That makes the content difficult to scan before the copy itself is assessed. The voice also relies on abstract SaaS phrasing such as "turn discovery intelligence into action across campaigns, content, positioning and targeting," without statistics, named case studies, or concrete examples in the 17-page sample. The homepage FAQ heading contains the typo "Frequently AskedQuestions." Break pages into H2/H3 sections and short paragraphs under 40 words, replace abstract nouns with concrete actions, and add one specific metric or client example per solution page. Fix the FAQ heading at the same time.

Egaki shows strong baseline stability signals, but two URL defects create avoidable indexability risk. The soft-404 probe returns HTTP 200 with the homepage title instead of 404 or 410. On /solutions/marketing-teams, the fetched non-trailing-slash URL returns 200 and internally resolves to a trailing-slash variant, while the canonical omits the slash. The site does have valid TLS 1.3 through 2027, HSTS with max-age=31536000, permissive robots.txt with a sitemap declaration, and clean single-hop root consolidation. Because Wayback data was unavailable, historical stability cannot be assessed. Return true 404/410 responses and make redirects and canonicals use one consistent slash convention.

Editorial QA is held back by the same structural pattern across the site: every page is one paragraph, so readers and answer engines receive no clear content hierarchy. The copy uses abstract phrases such as "turn discovery intelligence into action" and "prioritized set of actions," while question headings are followed by large blocks instead of concise answers. Navigation also repeats the same anchors: "privacy policy" appears 17 times, "terms of service" 17 times, and "what is geo" 15 times. The visible FAQ heading typo, "Frequently AskedQuestions," undermines the presentation of the FAQ content. Add direct 40–60-word answers after question headings, diversify useful anchor text, correct the heading, and trim the 208-character product-teams meta description below 160 characters.

Egaki’s technical SEO foundation is strong: robots.txt allows crawlers and declares a sitemap, sampled pages return HTTP 200, TLS 1.3 and HSTS are present, and raw-versus-rendered text parity supports reliable server-side rendering. Two defects need priority. The sitelist probe path returns HTTP 200 with the homepage title instead of 404/410, creating a soft-404 risk. Solution pages also resolve to trailing-slash URLs while their canonical tags omit the slash, producing conflicting URL signals. Core Web Vitals and structured-data presence were not assessed because the crawl covered 17 of 40 pages and lacked the required raw HTML/schema artifacts. Configure a true error response for unhandled paths and align redirects, final URLs, and canonicals.

Egaki is a credible foundation for teams evaluating an AI-discovery SaaS product. Clear positioning, usable navigation, strong visual execution, and solid technical SEO give the site a workable base.

The fixes are concrete. Break the single-paragraph pages into scannable sections, replace generic or abstract phrasing with specific evidence, name the intended audience directly, and make pricing easier to reach from key pages. Mobile performance also needs attention: the homepage's 5.2s LCP trails its 1.5s desktop result. Egaki is best suited to marketing, content, and product teams that want a clearly positioned AI-discovery platform and can tolerate an information architecture that still needs editorial refinement.

This 13-dimension review is based on a crawl of 17 pages completed on 2026-09-28, together with the public dimension score table and its one-line findings. The review covers positioning, messaging, usability, design execution, performance, writing quality, risk and stability, editorial QA, and technical SEO where the supplied evidence supports a score.

Accessibility, decision-support surfaces, and review-content integrity were excluded as not applicable. Docs & self-serve help was not assessed in the supplied material. Google Search Console data was not connected, so no Search Console enrichment is included. Pricing remains unknown in the supplied site facts. Read more about how SiteList scores.