PublishedVerifiedEvery 6 weeksSources5 namedAuthored bySquareRank Team
AI Overviews · § 1.3.4 · How-to
E-E-A-T on Squarespace 7.1 for AI Overviews
Google's Search Quality Rater Guidelines1 — the 182-page document last updated on 11 September 2025 — define E-E-A-T as Experience, Expertise, Authoritativeness, and Trustworthiness, with Trust as the most important page-quality indicator. AI Overviews uses these signals as a credibility filter on the candidate citation set. The Squarespace-side install is three JSON-LD blocks: a Person on /founder/, an Organization on the homepage, and an Article block on every editorial page whose author field points to the founder Person URL.
This leaf works through each of the four pillars in order, names the Squarespace-specific implementation, and ships the exact Person JSON-LD block to inject on the founder page — using the SquareRank founder, Billy Reiner, as the concrete worked example. The pattern transfers to any small-business Squarespace site whose founder is the editorial voice.
§01The short answer
TL;DR — three JSON-LD blocks and a real founder page
The E-E-A-T install on a Squarespace 7.1 site is mechanical once the editorial side is in place. Build a real founder page at /founder/ with name, photo, bio, location, knowsAbout list, and verifiable contact details. Inject Person JSON-LD on that page with sameAs links to LinkedIn, GitHub, professional profiles, and any third-party validation (podcast appearances, conference talks, published books). Inject Organization JSON-LD on the homepage with the brand's sameAs links. On every editorial page, the Article JSON-LD's author field points to the founder Person URL — not a fresh inline Person object per page. One canonical entity, referenced everywhere.
The editorial side is the harder side. The JSON-LD blocks take an hour to author and install; the founder page itself takes longer because it requires a real bio with verifiable claims. Squarespace's auto-emitted Article markup ships a basic author field but not the Person + sameAs entity wiring AIO uses as a credibility signal. The Code Injection layer is what closes the gap, and Code Injection is gated to Business plan and above — Personal plan sites cannot install the schema layer at all.
§02The definition
What E-E-A-T actually is in 2026
E-E-A-T is the four-letter acronym Google's quality rater guidelines use to evaluate content. Experience asks whether the content creator has first-hand experience with the topic. Expertise asks about the level of knowledge or skills relevant to the topic. Authoritativeness asks whether the creator and the website are a known source for the topic. Trustworthiness — Google calls this the most important page-quality indicator — asks whether the page is accurate, honest, safe, and reliable. The four pillars compound: a page weak on any one is read less confidently than a page strong on all four.
Google's quality rater guidelines1 document the framework in 182 pages, last revised 11 September 2025. The 2025 update expanded YMYL (Your Money or Your Life) to include government and civic information, reflecting Google's growing concern about misinformation in those areas. AI-generated content is judged by the same E-E-A-T benchmarks as human-written content. The implication is direct: AI-generated content cannot meet E-E-A-T without a named, verifiable author taking accountability for it.
§03Experience
Experience — first-hand evidence on the page
Experience is the easiest E-E-A-T pillar to fake on the surface and the hardest to fake convincingly. Google's quality raters are trained to look for first-hand detail: specifics that only someone who has done the thing would know. On a Squarespace site that means concrete numbers (how many sites the founder has built), named projects, verifiable timelines, and the kind of edge-case detail that wouldn't appear in a generic 'we help businesses' page. The schema side carries the visible side: the founder page lists projects and case studies; the Person JSON-LD encodes years of experience and topics the founder knows about.
A practical test: open your founder page, hide the bio behind your hand, and read only the verifiable detail. Number of years building Squarespace sites. Number of sites built. Notable projects with named clients (where confidentiality permits). City of operation. The verifiable detail should add up to a story; if all that remains is "10 years experience" without specifics, the page is light on experience signal regardless of what the bio claims.
For SquareRank specifically, the founder — Billy Reiner — carries verifiable detail across Behance, Dribbble, GitHub, and the personal sites billyreiner.com and billyreiner.de. The 10 years, 1,000+ sites figure originates on billyreiner.com itself, which is the kind of self-asserted claim AI engines weight more heavily when the same claim appears on third-party sources (the design portfolio on Behance, the code on GitHub). The Person JSON-LD encodes this entity graph through its sameAs array.
§04Expertise
Expertise — verifiable credentials in markup
Expertise is the pillar that maps most directly to JSON-LD. The Person type supports knowsAbout (an array of topics the person has knowledge about), jobTitle (current role), alumniOf (educational background), and worksFor (current organisation). On a Squarespace site, the founder Person should carry a knowsAbout array reflecting the topics the site is built around. For SquareRank: Squarespace SEO, Answer Engine Optimization, Generative Engine Optimization, JSON-LD structured data, AI search visibility, llms.txt, Squarespace 7.1, web design. Each entry should match a real cluster the founder has demonstrably worked on.
Schema.org's Person specification3 describes knowsAbout as "indicates topics a person has knowledge about, suggesting possible expertise but not implying it." The wording matters: knowsAbout is a self-asserted signal, not a verification claim. AI engines treat it as one input among many, weighted alongside external mentions (Authoritativeness) and on-page evidence (Experience). Stuffing knowsAbout with 50 unrelated topics weakens the signal; a focused list of 8-12 topics the founder demonstrably works in strengthens it.
The E-E-A-T install in numbers
4
pillars in the E-E-A-T framework: Experience, Expertise, Authoritativeness, Trustworthiness.
Authoritativeness is the pillar that lives mostly outside your own site. Google and the AI engines validate entities by checking whether the same person, with the same credentials, appears on independent third-party sources. The on-site implementation is the sameAs array on the Person JSON-LD: every credible external profile, listed as a URL. The off-site work is earning those profiles in the first place — LinkedIn, podcast appearances, conference talks, named quotes in industry publications, published books on Google Books, a Wikidata Q-ID where one exists.
Search Engine Land's 2026 GEO research4 identifies entity authority as a primary GEO signal and notes that "AI engines favour earned media — authoritative third-party sources — over brand-owned content." The implication for a small-business Squarespace owner is that the strongest investment is in the off-site work: getting on three podcasts in the founder's specialty, writing a guest article for a respected publication, speaking at a relevant conference. Each new third-party mention strengthens the entity over time and adds a new URL to the sameAs array.
For Billy Reiner specifically, the verified sameAs targets are: LinkedIn (canonical pointer used on the personal sites), GitHub (code presence), Behance (design portfolio), Dribbble (design work), Instagram, and the two personal sites billyreiner.com (English) and billyreiner.de (German portfolio). Twitter/X and Wikidata are currently absent — flagged in the SSOT as gaps to fill as those profiles get authored.
§06Trustworthiness
Trustworthiness — the most important indicator
Google's quality rater guidelines describe Trust as the most important of the four pillars: 'a page can be untrustworthy and have a low overall page quality even if other E-E-A-T characteristics are high.' Trust is built through a small set of mostly boring practices: HTTPS sitewide, a real privacy policy, a real terms of service, real contact information, transparent business practices, and accurate citations. On a Squarespace site, most of these are platform defaults — HTTPS is automatic, Privacy and Terms are template pages — but the contact information and citation discipline are author-controlled.
The contact-information question is the one most small-business sites get wrong. A site whose contact page lists only a contact form is materially less trustworthy than a site that lists a real email address. Squarespace makes both easy; the trust gain is on the side of the real email. For SquareRank, the contact email is [email protected], which is the same email used on the founder's personal sites — an additional consistency signal that ties the SquareRank entity back to the verifiable Billy Reiner identity.
Citation discipline is the other author-controlled trust lever. Every factual claim on the site should cite a named source with a date inline. The 2026 standard is "according to Search Engine Land's GEO research, published February 2026" rather than "studies show." Every page in this cluster carries 5-10 named sources in its right-rail manifest; every statistical claim in body copy has an inline citation that links back to the manifest. The pattern itself is a trust signal.
§07The JSON-LD
The Person JSON-LD to install on /founder/
The Person block lives on the founder page only, not on every page. Paste it into Page Settings > Advanced > Code Injection > Header. The block carries name, jobTitle, url (the canonical /founder/ URL), image (a real photo at a stable URL), knowsAbout (the topics array), and sameAs (the array of verifiable third-party profiles). Validate in Google's Rich Results Test after install. The block below is the production version on SquareRank, with billy's real verified sameAs targets — substitute your own founder's data using the same shape.
JSON-LDProduction Person block for /founder/ — paste into Page Settings > Code Injection > Header
Two notes on the block. First, the address is intentionally city-level rather than street-level — precise enough to anchor the entity geographically without exposing residential detail. Schema.org's Person type3 accepts address as a PostalAddress, and addressLocality alone is sufficient for entity disambiguation. Second, the image URL must point to a stable image that returns 200 OK on a HEAD request. AI engines validating the Person occasionally fetch the image; a broken image URL weakens the entity signal slightly without breaking the markup.
§08Author wiring
Wiring author to the founder Person on every article
Every editorial page on the site emits Article JSON-LD via the layout chrome. The author field points to the founder Person URL (not a fresh inline Person object). The Article layout in this codebase already does this — the schema graph it emits sets author to a Person object with name and url pointing at /founder/. The pattern is canonical: one Person entity, referenced from every page that has the founder as author. AI engines collapse the references onto a single entity and the page-level credibility inherits the founder's accumulated authoritativeness.
Google's Article schema documentation2 recommends including type and URL/sameAs on author markup. The "url" reference to a canonical Person page is the simplest implementation; Google then crawls the linked page, finds the full Person JSON-LD, and merges the entity graph. The alternative — inlining the full Person block on every article — is technically valid but creates maintenance burden (any change to the founder's knowsAbout or sameAs has to be propagated to every page).
JSON-LDThe author wiring — emitted automatically by the Article layout on every editorial page in this codebase
{"@type":"Article","headline":"E-E-A-T on Squarespace 7.1 for AI Overviews","author": {"@type":"Person","name":"Billy Reiner","url":"https://squareranked.com/founder/"},"publisher": {"@type":"Organization","name":"SquareRank","url":"https://squareranked.com/"}}
The Organization JSON-LD on the homepage5 completes the entity graph. The organisation carries its own sameAs links (brand social profiles), and the founder Person points to the same organisation via the worksFor property. The result is a small entity graph: founder Person worksFor Organization; Organization publishes Article; Article authored by founder Person. AI engines walk the graph and arrive at a consistent identity from any starting point.
