Where exeideas.com scores best
Their strongest categories — these are where the site shows real audit discipline.
- SSL Certificatesecurity
- Meta Titleonpage
- XML Sitemaptechnical
- Viewport Meta Tagtechnical
- Open Graph Tagssocial
- Robots.txttechnical
What exeideas.com should fix first
Their lowest-scoring categories — biggest leverage for an improvement sprint.
Which specific checks failed?
Priority-1 and priority-2 failures — these are the checks that most affect SEO + AEO outcomes.
- H1 Headingonpage · priority 1
The H1 heading is missing. Google + Bing + Yandex use H1 as a secondary ranking signal (after <title>) to confirm page topic. ChatGPT / Claude / Perplexity also lean on H1 when extracting page summaries for citation — a missing H1 forces them to infer the topic from <title> and body text, often less accurately. Accessibility screen readers also rely on H1 for page-level navigation.
- Exposed Pathssecurity · priority 1
Publicly-readable sensitive paths detected: /sitemap.xml.bak. These should not be accessible without auth — they often leak source code, credentials, or backups.
- Time to First Byte (TTFB)performance · priority 1
Time to First Byte is 2969 ms (2.97 sec) — Google flags this as "poor" (> 1.8 s per web.dev/articles/ttfb). The browser cannot begin rendering until the first byte arrives, so LCP cannot beat 2.97s. Every downstream Core Web Vital (LCP, INP, CLS) inherits this delay, and Page Experience signals trigger a soft demotion in Google + Bing rankings.
- HTML <head> completenessonpage · priority 1
2 essential head element(s) missing: Character encoding, Canonical URL. 7 recommended head element(s) missing: Open Graph title, Open Graph description, Open Graph image, ....
- Image Lazy Loadingperformance · priority 2
None of the 44 images on the page use lazy loading (loading="lazy"). All images are loaded simultaneously when the page opens, significantly slowing down initial load and consuming user bandwidth.
- Canonical Tagtechnical · priority 2
The canonical tag is missing. Without <link rel="canonical">, Google + Bing + Yandex may index multiple URL variants of the same content (with/without trailing slash, with tracking parameters like ?utm_source=, http vs https) and split link equity across the duplicates. AI search engines (ChatGPT / Claude / Perplexity) may also cite the wrong URL variant, fragmenting the citation graph for your content.
- HTTP Requests Countperformance · priority 2
The page loads 97 external resources — this is too many (2 CSS, 5 JS, 88 images). A high number of HTTP requests critically slows down page loading, as browsers are limited to 6 simultaneous connections per domain. This negatively affects all performance metrics.
- Knowledge Panel Readinessai-readiness · priority 2
Low knowledge-panel readiness — score 25/100. AI search engines and Google Knowledge Panel cannot confidently identify this brand. The cheapest, fastest fixes are: (1) add Organization JSON-LD with a sameAs chain (Wikipedia, Wikidata, LinkedIn, Crunchbase, GitHub, social), (2) make NAP (Name/Address/Phone) visible in the footer or contact page, (3) create a Wikidata entry (low notability bar), then (4) pursue Wikipedia once notability is established.
What does a 71/100 score actually mean?
A score in the 60-80 range is solidly average. AI engines may cite exeideas.com but inconsistently — the structural gaps (especially around schema, direct-answer format, and AI-bot accessibility) cost citation share.
Their AEO-specific (AI search readiness) score is 48/100. AEO lags overall — typical pattern. Sites optimize for Google SEO first, then realize AI search has different signals.
Recent SeoChatAI videos
How does YOUR site compare?
Free audit. Same 99 checks. 30 seconds. No signup. Beat their score? Embed our badge and prove it.