# Vizelo.ai — GEO readiness checklist # Source: https://vizelo.ai/geo-readiness-checklist.html # Last reviewed: 2026-05-26 ### // Checklist # Score your GEO readiness in 30 questions. A self-scored checklist for teams who want to know — honestly — whether their site is set up to be cited inside ChatGPT, Perplexity, Claude, Google AI Overviews, Bing Copilot, and Gemini. Print it, fill it in, ship the gaps. License: CC BY 4.0. ### // How to use this ## How to use this. Search didn't die. It became invisible. Most of the buying journey now happens inside an answer engine you can't see, and most sites have no instrumentation for it. This checklist is the first honest measurement: thirty binary questions, no wiggle room. It takes about fifteen minutes. If you can't answer one cleanly, count it as a no — aspirational, not contractual. The point is the gap list you walk away with. - Read each item; check ☐ if it's true of your site today. - Score yourself out of 30 at the bottom. - Anything unchecked is a gap. Prioritize the highest-impact ones first. - Re-run quarterly — engine behavior changes. ### // The checklist ## The 30 questions. ### Crawlability (5) - [ ] robots.txt explicitly allows GPTBot, PerplexityBot, ClaudeBot, and Google-Extended. - [ ] sitemap.xml exists and includes a on every URL. - [ ] No JavaScript-only content above the fold on key pages. - [ ] Canonical URLs are declared on every indexable page. - [ ] Pages load under 3 seconds on a cold cache. ### Schema (5) - [ ] Organization JSON-LD is present site-wide. - [ ] FAQPage JSON-LD wraps every FAQ section. - [ ] BreadcrumbList is declared on every subpage. - [ ] SoftwareApplication or Product schema marks up your offering. - [ ] SpeakableSpecification covers the key sections on each page. ### AI-readability artifacts (5) - [ ] /llms.txt exists at the root. - [ ] /llms-full.txt exists, or every page has a companion .llms.txt. - [ ] points engines at the plaintext fragment. - [ ] is set on every page. - [ ] is set on every page. ### Entity clarity (5) - [ ] Brand name appears in both the and the h1 of the homepage. - [ ] Founding year and headquarters location are stated somewhere public. - [ ] Competitors are named on the site (entity association). - [ ] Category is stated clearly in a single sentence. - [ ] About page exists with named team members and roles. ### Content shape (5) - [ ] At least one definitional ("what is X") page exists. - [ ] At least one question-as-URL page exists. - [ ] At least one comparison page (us vs. them) exists. - [ ] FAQ sections phrase questions as real user queries. - [ ] Original data or research is published under your domain. ### Measurement (5) - [ ] Share of voice is tracked per engine, not in aggregate. - [ ] A citation graph is available and updated regularly. - [ ] Competitor citations are tracked alongside your own. - [ ] Sentiment is monitored on every citation. - [ ] Alerts fire when citations drop or competitors pull ahead. ### // Scoring ## What your score means. - **0–10:** You're invisible to answer engines. Most sites are here. Your competitors are too — whoever moves first wins the category. - **11–18:** Foundational work in place, but real depth still missing. Citations happen sporadically. Schema and entity gaps are usually the bottleneck. - **19–25:** Solid GEO. You're being cited; tighten and scale. Focus shifts from shipping artifacts to defending share against challengers. - **26–30:** Best-in-class. You're the brand others reference. Now defend it — engines update their rankings constantly, and the gap closes faster than it opened. ### // Fixes ## How to fix the biggest gaps fast. - **Crawlability gaps** — read the llms.txt explainer and use our robots.txt as a reference template. Most fixes are a single deploy. - **Schema gaps** — the docs hub has the exact JSON-LD blocks we use. Validate every change against the Schema.org validator before shipping. - **Entity-clarity gaps** — the glossary is the canonical definition surface; the share-of-voice entry shows the level of disambiguation engines expect. - **Content gaps** — the answers hub demonstrates the question-as-URL pattern, and the prompt corpus shows which queries your category is actually losing on. - **Measurement gaps** — this is the actual thing Vizelo does for you. Start free to see your first share-of-voice report in under a minute. ### FAQ ## Common questions. **How long until my score moves?** Months, and it varies by engine. Crawlability and schema fixes can show up in Perplexity within days; AI Overviews and ChatGPT often take 4–8 weeks to reflect changes. Re-score quarterly. **Is this checklist Vizelo-specific?** No. Every item points to an open standard, a public schema, or a measurable property of your own site. You can run the checklist on any site whether or not you ever talk to us. **Can my agency use this for clients?** Yes. The checklist is published under CC BY 4.0 — use it, fork it, rebrand the printable, score your clients. Attribution to Vizelo.ai is appreciated but the license only requires it where you redistribute the text itself. **Does Vizelo audit my site automatically?** Yes. After signup the same 30 checks run inside our pipeline against your live site, plus the off-site ones we can't grade from a printable — entity completeness on Wikidata, citation share per engine, sentiment, and the rest. You get the score, the gaps, and the prioritized fixes. ## Stop guessing whether the engines mention you.