Disable default Schema

Hola @jmzolezzi

Thanks for the kind words, and this is a good request.

What you can do today, with the version you have installed:

Go to ‘Visibility → Discover → Meta tags and structured data’ and uncheck ‘JSON-LD: Article and BreadcrumbList’. The emitter is not even loaded after that, so no structured data is written on your posts and pages. Then, leave “Site Identity” checked, further down the same tab: it only writes the Organization and WebSite JSON-LD on your home page (or on the page you choose in “Output page”), never anywhere else. If you also want the author archives clean, uncheck “JSON-LD: Person on author archives”.

I have just tested that exact setup on a clean install: posts and pages serve zero JSON-LD blocks, the home page still serves Organization, WebSite and SearchAction. So the result you described is available right now.

Two things to know before you flip it, because that switch is a blunt one: it also drops the BreadcrumbList, which is what feeds the breadcrumb trail in Google results, and the FAQPage block rides in the same graph, so it goes off with it.

And what you actually asked for, which is finer control, is going to be built. In the next release, the schema type selector gains a None option, both per content type in the Discover tab and per entry in the Schema type field of either editor. Picking None is a full withdrawal on that content: no Article or WebPage, no BreadcrumbList and no FAQPage, so a specialised schema plugin owns the document with nothing competing with it. You can leave pages to your other plugin while keeping Article on posts, or hand over a single page, and a single entry can always opt back in by choosing a real type. Site Identity stays a separate setting either way, so Organization on the home page keeps working.

It is version 2.6.0, already finished and tested, going out shortly. Thanks for asking for it, that is where it came from.

Fernando

You are right, and this one is on us rather than a preference of yours.

The author node belongs to the Article family. Visibility was adding it to every page type as well, which is not what the rest of the ecosystem does: other plugins documents the same property on its WebPage piece as conditional, only for pages with explicit authorship such as a native Post, and Google’s Article rich result covers Article, NewsArticle and BlogPosting, never WebPage.

On a contact page or a legal notice it published whoever created the entry plus a link to its author archive, a URL that exposes the user slug and that many sites do not even serve. wordCount, articleSection and keywords were already restricted to Article types; author was not, and that was an oversight.

Also, a heads-up so 2.6.0 does not disappoint you: the None option retires the whole graph on that content, breadcrumb included. It is for handing a content type over to a specialised schema plugin, not for dropping one field.

What you asked for is in 2.6.1: pages no longer carry the author, and they keep their BreadcrumbList. If some of your pages are signed editorial work, a new Discover toggle, “JSON-LD: author on pages”, brings it back.

You can re-enable “Structured data on singulars” once you update, and you get your breadcrumbs back without the author on pages.

Fernando