Help with Press Advantage SEO Press Release

I am setting up a press release/company profile for a client.

Use only verified public company information from the client website and any company listings I provide. Do not invent facts. Be practical, concise, and direct.

CLIENT INFO / SOURCES:

  • Company name:
  • Website:
  • Main location:
  • Service area:
  • Industry:
  • Extra verification links I want considered:
  • Release angle if relevant (anniversary, expansion, award, new service, acquisition, hiring, community involvement, etc.):

YOUR JOB:
Help me build the following for this client.

  1. VERIFIED FACT SUMMARY
    Before writing anything else, summarize:
  • what is clearly verified,
  • what appears likely but is not fully verified,
  • what should not be claimed.
  1. ABOUT / BOILERPLATE TEXT
    Write:
  • one normal press-release-friendly About text,
  • one version under 255 characters.

Rules:

  • Keep it broad enough to reflect the company’s full scope.
  • Do not over-focus on 1 or 2 services unless the business is truly narrow.
  • Include years in business, family-owned, awards, etc. only if clearly verified.
  • Keep it factual and usable.
  1. SCHEMA SET A — SIMPLE PRESS RELEASE SCHEMA
    Create a clean, paste-ready JSON-LD block meant for a release platform profile or organization page.

Design this schema exactly as a simple LocalBusiness schema, not a full site graph.

Required structure:

  • @context
  • @type = LocalBusiness
  • name
  • image
  • url
  • telephone
  • address
  • @type = PostalAddress
  • streetAddress
  • addressLocality
  • addressRegion
  • postalCode
  • addressCountry
  • geo
  • @type = GeoCoordinates
  • latitude
  • longitude
  • openingHoursSpecification
  • @type = OpeningHoursSpecification
  • dayOfWeek
  • opens
  • closes
  • sameAs

Rules for Schema Set A:

  • Keep it simple and platform-safe.
  • Use only fields that can be verified.
  • Do not include unsupported extras unless I specifically ask.
  • Use the real current domain.
  • Include full script tags:
  • If a field cannot be verified, omit it and tell me why.
  1. SCHEMA SET B — FULL WEBSITE BUSINESS SCHEMA
    Create a more complete website-ready schema design for the client site.

Default design should be a clean @graph with these objects:

A. Place

  • @type = Place
  • @id = homepage URL + #place
  • geo
  • hasMap if clearly available
  • address

B. Organization / Business Entity

  • use the most specific business type possible only if clearly appropriate,
    otherwise use LocalBusiness
  • common examples:
  • HVACBusiness
  • RoofingContractor
  • Electrician
  • Plumber
  • Dentist
  • Attorney
  • RealEstateAgent
  • AutoRepair
  • LocalBusiness
  • include:
  • @id = homepage URL + #organization
  • name
  • legalName if verified
  • alternateName if useful and verified
  • url
  • email if verified
  • telephone
  • address
  • logo
  • image if available
  • description
  • priceRange only if appropriate and verified enough
  • openingHours or openingHoursSpecification
  • sameAs
  • foundingDate only if clearly verified
  • areaServed only if clearly verified
  • location referencing the Place object if used

C. WebSite

  • @type = WebSite
  • @id = homepage URL + #website
  • url
  • name
  • alternateName if appropriate
  • publisher referencing the organization
  • inLanguage
  • SearchAction only if the site actually has search

D. WebPage

  • @type = WebPage
  • @id = homepage URL + #webpage
  • url
  • name
  • isPartOf referencing the WebSite
  • about referencing the organization
  • primaryImageOfPage if available
  • inLanguage

Optional objects only if relevant and clearly useful:

  • ImageObject
  • Person
  • Article
  • FAQPage
  • Service
  • Review
  • AggregateRating

Rules for Schema Set B:

  • Keep it clean and intentional, not bloated.
  • Do not add every possible schema type just because it exists.
  • Prefer accuracy over completeness.
  • Use the client’s real current domain and real brand details.
  • If a field is unverified, omit it.
  • If the existing site schema appears messy or outdated, tell me what should be cleaned up.
  1. SCHEMA COMPARISON / QA
    Compare both schema sets and explain:
  • what each one is for,
  • what fields are intentionally different,
  • what should stay simple in the press-release schema,
  • what belongs only on the website schema,
  • any risky claims or outdated fields to avoid.
  1. TITLE KEYWORD / TARGET PHRASE
    Recommend the best “words to include in the title” for the release setup field.

Rules:

  • If the release is general company news, use a broad business keyword phrase.
  • If the release is about a specific service, use service + city.
  • No punctuation in the keyword phrase.

Give:

  • best choice,
  • 2 alternates,
  • one-sentence reason.
  1. OPTIONAL RELEASE SETTINGS
    Explain in plain English what to do with:
  • webhook URL
  • standard release instructions
  • dateline override

Then recommend what I should enter for this client, including when I should leave a field blank.

OUTPUT FORMAT:
Return the answer in this exact order:

A. Verified facts summary
B. About text full version
C. About text under 255 characters
D. Schema Set A — Simple Press Release Schema
E. Schema Set B — Full Website Business Schema
F. Schema comparison / QA notes
G. Best title keyword phrase + 2 alternates
H. Optional release settings recommendation
I. Warnings / claims to avoid

RULES:

  • Do not make up facts.
  • Do not rely on unsupported claims.
  • Keep press release schema simple.
  • Keep website schema clean and intentional.
  • Omit unverified fields instead of guessing.
  • Be concise, practical, and usable.