Schema Isn’t Appearing

If expected schema is missing, check these items in order:

1. Confirm SETN is active.
2. Confirm the page is eligible for the schema type.
3. Confirm required Business Profile or content fields are complete.
4. Review provider compatibility to see whether another supported plugin owns the schema.
5. Clear WordPress, host, CDN, and browser caches.
6. View page source and search for application/ld+json.
7. Test again with non-essential plugins disabled on staging if needed.

When contacting support, include the page URL, WordPress and PHP versions, SETN version, SEO provider, caching/CDN tools, and the schema type you expected.

llms.txt Returns a 404

First confirm which provider owns llms.txt. Then test the exact URL shown by SETN or that provider.

If the root /llms.txt URL fails, test the SETN fallback URL if one is displayed. If the fallback works, refresh WordPress permalinks under Settings → Permalinks → Save Changes, clear caches, and review server/security rules.

A 404 on llms.txt does not automatically indicate a schema or Knowledge Graph problem.

License Won’t Activate

Verify the license key, product, site limit, domain, SSL/HTTPS connectivity, and outbound WordPress HTTP access.

If all seats are in use, disconnect an old domain. If the site was migrated or cloned, refresh or reconnect the license on the new domain.

Do not send your full license key in a public ticket.

Update Isn’t Available

Confirm the license is active and eligible, then check the release channel and installed version.

Go to Dashboard → Updates → Check Again. Clear object cache or transients if your environment aggressively caches update checks.

A Beta or Release Candidate build may not be offered to a Stable-channel site.

Duplicate Schema Detected

Duplicate schema usually means more than one plugin, theme, or custom snippet outputs the same entity.

Review provider status, inspect each JSON-LD block in page source, and identify which system should own the overlapping schema type. Also inspect theme settings, WPCode, child-theme functions, and custom plugins.

Do not disable schema randomly. Make one ownership change at a time and revalidate after clearing caches.

SEO Plugin Compatibility

If compatibility status looks wrong after installing, disabling, or replacing an SEO plugin, clear caches and refresh SETN provider detection.

Confirm that the active provider and its relevant feature are actually enabled. Some SEO plugins let users enable schema or llms.txt independently.

Changes Aren’t Appearing

Reload the SETN admin screen to confirm the setting actually saved, then clear every cache layer: browser, WordPress page cache, object cache, host cache, CDN, and page-builder-generated cache where applicable.

View page source to determine whether stale HTML is still being served.

Caching & CDN Considerations

Schema is often embedded in the cached HTML response, so cached pages can continue serving old JSON-LD after an admin change.

After major SETN changes: save settings, purge WordPress cache, purge host cache, purge CDN cache, open the page in a private window, view source, and validate again.

Do not disable site-wide caching permanently unless troubleshooting proves it is necessary.

Plugin Conflicts

Common conflict categories include SEO/schema plugins, security tools, caching/optimization plugins, membership plugins, redirects, maintenance mode, REST/API restrictions, and custom code.

On staging, keep SETN active and deactivate non-essential plugins. Reactivate them one at a time until the problem returns.

If plugin testing does not identify the issue, test with a default WordPress theme on staging.

Schema Validation Shows an Error

Determine whether the message is an actual Schema.org syntax error, a missing field required by a specific search feature, or an optional recommendation.

Compare the validator message with the page content and SETN diagnostics. Do not add inaccurate data simply to silence a recommendation.

Business Information Is Incorrect in Schema

Review the SETN Business Profile first, then check whether another plugin or theme is outputting a second Organization entity with different data.

Confirm the canonical organization name, URL, logo, contact information, and location details. Clear caches after corrections.

Wrong Provider Is Detected

If SETN reports the wrong SEO/schema provider, confirm which plugins are currently active and whether old plugin files or cached endpoints remain.

Clear caches, refresh compatibility status, and disable leftover or duplicate SEO plugins. If the issue persists, provide support with the active plugin list and versions.

Site Migration / Domain Change

After moving a site, update any organization URLs that changed, clear caches, review canonical URLs, refresh compatibility status, and reconnect the license if needed.

Check Connected Domains so the old site does not continue consuming a seat unnecessarily.

Revalidate schema on important pages after DNS and CDN changes have settled.

How to Safely Test on Staging

Use staging for upgrades, provider changes, and conflict testing whenever practical.

1. Create a current production backup.
2. Refresh the staging copy if needed.
3. Prevent staging from being indexed publicly.
4. Test the SETN change.
5. Compare schema and diagnostics before and after.
6. Document the result before repeating the change in production.

Do not expose customer data, private license information, or unfinished staging content publicly.

What to Include When Contacting Support

Providing the right information helps support reproduce issues faster.

• Website URL
• SETN Schema Builder version
• WordPress version
• PHP version
• Active theme
• SEO/schema provider and version
• Caching/CDN tools
• Exact error message
• Steps to reproduce
• Screenshots or diagnostic output
• Whether the issue also occurs on staging

Never include passwords, secret keys, or full license keys in public posts.