Kaliber Group — Performance Marketing, Augmented by AI

How to Fix AI Readability on Squarespace (2026)

19 May 2026

Why this matters for Squarespace sites

Squarespace is design-first by design. Sites launch fast, look polished, don't need ongoing maintenance. The trade is control — robots.txt editing, theme template access, a plugin ecosystem all don't exist. Squarespace decided the defaults; you live with them.

For AI Readability that cuts both ways. You get a valid sitemap, correct canonicals, Article schema on blog posts, and per-page SEO fields for free. More than most platforms give you. But it caps your ceiling — signals AI engines look for that Squarespace won't let you add without Code Injection, and auto-generated signals you can't enrich.

The fixes are ordered by how much each moves the audit score given Squarespace's constraints.

What Google said in May 2026

Google published an updated AI Search guide on May 7, 2026. The headline: optimising for generative AI search is optimising for the search experience, and thus still SEO.

Three claims worth knowing:

• No special files needed. llms.txt and agents.md give no benefit for Google's AI surfaces. They may still help niche LLM tools that read them, but the broad-adoption case is dead.
• No content chunking needed. Markdown mirrors, sitemap.md, and similar parallel formats are unnecessary. Google's systems handle multi-topic pages natively.
• No special schema needed for AI. Schema still helps traditional rich results and is still consumed by ChatGPT, Claude, and Perplexity. But adding schema because of AI search is no longer the angle.

Google also stopped rendering FAQ rich results the same day. The markup still parses; the SERP feature is gone.

1. Can you allow AI crawlers in robots.txt? (No, and that's the answer)

The honest answer: no. Squarespace auto-generates robots.txt and won't let you edit it on any plan. There's no workaround inside the platform.

The default robots.txt allows all crawlers under a wildcard User-agent: * rule. GPTBot, ClaudeBot, and Google-Extended will respect that wildcard and crawl by default — so functionally your site is reachable. But the audit looks for explicit User-agent lines, which Squarespace won't let you add. You lose those weight points and there's nothing to do about it.

2. Add Organization schema

Organization schema is how AI engines link your domain to your brand. Squarespace doesn't add it automatically. Adding it requires Code Injection, which is Business-plan-and-above only.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Your Business Name",
  "url": "https://yourdomain.com",
  "logo": "https://yourdomain.com/path-to-logo.png",
  "sameAs": [
    "https://instagram.com/your-brand",
    "https://linkedin.com/company/your-brand"
  ],
  "contactPoint": {
    "@type": "ContactPoint",
    "telephone": "+65-6000-0000",
    "contactType": "Customer Service"
  }
}
</script>

If your business has a physical location, swap "@type": "Organization" for "@type": "LocalBusiness" and add an address block. AI engines treat LocalBusiness as a stronger signal for geo-relevant queries.

3. Write meta descriptions that say something

AI engines read meta descriptions to decide whether to surface a page in an answer summary. Squarespace's per-page SEO field is empty by default — and not auto-populated from page content. If you skipped it during page creation, the meta either falls back to the site-wide default or is blank.

A description that passes names at least one of: a specific category, a named differentiator, or a location. "Strategy consulting for SEA family businesses. 60-day engagements" passes (category, audience, geography, differentiator). "Trusted advisors helping you grow your business" fails — nothing concrete to extract.

4. Fix heading hierarchy

AI engines use headings to map the page. The audit flags pages with more than one H1, skipped levels, or fewer than five H2/H3 headings on a substantive page.

The Squarespace bug: most templates render the page title as H1 automatically, then a designer adds another text block set to "Heading 1" inside the content. Two H1s. Some templates also set the site logo to H1 on the homepage only — inconsistent across the site.

The fix

One element set to Heading 1 per page. Body content starts at Heading 2, subsections at Heading 3. Don't skip levels.

5. Add Service or FAQ schema

Squarespace auto-renders Article schema on blog posts, BreadcrumbList on most pages, and basic Product schema on Commerce product pages. Service, FAQPage, and LocalBusiness aren't included — those need page-level Code Injection (same mechanism as Organization schema, scoped to one page).

Example Service schema for a single service page:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Service",
  "name": "Performance Marketing",
  "provider": {
    "@type": "Organization",
    "name": "Your Business Name"
  },
  "areaServed": "Singapore",
  "description": "Senior-led performance marketing for B2B and consumer brands.",
  "serviceType": "Marketing Services"
}
</script>

6. FAQ schema after Google's May 2026 change

Short answer: keep using it on pages that are genuinely Q&A. Stop using it as a SERP-snippet hack on pages that aren't.

The SERP rich result is gone. The markup still parses cleanly. Non-Google LLMs (ChatGPT, Claude, Perplexity) appear to still consume FAQ schema when summarising — Google hasn't confirmed whether their own AI surfaces use it.

On Squarespace, add it via per-page Code Injection following the same pattern as Service schema. Structure at schema.org/FAQPage. Don't mark up questions that aren't visible on the page — schema describing content that isn't there is a penalty signal.

7. Make your content concrete enough to be cited

This is the check Google would say matters most. The audit scores three things on the actual content: specificity (does the page name real products, services, or methods?), differentiation (does it distinguish you from alternatives?), and credibility (does it name real clients, results, proof?).

Squarespace's design polish encourages a particular failure mode — beautiful hero sections with aspirational copy ("Where vision meets reality") that look professional but give AI engines nothing to extract. Two patterns to fix:

Aspirational hero copy. Replace with a specific claim: what you do, for whom, with what outcome. "Senior-led performance marketing for SEA consumer brands. Most engagements move CAC down 30%+ in 12 weeks" gives an AI engine four citation hooks. The aspirational version gave zero.

Image-heavy pages with thin text. Squarespace's design control encourages visual storytelling — good for users, bad for AI parsing. AI engines extract from text, not images. If your service page is 90% imagery with three captions, you're not citable. Add 200-400 words per major service. Use Heading 2 / Heading 3 to structure it.

8. Verify everything is actually working

Three free tools. Take five minutes per page.

Schema: paste your page URL into Google's Rich Results Test. Critical for Squarespace — Code Injection only renders on the PUBLISHED site, not the editor preview. Always test the live URL after publishing.

Robots.txt: visit yourdomain.com/robots.txt in incognito. You'll see Squarespace's auto-generated rules. Nothing to fix or verify — the platform controls it entirely.

End-to-end: re-run the AI Readability Checker. Squarespace sites typically cap at 60-70 with all the above applied — most unaudited Squarespace sites score 25-40. The lift is real even with the ceiling.

What to fix first — a half-day order of operations

First (20 minutes). Add Organization schema via Settings → Advanced → Code Injection → Header. Business plan required. Verify on the homepage with Rich Results Test.

Second (an hour). Rewrite homepage hero and top three service pages for concrete claims. Aspirational taglines out. Specific category, audience, outcome in. The one fix Squarespace lets you do freely without plan upgrades — and the highest-leverage one.

Third (an hour). Fill in the per-page SEO Description field for every important page. 120-160 characters with a concrete claim each.

Fourth (an hour). Fix heading hierarchy on top pages. One H1 per page, body content starts at H2.

Fifth (30 minutes). Add Service or FAQPage schema to key pages via per-page Code Injection where genuinely applicable. Don't add FAQ schema to pages that aren't really Q&A.

Past these five, you're hitting Squarespace's structural ceiling. Robots.txt AI-bot allow lines, richer schema, finer control — not available on the platform. Sites that need to push past 70 typically migrate, but only when design, performance, or commerce reasons also justify the move.

One pass, lasting effect

None of these fixes need ongoing maintenance once set up. Code Injection blocks sit in Settings forever. SEO descriptions, once written well, persist — though new pages need their own. Heading hierarchy stays fixed unless someone changes the page structure.

Squarespace's ceiling is lower than a fully customisable platform's. But the floor lifts dramatically with three Code Injection blocks and a content audit. A Squarespace site going from 25 to 65 reaches AI engines more reliably than a WordPress site going from 25 to 75 but never bothering with Organization schema.

If you've hit Squarespace's ceiling and need to push further — or your audit surfaces fixes that need deeper customisation than Code Injection can give — that's the conversation about platform migration. Get in touch, or read about the GEO & AI Search service.

Frequently asked questions