AUTHORITY LION — BLUEPRINTS

Shields & Boris — Assembled Blueprint

← Shields & Boris hub

Contents
Authority Blueprint v3 — shieldsandboris.com Homepage

AUTHORITY LION — AUTHORITY BLUEPRINT

shieldsandboris.com — Homepage Blueprint

The Elder Law Offices of Shields & Boris • Wexford, PA • Generated June 18, 2026

Scored with Authority Lion v3 model (binary checklists, markup-only schema manifest, reconciled positioning, section-aware cognitive load, render-gap check). Re-scored from the same captured page state as the v2 run, so the only variable is the model.

Executive Summary

42/100
v3 Total (v2: 55)
Fragmented
Grade (v2: Indexed)
1x
Access Multiplier
FIX FIRST
Verdict

Verdict: FIX FIRST — The site has a genuinely good local-business schema graph (LegalService across 5 offices), but under the stricter v3 model the gaps show clearly: thin content, a half-built AI-readability layer, an over-weighted hero, and — new in v3 — two render-gap conflicts where the machine layer contradicts the page. The drop from 55 to 42 is entirely recalibration, not a site change: same captured page, read more honestly. The fastest, highest-leverage gains are technical and free.

⚠ Two render-gap conflicts — FIX FIRST, before anything else

  • Fact conflict (phone). The hero shows (724) 204-6628; the title tag and schema say 724-862-4860. AI surfaces a different number than the visitor sees. Pick one, make it consistent everywhere.
  • Identity mismatch (OnceHub leak). The page's og:title is "Online appointment scheduling" and twitter:site is @OnceHub — metadata from the embedded scheduler, not the firm. A shared link or an AI preview attributes this page to OnceHub, not Shields & Boris.

The v3 story: a thin site drops hard, a strong one barely moves

Under v3, Shields & Boris fell 55 → 42 (−13, a full grade). For contrast, Authority Lion (a strong site) held at 81 → 80 (−1). That spread is the point of the recalibration — the model now discriminates instead of compressing everything toward the middle.

Categoryv2v3ΔWhy
Schema Quality1811−7 Markup-only manifest. Strong present set (LegalService, PostalAddress, Geo, openingHours, sameAs, logo) but missing structural WebSite/WebPage/BreadcrumbList/ContactPoint/areaServed/knowsAbout, and on-page services/attorneys/testimonials are unmarked. Coverage 8/21 → 8 + Validity 3 (empty @id). recalibration
AI Readability87−1 Title 4→3 (64 chars over band, no firm name); headings 1→0 (7×H1, zero H2, skipped levels, utility labels); meta 3→4 (value-prop credited). recalibration
Content Depth116−5 Additive checklist removes in-band inflation: ~800 words (+2, Basic band), team (+2), social proof (+2). No FAQ / process / 3+ data points. recalibration
Positioning Clarity18180 Reconciled rollup: round(25/40×20)+round(9/10×5)=13+5. Category sum still 25/40 but composition shifted (C2 & C8 down, C1 & C7 up). G5 still fails. recalibration (net flat)
Technical (18/50) × 1x = 18  |  Content & Positioning: 24/50  |  Total: 42/100 (v2: 55)

Net: −7 −1 −5 +0 = −13, all recalibration. Scope: this scores the homepage. The full site has 100+ pages (8 practice-area pages, attorney bios, blog) — a strong foundation the homepage doesn't yet leverage. Per-page scoring is a separate engagement.

1. Schema Quality — 11/25

v3 scores schema as markup only, against the homepage gold-standard manifest. It never penalizes missing content (that's Content Depth) — only missing structural markup and on-page content that isn't marked up. Below is the type checklist; the report does not include written-out JSON-LD. Building the missing schema is available as a separate engagement.

Schema — types that should be on a homepage

Schema typeBucketStatus
LegalService (niche LocalBusiness)Structural✓ Present
WebSiteStructural✗ Missing
WebPageStructural✗ Missing
BreadcrumbListStructural✗ Missing
PostalAddressStructural✓ Present (primary + 5 offices)
ContactPointStructural✗ Missing (phone on LegalService, no formal ContactPoint)
GeoCoordinatesStructural (dep: address)✓ Present (per office)
openingHoursSpecificationStructural✓ Present
areaServedStructural✗ Missing
sameAsStructural✓ Present (FB, Twitter, LinkedIn)
knowsAboutStructural✗ Missing (no topical authority)
logo / imageStructural✓ Present
Service (8 practice areas on page)Content-driven✗ Missing — content present, not marked up
Person (8 attorneys on page)Content-driven✗ Missing — content present, not marked up
Review / AggregateRating (4 testimonials on page)Content-driven✗ Missing — content present, not marked up
FAQPageContent-driven◯ Needs content first — no FAQs on page (see Content)

Validity 3/5 — parses and correct type, but the LegalService has an empty @id (breaks entity linking) and the graph isn't cross-linked (no WebSite/WebPage). Coverage = 20 × 8/21 weighted ≈ 8. Schema = 8 + 3 = 11. Note: FAQPage isn't charged here — with no FAQ content it's a content gap, counted once in Content Depth.

2. AI Readability — 7/25

Signalv3Binary breakdown
Title tag3/5present ✓ · 50–60 chars ✗ (64) · service type ✓ · location ✓ · business name ✗. "Elder Law Attorney | Wexford, Beaver, Bridgeville, PA | 724-862-4860"
Meta description4/4present ✓ · ≤160 ✓ (113) · page-specific ✓ · value prop ✓
Canonical0/2no <link rel="canonical"> on the homepage
OG / Twitter (firm-owned)0/4the only OG/Twitter tags belong to the embedded OnceHub scheduler, not the firm — fails the firm-owned test (see render gap)
llms.txt0/3/llms.txt returns 404
AI crawler directives0/3/robots.txt returns 404 — no file, no explicit AI-crawler invitation
Heading structure0/4one H1 ✗ (seven) · H2 present ✗ (zero) · no skipped levels ✗ (jumps to H3/H5) · descriptive ✗ (utility labels like "Pick a date and time")

3. Content Depth — 6/25

ComponentMaxv3Detail
Word count8+2~800 words of firm copy (Basic band, 500–999). Much of the raw page length is the embedded widget, not firm copy.
FAQ on page50No FAQ section and no FAQPage schema. A major miss for an audience that searches in questions.
Service / process depth308 practice areas, one teaser sentence each — no deliverables or process
How-it-works content20No engagement process (ties to the failed G5 gate)
Citable data points30Only "65 years of combined experience" (under the 3+ threshold)
Team credentials2+28 attorneys named with photos and bio links
Social proof2+24 named testimonials + a Google review link

Biggest unlock: an inline FAQ with answers (+3, plus FAQPage schema and AEO citation value at once), then real service detail (+3) and a 3-step process (clears gate G5).

4. Positioning — 18/25 (rollup)

v3 uses one canonical positioning rubric: 10 gates + 8 scored categories. Positioning Clarity (25) = round(categories/40 × 20) + round(gates/10 × 5) = round(25/40×20) + round(9/10×5) = 13 + 5 = 18.

4A. Gates — 9/10 Pass

G1 hero offer ✓ · G2 customer-as-hero ✓ (weak) · G3 direct CTA ✓ · G4 stakes ✓ · G5 plan ✗ FAIL · G6 one-liner ✓ (weak) · G7 no jargon ✓ · G8 success vision ✓ · G9 guide positioning ✓ · G10 transitional CTA ✓.

G5 fails (no visible plan). There's a booking widget, but no numbered "how it works" process. A single gate failure triggers the FIX FIRST overlay. Adding a 3-step plan ("1. Schedule a free call → 2. We build your protection plan → 3. Your legacy is secured") clears it — the highest-leverage positioning fix.

4B. Scored categories — 25/40

#Categoryv2v3Note
C1SB7 Completeness34binary: 5–6 of 7 present (Plan missing); v2 under-read its own table
C2Cognitive Load43the recalibration. Hero ~25 lbs → ceiling 3. See load curve below
C3PEACE Sound Bites33empathy implied, not stated
C4Story Loop Integrity33booking widget interrupts the narrative
C5Specificity & Survival33"65 years" concrete; outcomes thin
C6Copy Voice33competent template; no banned phrases
C7Funnel Architecture34binary: 4 of 5 layers met (only risk-reversal missing)
C8Repetition32headers are utility labels; a header-only reader doesn't get the story
Sum2525C2 & C8 down, C1 & C7 up — net flat

The cognitive-load recalibration did land (C2 4→3) — it's just offset in the 25-pt rollup by binary consistency corrections elsewhere.

5. Cognitive Load — section load curve

v3 scores cognitive load as a curve down the page, not one number. Hero held to near-zero; weight is earned deeper. C2 ceiling is set by the hero: 0–10 lbs→5, 11–20→4, 21–30→3.

SectionPhrasesLoadvs threshold
Hero "The Elder Law Offices of Shields & Boris" (company-as-hero, leads the H1, +15) · "Protecting Your Family Legacy" ("Legacy" is abstract — reader must translate to home/savings/family; +10, partial survival override for "Your family") ~25 lbs near-zero target — over → C2 ceiling 3
Primary CTA "Speak with a lawyer!" / "Schedule a call!" ~3 lbs <10 ✓
Mid: proof "Together our attorneys have over 65 years of legal experience." · "Don't wait for a crisis to begin planning for long-term care." ~5 lbs <25 ✓ (concrete, survival-linked)
Mid: booking widget Embedded OnceHub calendar: "Invalid date / No available times in June" ~10 lbs <25 ✓ but flagged (clutter + render gap)
Deep: practice areas, bios 8 practice-area teasers, attorney bios light high allowed

Hero fix (25 → ~8 lbs): lead with the customer outcome, ground "legacy" in concrete nouns, move the firm name to the logo line.

"Protect your home, your savings, and your family from the cost of long-term care. Pennsylvania elder-law attorneys with 65 years of experience — planning that works before a crisis hits."

Concrete nouns (home, savings, family) replace abstract "legacy"; the customer outcome leads; authority and stake stay intact. Lifts C2 from 3 to 5.

6. Human ↔ Machine Mismatch (render gap)

AEO works only when the human and the machine read the same story. v3 diffs the screenshot (human view) against the HTML/schema/meta (machine view). This page has two fix-first conflicts:

TypeHuman side (screenshot)Machine side (HTML / schema / meta)Impact
Fact conflict Hero phone (724) 204-6628 Title + schema say 724-862-4860 AI surfaces a different, conflicting number than the visitor sees
Identity mismatch Page is the law firm og:title "Online appointment scheduling", twitter:site @OnceHub (embedded widget) A shared link or AI preview attributes the page to OnceHub, not the firm

Both are FIX-FIRST (same weight as a gate failure). The firm has no noindex in its own <head> — the noindex on the page belongs to the OnceHub widget — so the access multiplier stays 1x. Worth confirming on render that the widget's noindex never bleeds into the firm's head.

7. Priority Fixes

FixImpact
Resolve the phone-number conflict + remove/scope the OnceHub OG/Twitter leakrender gap — FIX FIRST
Add a visible 3-step plan ("Schedule a call → We build your plan → Your legacy is secured")clears gate G5
Add robots.txt (AI-crawler allows + sitemap) and llms.txtAI Readability +6
Add firm-owned OG/Twitter; collapse 7 H1s to one + add H2s; add canonicalAI Readability +5–6
Fill the structural schema gaps (WebSite/WebPage/BreadcrumbList/ContactPoint/areaServed/knowsAbout, fix empty @id) and mark up the on-page services/attorneys/testimonialsSchema +6–8
Add inline FAQ with answers (unlocks FAQPage); expand practice-area copyContent +5 / Schema +1
Lighten the hero (lead with customer outcome, ground "legacy")C2 3→5

Schema implementation (the actual JSON-LD) is delivered as a separate build engagement, not part of this report.

Authority Lion • Authority Blueprint • shieldsandboris.com

Generated June 18, 2026 • Scoring model v3 (homepage scope)

© 2026 Authority Lion. All rights reserved.

Authority Lion • blueprints.authoritylion.com