Google Business Profile, Wired Into Squarespace

The relationship between GBP and the website is bidirectional. GBP carries the primary entity data — name, category, address, hours, phone, photos, reviews — and Google reads the linked website to verify those signals are real. If the website's contact page shows a different address than the GBP listing, Google treats the conflict as a low-confidence signal and the local-pack ranking suppresses. If the website carries LocalBusiness JSON-LD⁵ that matches the GBP listing exactly, Google reads the match as a high-confidence signal and the local-pack ranking lifts.

Three settings on GBP have outsized influence on this evaluation: primary category, mode (storefront vs service-area), and the website link. Everything else on the listing matters but at lower weight. The next three sections cover each in install order.

The category-selection step inside GBP shows a long autocomplete list of options. The pattern is to start typing your service ('photographer', 'attorney', 'restaurant', 'plumber') and pick the most specific match the list offers. Generic top-level categories ('Business', 'Service', 'Shop') almost always rank worse than specific child categories — Google interprets specificity as confidence in the entity's actual service area.

Secondary categories are an underused lever. Up to nine secondary slots are available, and they let a business signal adjacent service breadth without splitting the primary identity. A family law attorney can list Family Law as primary, then add Divorce Attorney, Child Custody Attorney, and Mediator as secondaries to capture those query shapes. The rule of thumb: only add secondaries for services you actively advertise and would actually take a client for — not aspirational categories.

The website link is checked during the verification flow but does not influence whether verification succeeds. Google verifies that the business exists at the address, not that the website is well-built. The reason to set the website link correctly during initial verification is purely future-tense: once verified, the listing's website field is the URL Google reads to cross-check the on-page LocalBusiness schema and the contact-page address.

Service-area businesses verifying by video² walk through what they do, where they operate, and any relevant equipment or signage. The recording is reviewed by Google and approved or rejected within five days in most cases. Re-verification (required when GBP detects significant profile changes) typically uses the same method as initial verification.

Service-area-business mode³ changes the implications on the Squarespace side. A storefront listing means the Location block on the contact page renders the full address visibly, the footer shows the address, and the LocalBusiness JSON-LD includes a full PostalAddress. A service-area listing means the address is hidden from GBP, and the Squarespace site should either omit the street address from the Location block (showing only city/region) or use a Map block that shows the coverage area rather than the office address. Exposing a street address on the Squarespace site that the GBP listing hides reads as a mode conflict and can suppress ranking.

Hybrid practices — an office where some clients visit, plus travel for others — usually pick storefront mode (because there is a public address) and list additional service areas in the GBP service-area field. On the Squarespace side, this means the address is visible and the LocalBusiness JSON-LD includes both address (the office) and areaServed (the travel zone). The wedding photographer pattern is the cleanest hybrid: a small studio for headshots (visible address), plus travel-to-venue weddings (service area).

Squarespace 7.1 sites canonicalise to HTTPS, the bare domain (no www) by default, all-lowercase URLs, and a trailing slash on top-level pages. Verify with a browser View Source on your contact page: search for <link rel="canonical" and copy the value verbatim into the GBP website field. If your site uses /contact (no trailing slash) and your GBP says /contact/ (with trailing slash), the conflict is small but real.

Pointing the GBP website field at the homepage rather than the contact page is a common 2026 pattern that loses leverage. The contact page is where the LocalBusiness JSON-LD lives, where the Location block renders the address, and where the cross-reference with GBP is most direct. Point at the page that holds the local-SEO signal, not the page that holds the brand.

The Squarespace-specific implementation note is that Code Injection at the page level loads the script tag inside the head element of that page only. Open the page editor on the contact page, click Settings (gear icon), expand Advanced, paste the JSON-LD script into the Page Header Code Injection field, save. The full copy-paste JSON-LD library — with subtype options for medical, legal, food, automotive, and many other industry-specific variants — is in Pillar 3's LocalBusiness schema page.

 <script type="application/ld+json"> { "@context": "https://schema.org", "@type": "LocalBusiness", "name": "Maple Avenue Photography", "url": "https://yourstudio.com/contact/", "telephone": "+1-828-555-0136", "address": { "@type": "PostalAddress", "streetAddress": "42 Maple Ave Suite 3", "addressLocality": "Asheville", "addressRegion": "NC", "postalCode": "28801" } } </script> 

The mirror is one-way at install time and one-way for updates: when you change your hours on GBP, also change them in the JSON-LD; when you renumber your phone, also update it in the JSON-LD. There is no auto-sync between GBP and the Squarespace site — both surfaces are owner-maintained. The audit cadence is quarterly, the same as the directory-web NAP audit.