Here is how schema markup goes wrong at most companies: someone reads that schema is good for SEO, hands the task to a developer, and the developer — who is competent and well-meaning and has absolutely no idea what the right answers are — makes a series of decisions they have no basis for making.

They decide the site represents an Organization rather than a Person, because it feels more professional. They leave the author fields blank on posts because filling them in correctly would require knowing things nobody told them. They implement Article schema on everything, including the pages that are actually FAQs, HowTos, and service offerings, because Article is the default and changing it would require understanding what the content is trying to do.

The markup is technically correct. The JSON-LD validates. The Rich Results Test passes. And the schema is still wrong, because the decisions embedded in it are wrong.

Schema isn’t a technical problem. It’s an editorial one.

What schema actually asks

The schema markup guide covers the implementation side — what types exist, how JSON-LD works, how to structure the data. That’s the how. This is the why, and more specifically, the who: who should be making these decisions, and what are they actually deciding?

When you implement schema, you are making a series of explicit declarations to Google about your content. Every one of those declarations is a positioning decision. Whether your site represents a Person or an Organization is a brand decision. Whether a piece of content is classified as an Article or a BlogPosting or an FAQPage or a HowTo is a content strategy decision. A developer can implement whatever you tell them. They cannot tell you who you are.

The declarations nobody makes deliberately

There’s a specific flavor of schema problem I see on almost every site I audit: the homepage is set to Organization when the brand is built entirely around one person’s expertise and credibility. The personal authority — the 14 years of professional history, the institutional bylines, the demonstrated expertise — is being declared away by a single dropdown choice that nobody thought about.

On the flip side, I see solo practitioners set to Organization because they thought it sounded more official. And so the Person entity that Google could be associating with their work, the E-E-A-T signals that could be accumulating around their name, are getting attributed to a ghost.

These aren’t mistakes in the schema. They’re mistakes in the thinking that preceded the schema.

Schema as content strategy

When you decide to create a series of how-to posts, you’re also deciding to implement HowTo schema. When you establish an author as a byline, you also establish them as a Person entity with a structured author page and external citations. When you choose your content types — pillar pages, case studies, FAQs, service pages — you’re also choosing your schema types.

This is not more work. It’s the same work done in the right order, by the right people, with the right questions asked upfront. That someone is an editor, not a developer.

What to do if you’ve been doing it wrong

Most sites have been doing it wrong. The good news is that schema is not a ranking factor in the traditional sense — getting it wrong doesn’t penalize you, it just means you’re leaving structured data opportunities on the table. The fix is mostly editorial clarification, not technical overhaul.

Start with the foundation: get the site representation right, the author schema right, and the page-type schema right. Those three things — Organization vs. Person, author as entity, content typed correctly — are 80% of the value.

The remaining 20% is the advanced work: FAQPage on your FAQs, HowTo on your tutorials, the advanced schema markup types that signal specific expertise to specific Google products. That work requires someone who understands both the technical format and the strategic intent behind each piece of content.

The developer is waiting for that person to tell them what to build. What happens in most organizations when schema gets filed under IT and forgotten — the accountability gap and what it costs.

---