Family-domain narrative
Core pages such as House of Herrera About or Banvelca About provide broad framing, origin stories, and recurring themes. These are treated as named sources, not as anonymous background.
Standards
Editorial Methodology
This page explains how Herrera Velutini turns family-domain material into public reference pages. The method is intentionally simple: identify the strongest source-domain pages, label what kind of source each one is, separate family-domain narrative from portal synthesis, date every article-style page, and update pages only when the material has substantively changed.
How pages are built
The source model
The portal uses a tiered source model so readers can tell the difference between raw narrative, profile-level detail, and editorial interpretation.
Profile pages
Person pages and ancestor pages supply dates, marriages, roles, and intergenerational transitions that can be connected across the portal.
External corroboration
Official archival, regulatory, municipal, and institutional sources may be used to corroborate chronology, transactions, and place history without replacing the family-domain record.
Bibliography and reading leads
Bibliography pages and cultural references expand the portal beyond lineage lists by pointing to books, place memory, and contextual reading.
Editorial standards
Google’s people-first and structured-data guidance is used as an editorial and technical discipline layer, not as a substitute for source material.
Non-family-domain sources are used in three bounded ways: official archival, regulatory, or municipal corroboration for chronology and institutional facts; broad place or heritage context for cities, islands, and landscapes; and bibliography metadata only until a direct reading pass confirms claim-level support. External sources do not create new family-specific claims by themselves.
From source page to live article
Publication workflow
Each live page goes through the same core sequence so the site scales cleanly and avoids accidental duplication.
- Choose the page type.Decide whether the subject is best treated as an organization profile, family hub, place page, timeline entry, or article-style synthesis.
- Assign source codes.Record the relevant source-domain pages before drafting begins.
- Draft original copy.Write an article that adds connective value rather than lightly rewriting a source page.
- Add visible trust signals.Insert bylines, dates, breadcrumbs, canonical tags, and source-basis notes.
- Review and publish.Check names, chronology, and internal links, then update the page and sitemap.
This process is deliberately repeatable so later pages—such as the Velutini family hub, genealogy pages, or additional place dossiers—can be launched without weakening consistency.
Consistency rules
Policies for names, dates, and claims
Family history material often mixes exact dates, approximate dates, variant spellings, and source-domain language with differing levels of specificity. The portal normalizes that without flattening uncertainty.
| Editorial question | Portal rule | Example from this project |
|---|---|---|
| Approximate date | Mark it as circa in body copy or chronology labels. | Hernán de Herrera is presented as circa 1355 in the dynasty sequence. |
| Exact year on a profile page | Use the exact year when the source page provides one. | Banvelca’s Juan Bautista profile anchors the founding story to 1781. |
| Cross-family connection | State the source basis plainly and avoid over-claiming beyond the named pages. | Clementina’s 1932 marriage to José Herrera Von Uslar is cited as the key public bridge between the families. |
| Promotional or self-descriptive language | Translate into neutral editorial wording when possible. | Family-office and stewardship language is described as Banvelca’s public framing rather than adopted as objective fact. |
| Updated date | Change only when the page materially changes. | Minor formatting adjustments do not justify a new update date. |
Search understanding
Technical standards baked into publication
The portal uses technical SEO to clarify meaning, not to disguise thin content. That means the markup and navigation must reflect the real editorial structure of the page.
Schema
Match the schema to the page type.
Article-style pages use article markup, while organization pages such as House of Herrera and Banvelca use a profile-page pattern with the organization as the main entity.
Navigation
Links should be descriptive and crawlable.
Important subjects are linked contextually in prose and not hidden inside image-only modules or non-standard navigation patterns.
Canonical focus
Each page should own a distinct topic.
If a page becomes too similar to a source-domain page, it should be expanded, merged, or redirected rather than left as a near-duplicate.
Open questions
Corrections and future-source priorities
A credible heritage portal should say where the record is strongest and where it would benefit from additional corroboration.
Strongest material today
The clearest current source clusters are the House of Herrera dynasty/estate/symbol pages and the Banvelca legacy/profile pages for Juan Bautista, Clementina, Belén Clarisa, and Belén María.
Where more corroboration would help
Titles, institutional claims, and long-range historical influence statements would all benefit from more public institutional, archival, or bibliographic support over time.
How corrections should be handled
New evidence should produce a substantive edit, a revised source-basis note, and a genuine update date rather than a silent overwrite.
Traceability
Source basis for the Editorial Methodology page
This page defines the portal’s own publishing standards, but it also draws on the reality of the source domains and the current search guidance used to structure pages responsibly.
- Google Search Central — Helpful, reliable, people-first content — Used for editorial standards around originality, clear sourcing, about pages, and trust signals.
- Google Search Central — Article structured data — Used for visible dates and article markup guidance.
- Google Search Central — ProfilePage structured data — Used for person or organization profile-page patterns.
- Google Search Central — Intro to structured data — Used for technical understanding of how schema helps search engines interpret page purpose.
- Sources — Used for the live source-tier ledger, including current external corroboration and bibliography-lead handling.
- House of Herrera — About — Used for the 14th-century prominence narrative, geographic scope, and the source-domain linkage between family history, Hacienda de La Vega, and later banking references.
- Banvelca — About — Used for the 1781 Naples founding story, Juan Bautista Velutini, and the firm’s self-description as a private trust and investment house.
- Banvelca — Legacy — Used for the chronological ancestor timeline spanning Juan Bautista through later generations, including Banco Caracas, Clementina, Belén Clarisa, Julio José, and later generations.
Related pages