AEO for Squarespace
Squarespace supplies structured data and a managed AI-crawler control. Check the built-in output and the supported settings before you add extra code.
Default robots.txt behavior
Settings → Crawlers has a “Block known artificial intelligence crawlers” checkbox. It is unchecked by default. When checked, it requests exclusions for Squarespace’s managed list. It is not an editor for custom User-agent rules. Code Injection changes page HTML. It does not create a root robots.txt file.
Decide whether to permit search and user-fetch crawlers separately from training crawlers, within the controls your platform provides. See how AEOprobe distinguishes crawler roles.
Default structured data
Squarespace automatically supplies Blog post, Event, Local business, Organization, Product and Website schemas for the relevant content. You cannot edit or remove those built-in schemas directly. Squarespace also generates and updates the sitemap. Inspect the actual page before you add extra JSON-LD.
Common AEO issues
| Issue | Impact | Fix |
|---|---|---|
| Supplementary JSON-LD repeats built-in facts | ImpactCustom scripts can conflict with markup Squarespace already supplies. | FixInspect the existing structured data. Correct its source content before you add a separate script. |
| Page-specific markup is injected site-wide | ImpactA script can describe a product or FAQ that is absent from other pages. | FixUse Page Header Code Injection where it is available. Do not put page-specific facts in the site-wide Header field. |
Step-by-step guide
- 1
Review the managed crawler setting
Open Settings → Crawlers. Decide whether “Block known artificial intelligence crawlers” matches your policy. Then save. Inspect /robots.txt. The setting requests compliance from the managed bot list.
- 2
Check the built-in page markup
Inspect a representative blog post, product or other relevant page. Compare its schema with the visible content and business information. Correct the underlying content. Do not duplicate built-in Organization or Product markup.
- 3
Add a specific missing script if your plan allows it
Code Injection is available on Core, Plus, Advanced and eligible legacy plans. For a page-specific addition, open Pages → the page’s gear icon → Advanced → Page Header Code Injection. Save, then check the published page. The blog-level Post Blog Item field applies to every post.
Official documentation
- Squarespace crawler control(opens in a new tab)
Managed bot list, default choice and its limits.
- Squarespace built-in SEO(opens in a new tab)
Automatic schema and sitemap behavior.
- Squarespace Code Injection(opens in a new tab)
Current plan access and site-wide versus page-specific fields.
Questions
Can I edit individual AI-bot rules?
No. The documented Crawlers control applies Squarespace’s managed list. It does not offer custom bot groups or page-by-page AI-crawler exclusions. Code Injection is not a workaround for robots.txt.
Do I need custom JSON-LD for every page?
No. Squarespace already generates several schema types. Add extra JSON-LD only to fill a specific gap. Your plan must allow it. Keep it consistent with the page’s existing markup and visible content.
The free audit checks up to 3 public pages with no sign-up. Structured data checks read JSON-LD only. Microdata and RDFa are not parsed. Findings do not guarantee rankings or AI citations.
A saved-site audit costs 20 credits. It covers up to 10 pages on Free, 50 on Watch and 100 on Pro. AEOprobe plans are Free at €0/month, Watch at €7/month and Pro at €21/month. Your account shows what you can buy.
Run the free audit on your site