THE GRAPH SERIES / Search. Structure. Content.Meet your intelligence stack
Appearance Circadian
Choose your theme

Circadian: Light 6 AM–6 PM. Dark 6–10 PM and 2–6 AM. Agentic 10 PM–2 AM. Motion settings always take priority.

Field notes / Structured data

Manual schema markup or a generated entity graph: compare the maintenance, not the markup

Both approaches end at the same place: structured data in the page. The difference is where the truth lives. Manual markup keeps it inside each page, edited one file at a time. A generated graph keeps it in one entity model that pages are rendered from. The right choice depends on how many pages, products, and editors that truth has to survive.

YOUR NEXT STEPCHOOSE A GOAL
What would be useful next?

The short answer

Both approaches produce the same markup on day one. They differ in where the truth lives: inside each page, edited file by file, or in one entity model that pages are generated from. Choose by how much change the truth has to survive…

  1. 01 / Establish the context
  2. 02 / Review the right fit
  3. 03 / Take the next step

Your choice stays on this page. No click or selection tracking.

01

The short answer

Manual markup is a writing task: a person who understands the page adds the structured data that describes it. A generated entity graph is a modeling task: the entities and their relationships are defined once, and each page's markup is produced from that model.

Neither changes what schema is. They change who, or what, keeps it true as the site changes.

For a handful of stable pages, manual markup is honest, fast, and sufficient. The case for generation appears with scale and change: many pages describing the same entities, facts that move, and more than one hand editing. That is where page-by-page truth quietly becomes several truths.

02

Decision criteria

  • How many pages describe the same entities: the business, its products, its locations?
  • How often do the underlying facts change: names, offers, addresses, people?
  • How many people or tools produce and edit pages?
  • What happens when two pages disagree about the same entity, and who would notice?
  • Can you validate the whole graph at once, or only one page at a time?
  • What will this site look like after the next redesign or migration?
03

Side by side

Same output, different operating cost. The rows are where the decision actually lives.
DimensionManual markupGenerated entity graph
Source of truthEach page's markup, edited in placeOne entity model; pages rendered from it
ConsistencyDepends on every editor remembering every pageEnforced by the model; conflicts surface at generation
Cost of a changed factFind and edit every affected pageChange the model; regenerate the affected pages
ValidationPer page, mostly syntaxWhole graph: identifiers, relationships, contradictions
Startup costLow; the first page can be marked up todayHigher; the model has to be designed first
Failure styleQuiet drift between pagesA model error propagates, visibly, until fixed
04

Tradeoffs that decide it

Manual markup fails quietly. Nothing breaks; the graph simply stops agreeing with itself, one forgotten edit at a time, and the disagreement is usually discovered by a machine resolving the wrong entity. A generated graph fails loudly: a modeling error appears everywhere at once, which is uncomfortable and useful, because it is found in validation instead of in production behavior.

Most real sites land in between. Recurring entities (the business, products, locations, people) belong in a model where they can be kept consistent. One-off pages can carry careful hand-written markup. The discipline is knowing which is which, and auditing the result as one graph either way.

The schema markup guide
05

A worked comparison on one page

Take one service page. The manual way is to write the JSON-LD by hand: a WebPage node, a Service node, the Organization, and a BreadcrumbList, each field filled in from the page. A careful pass takes about an hour, and the result is exact — because a person who understands the page wrote it. The cost arrives later: every change to the service means editing the block, and every new page means writing another one.

The graph way is to define the entities once. The service, the business, and the relationship between them are stated in a model. Each page’s markup is then produced from that model, so the service page, the services index, and the related guides all describe the same service in the same words. A change to the service is one edit to the model, and every page that references it updates. The cost arrives first: the model has to be built, and it has to be right, before any page benefits.

Manual wins when the site is small and stable — one page, a few entities, content that rarely changes. The graph wins when the site is large, when entities are shared across pages, or when the content changes often. The migration path is to start with the manual block, extract the entities into a model, generate from the model, and keep the manual block as the reference until the generated output matches it. SchemaGraph examines the graph the pages describe, whichever way the markup was produced, so drift and contradiction are visible before you choose an approach.

The choice is not about which method is more correct. Both produce the same structured data when they are done well. The choice is about where the work is paid: a little at a time, on each page, or once, in the model, and then never again for that entity.

The model also outlives any single page. When a page is redesigned or a service is renamed, the model stays, and the new page is generated from it. The manual block is rewritten from scratch.

06

Common questions

Does generated markup rank better?

Markup describes; it does not rank by itself. The gain from generation is consistency and maintainability across many pages, not a more powerful tag.

Can I start manually and switch later?

Yes. Carefully marked-up pages are the inventory the entity model gets built from, so early manual work is not wasted, provided the facts in it are accurate.

Where does SchemaGraph fit?

SchemaGraph examines the graph your pages describe, whichever way the markup was produced, so drift and contradiction are visible before you choose an approach.

Accessibility & reading

Adjust this site to your needs. Preferences stay on this device. Your browser’s zoom and assistive technology continue to work.

Reading text size

100%

100%, 112%, 125%, or 150%. You can also use your browser’s zoom.

Reading preferences

Motion and attention

Your device’s reduced-motion setting takes priority.

Need another way to access something?

Tell HGM the page, the task, the barrier, and your preferred format or way to communicate. You do not need to share medical details or create an account.

No analytics, retargeting, advertising pixels, tracking identifiers, or sale of visitor data. These controls use local device storage only.

These optional controls support access. They do not replace accessible page design or an individualized accommodation process.

Find your next step.

Marketing Intelligence Infrastructure | Holistic Growth MarketingCompany & ecosystemAbout HGM | Holistic Growth MarketingCompany & ecosystemCompany Profile | Holistic Growth MarketingCompany & ecosystemServices | Holistic Growth MarketingCompany & ecosystemGraph Series | Holistic Growth MarketingGraph SeriesSchemaGraph | Holistic Growth MarketingGraph SeriesSearchGraph | Holistic Growth MarketingGraph SeriesCopyGraph | Holistic Growth MarketingGraph SeriesSearch Intel OS | Holistic Growth MarketingCompany & ecosystemPlatform Architecture | Holistic Growth MarketingCompany & ecosystemMarketing Intelligence Infrastructure | Holistic Growth MarketingCompany & ecosystemData Governance | Holistic Growth MarketingCompany & ecosystemDeployment Architecture | Holistic Growth MarketingCompany & ecosystemCustomer-Controlled Data Infrastructure | Holistic Growth MarketingCompany & ecosystemCRM Integrations | Holistic Growth MarketingCompany & ecosystemIntelligence CRM | Holistic Growth MarketingCompany & ecosystemPricing and Engagements | Holistic Growth MarketingCompany & ecosystemGraph Series Subscriptions | Holistic Growth MarketingCompany & ecosystem