Free Corporation Schema Generator

Why many brands confuse search engines

How SwiftSchema helps

How it works

What is Corporation structured data?

Corporation is an Organization subtype used for incorporated entities, holding companies, and public companies. It complements WebSite, AboutPage, and ContactPage schema by defining the entity at the brand level—legal name, canonical URL, logo, headquarters, contact points, subsidiaries, and official profiles. This schema feeds knowledge panels, SGE, and voice assistants, helping them disambiguate your brand from similarly named companies.

Required and high-impact properties

1. name — your legal or commonly known name; match SEC filings or global branding.
2. url — canonical homepage URL (https, non-tracking).
3. logo — absolute logo URL. Prefer ImageObject with url, width, height.
4. contactPoint — at least one entry (customer support, sales) with contactType, telephone, areaServed, availableLanguage.
5. address — HQ address via PostalAddress; include streetAddress, addressLocality, addressRegion, postalCode, addressCountry.
6. sameAs — list verified profiles (LinkedIn, Crunchbase, SEC filings, Wikipedia, press kit).
7. founder / foundingDate — optional but useful for credibility.
8. parentOrganization / subOrganization — describe corporate structure if you have subsidiaries or belong to a larger conglomerate.
9. hasOfferCatalog / department — enumerate product lines or divisions.

Content prep checklist

• Align legal name, DBA, and tagline across the homepage hero, About page, and Organization schema.
• Host logos at stable URLs (e.g., /logo.png) and ensure they return 200 without authentication.
• Update About and Contact pages with leadership info, addresses, and contact channels that match your schema.
• Compile a list of official profiles with canonical URLs (LinkedIn, Twitter/X, Crunchbase, Glassdoor, Wikipedia).
• Document contact numbers and emails per department with owners/SLA so contactPoint entries remain accurate.
• If public, include tickerSymbol and investor relations links; if private, keep the focus on brand and contacts.

Implementation workflow

1. Gather entity data (legal name, HQ, EIN if needed, brand colors, logos, leadership).
2. Generate Corporation JSON‑LD using this tool and include additional properties like foundingDate or tickerSymbol if public.
3. Deploy the schema globally in your layout (e.g., <head> of every page) or at least on the homepage/About/Contact.
4. Add LocalBusiness schema on office/location pages instead of stuffing all addresses into the corporation block.
5. Validate in Rich Results Test and the Schema Markup Validator; fix warnings about missing logos or invalid contact points.
6. Monitor knowledge panels and Search Console for brand queries; update schema when leadership changes, mergers occur, or logos rebrand.

Subsidiaries, brands, and joint ventures

• If you own multiple brands, create separate Organization/Corporation schema for each, linking them via parentOrganization and subOrganization.
• For joint ventures, specify parentOrganization as a list and clarify the role in the description.
• Use department to represent business units (e.g., “Enterprise SaaS,” “Consumer Banking”).
• When selling a spin-off, remove the subOrganization reference and update the new owner’s schema accordingly.

Logo best practices

• Provide square and horizontal versions; Google prefers 112×112 or larger.
• Use transparent PNG/WebP when possible.
• Avoid including text that becomes illegible at small sizes.
• Serve via fast CDN with long cache lifetime and versioning via query strings or file names.
• Keep backup logos referenced in your design system in case you need to roll back.

sameAs linking strategy

• Include only authoritative profiles you control or that are recognized entities (LinkedIn, Crunchbase, Wikipedia, SEC).
• Avoid linking to social profiles you rarely update; stale accounts hurt trust.
• If you maintain press kits or investor relations pages, link them to help search engines find official assets faster.
• Keep the list under 20 links to reduce noise.

ContactPoint guidance

• Create separate contactPoint entries for Support, Sales, Billing, and HR. Each should have contactType, telephone, areaServed, availableLanguage, and optionally contactOption (TollFree, HearingImpairedSupported).
• If you offer chat or email-only support, include email and note the channel in contactType.
• Update contact points whenever numbers change or new regions launch; stale data can result in policy issues.

Troubleshooting checklist

• Inconsistent naming: if your homepage says “SwiftSchema,” but schema uses “Swift Schema LLC,” align them or mention both (alternateName).
• Logo fetch errors: use Google’s URL Inspection to verify the logo is crawlable; fix robots.txt or CDN blocks.
• Duplicate schema: ensure only one Corporation block loads per page. If a CMS plugin injects Organization data, disable or merge it.
• Missing sameAs: add at least a few strong profiles so Google can corroborate entity info.
• Office data in Corporation block: keep specific addresses and hours inside LocalBusiness schema for each office.

Maintenance tips

• Keep a brand guidelines doc with schema fields (name, logos, profiles). Update it whenever rebrands or acquisitions occur.
• Assign ownership (brand/PR team) for schema updates. Add schema review to quarterly marketing ops checklists.
• Monitor knowledge panel feedback or manual edits—if Google displays an old logo, update both the schema and the image in Search Console’s “Brand” section (if available).
• When launching in new countries, localize Organization schema (translated name, region-specific sameAs) if you operate separate brands.

Common Errors & Fixes

• Only Corporation schema: pair with WebSite, AboutPage, ContactPage to provide full context.
• Missing logo: supply a stable, crawlable logo URL or ImageObject.
• No sameAs: add official social and business profiles to confirm identity.
• Mixing addresses: use LocalBusiness schema for offices; keep corporate HQ address only in the Corporation block.
• Outdated leadership/contact info: update founder, foundingDate, contactPoint, and parentOrganization whenever corporate structure changes.

On-page parity checklist

• Legal name on-page matches name (include alternateName if both legal and brand names are shown).
• Logo shown in header/footer matches the logo URL and dimensions; logo URL is crawlable.
• HQ address and contact details on About/Contact pages match address and contactPoint.
• Official profiles linked on the site match sameAs entries; no dead or unofficial links.
• Canonical domain in schema matches site canonicals; avoid staging or alternate domains.
• Only one Corporation schema block per page; remove conflicting Organization/CMS-injected blocks or consolidate them.

Validation routine

• Run Rich Results Test/Schema Validator after branding or template changes.
• Use URL Inspection on the logo URL to confirm crawlability.
• Spot-check knowledge panel/search snippets for correct logo/name; adjust schema and site assets if discrepancies appear.
• Revalidate after adding new sameAs links or changing contact numbers/emails.