jared
/
SecondBrain
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
SecondBrain/convention/2026-06-30-llf-schema-gbp-u...

2.8 KiB
Raw Blame History

summary tags
llf-schema gbp_url holds an SDD URL on PLD by design (Gary's anti-duplicate-GMB strategy); never "fix" it, fix the verifier instead
scope/global
type/decision
client/lento-law
project/llf-schema
convention/do-not-remediate

llf-schema gbp_url cross-link is INTENTIONAL — do not "fix" it

TL;DR for the AI

A PLD office whose gbp_url contains a studentdisciplinedefense.com URL is correct, not a data-entry mistake. Do not propose to remediate it, do not file it as a data-quality defect, and do not re-raise it every release. This note exists because the AI keeps re-flagging it and the developer has to catch it manually every time.

The fact

The llf-schema WordPress plugin's gbp_url ACF office field deliberately holds different kinds of URL on each site. This is Gary Steel's anti-duplicate-listing SEO strategy, confirmed in the client meeting "Alignment PLD/SDD SEO & Schema" (2026-06-16), decisions D-041 / D-043.

PLD office gbp_url  →  the corresponding SDD location-page URL
                       (a studentdisciplinedefense.com URL, NOT a Google URL — by design)
SDD office gbp_url  →  the real Google Business Profile g.page link

Effective chain:    PLD page --sameAs--> SDD page --sameAs--> Google Business Profile
  • "GBP" = Google Business Profile (formerly Google My Business / GMB).
  • The field name is a known "footgun" (D-041): on PLD the value is an SDD URL despite the name implying a Google URL. The value is right even though the name is misleading.
  • Rationale: linking the same Google listing from two sites triggers Google duplicate-listing penalties. SDD is the single source of truth per location; PLD routes through SDD.
  • PLD: professionallicensedefensellc.com. SDD: studentdisciplinedefense.com.

Rule for the AI

  • A PLD gbp_url pointing at SDD is CORRECT. Never "fix"/remediate it or treat it as a defect.
  • Live v0.2.2 output (1 LegalService node per office page, WebPage.about → #legalservice) is correct and not to be changed by default.
  • The "2 LegalService nodes / WebPage.about → #location-*" situation only arises in the unreleased per-office-node work (D-042, v0.2.5+). If a verifier flags the HQ office page in that context, the fix is to update the verifier profile to accept the documented D-042 Option A output — never edit live ACF data or change the cross-link strategy.

Sources

  • llf-schema CLAUDE.md → "INVARIANT — gbp_url cross-link is INTENTIONAL" section.
  • llf-schema docs/decisions/2026-06-19-sdd-multisite-decisions.md (D-041, D-043).
  • llf-schema openspec/changes/2026-06-20-sdd-service-descriptions-and-hq-node/design.md (D-042 HQ-node resolution).
  • Client repo philly-search-engine-marketing/DECISIONS.md (2026-06-16) + meeting transcript.