Add schema.org metadata to whitelisted markup

  • Unknown's avatar
    pinglaura · Member ·

    I am frustrated to learn that the simple Schema.org HTML metadata is being stripped out of html content in posts and pages. This is structured data that is very helpful for content indexing.

    To be specific, what I’m finding is that everything within <meta> element parameters gets stripped, leaving only the plain text contained within the elements.

    Example using the Schema.org book type (cf. http://schema.org/Book):

    One one of my Premium Plan sites, I have book listings with structured metadata I want to include in the pages listing each. Here is the kind of thing I’m trying to paste in:


    <ul class="book-meta" itemscope itemtype="http://schema.org/Book">

  • <link itemprop="bookFormat" href="http://schema.org/Hardcover">Hardcover ISBN:</link> <span itemprop="isbn">978-0-9912667-5-3</span>
  • <link itemprop="bookFormat" href="http://schema.org/Paperback">Paperback ISBN:</link> <span itemprop="isbn">978-0-9912667-4-6</span>
  • <link itemprop="bookFormat" href="http://schema.org/Paperback">Large-Print Paperback ISBN:</link> <span itemprop="isbn">978-1-193194-14-8</span>
  • <link itemprop="bookFormat" href="http://schema.org/EBook">EBook ISBN:</link> <span itemprop="isbn">978-0-9912667-8-4</span>
  • <meta itemprop="genre" href="https://www.bisg.org/bisac/bisac-subject-headings-list-fiction">Fiction / Historical</meta>
  • <meta itemprop="genre" href="https://www.bisg.org/bisac/bisac-subject-headings-list-fiction">Fiction / Fantasy / Historical</meta>
  • <meta itemprop="genre" href="https://www.bisg.org/bisac/bisac-subject-headings-list-fiction">Fiction / Horror</meta>

    • What gets through in publishing, however, is only:


    <ul class="book-meta">

  • Hardcover ISBN: 978-0-9912667-5-3
  • Paperback ISBN: 978-0-9912667-4-6
  • Large-Print Paperback ISBN: 978-1-193194-14-8
  • EBook ISBN: 978-0-9912667-8-4
  • Fiction / Historical
  • Fiction / Fantasy / Historical
  • Fiction / Horror

    • Even <span itemprop="isbn"> gets stripped out.

    Can there really be security concerns about simple html values do not load remote content? (Google even

    Please whitelist this.

    Being able to use structured metadata—and it doesn’t have to be Schema, it could be Dublin Core or any structured data Google recommends—would add great SEO value to WordPress.com-hosted blogs that can take advantage of it.

    Imagine the value of having WordPress.com-hosted sites showing up with rich data in search engine results for recipes, books, music, photography.

    (Before someone replies with “upgrade to a Business Plan”, let me say that most creative artists, recipe sharers, etc. are living in the long tail of the web. Tripling the monthly cost of a website is nontrivial to most of us who are just trying to put our creativity out there. What I am proposing is a simple modification to whitelisted html tags.)

    I’ve seen this request posted in the forums here every few years. One response in 2016 said this was being considered because of the SEO value. I ask that this be considered now. No risk (that I am aware of) with great upside, yes?