Your CMS schema, mapped automatically.
SemlyPro crawls your CMS schema once and maps every published article to the right fields, content types, and taxonomies. No manual mapping. No field-config screens. Zero per-article setup.
AI Overview answer block
What is auto schema detection?
Auto schema detection is the process of automatically discovering a CMS’s content model — custom fields, content types, taxonomies, references — and mapping incoming articles into the correct shape without manual configuration.
Critical for headless CMSes (Sanity, Contentful, Strapi) where every project has a unique custom schema, and for multi-brand teams managing dozens of distinct CMS structures.
Sanity, Contentful, Strapi schemas auto-detected.
Brand-specific fields mapped without per-article setup.
Categories, tags, and references auto-populated.
Trusted by content teams winning AI search
Why now
Manual schema mapping is the hidden tax of headless CMSes.
Every Sanity, Contentful, or Strapi project has a unique custom schema. Most publishing tools require manual field configuration per article. The setup tax kills the workflow.
SemlyPro maps your full CMS schema in seconds, once per connection.
You never see a field-mapping screen. The schema is detected, applied, done.
Including Sanity, Contentful, Strapi — the tricky ones.
The closed-loop difference
Other publishers ask you to map fields. SemlyPro just maps them.
Letterdrop, Beehiiv, ContentKing all require manual field configuration per CMS connection. SemlyPro auto-detects everything in one schema crawl.
Capability
Manual-mapping publishers
SemlyPro
How it works
From CMS connect to mapped schema.
01
Connect
OAuth or API token to your CMS. Five-second setup.
02
Crawl schema
We query the CMS’s schema endpoint and discover every content type, field, and reference.
03
Map fields
Article H1 → title field. Body → portableText/blocks. Featured image → OG image field. Tags → taxonomy refs.
04
Apply forever
Future articles auto-populate every field correctly. No per-article mapping ever again.
What’s inside
Six pillars of zero-config publishing.
Schema endpoint crawl
Sanity GraphQL schema, Contentful Content Model API, Strapi /api endpoints — all crawled on connect.
Field-type aware mapping
String, slug, image, reference, portableText, rich-text — each field type mapped to the right article field.
Custom field support
Brand-specific fields (e.g., "authorDisplayName" or "callToActionColor") detected and populated from brand kit.
Taxonomy auto-population
Categories, tags, content groups — populated from article H2 headings + entity extraction.
One-click field override
Auto-detection is the default. Override per field if your CMS has quirks. Saved as defaults for future articles.
Re-detect on schema change
CMS schema changed? Click re-detect. We diff the new schema and apply changes without breaking past articles.
Who it’s for
Built for teams running real production CMSes.
No more per-CMS YAML config files. Auto-detection just works.
Zero config files
You never see a field-mapping screen. Just write and publish.
Zero per-article setup
Connect 50+ client CMSes without per-client field-mapping ceremonies.
50 CMSes in one workspace
Each brand has its own Sanity workspace? Each one auto-detected separately.
Multi-CMS, one workflow
Customer proof
Real schemas detected. Real time saved.
Hero case study
How [Customer] cut 8 hours of monthly setup
Managing 12 client Sanity workspaces, [Customer]’s previous publishing tool required 30 minutes of field mapping per client. SemlyPro auto-detected all 12 schemas in under a minute. Net savings: 8 hours/month of pure ops work.
“I used to dread connecting a new Sanity workspace. SemlyPro made it a click.”
“The re-detect-on-schema-change feature saved us when our dev team renamed three fields.”
Pricing
Auto schema detection, from $149/mo.
Every plan includes the full closed loop — research, generation, and publishing to 12 CMSes.
Business Pro
Growing teams & agencies
Full plan includes the closed loop
FAQ
auto schema detection, questions answered.
Automatically discovering a CMS’s content model — custom fields, content types, taxonomies, references — and mapping incoming articles into the correct shape without manual configuration.
All 12: WordPress (custom post types and ACF), Webflow (CMS collections), Shopify (article fields), HubSpot, Sanity (GROQ schema), Contentful (content model API), Ghost, Wix, Squarespace, Strapi, Notion, Framer.
Auto-detection handles 95%+ of custom fields. For the 5% edge cases, one-click manual override is available. Overrides are saved as defaults for future articles.
Yes. SemlyPro detects every content type (e.g., Post, Page, Product, CaseStudy) and matches the article’s page type to the right CMS type.
Yes. Categories, tags, and content groups extracted from article H2 headings and entity recognition. Manual override available.
Click re-detect. We diff the new schema against the existing mapping and apply changes without breaking past articles. Schema-change alerts available on Pro plan.
No. Works for WordPress (with ACF / custom post types), Shopify, HubSpot, and all other 12 CMSes. Headless CMSes (Sanity, Contentful, Strapi) benefit most because their schemas vary per project.
Yes. JSON export of the full mapping. Useful for dev teams who want to version-control the publish configuration.
Yes. We query your Sanity Studio schema endpoint and map every field type — including references, arrays, blocks, and custom validation.
Zapier and Make require manual field mapping per zap. They don’t detect custom field types automatically. SemlyPro auto-detects everything in one schema crawl and saves the mapping forever.
Skip the field-mapping screen. Just publish.
14-day free trial · 12 CMSes auto-detected · Zero manual config