Myth: llms.txt improves Google AI Overviews
Google stance: no stated ranking impact.
Do instead: CRM Insights already has llms.txt — keep Googlebot access strong; treat llms.txt as optional Lens B only.
SEO & GEO Audit
CRM Insights — audit deliverable for Google AI, ChatGPT, Perplexity, and Claude (refreshed August 2026)
This August 2026 refresh covers 100 URLs from sitemap-index.xml → sitemap-0.xml on the canonical host crminsights.co.uk. The relaunched site is in strong technical shape: meta descriptions and social images are in place, Organization + ProfessionalService + WebSite + FAQPage schema ship on the homepage (with LinkedIn sameAs), llms.txt is live, and all nine major AI crawlers are allowed. The one remaining site-level critical for Google AI visibility and crawl consistency is the www TLS / redirect failure (CN=*.cloudns.net SAN mismatch). For ChatGPT, Perplexity, and Claude, the opportunity is extractability — only ~21% of audited pages show citations, hubs still lack visible freshness, and About / Start / AI readiness need stronger statistics with context — while keeping people-first, non-commodity CRM POV for Google.
Scope: 100 URLs from sitemap-index.xml / sitemap-0.xml (cap 100; includes services, case studies, Start/Improve/Optimise hubs, resources, careers).
Site-level: robots.txt and sitemap OK; Organization + WebSite + ProfessionalService + FAQPage present on homepage; llms.txt present; all 9 major AI crawlers allowed.
Critical: Fix www TLS / redirect to apex (*.cloudns.net cert on www).
Different AI surfaces discover and cite content in different ways. Recommendations are tagged where the best action differs by platform.
Homepage (crminsights.co.uk) and site-wide checks.
Fastest remaining impact after the relaunch — host consistency first, then Lens B extractability on hubs.
*.cloudns.net cert (or redirect www → https://crminsights.co.uk before TLS fails). Critical for shared links and crawlers.Fix www.crminsights.co.uk TLS / redirect — www still presents CN=*.cloudns.net; browsers reject the host. Align DNS + cert + 301 so one canonical host wins.
Protect non-commodity CRM POV — Prefer original workshop / case-study evidence over generic “top CRM tips” listicles when expanding content. No commodity title patterns detected in this crawl.
Keep meta and social tags healthy — Technical meta is largely complete after relaunch; spot-check new pages against the 150–160 character band.
Citations and statistics on hubs — Priority: homepage, About, Services, AI CRM readiness, Start/Improve/Optimise. About and Start still lack stats; most hubs lack citations (~21% site-wide).
Freshness signals — ~76% of crawled pages have some freshness signal, but key hubs (homepage, About, Improve, Optimise, Start) still do not. Add dateModified or visible “Last updated” (llms.txt already maps key URLs).
Entity schema already live — Organization + ProfessionalService with LinkedIn sameAs are present; keep them aligned with NAP and directory listings rather than re-adding schema.
Booking / forms agent-friendliness — Confirm book-an-appointment and contact flows remain crawlable with clear labels (not blocked behind opaque widgets).
Third-party corroboration — Keep award / partner / Workbooks mentions consistent with LinkedIn and directory listings.
Skip Google GEO myths — llms.txt is already present and is neutral for Google AI Overviews; do not chase AI-tone rewrites or fan-out query spam.
Google-scoped myths. Some tactics remain useful for broader AI citation when framed correctly.
Google stance: no stated ranking impact.
Do instead: CRM Insights already has llms.txt — keep Googlebot access strong; treat llms.txt as optional Lens B only.
Google stance: no special chunking requirement.
Do instead: structure CRM guides with clear headings and direct answers for buyers and operators.
Google stance: people-first content wins.
Do instead: keep original consultancy expertise, workshops, and case-study evidence.
Google stance: thin scaled content is risky.
Do instead: deepen Start / Improve / Optimise hubs and case studies rather than spawning near-duplicate FAQ pages.
Google stance: inauthentic signals are risky.
Do instead: authentic awards, Workbooks partnership proof, and LinkedIn entity consistency.
Traditional SEO and Google generative search (AI Overviews, AI Mode) share the same foundation: indexed, crawlable pages and helpful, reliable, people-first content. Google retrieves supporting links from its Search index using ranking systems — for Google, strong SEO is generative search optimisation. ChatGPT, Perplexity, Claude, and Copilot use different retrieval paths (training data, live browse, proprietary indexes), so this audit also covers multi-platform citation: AI crawler access, extractable content (citations, statistics, expert quotes, clear answer blocks), schema for entity clarity, freshness, and authentic authority signals. Where Google and other platforms disagree — for example llms.txt — recommendations are tagged so you know what helps where.
Rich results + multi-platform entity resolution — not required for Google AI Overviews. Organization is already live on the homepage (below is the current block for reference / future edits). Keep ProfessionalService and FAQPage aligned with visible content.
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "CRM Insights",
"url": "https://crminsights.co.uk/",
"logo": "https://crminsights.co.uk/assets/crm-insights-logo.png",
"email": "[email protected]",
"telephone": "01733 902 340",
"areaServed": "United Kingdom",
"description": "Independent UK CRM consultants helping leadership teams connect CRM, sales, marketing and operations data so better decisions become easier.",
"sameAs": [
"https://www.linkedin.com/company/crm-insights-ltd/"
]
}
Re-check after the www host fix, or whenever schema/NAP details change.