
內容簡介
Codedication Schema Blocks 外掛提供結構化資料的功能,讓使用者能夠在編輯器中直接撰寫內容,並自動生成 JSON-LD 標記,確保訪客與搜尋引擎所讀取的資料一致,提升網站的 SEO 效果。
【主要功能】
• 九種內容區塊:FAQ、評價、食譜等
• 自動生成 JSON-LD 標記
• 直觀的設定介面與即時預覽
• 支援多種豐富結果類型
• 作者資料的結構化管理
• 內容與搜尋引擎標記一致性
外掛標籤
開發者團隊
原文外掛簡介
Structured data that lives with your content
Most schema plugins park your structured data somewhere else: a metabox, a separate settings screen, a template file. The page says one thing, the markup says another, and nobody notices until a rich result quietly disappears.
Schema Blocks works the other way round. You write the recipe, the FAQ, the product details or the job ad as blocks in the editor, and those same blocks emit the JSON-LD. What a visitor reads and what a search engine parses come from the same source, so they cannot drift apart.
Nine blocks for the things people actually publish
FAQ – questions and answers in a native accordion. Visitors get a real disclosure widget, machines get FAQPage / Question / Answer markup they can read.
Review – review snippets with a 1-5 rating for products, books, movies, restaurants, local businesses or any Thing. Pros, cons, rating explanation, and book details (author, publisher, ISBN, page count, external identity URLs) when the reviewed item is a book.
Recipe – recipe rich results built from inner blocks: ingredients, instructions and nutrition are content on the page, not hidden fields. Plus prep, cook and total time, yield, category, cuisine, keywords and rating.
Product – product rich results with price, currency, availability, condition, SKU, GTIN and MPN, brand, manufacturer and aggregate rating.
Event – event rich results with start and end dates, attendance mode, status, a physical or virtual location, organizer and ticket offers.
Local Business – local business markup with subtype (Restaurant, Store, ProfessionalService and dozens more), address, geo coordinates, telephone, price range, cuisine served and opening hours.
How-To – ordered steps with images, estimated cost, total time, tools and supplies, described in the page itself.
Job Posting – job posting rich results with employment type, hiring organization, location, posting and validity dates, and base salary.
Breadcrumb – breadcrumb markup generated from your site hierarchy, or a manual trail when the hierarchy does not match the story. Where the block is used it replaces the site-wide trail, so a page never emits two.
Configure the site once
The Settings screen holds everything that belongs to the whole site, with a live JSON-LD preview and a completeness ring next to it:
Site Identity – Organization or Person, with name, logo, description, contact details, address, social profiles and founding year.
WebSite – site name, alternate name, description, language and the search action.
Breadcrumbs – the site-wide BreadcrumbList, with separator and home label.
Content – map each public post type to Article, Blog posting or nothing. Posts default to Article, so a normal blog is marked up correctly the moment you activate the plugin.
Blocks – switch off the blocks you do not use. They leave the inserter and stop emitting anything.
Advanced – Wikidata ID, Wikipedia URL, legal name, VAT ID and employee count for organizations; job title, credentials and ORCID, LinkedIn or ResearchGate profiles for people; areas of expertise for either, emitted as knowsAbout. There is also a switch that suppresses the site-level nodes when another plugin already emits them.
Validgraph – the optional validation connection described below.
Your authors are people, not strings
An author name typed into a field is text. An author entity is something a search engine can recognise across your site and beyond it.
Every WordPress user gets a Schema – author profile section on their profile screen:
Job title, honorific prefix, credentials and areas of expertise.
sameAs URLs: LinkedIn, ORCID, Wikidata, a personal site.
Where they studied (alumniOf) and which colleagues they work with, picked from the other authors who have a profile, so the Person nodes reference each other.
An avatar override, and two opt-ins that tie the author to the site organization: member of it (worksFor) and founder of it.
Those fields enrich the Person node referenced by every article that user writes, down to givenName and familyName taken from their WordPress first and last name. Their author archive is typed as ProfilePage, and the Organization node lists the authors who opted in as employee and founder: the full roster on the front page, the current author elsewhere.
This is about being unambiguous, which is what E-E-A-T signals are made of. Nobody can promise you a ranking from it.
Per-post control when the site-wide rule is wrong
A Schema panel in the document sidebar overrides the defaults for a single post or page:
Content type – Article, Blog posting, News article, or none, whatever the post type mapping says.
Page type – About page, Contact page, Profile page, Item page or Collection page.
There is also a smart rule you never have to configure: when the main content of a page is a schema block, that entity becomes the page’s mainEntity instead of a redundant Article node.
One connected graph, not a pile of snippets
The plugin prints a single
