SETN Schema Builder

SETN Schema Builder helps WordPress websites create AI-ready structured knowledge using JSON-LD, connected entities, services, topics, FAQs, semantic relationships, Schema Health diagnostics, and llms.txt. It can work alongside popular SEO plugins or operate as a standalone structured-data system, helping search engines and AI systems better understand what your website, organization, and content are about. What SETN Schema Builder Does SETN Schema Builder helps WordPress websites create a clearer, more connected layer of structured knowledge for search engines, AI systems, and other machines that need to understand what your site is about. Instead of treating schema as a collection of disconnected markup blocks, SBP helps organize important information about your business, services, topics, FAQs, and related entities into a more consistent knowledge structure. The Free edition includes tools for:

• Business and organization identity
• Service information
• Schema Topics
• Semantic relationships
• JSON-LD structured data
• FAQ schema
• llms.txt
• Schema Health and diagnostics
• Compatibility with existing SEO and schema plugins

How It Works SBP adds a structured knowledge layer inside WordPress. You configure your core business information, services, topics, FAQs, and other important entities. SETN Schema Builder then uses that information to create machine-readable relationships and structured data that can help search engines and AI systems better understand the context of your website. SBP can work in two primary ways: Compatible Mode Use SBP alongside supported SEO and schema plugins such as Yoast SEO, Rank Math, AIOSEO, and SEOPress while reducing unnecessary overlap. Standalone Mode Use SETN Schema Builder as the primary structured-data system when another schema provider is not managing the site. SBP also provides Schema Health tools so you can review how your structured knowledge is configured and identify missing or incomplete information. Why You Need It Traditional SEO helps search engines discover and evaluate pages. Structured data helps machines understand what those pages mean. AI search, answer engines, search engines, assistants, and other machine-readable systems increasingly rely on clearly defined entities, relationships, and context. A typical business website may contain information about:

• The organization
• Services
• Locations
• Authors
• Products
• FAQs
• Subjects and topics
• Relationships between those entities

That information often exists across different pages without a consistent machine-readable connection between it. SETN Schema Builder helps connect those pieces. The goal is not to promise rankings, citations, or AI visibility. The goal is to make your website's important information more explicit, consistent, connected, and machine-readable. Built to Work With Your SEO Stack You do not necessarily have to replace your existing SEO plugin. SETN Schema Builder is designed to coexist with common WordPress SEO and schema tools. When another supported provider manages core schema, SBP can focus on supplemental structured knowledge such as services, topics, relationships, FAQ information, and AI-discovery features. Your SEO plugin helps optimize pages. SETN Schema Builder helps machines understand the knowledge behind those pages. This allows SBP to complement your existing SEO stack instead of forcing you to rebuild it. AI-Ready Without the Hype SETN Schema Builder does not guarantee AI citations, search rankings, crawler access, or inclusion in AI systems. Instead, it gives WordPress site owners a practical way to improve the structure, consistency, and clarity of the information they make available to machines. SBP is designed to help create a stronger machine-readable foundation for modern search, structured data, knowledge graphs, and AI discovery. Key Features

• Business and organization identity management
• Service schema and structured service information
• Schema Topics for semantic subject organization
• Semantic relationships between important site entities
• JSON-LD structured data generation
• FAQ schema support
• llms.txt generation and delivery
• Schema Health diagnostics
• AI Discovery status and diagnostics
• Provider-aware compatibility
• Standalone schema mode
• Service-area business support
• Built-in documentation and setup guidance

Free distribution and privacy SETN Schema Builder is developed by SE TN Consultants. In Compatible Mode, overlapping provider-owned core entities are deferred while independently valid supplemental entities may still be emitted, including FAQPage, Service, DefinedTerm, and DefinedTermSet entities without guessing provider identifiers. Free creates the structured-knowledge foundation. Map foundational entity and Topic relationships, inspect the Entity and Relationship registries, and publish connected AI-ready structured data. Automatic related-content discovery, confidence scoring, Pin/Ignore curation, and prioritized relationship recommendations require a separately distributed Pro or Agency edition. The WordPress.org edition contains no license client, private updater, or paid-feature implementation. Updates are delivered only by WordPress.org. Commercial SETN Schema Builder editions are distributed separately and may add licensed intelligence features and direct private updates. The Free edition makes no external licensing or commercial service calls during normal operation. The Updates & Resources screen uses WordPress.org for update checks. No license, registration, mailing-list signup, time limit, or usage quota is required. Optional news and commercial-edition links are normal links and do not automatically transmit the site domain, administrator email, configuration, or diagnostics. Free includes a cacheable /llms.txt assembled from bounded public SBP Organization, Service, Topic, and eligible FAQ knowledge. The shared delivery layer maintains an ownership-verified physical fallback when SBP owns the endpoint, without registration or licensing. It never overwrites an unverified public file and does not crawl or publish arbitrary WordPress content. Configured public organization and contact information may intentionally appear in frontend JSON-LD and /llms.txt. Deleting the Free package preserves customer settings, Topics, relationships, entity identities, FAQs, and content because the commercial licensing-only uninstall routine is excluded.

1. Install and activate SETN Schema Builder from WordPress.org.
2. Open SETN Schema Builder > Settings and complete the Business Profile.
3. Choose Standalone Mode when SBP should own JSON-LD, or Compatible Mode when a supported schema provider should own it.
4. Configure Services and optional Schema Topics.
5. Enable FAQPage only after selecting a page that visibly contains the configured questions and answers.
6. Review Schema Health.
7. Use Updates & Resources for WordPress.org update status, documentation, and optional news or upgrade links.

Network activation is not supported in v1. On Multisite, activate and configure SBP separately per site.

1.0.1

• Restores the shared entity registry and graph validator omitted from the WordPress.org 1.0.0 publication, fixing fatal activation.
• Adds complete package inventory, dependency, syntax, runtime, and upgrade release gates.
• Preserves existing settings, Topics, relationships, schema output, and license-independent Free updates.

1.0.0

• Corrects Service applicability, decoded schema titles, description fallback, address privacy controls, and neutral public Topic naming.
• Adds a conservative allowlisted Organization/business type setting while preserving the legacy ProfessionalService default.
• Connects supported supplemental Service and Topic entities through documented Yoast SEO and Rank Math graph filters without guessing provider IDs.
• Preserves the shared Free foundation, package boundaries, hybrid /llms.txt delivery, and all saved customer data.

1.0.0-rc3

• Standardizes the public company, product, attribution, slug, and text-domain naming for release.
• Finalizes the WordPress.org readme, screenshot captions, Free update-list destination, and RC3 package metadata.
• Adds a packaged admin-menu icon and keeps the absolute llms.txt filesystem path out of the normal Schema Health view.
• Preserves RC2 licensing, update delivery, package separation, saved data, and hybrid /llms.txt delivery behavior.

1.0.0-rc2

• Finalizes Free foundational relationships while reserving automatic discovery, scoring, recommendations, and Pin/Ignore curation for Pro and Agency.
• Ensures the WordPress.org package contains the polished locked presentation but no operational paid discovery implementation.
• Preserves Topics, registries, schema output, settings, and existing relationship data through package replacement.

1.0.0-rc1

• Adds release-candidate packaging, WordPress compatibility, compliance, readme, and SHA-256 verification gates without adding product features.
• Keeps the public Stable tag at the numeric 0.9.5 release until final 1.0.0 publication.

0.9.5-beta

• Reports generic schema mode and exact detected SEO/schema provider separately.
• Reports whether SETN Schema Builder or another provider owns /llms.txt and keeps SBP knowledge/schema features active when deferred.
• Detects physical public llms.txt files before WordPress rewrites, attributes bounded All in One SEO and Yoast signatures, and reports unknown files conservatively without mutation.
• Preserves the curated FAQ Q&A, complete Organization description, raw Markdown links, real newlines, and targeted cache behavior introduced in v0.9.4.

0.9.4-beta

• Adds curated AI-readable /llms.txt, a shared read-only public knowledge layer, targeted per-site caching, and factual Schema Health visibility. llms-full.txt and public/write Abilities remain deferred.
• Includes exact curated FAQ questions and answers after public-page eligibility verification, with clean Markdown and word-safe bounded text.
• Preserves an existing provider's /llms.txt rewrite and reports factual route ownership in Schema Health.

0.9.3-beta

• Adds durable Service identities, authenticated commercial package checks, explicit Multisite policy, bounded frontend relationship behavior, expanded provider compatibility, and separate Free/commercial release artifacts.