Codedication Schema Blocks vs UTSSites Auto FAQ Schema

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 containing one @graph. Inside it, every entity has a stable @id and references the others: the WebPage node points at the site identity and the WebSite, the article points at its author, the breadcrumb trail belongs to the page, and the primary image is a node instead of a bare URL. Posts mapped to Article carry the detail a machine needs to place them: the manual excerpt as description, the word count, the tags as keywords and every category in articleSection, alongside headline, dates, publisher, primary image and the author entity. Block-level entities join the same graph. A Recipe can take its author from the post author, an Event can name your Organization as the organizer, a Product can point its brand and manufacturer at the site identity, and a Local Business block can become the site identity rather than compete with it. Optional: check your work before you publish Connect a ValidGraph account under Settings and the editor gains a validation panel: a completeness score, an AI discoverability breakdown, rich-result eligibility, errors, range warnings and the recommended fields you have left empty, per schema on the page. A small indicator on each block shows its state, and a summary appears in the pre-publish panel. It is entirely opt-in and read-only. The API key is stored on your server and every call goes through a server-side proxy, so it never reaches the browser. Skip it and the plugin emits exactly the same markup, which you can check with the Google Rich Results Test and the Schema.org Validator. It sits beside your SEO plugin Schema Blocks is not an SEO plugin and does not want to replace one. It writes structured data; Yoast SEO, Rank Math, All in One SEO or The SEO Framework keep doing titles, meta descriptions, sitemaps and redirects. If another plugin already emits the same node type, the plugin tells you: a notice on the settings screen lists the conflicts it detects. From there you either disable that schema type in the other plugin, or use the Advanced switch to stop emitting the site-level nodes here. For developers The output is filterable at every level, and the extensibility contract (1.8.0) is documented and versioned: cddc_schema_faq_output, cddc_schema_review_output, cddc_schema_recipe_output, cddc_schema_product_output, cddc_schema_event_output, cddc_schema_local_business_output, cddc_schema_howto_output, cddc_schema_jobposting_output, cddc_schema_breadcrumb_output – the node each block emits. cddc_schema_blocks_graph_nodes – the whole @graph before it is printed. cddc_schema_blocks_author_person – enrich the author Person node. cddc_schema_blocks_page_content_type – override the content type per post in code. cddc_schema_blocks_identity_extra_schema, cddc_schema_blocks_organization_schema, cddc_schema_blocks_website_schema, cddc_schema_blocks_breadcrumb_schema – the site-level nodes. Schema_Graph::flag_main_entity(), Schema_Graph::ensure_author_person() and Schema_Graph::registered_identity_id() are public seams for add-ons. The editor toolkit used by the blocks is exposed on window.cddcSchema.ui, so an add-on can build cards that look native. Blocks are registered from block.json, rendered server-side, and the FAQ accordion uses the Interactivity API with no jQuery and no custom front-end framework. Privacy The plugin generates and prints JSON-LD on your own server. Nothing is sent anywhere unless you connect a ValidGraph account with your own API key, and until you do, no request leaves your site.

UTSSites Auto FAQ Schema is the most intelligent, fully automatic FAQ schema plugin for WordPress. While other plugins make you manually enter every question and answer, this plugin reads your existing content — headings, paragraphs, bold text — and automatically generates perfect Google-ready FAQPage JSON-LD schema in seconds. Install. Activate. Done. No shortcodes. No manual work. No coding required. ⚡ Zero config. Auto detect. Unlimited FAQs. Google-ready schema. Instant rich snippets. 🏆 Why Choose UTSSites Auto FAQ Schema? ✅ Zero manual work — no questions to enter, no shortcodes to add ✅ 3 smart detection strategies — headings, paragraphs, bold text ✅ 40+ question patterns — detects any natural question format ✅ Unlimited FAQs — no artificial limits in the free version ✅ 100% Google compliant — passes Rich Results Test every time ✅ Zero performance impact — no JS, no API calls, no slowdowns ✅ Free forever — GPL open source, no license keys needed ⚡ How It Works — Fully Automatic Every time a visitor loads your page, the plugin silently: Checks eligibility — Is this post type enabled? Is this page excluded? Is schema active for this post? Scans your content — Runs 3 detection strategies in priority order Deduplicates — Removes duplicate questions found across strategies Applies limits — Trims to your configured FAQ limit and answer length Injects schema — Outputs valid FAQPage JSON-LD into your head Google indexes it — Rich snippet dropdowns appear in search results The entire process adds less than 1ms to page load. Truly invisible. 🔎 3 Smart Detection Strategies Strategy 1 — H2 to H5 Heading Detection (Highest Priority) Scans all question-style headings in your content. Any H2, H3, H4, or H5 that ends with “?” or contains a question word is automatically detected. The paragraph immediately following becomes the answer. You choose which heading levels to include from Settings. Strategy 2 — Paragraph Tag Detection No heading structure needed. If any paragraph contains a sentence starting with a question word and ending with “?”, the question is extracted automatically — and the next paragraph becomes the answer. Perfect for blog articles and natural prose. Strategy 3 — Bold / Strong Tag Detection Detects questions inside strong or b tags. Perfect for FAQ-style content where questions are bolded and answers follow in the next paragraph. ✨ Complete Free Feature List Detection & Core H2, H3, H4, H5 heading detection — choose levels individually Paragraph tag sentence detection Bold / Strong tag detection 40+ question word patterns — How, What, Why, When, Where, Who, Which, Can, Could, Is, Are, Was, Will, Should, Does, Did, Tell me, Explain, Define, Describe, Give me, Show me, and more Detect questions without “?” — detect question-word headings even without question mark Hash-based smart deduplication — identical questions appear only once Answer auto-extraction — next sibling element becomes the answer automatically Schema Output Valid FAQPage JSON-LD schema — schema.org fully compliant Passes Google Rich Results Test — 100% validation Injected into head via wp_head hook Proper JSON encoding with special character escaping Configurable max and min answer length Settings & Control Global enable / disable toggle Post type selection — Posts, Pages, Products, Custom Post Types Heading level toggles — H2, H3, H4, H5 individually Paragraph detection toggle Bold detection toggle Unlimited FAQs per page — no artificial cap Max answer length in characters Min answer length filter — skip very short answers Exclude specific post/page IDs Custom question patterns — add your own Per-Post Control Sidebar meta box in every post and page editor Per-post schema disable toggle Per-post custom FAQ limit override Live FAQ preview — see detected questions before publishing Full JSON-LD preview per post Live Schema Preview Bulk preview of recent posts in Settings page FAQ List tab — human-readable question and answer list JSON-LD tab — exact raw schema code injected into page head FAQ count badge Compatibility WordPress 5.5 to 6.9 PHP 7.4+ Gutenberg Block Editor Classic Editor Elementor, Divi, WPBakery, Beaver Builder WooCommerce product pages Rank Math SEO — conflict-safe Yoast SEO — conflict-safe WPML, Polylang — multilingual ready All major caching plugins Multisite compatible No external dependencies — zero external API calls GPL-2.0+ open source 📈 Why FAQ Schema Matters for Your SEO Google displays FAQ rich snippets for content with valid FAQPage schema. These expandable dropdowns appear directly below your search listing: 2 to 5x more SERP visibility — your listing dominates the page Higher Click-Through Rate — more screen space means more clicks Lower bounce rate — users who click already know what to expect Competitive advantage — most sites still don’t use FAQ schema 💎 Pro Version — For Serious SEO Professionals 👉 View All Pro Plans & Pricing FAQ Management (Pro) Manual FAQ Builder with Drag & Drop Reorder Custom Answer Override per FAQ Export / Import FAQs in JSON format Broken FAQ Detector Answer Length Optimizer Smart FAQ Score — Excellent / Good / Fair / Poor rating FAQ Templates Library — 6 niche templates AI-Powered Features (Pro) AI FAQ Suggestions — Google Gemini AI FAQ Suggestions — Groq (Llama) AI FAQ Suggestions — OpenAI GPT-4 Tone-Aware AI — Medical, Legal, Tech, eCommerce AI FAQ Quality Check PAA Suggester — Google Autocomplete Long-tail Question Suggester Advanced Schema Types (Pro) HowTo Schema with HowToStep support QAPage Schema Video FAQ Schema — YouTube integration Article + FAQ Combined Schema Schema Expiry Date Conditional Schema Rules per category or tag One-Click Google Rich Result Test Schema Validator in-plugin Rank Math / Yoast Conflict Handler Integrations & Analytics (Pro) Google Search Console Integration Analytics Dashboard + CSV Export FAQ A/B Testing Gutenberg FAQ Accordion Block Elementor FAQ Widget FAQ Shortcode + Widget WooCommerce Advanced Integration REST API (4 endpoints) Zapier / Webhook White Label — Full Rebrand Client PDF Reports Multi-site Network Support Priority Support + All Future Updates Pricing Starter — $19/yr — 1 site Pro — $49/yr — 3 sites (Most Popular) Agency — $99/yr — Unlimited sites Lifetime — $199 one-time — Unlimited sites, all future features forever 👉 Get Pro Today