On-page SEO
Whether important pages are crawlable, indexable, internally linked, and written around a clear buyer/search intent.
- •Titles and meta descriptions
- •H1/H2 structure
- •Canonical URLs
- •Internal links
- •Indexable page depth
Audit Methodology
Our website audits score the signals that determine whether a site can be found, understood, cited, trusted, and converted — by humans, search engines, and answer engines.
Seven-area scorecard
Each dimension is scored from live evidence. We do not treat one technical file, one schema block, or one AI-search trick as a replacement for a useful, crawlable, internally linked website.
Whether important pages are crawlable, indexable, internally linked, and written around a clear buyer/search intent.
Whether the site gives answer engines direct, citeable, plain-language answers and whether the brand is actually surfaced and cited in observed AI/search samples.
Whether search systems can understand who the business is, where it truthfully operates, who it serves, and whether independent profiles, citations, reviews, and discovery results corroborate those claims.
Whether the site proves expertise with substantive, non-commodity evidence: methods, implementation detail, original observations, limitations, and dated source-backed analysis.
Whether bots, users, and emerging browser agents can fetch, render, understand, and navigate the site without avoidable friction.
Whether forms, navigation, contrast, labels, tap targets, reflow, and content structure meet practical WCAG 2.2 expectations; automation is kept separate from manual and assistive-technology evidence.
A weighted judgment of how findable, understandable, trustworthy, and conversion-ready the site is today.
Evidence discipline
We fetch the public site, robots.txt, sitemap files, representative pages, rendered screenshots, schema blocks, metadata, and crawl status evidence from the current live web.
Before scoring, we record the model ID and hash, current tool versions, crawl timestamp, and evidence availability. A higher target never changes the scoring rules mid-run.
Each category is scored from fresh evidence. Missing Search Console, review, citation, field-performance, direct-AI, manual-accessibility, or assistive-technology data stays unavailable instead of receiving assumed credit.
We separate fast in-control fixes from deeper content, design, platform, and authority work so teams know what can move first.
For implemented changes, we build or serve the site, check critical URLs, parse schema, verify robots/llms/sitemap bodies, and capture visual evidence.
AI-search standard
Crawlable pages, useful visible answers, internal links, accurate structured data, entity proof, local signals, performance, and accessibility still do the heavy lifting.
Direct citations, Search Console generative-AI reporting, local discovery, reviews, profiles, and independent mentions are scored as outcomes. Technical readiness alone does not receive those points.
We add curated resource indexes like llms.txt, but treat them as optional supporting context—not a Google ranking lever or substitute for real pages.
We run Chrome Lighthouse Agentic Browsing for semantic markup, labels, focus, and agent-ready interactions. Because Chrome marks the category informational and unbenchmarked, it remains a QA gate rather than an invented score weight.
Common questions
No. Google Search Central states there is no special AI-only schema or machine-readable file required for AI Overviews or AI Mode. We still use accurate Schema.org markup where it matches visible content because it helps search systems understand the page.
LeadByAI treats llms.txt as a curated resource index for inference-time assistants. It supports discovery and context, but it does not replace crawlable pages, internal links, robots.txt, sitemaps, canonical tags, or visible source text.
We combine direct citation samples, standard search discovery, and—when the client can provide it—Google Search Console generative-AI performance reporting. We keep observed outcomes separate from owned-site readiness so technical preparation cannot be mislabeled as market visibility.
Not yet. Chrome describes the category as experimental and informational. We run it as a hard QA gate for semantic and agent-ready regressions, but we do not invent an official weight until a benchmarked industry standard exists.
No. The ADA/accessibility score flags practical user-friction and risk signals. It is not legal advice and is not a formal WCAG or ADA certification.