Skip to content
50% OFF $299 $599
Lock in
§ 1.2.5 ARTICLE
Published Verified Every 6 weeks Sources 5 named Reading time 6 min

Perplexity × Squarespace · § 1.2.5

Squarespace × Perplexity, the 15-Point Install Checklist

Fifteen items, four lanes, one full Perplexity install for a Squarespace site. Crawlers (3 items). Schema (3 items). Content (5 items). Measurement (4 items). Ship one lane per session and the full install lands in a long weekend.

How to use this checklist

The checklist is grouped into four lanes that map to the leaves in this cluster: Crawlers (the unblock-perplexitybot leaf), Schema (the citation-hygiene leaf), Content (the comparison-content and citation-hygiene leaves together), and Measurement (the hub's measurement section). Each item is independently shippable. The recommended cadence: one lane per session, 60-90 minutes each, with the full install landing in a single long weekend for most small-business Squarespace sites.

The order matters. Crawlers ship first because the rest of the install produces content the engine cannot read if crawlers are blocked. Schema ships second because it gates Perplexity's confidence to cite. Content ships third because it produces the extraction units the engine quotes. Measurement ships last because it produces the signal you need to know which content earned which citations.

Each item below references the leaf in this cluster where the full pattern is documented. The checklist itself is intentionally short — one or two sentences per item — because the depth lives in the leaves. Use this page as the shipping reference; use the leaves as the implementation reference.

Crawlers — 3 items

The crawler lane confirms that PerplexityBot and Perplexity-User can both reach your Squarespace site. Neither bot appears on Squarespace's 26-bot AI exclusion list, so the default state is permissive — the audit is the discipline that confirms it. Most sites pass all three items without intervention; the rare exceptions are sites with custom Code Injection rules or CDN-layer AI bot blocks.

  1. 01

    Open yoursite.com/robots.txt in a private window

    Confirm no Disallow rules for PerplexityBot or Perplexity-User. Neither appears on Squarespace's 26-bot AI exclusion list, so the default state should be permissive.

  2. 02

    Audit Code Injection for noai meta tags

    Open Settings > Advanced > Code Injection. Search the Header and Footer fields for 'Perplexity' and 'noai'. Remove any injected directives that block Perplexity user-agents.

  3. 03

    Check your CDN or WAF for Perplexity-blocking rules

    If your Squarespace site proxies through Cloudflare, Fastly, or AWS WAF, log in and audit AI-bot-blocking rules. Cloudflare's managed rules can block Perplexity outside Squarespace's panel.

Full walkthrough with the user-agent verification test and the CDN-layer fix paths lives in the unblock-perplexitybot leaf1.

Schema — 3 items

The schema lane installs the entity graph Perplexity uses for author and publisher attribution. Three structured-data blocks carry the load: Article JSON-LD on every editorial page, Person JSON-LD on the founder page, and Organization JSON-LD on the homepage. The injections live in Squarespace's Code Injection panel, with site-wide schema available on the Business plan and above.

  1. 04

    Inject Article JSON-LD on every editorial page

    Page Settings > Code Injection. Include headline, datePublished, dateModified, author (pointing to /founder/), publisher (pointing to your Organization), and mainEntityOfPage.

  2. 05

    Inject Person + Organization JSON-LD site-wide

    Settings > Advanced > Code Injection (Business plan and above). Person on /founder/ with sameAs links to LinkedIn, Wikidata, and verifiable public profiles. Organization on the homepage referencing the Person as founder.

  3. 06

    Validate every JSON-LD block in Google's Rich Results Test

    Paste each page's rendered HTML into search.google.com/test/rich-results. Resolve any errors before considering the schema layer shipped. Perplexity uses the same structured-data signals Google does.

Full copy-paste JSON-LD graph and the per-plan Code Injection placement pattern live in the citation-hygiene leaf5.

Content — 5 items

The content lane is the longest one and the highest-leverage. Five items cover the patterns Perplexity rewards: 134-167 word passage leads under every H2, comparison structure across 30 percent of editorial content, 2+ named sources per page, 2026 year-signals in titles and openings, and consistent byline metadata at the top of every article. Each item ships independently; together they earn citation cards on competitive product-research queries.

  1. 07

    Open every H2 with a bolded 134-167 word lead

    The lead is the passage Perplexity extracts into citation cards. Make it self-contained — readable without the surrounding context. Use the AnswerBlock pattern this site demonstrates.

  2. 08

    Convert at least 30% of editorial content to comparison format

    H3-per-option structure. Bolded one-sentence verdict at the top of each. 134-167 words of body underneath with a named source, a specific number, and a concrete use case.

  3. 09

    Cite 2+ named 2026 sources per page

    Replace every 'studies show' with a named publisher and a date. Link out to the primary source where possible. Two minimum; more on technical content.

  4. 10

    Add 2026 year-signals to titles, H1s, and opening paragraphs

    Year-language earns higher Perplexity citation rates than undated content. One mention per major section is the upper bound where the signal stops adding weight.

  5. 11

    Add a byline and last-verified date at the top of every article

    Byline links to /founder/. Last-verified date matches the dateModified in your Article JSON-LD. The consistency across rendered metadata and structured data is a signal Perplexity's algorithm appears to verify.

Full content-pattern walkthrough with the block-by-block Squarespace 7.1 implementation lives across the citation-hygiene leaf and the comparison-content leaf3.

Measurement — 4 items

The measurement lane closes the install loop. A weekly tracking spreadsheet for 10-15 queries you want to be cited for. A Friday cadence for running those queries in Perplexity and logging results. A GA4 channel grouping for the tagged Perplexity referral traffic that does carry a referrer header. A six-week re-audit cadence to catch drift in the upstream documentation that this checklist references.

  1. 12

    Build a 10-15 query tracking spreadsheet

    Branded and non-branded queries you want to be cited for. Columns for each AI engine (Perplexity, ChatGPT, Claude, Gemini, Google AIO). Update weekly.

  2. 13

    Run the tracking queries in Perplexity every Friday

    Open perplexity.ai, run each query, log whether your site appears in the source cards. Screenshot the cards for the queries that surface you, for evidence.

  3. 14

    Add a GA4 channel grouping for AI search traffic

    Create a custom channel called 'AI Search' with regex matching perplexity.ai, chatgpt.com, claude.ai, and gemini.google.com. Most AI traffic still arrives without a referrer, but the tagged subset is measurable.

  4. 15

    Re-audit the full checklist every 6 weeks

    Crawler docs change, schema specifications evolve, content drift sets in. The cadence in this site's masthead is every 6 weeks; replicate it on your own editorial pages.

Full measurement template, the GA4 regex, and the recommended-query lists by industry live in the cluster hub's measurement section. The crawler-watch step references the Cloudflare investigation4 and the Squarespace help-center documentation2 for the upstream source dates that drive the six-week re-audit cadence.

Keep reading · § 1.2.5