section stringclasses 10
values | field stringlengths 4 25 | plain_language_question stringlengths 29 68 | schema_org_type stringclasses 6
values | schema_org_property stringlengths 3 16 | priority stringclasses 3
values | recommended_status stringclasses 4
values | why_it_matters stringlengths 51 94 | example_value stringlengths 1 56 | notes stringlengths 28 101 |
|---|---|---|---|---|---|---|---|---|---|
Basic identity | brand_name | What is the public name of the brand? | Organization | name | High | Core | The brand name is the primary label used for recognition and disambiguation. | Farosio | Use the same spelling and capitalization across official profiles. |
Basic identity | official_website | What is the official website of the brand? | Organization | url | High | Core | The website is the main canonical destination for the brand. | https://farosio.com | Use the canonical HTTPS URL. |
Basic identity | short_description | How should the brand be described in one or two sentences? | Organization | description | High | Core | A concise description helps humans and machines understand what the brand does. | Structured public profiles for AI-visible brands. | Avoid vague marketing language when a concrete description is possible. |
Basic identity | logo | What is the official brand logo? | Organization | logo | High | Core | A logo helps connect the visual brand identity across public surfaces. | Use a stable image URL with appropriate dimensions. | |
Basic identity | tagline_or_slogan | What short phrase summarizes the brand? | Organization | slogan | Medium | Recommended | A slogan can reinforce positioning when it is stable and public. | Build your brand signal. | Keep it consistent with the website and public profiles. |
Basic identity | founding_date | When was the brand founded or launched? | Organization | foundingDate | Medium | Recommended | Founding date gives basic chronology and helps distinguish similarly named entities. | 2026 | Use the most accurate public year or date available. |
Founder and ownership | founder_name | Who founded or publicly represents the brand? | Organization | founder | Medium | Recommended | Founder information can support identity and accountability for small brands. | Nitin Kumar Gupta | Include only public information the brand is comfortable sharing. |
Location and reach | location_country | Where is the brand primarily based? | Organization | addressCountry | Medium | Recommended | Country context helps disambiguate brands and public records. | Mexico | Use the operating or registered country when appropriate. |
Location and reach | location_city | What city is the brand associated with? | Organization | addressLocality | Low | Contextual | City context can help local recognition and disambiguation. | Mexico City | Use only if the brand wants to publish city-level information. |
Location and reach | area_served | Where does the brand serve customers or users? | Organization | areaServed | Medium | Recommended | Area served explains whether the brand is local, national, regional, or global. | Global | Do not imply availability in markets the brand does not serve. |
Official links | social_profiles | What official social profiles belong to the brand? | Organization | sameAs | High | Core | Official links help connect the same brand entity across the web. | https://x.com/farosioapp | Only include official and controlled profiles. |
Official links | external_company_profiles | What external company or product profiles identify the brand? | Organization | sameAs | Medium | Recommended | Stable external profiles can strengthen entity consistency. | https://www.crunchbase.com/organization/farosio | Use only public and stable URLs that clearly represent the brand. |
Official links | wikidata_item | Does the brand have a public knowledge graph item? | Organization | sameAs | Medium | Conditional | A stable knowledge graph item can help entity recognition when it is accurate and supportable. | https://www.wikidata.org/wiki/Q139913244 | Do not create unsupported or promotional knowledge graph entries. |
Offerings | offering_name | What product or service does the brand offer? | Product or Service | name | High | Core | Offerings explain what the brand actually provides. | Brand Trust Profile | Use clear names that customers would recognize. |
Offerings | offering_description | What does the product or service do? | Product or Service | description | High | Core | Offering descriptions help machines and people connect the brand to relevant needs. | A structured public profile for independent brands. | Avoid exaggerated claims and unverifiable promises. |
Offerings | offering_category | What category best describes the offering? | Product or Service | category | Medium | Recommended | Category helps place the offering in a useful context. | Brand identity software | Use the closest truthful category rather than forcing a trendy label. |
Offerings | pricing_signal | Is the offering free or paid? | Offer | price | Medium | Conditional | Pricing information can reduce uncertainty for evaluators. | 0 | Only publish price data that is current and accurate. |
Offerings | availability_channels | Where can customers access or buy the offering? | Offer or Organization | availableChannel | Medium | Recommended | Availability channels help users find the official way to engage. | Website | Use official channels rather than uncontrolled marketplaces. |
Narrative | brand_story | What story should people understand about the brand? | Organization | description | Medium | Recommended | A short narrative helps explain why the brand exists and what it is trying to solve. | Farosio helps brands become easier to understand online. | Schema fields cannot capture every narrative nuance; pair structured data with readable page content. |
Narrative | differentiation | What makes the brand meaningfully different? | Organization | knowsAbout | Medium | Recommended | Differentiation helps avoid reducing the brand to a generic category. | Brand-facing identity profiles | Use truthful differentiators that can be supported by the product and public content. |
Narrative | values_or_focus | What values or operating focus should the brand be known for? | Organization | knowsAbout | Low | Contextual | Values can help human evaluators understand the brand beyond features. | Free access for independent brands | Keep values specific and avoid broad claims that sound generic. |
Credibility | domain_verification | Can the brand show control of its official domain? | Organization | url | High | Core | Domain control supports the connection between the profile and the official website. | DNS TXT verification | Domain verification proves domain control; it does not prove every brand claim. |
Credibility | public_contact | How can media, partners, or customers contact the brand? | Organization | contactPoint | Medium | Recommended | A public contact point makes the brand easier to evaluate and reach. | hello@farosio.com | Use a public brand email, not a private login email. |
Credibility | press_or_articles | Are there public articles or posts about the brand? | CreativeWork | about | Low | Conditional | External references can support discovery and credibility over time. | Medium founding article | Only use references that are public and relevant. |
Credibility | reviews_or_testimonials | Does the brand have real customer reviews or testimonials? | Organization | review | Low | Conditional | Genuine reviews can help human evaluators when available. | Customer review | Do not fabricate reviews or publish unverified ratings. |
Credibility | certifications_or_awards | Does the brand have relevant certifications, awards, or credentials? | Organization | award | Low | Conditional | Formal recognitions can support trust in specific contexts. | Industry award | Only publish awards or certifications that can be substantiated. |
Freshness | date_modified | When was the public brand profile last updated? | CreativeWork | dateModified | Medium | Recommended | Freshness helps readers and crawlers understand whether the information is current. | 2026-05-26 | Update this when meaningful profile information changes. |
Language | in_language | What language is the public profile written in? | CreativeWork | inLanguage | Medium | Recommended | Language metadata helps crawlers and users interpret the page correctly. | en | Use language codes that match the page content. |
Machine readability | json_ld_output | Is the brand information available in machine-readable format? | WebPage | mainEntity | High | Core | Machine-readable data reduces ambiguity for crawlers and AI systems. | Organization JSON-LD | Structured data should match visible public content. |
Brand Structured Data Reference v1.0
This reference maps common public brand facts to structured data concepts that can help people, search engines, and AI systems understand a brand more clearly.
It is intended for independent brands, small businesses, founder-led companies, service providers, local businesses, and early-stage products that need a clearer public identity online.
This is not a ranking guide and it does not guarantee search visibility, rich results, AI recommendations, indexing, or commercial outcomes. It is a practical field map for publishing clearer and more consistent brand information.
Files
brand_structured_data_reference_v1.tsv— the main field reference.
DOI
Zenodo record: https://zenodo.org/records/20402778
Version DOI: https://doi.org/10.5281/zenodo.20402778
All-versions DOI: https://doi.org/10.5281/zenodo.20402777
Columns
section— the broad area of brand identity.field— the brand fact or signal.plain_language_question— a founder-friendly way to ask for the information.schema_org_type— the closest Schema.org type or concept.schema_org_property— the closest Schema.org property where applicable.priority— suggested priority for early brand visibility work.recommended_status— whether the field is core, recommended, contextual, or conditional.why_it_matters— why the field can help public understanding.example_value— a simple illustrative value.notes— caution or implementation notes.
Suggested Use
Use this reference to plan a public brand profile, website schema markup, entity SEO work, crawler-readable brand pages, or internal brand data collection.
For a small brand, the first priority is usually to publish the core identity fields clearly and consistently:
- Brand name
- Official website
- Short description
- Logo
- Founder or owner where appropriate
- Location or area served
- Official social links
- Main products or services
- Public credibility references
Version
Version: 1.0.0
Date: 2026-05-26
Author: Nitin Kumar Gupta, Farosio
Citation
Gupta, N. K. (2026). Brand Structured Data Reference v1.0 (1.0.0) [Data set]. Zenodo. https://doi.org/10.5281/zenodo.20402778
License
This reference is released under the Creative Commons Attribution 4.0 International License.
- Downloads last month
- 17