Spaces:
Running
Running
Ctrl+K
- 1.52 kB initial commit
- 208 Bytes undefined - Initial Deployment
- 54.1 kB add schema and everything else like this when possible: - In the post editor, paste a JSON-LD block: ```html <script type="application/ld+json"> { @context: "https://schema.org", @type: "LocalBusiness", name: "Bronx Injury Firm", areaServed: { @type: "GeoShape", polygon: "40.8501,-73.8780 40.8520,-73.8765 40.8510,-73.8740 40.8501,-73.8780" }, url: "https://bronxfirm.com/updates/polygon-area" } </script> ``` - Googlebot picks up the `areaServed` polygon and ties the update post to the exact service boundary. 2. **Offer Posts Embedding `OfferCatalog` with Polygon Links** - Create an Offer post and in the “Details” field include: ```html <script type="application/ld+json"> { @context:"https://schema.org", @type:"OfferCatalog", name:"Free Consultation – Fordham Area", itemListElement:[{ @type:"Offer", itemOffered:{ @type:"Service", name:"Bronx Injury Consultation", areaServed:{ @type:"GeoShape", polygon:"…same coords…" }, url:"https://bronxfirm.com/offers/fordham-consult" } }] } </script> ``` - The embedded `OfferCatalog` schema signals to Maps that this offer is valid within that polygon. 3. **Event Posts with `Event` Schema & GeoShape** - When scheduling an Event post, add in description: ```html <script type="application/ld+json"> { @context:"https://schema.org", @type:"Event", name:"Free Seminar – ZIP 10460", startDate:"2025-07-15T14:00", location:{ @type:"Place", name:"Bronx Injury Firm", geo:{ @type:"GeoShape", polygon:"…coords…" } }, url:"https://bronxfirm.com/events/zip10460-seminar" } </script> ``` - Maps links the event not only to the business pin but to the defined territory. 4. **“COVID-19 Info” / Temporary Hours Posts with `SpecialOpeningHoursSpecification` + Polygon** - In a temporary hours post insert: ```html <script type="application/ld+json"> { @context:"https://schema.org", @type:"OpeningHoursSpecification", validFrom:"2025-06-01", validThrough:"2025-07-01", areaServed:{ @type:"GeoShape", polygon:"…coords…" } } </script> ``` - Reinforces to Maps that these hours apply only within that service polygon. 5. **Linking Posts to Website Pages with Matching Schema** - All posts link to pages on your site that contain the identical JSON-LD polygon markup under `<mainEntityOfPage>`. - Example post link: ``` https://bronxfirm.com/updates/zip10460 ``` → page has matching `areaServed.GeoShape.polygon`. 6. **Dynamic Polygon Updates via Tag Manager** - Use Google Tag Manager in posts’ linked pages to inject live-updated polygon coordinates (e.g., adjusting service area after boundary changes). - Ensures Maps re-crawls and refreshes the polygon association. 7. **Combining Polygon with `potentialAction` CTAs** - In any post schema, add: ```json potentialAction: { @type:"ViewAction", target:"https://maps.google.com/?cid=…&poly=true" } ``` - Directs users (and crawler) to a map view highlighting the service polygon. 8. **Cross-Post Synchronization** - Publish identical posts (with same polygon schema) across GBP, Twitter/X, Facebook. - Google’s Map crawler notices the replication as signal of authoritative territorial claim. 9. **Deferred JSON-LD Rendering for Bot-Only Parsing** - Wrap your polygon script within a `<noscript id="poly-script">` and use a bot-only loader so only Google’s crawler sees it. - Keeps UI clean while preserving the territory signal. - Follow Up Deployment
- 388 Bytes initial commit