Sunnyside Medicare

Table of Contents

Quick Checklist for Repeat Use

Gather these items before asking ChatGPT to create or update a Client Data record.

  1. Website / Content Export (JSON from Content Magic)
    • Services and service pages
    • Service areas and location pages
    • Products, manufacturers, and partners
    • Primary contact info
    • Legal name or former business names if listed
    • Social profile links
    • Google Maps, review, contact, and location links if present on the site
    • Trust details, warranties, financing, certifications, and proof points
  2. Google Business Profile Data Per Location (copy/paste front-end and back-end data for each profile)
    • Business name, category, phone, website URL, and description
    • Storefront, service-area business, or hybrid setup
    • Address or public location details
    • Service areas
    • Hours
    • Opening / formation date when available
    • Services and products
    • Google Maps URL, CID map URL, review URL, and map iframe/embed code if available
    • All other data
  3. Other Social, Citation, Directory, and Entity Asset URLs
    • Search the company name and collect live public profiles.
    • Look for BBB, Yelp, Facebook, Nextdoor, MapQuest, BuildZoom, Thumbtack, Angi, Houzz, chamber profiles, manufacturer profiles, PR profiles, and other relevant assets.
    • Separate true client profiles from related vendors/manufacturers/partners.
  4. Manually Provided Information
    • Full logo URL, square logo/icon URL, and 3 primary image URLs
    • Not offered services
    • Trust, proof, and writing context
    • Any brand voice and writing rules
    • Any client-confirmed corrections to names, phone numbers, service areas, services, or claims
  5. Entity Stack Output URLs (once created)
    • Google Asset Sheet URL and embed code (create in client Google Drive directory)
    • Google Site URL
    • ID Page / AWS URL

How to Prepare a Client Data Page

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.

1. Website / Content Export

  • Best: Marketing Sux Content Magic full content export from the current website.
  • Acceptable: XML sitemap, important page URLs, or pasted page copy.
  • Include: homepage, about, contact, services, location/service-area pages, reviews/testimonials, products, warranties, financing, and global content/options if available.
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.

2. Google Business Profile Data

Gather this once per GBP profile/location.

  • Public business name, address, city, state, ZIP, country
  • Storefront / service-area business / hybrid type
  • Primary and additional GBP categories
  • Phone, website URL, appointment URL
  • Business description, hours, services, products, and service areas
  • Google Maps listing URL, review link, embed code, and CID URL if available

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.

3. BrightLocal / Citation Campaign Data

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.

4. Social, Citation, Directory, and Entity Asset URLs

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.

5. Entity Stack Outputs

When these are built, add them as fixed fields, not random notes. Leave blank until they exist.

  • Primary Entity Home URL, usually the homepage unless the About page or another page is the source-of-truth entity page
  • Google Site URL
  • Google Drive Stack URL
  • Google Asset Sheet URL
  • Google Asset Sheet Embed Code
  • ID Page / AWS URL
  • ID Page HTML File URL if different
  • Press Advantage Org Page URL
  • Press Advantage Iframe URL
  • Primary Entity Video URL
  • Google MyMap URL
  • Entity Stack Notes, public-safe only

6. Services and Service Pages

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 damage

7. Not Offered Services

Metal roofing
Windows
24/7 emergency service
Commercial flat roofing

8. Service Areas and Location Pages

Service 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 / Global

For 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.

9. Content / Page Targets and Page Summaries

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.

10. Products, Manufacturers, and Partners

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://...

11. Trust, Proof, Brand Voice, and Writing Context

  • Warranty information
  • Financing details
  • Certifications / credentials
  • Associations / awards
  • Licensing / insurance notes
  • Family-owned / locally owned details
  • Key differentiators
  • What the client wants to be known for
  • Things to avoid saying
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.

12. Logo URLs and Primary Photo URLs

  • Full logo URL
  • Square GBP logo / icon URL
  • Primary photo 1 URL
  • Primary photo 2 URL
  • Primary photo 3 URL
  • Location / GBP photo URL if needed
  • Product image URLs if needed
  • Manufacturer or partner logo URLs if available

13. Character and Formatting Rules

  • Business Description: keep under 500 characters when possible for BrightLocal/citation reuse.
  • GBP Description: keep under 750 characters. Avoid URLs, HTML, promotional language, and keyword stuffing.
  • GBP Service Description: keep each offered-service description at or under 300 characters. Avoid URLs, HTML, pricing promises, or unverifiable claims.
  • Product Names: keep short, ideally under 58 characters.
  • Product Descriptions: keep under 750 characters.
  • Services: order by importance. Citation submissions may only use a limited number.
  • Public-facing fields: write to the customer.
  • Writing context fields: write to the internal team or ChatGPT.

14. Final Prompt to Send ChatGPT

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.

Client Data

Data QA Warnings

No obvious service/product data warnings found.

Branding & Primary Photos

Full Logo URL
Square GBP Logo / Icon URL
Primary Photo 1 URL
Primary Photo 2 URL
Primary Photo 3 URL

Core Business Identity

Public Business Name
Legal Business Name
Former / Old Business Names
Formation Date
Primary Business Category
Additional Categories
Global Service Territory
Business Description

Contact, Website & Entity Home

Primary Phone
Primary Email
Website
About Page
Contact Page
Appointment / Booking

Trust / Proof

Value Props / Trust Notes
Warranties
Financing Options
Certifications / Credentials Notes
Manufacturer / Brand Partners
Associations / Awards Notes
License / Insurance Notes

Brand Voice / Writing

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.

Toneclear, plainspoken, helpful, low-pressure, compliance-careful
Writing Do’s
  • Write for people turning 65, retirees leaving employer coverage, current Medicare members reviewing plans, and family members helping someone compare options.
  • Focus on practical decision factors: doctors, prescriptions, coverage, cost, benefits, plan types, enrollment timing, and local provider access.
  • Use safe, flexible language such as compare Medicare plans, review options, understand coverage, no-cost guidance, licensed Medicare agents, independent broker, multiple carrier options, enrollment support, and annual plan review.
  • Keep copy customer-facing and easy to scan. Let the page writing prompt control structure, Surfer optimization, length, and field output.
Writing Don’ts
  • Do not claim best plan, lowest cost, guaranteed savings, guaranteed approval, all plans, every carrier, every plan in your area, #1, or government/official Medicare status unless separately verified and approved.
  • Do not imply a person qualifies for extra benefits, savings, giveback benefits, OTC benefits, transportation, dental, vision, or hearing benefits unless eligibility and plan availability are verified.
  • Do not invent review counts, ratings, awards, credentials, carrier relationships, office locations, service areas, or plan-specific benefits.
  • Do not use scare tactics, aggressive urgency, or pressure around enrollment windows.
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

Generators / Outputs

Outputs are grouped by placement and usage. The QA section is for review before execution; the asset sections below follow the build order.

Generate AI QA Check — Copy All Generator Outputs

QA / Notes / Instructions

Core Asset Coverage / Scenario QA
QA / Missing Data Notes
Entity SEO Strategy / QA
Entity Stack Output URLs
Entity Stack Execution Checklist

Google Asset Sheet

Google Sheet Asset Rows

Google Site

Google Site Build Pack
Google Site Embed HTML — Home
Google Site Embed HTML — Services
Google Site Embed HTML — Service Areas
Google Site Embed HTML — Entity Assets
Google Site Embed HTML — Contact

ID Page / Entity Hub

ID Page HTML — Full index.html
Combined Entity / ID Page Schema JSON-LD
{
    "@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/"
        }
    ]
}

Website

Website Schema — Homepage / Organization
{
    "@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/"
        }
    ]
}

Company Writing Prompt

Page Writing Instructions / Prompt Context

Debug / Advanced

Advanced / Debug — Organization Schema JSON-LD
{
    "@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/"
}
Advanced / Debug — LocalBusiness Schema JSON-LD
{
    "@context": "https://schema.org"
}
Advanced / Debug — Service Schema JSON-LD
{
    "@context": "https://schema.org"
}