Technical foundation
Whether AI can fetch and render the page cleanly. 8 checks: DOM size, render-blocking resources, above-the-fold lazy loading, inline JS weight, image dimensions, viewport, canonical, horizontal scroll on mobile.
Common deductions
- Images without width and height, so the box collapses before load and the layout shifts
- Several synchronous scripts in head, pushing the first paint back
- The hero image marked loading="lazy", which slows LCP directly
How to fix
- Add width and height to every img — CSS still controls the displayed size
- Add defer or async to scripts; add fetchpriority="high" to the hero image
- Keep DOM nodes under 2,000; going over usually means components nested too deep
Structured data
Whether machines can read who you are and what this page is. 8 checks: JSON-LD present, parses, required fields, Organization completeness, sameAs, entity naming, page-type match, breadcrumbs.
Common deductions
- Only Organization declared, with WebSite and WebPage missing
- Organization has no sameAs, so AI cannot align the brand with outside sources
- schema says WalkGEO while the title says something else
How to fix
- Complete the Organization + WebSite + WebPage trio
- Point sameAs at real profiles: social pages, encyclopedia entries, GitHub repos (source: the schema.org sameAs definition)
- For bilingual brands, declare the alias in alternateName so the two names stop fighting
Content trust
Whether the content reads like it came from a credible source. 16 checks: value proposition, target audience, lead concision, readability, methodology, author info and byline, authoritative citations, editorial policy, number density, customers and testimonials, updated date, contact, legal links, claim attribution.
Common deductions
- Not a single concrete number on the page — only adjectives
- No byline, so AI cannot tell who is making the claim
- Borrowed conclusions with no source given
How to fix
- Give every claim a source: institution + year + number
- Add an author card on articles: name, role, relevant background
- Put privacy policy, terms and a clickable contact in the footer
AI accessibility
Whether what AI reads is the same thing you see. 10 checks: H1 present and unique, indexable, body text in HTML, semantic landmarks, html lang, heading order, image alt, text-to-markup ratio, footer not script-injected.
Common deductions
- Body copy rendered by JS, so the crawled HTML is empty
- Two H1s on one page, or none at all
- Heading levels jumping from h2 straight to h4
How to fix
- Server-render or prerender the key body copy instead of waiting on JS
- One H1 per page; organise the rest with h2 and h3
- Step heading levels down one at a time
Citation readiness
Whether a passage can be lifted whole. 14 checks: self-containment, answer-block length, numbers, named entities, definition sentence, question-style headings, answer immediacy, numbered structure, lists and tables, originality signal, filler intro, block count, heading length, FAQ structure.
Common deductions
- Paragraphs opening with "it", "this" or "therefore" — meaningless once extracted
- Headings like "Our advantages" instead of the question a user would ask
- Three paragraphs of setup before the answer, so AI skips past
How to fix
- Give the first sentence a full subject: change "it lifts conversions 37%" to "WalkGEO monitoring lifts conversions 37%"
- Rewrite headings as the question users actually ask, e.g. "How is GEO different from SEO?"
- Put the answer in the first paragraph under the heading; move setup below
Brand authority
Whether AI can confirm you are a real entity. 8 checks: naming consistency, logo, social footprint, about page, contact entry, Wikipedia/Wikidata, GitHub ecosystem, external authority sources.
Common deductions
- No about page, so nobody knows who you are or where the team sits
- No third-party page mentions you anywhere
- The brand name is spelled differently in different places
How to fix
- Build an about page: what the company does, who is on the team, where it is registered, how to reach it
- Fill sameAs with every external link that proves identity
- Earn third-party mentions: trade press, open-source repos, review sites