Gather these items before asking ChatGPT to create or update a Client Data record.
Use this page as the master data source for a client’s SEO, GBP, citations, schema, entity assets, Google Site / ID Page work, and writing prompts. Gather the items below, then paste/upload them in one ChatGPT conversation and ask for a Content Magic JSON import patch.
I uploaded the client’s current website export. Use it to extract business identity, services, service pages, location pages, trust details, brand voice, warranties, financing, products, manufacturer partners, entity assets, and writing context. Preserve existing fields unless the new data is clearly better.Gather this once per GBP profile/location.
Maps link: Open Google Maps → search business → open correct listing → Share → Copy link.
Map embed: Open Google Maps listing → Share → Embed a map → Copy iframe code.
Review link: Open GBP dashboard → Ask for reviews → copy the review request link. If missing, paste the Maps link and note it.
Paste/export campaign data when available: business name, address, phone, website, category, description, services/products, hours, payment methods, public contact info, and logo/photo URLs.
Do not paste private logins, passwords, payment data, or billing notes.
Asset Name | Asset Type | URL
Facebook Profile | Social Profile | https://...
BBB Profile | Review Profile | https://...
CertainTeed Profile | Manufacturer Profile | https://...
Google Maps Listing | Google Maps | https://...Include Facebook, Instagram, LinkedIn, YouTube, Yelp, BBB, Angi/HomeAdvisor, Houzz, Nextdoor, Yellow Pages/Superpages/DexKnows, manufacturer profiles, vendor/partner profiles, financing profiles, press/PR profiles, and any other live public profiles.
When these are built, add them as fixed fields, not random notes. Leave blank until they exist.
Service Name | Primary Keyword | Service Page URL | Notes
Residential Roofing | residential roofing | https://example.com/residential-roofing/ | Core service
Roof Repair | roof repair | https://example.com/roof-repair/ | Includes leaks and storm damageMetal roofing
Windows
24/7 emergency service
Commercial flat roofingService Area | Type | State | Page URL | Assigned GBP Location
Livonia | City | MI | https://example.com/service-area/livonia-mi/ | Main Office
Metro Detroit | Region | MI | | Unassigned / GlobalFor GBP service areas, keep the list practical. Do not stuff unlimited cities. Use no more than about 20 accurate areas per GBP profile unless there is a clear reason.
Use this when the client has existing service pages, service-area pages, or important sitemap pages that should feed Google Site page bodies, service-area schema, and writing prompts.
Page Label | Page Type | Page URL | H1 / Title | Primary Keyword | Related Service | Related Service Area | Page Summary
Fraser Roofing Page | Service Area | https://example.com/roofing/fraser-mi/ | Roofer in Fraser, MI | roofer in Fraser MI | Roofing | Fraser, MI | Short 250–500 character customer-facing summary.Keep summaries short and customer-facing. Pull them from the live page excerpt, hero section, meta description, or best short page summary from the Content Magic export.
Name | Type | Description | URL
CertainTeed | Manufacturer | Roofing and siding product manufacturer used by the client. | https://...
VELUX | Manufacturer | Skylight manufacturer used by the client. | https://...
Acorn Finance | Financing Partner | Financing option available to customers. | https://...Brand Voice:
Plainspoken, helpful, local expert. Avoid hype and scare tactics.
Writing Do's:
Use direct explanations.
Tie services to real customer problems.
Mention warranties and proof when relevant.
Writing Don'ts:
Do not claim 24/7 emergency service unless confirmed.
Do not mention services listed as not offered.
Do not overuse city names unnaturally.I am creating/updating a Client Data record for [CLIENT NAME].
Use the uploaded website export, pasted GBP data, BrightLocal/citation data, social/profile URLs, entity stack output URLs, service lists, service area lists, trust notes, brand voice notes, and logo/media information to generate a Content Magic JSON import patch for the Client Entity Profile ACF fields.
Preserve existing data unless the new data is clearly better.
Do not invent verified credentials, licenses, awards, or services.
Use dummy placeholder content only where I explicitly ask for it.
Keep public-facing fields customer-ready.
Keep writing context fields internal and instruction-focused.
Use one GBP location row per Google Business Profile.
Use one service row per offered service.
Use service area page URLs when available.
Add all live public profiles to Entity Assets.
Add Google Site, Google Sheet, ID Page/AWS, Press Advantage, and related stack URLs to Entity Stack Outputs when available.
Generate the import JSON as a downloadable file.No obvious service/product data warnings found.
| Full Logo URL | |
|---|---|
| Square GBP Logo / Icon URL | |
| Primary Photo 1 URL | |
| Primary Photo 2 URL | |
| Primary Photo 3 URL |
| Public Business Name | |
|---|---|
| Legal Business Name | |
| Former / Old Business Names | |
| Formation Date | |
| Primary Business Category | |
| Additional Categories | |
| Global Service Territory | |
| Business Description |
| Primary Phone | |
|---|---|
| Primary Email | |
| Website | |
| About Page | |
| Contact Page | |
| Appointment / Booking |
| Value Props / Trust Notes | |
|---|---|
| Warranties | |
| Financing Options | |
| Certifications / Credentials Notes | |
| Manufacturer / Brand Partners | |
| Associations / Awards Notes | |
| License / Insurance Notes |
| Brand Voice Summary | Sunnyside Medicare helps people understand Medicare options with clear, no-pressure guidance from licensed agents. Copy should be plainspoken, practical, and trustworthy without becoming stiff or overexplained. The main job is to help readers compare plans, understand enrollment timing, and feel clear about next steps. |
|---|---|
| Tone | clear, plainspoken, helpful, low-pressure, compliance-careful |
| Writing Do’s |
|
| Writing Don’ts |
|
| Landing Page Writing Instructions | Use Sunnyside’s existing page template and the page writing prompt as the primary structure. Client-specific page copy should explain local Medicare help, plan comparison, plan types, enrollment support, and annual review where relevant. Use city/state language only when the page is location-focused. Do not let client voice rules override Surfer guidance, field rules, or the page brief. |
| Compliance / Claim Notes | Medicare compliance controls all public copy. Keep Medicare Advantage, Part D, Medigap, benefits, costs, carriers, enrollment, and eligibility language accurate and conservative. Do not make plan-specific claims unless verified against current plan documents and approved compliance language. If Sunnyside is acting as a TPMO for Medicare Advantage or Part D marketing, use the current CMS/carrier-approved TPMO disclaimer in the proper site, footer, form, or page area. Do not improvise the disclaimer in body copy. Use no-cost guidance or no direct cost to you only to describe the client-facing cost of working with the agency. Do not imply Medicare, healthcare services, coverage, or benefits are free. |
| Company Writing Context |
Outputs are grouped by placement and usage. The QA section is for review before execution; the asset sections below follow the build order.
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "Organization",
"@id": "https://stuff.marketingsux.com/client-data/sunnyside-medicare/#organization",
"mainEntityOfPage": "https://stuff.marketingsux.com/client-data/sunnyside-medicare/"
}
]
}{
"@context": "https://schema.org",
"@graph": [
{
"@type": "Organization",
"@id": "https://stuff.marketingsux.com/client-data/sunnyside-medicare/#organization",
"mainEntityOfPage": "https://stuff.marketingsux.com/client-data/sunnyside-medicare/"
}
]
}{
"@context": "https://schema.org",
"@type": "Organization",
"@id": "https://stuff.marketingsux.com/client-data/sunnyside-medicare/#organization",
"mainEntityOfPage": "https://stuff.marketingsux.com/client-data/sunnyside-medicare/"
}{
"@context": "https://schema.org"
}{
"@context": "https://schema.org"
}