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 July 2026)
This refresh covers 100 URLs from sitemap-index.xml → sitemap-0.xml on the canonical host crminsights.co.uk (you asked for www.crminsights.co.uk; that host still fails because the TLS certificate is apex-only). Since the March 2026 audit, the site has moved to a stronger technical foundation: meta descriptions and social images are largely in place, single H1s are consistent, ProfessionalService + WebSite + FAQPage schema appear on key templates, llms.txt is live, and all nine major AI crawlers are allowed. Remaining priorities for Google AI visibility: fix the www TLS/redirect issue and keep people-first CRM content snippet-eligible. For ChatGPT, Perplexity, and Claude, the opportunity is extractability — citations, statistics with context, and visible freshness signals on hub and article pages — plus adding an explicit Organization entity (or enriching ProfessionalService with sameAs) so AI systems resolve “CRM Insights” cleanly.
Scope: 100 URLs from sitemap-index.xml / sitemap-0.xml (cap 100; includes services, case studies, Start/Improve/Optimise hubs, resources).
Site-level: robots.txt and sitemap OK; WebSite + ProfessionalService + FAQPage present on homepage; Organization missing; llms.txt present; all 9 major AI crawlers allowed.
Critical: Fix www TLS / redirect to apex; add Organization (or enrich ProfessionalService with sameAs).
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 impact after the site rebuild — host consistency, entity schema, then Lens B extractability on hubs.
Fix www.crminsights.co.uk TLS / redirect — Certificate is issued for the apex only; browsers reject www. Align DNS + cert + 301 so one canonical host wins.
Keep meta descriptions in the 150–160 band — Most pages are fixed since March; patch the few short ones (e.g. refer, one resources page).
Protect non-commodity CRM POV — Prefer original workshop / case-study evidence over generic “top CRM tips” listicles when expanding content.
Organization schema + sameAs — You already ship ProfessionalService and FAQPage; add Organization (or sameAs on ProfessionalService) so “CRM Insights” resolves as one entity.
Citations and statistics on hubs — Priority pages: homepage, About, Services, AI CRM readiness, Start/Improve/Optimise. Add source links and concrete numbers with context.
Freshness signals — dateModified or visible “Last updated” on maintained guides and service pages (llms.txt already maps key URLs).
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. FAQPage is already present on the homepage and several hubs; add Organization (or enrich ProfessionalService with the same fields).
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "CRM Insights",
"url": "https://crminsights.co.uk",
"logo": "https://crminsights.co.uk/wp-content/uploads/2020/03/logo.png",
"description": "UK CRM consultants and Workbooks CRM partners — workshops, migration, onboarding optimisation, and ongoing support.",
"sameAs": [
"https://www.linkedin.com/company/crm-insights-ltd"
],
"contactPoint": {
"@type": "ContactPoint",
"contactType": "sales",
"url": "https://crminsights.co.uk/about-us/contact-us/"
}
}
Use after implementing Organization schema and the www host fix.