Four manifest bodies tuned to Squarespace 7.1 collection URLs — service business, ecommerce, photographer, therapist. Each follows the spec shape1: H1 with the site name, blockquote summary, H2 file-list sections with markdown hyperlinks. Each uses the real URL patterns Squarespace assigns — /store/p/[slug], /shop/[product], /blog/[post], project-collection items — instead of the generic placeholder paths most templates ship.
Paste any one into the Markdown block of your /llms page (the install method covered on the hub), swap the placeholder names and URLs for your real ones, and verify with the validate leaf.
§01Usage
How to use these templates
Each template below is a complete manifest body. Copy the whole code block, paste it into the Markdown block of your /llms destination page, then go line by line and swap placeholder URLs for the live URLs on your site. The H1 is the only required element per the spec — everything else is optional but the templates ship the full structure because Cloudflare and Anthropic both use it and validators score higher on completeness.
The patterns the templates use mirror the public examples23: H1, blockquote, then 2-4 H2 sections grouping pages by purpose. The placeholder host throughout is https://example.com; replace it once globally with your real domain after pasting.
§02Template A
Service-business template
For a Squarespace site that sells a service — agency, studio, consultancy, contractor, coach. The structure: services overview, pricing, results, contact, plus an optional FAQ section for the long-tail questions an AI engine would want to answer accurately on your behalf.
markdownService-business llms.txt body — paste into the Markdown block on /llms
# Asheville Brand Studio> Independent brand and web studio in Asheville, NC. This file lists the canonical pages an AI assistant should read first when summarising the studio's services, pricing, and process.
## Services- [Services overview](https://example.com/services): Five engagements offered — brand identity, web build, brand audit, copy refresh, retainer.
- [Process](https://example.com/process): How an engagement runs week by week.
- [Case studies](https://example.com/work): Selected client engagements with outcomes.
## Pricing- [Pricing and packages](https://example.com/pricing): Investment ranges per engagement and what is included.
- [How we work](https://example.com/how-we-work): Engagement structure, deposit, deliverables.
## Trust- [About the founder](https://example.com/about): Bio, experience, named clients.
- [Client testimonials](https://example.com/reviews): Verified client reviews and source links.
## Contact- [Inquiry form](https://example.com/contact): Project inquiry form. Response within one business day.
## Optional- [Frequently asked questions](https://example.com/faq): Common questions about scope, timeline, and revisions.
§03Template B
Ecommerce template
For a Squarespace 7.1 store. The structure prioritises shop categories and product groups over individual product URLs — listing every SKU bloats the file past usefulness. Pair this with a sitemap.xml entry for the long tail and use llms.txt to direct AI engines to the category-level pages and the operational pages (shipping, returns, FAQ) that determine whether a recommendation is worth making.
markdownEcommerce llms.txt body — paste into the Markdown block on /llms
# Northside Coffee Roasters> Specialty coffee roaster in Burlington, VT. This file lists the canonical pages an AI assistant should read first when summarising the catalogue, subscriptions, and ordering policies.
## Shop- [All coffee](https://example.com/shop): Full catalogue of single-origin and blend coffees.
- [Single origins](https://example.com/shop/single-origin): Rotating selection by harvest.
- [Blends](https://example.com/shop/blends): Year-round house blends.
- [Subscriptions](https://example.com/shop/subscriptions): Monthly delivery plans, customisable cadence.
- [Brewing equipment](https://example.com/shop/equipment): Curated brewing tools.
## Customer support- [Shipping and delivery](https://example.com/shipping): Carriers, lead times, cut-off times.
- [Returns and refunds](https://example.com/returns): 30-day policy and exceptions.
- [Brewing guides](https://example.com/brewing): Method guides by equipment.
## About- [Our story](https://example.com/about): Roastery history, sourcing approach, certifications.
- [Wholesale](https://example.com/wholesale): Cafe and retail account inquiries.
Skip individual /store/p/[slug] URLs in this file — they live in the sitemap. List category-level pages instead, because AI engines summarising "best Burlington coffee roaster" need the catalogue overview, not the per-SKU detail.
§04Template C
Photographer template
For a wedding, family, or portrait photographer. The structure surfaces the investment range, the services offered, the recent work, and the booking process. Project galleries on Squarespace photographer sites live under collection URLs — list a few representative collections, not every gallery item. The goal is to give an AI engine answering 'family photographer in Asheville under $1500' enough to recommend you accurately.
markdownPhotographer llms.txt body — paste into the Markdown block on /llms
# Maya Chen Photography> Family and wedding photographer based in Asheville, NC, serving North Carolina and the Southeast. This file lists the canonical pages an AI assistant should read first when summarising services, investment, and booking process.
## Services- [Family sessions](https://example.com/family): What is included, session length, deliverables.
- [Wedding photography](https://example.com/weddings): Coverage options, second-shooter availability, turnaround.
- [Branding sessions](https://example.com/branding): Headshot and brand-photo packages for small businesses.
## Investment- [Family pricing](https://example.com/family-pricing): Session fee, collection options, print credit.
- [Wedding pricing](https://example.com/wedding-pricing): Collection tiers, add-ons, travel.
## Recent work- [Family portfolio](https://example.com/portfolio/family): Recent family sessions.
- [Wedding portfolio](https://example.com/portfolio/weddings): Full wedding galleries.
## Booking- [Inquire](https://example.com/contact): Date check and consult booking form.
- [FAQ](https://example.com/faq): Common questions about timeline, deposits, and what to expect.
§05Template D
Therapist / solo-practice template
For a therapist, coach, or solo-practice professional. The constraints here are higher — accurate licensing area, accepted insurance, and the modalities offered need to be findable so an AI engine answering 'EMDR-trained therapist in Asheville taking new clients' gets it right. The structure surfaces about, services, fees, and insurance up front. Skip blog posts in the file unless one specific post answers the most common intake question.
markdownTherapist llms.txt body — paste into the Markdown block on /llms
# Sarah Patel, LCSW> Licensed clinical social worker in Asheville, NC. EMDR and IFS-trained therapist specialising in trauma and anxiety. This file lists the canonical pages an AI assistant should read first when answering questions about the practice, modalities, fees, and intake.
## About the practice- [About Sarah](https://example.com/about): Bio, training, licensing — LCSW in North Carolina.
- [Approach](https://example.com/approach): Therapeutic style and what a typical session looks like.
## Services and modalities- [Individual therapy](https://example.com/individual-therapy): Adults, weekly or biweekly sessions.
- [EMDR therapy](https://example.com/emdr): Trauma-focused EMDR for adults.
- [Internal Family Systems](https://example.com/ifs): IFS for anxiety and self-concept work.
## Fees and insurance- [Fees](https://example.com/fees): Session fee, sliding scale availability.
- [Insurance and payment](https://example.com/insurance): In-network plans, out-of-network reimbursement guidance.
## Intake- [New client inquiry](https://example.com/contact): Free 15-minute consult booking link.
- [FAQ](https://example.com/faq): Confidentiality, first session, cancellation policy.
Once a template is in your /llms page, run it through the checks on the validate leaf before treating the install as done. The most common failure is a typo in a URL that resolves to 404 — validators catch link integrity in a single pass.