CMS search-readiness evidence
Contentful is a headless content platform, so many search-readiness controls belong to the delivery application rather than the CMS itself. The distinction matters when auditing SEO and AI-search readiness.
20
checks
2
documented answers
18
unverified
“Unverified” means the research pass did not retrieve a first-party source that settled the check. It does not mean the platform lacks the capability.
Platform context
A headless content platform. Its own guide states that robots.txt is not managed in Contentful, which is the clearest example of a CMS not owning delivery-layer controls.
View first-party documentation →20-check evidence map
CMS-01
Not verified: no first-party Contentful source confirming "HTTP crawlability" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.
Contentful's own guide assigns robots.txt and sitemap generation to the delivery layer, so the platform itself offers nothing to verify for this cell.
CMS-02
Not a Contentful capability: Contentful's own SEO guide states that robots.txt is not managed in Contentful, which places this control with whoever builds and hosts the front end.
N/A here means the platform does not offer this control, not that the control is unavailable to a Contentful site. Confirming what a specific Contentful-built site serves still requires observing that site's robots.txt.
Technical SEO elements — Contentful SEO guide →CMS-03
Not verified: no first-party Contentful source confirming "Indexability" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.
Contentful's own guide assigns robots.txt and sitemap generation to the delivery layer, so the platform itself offers nothing to verify for this cell.
CMS-04
Not verified: no first-party Contentful source confirming "Content rendering" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.
Contentful's own guide assigns robots.txt and sitemap generation to the delivery layer, so the platform itself offers nothing to verify for this cell.
CMS-05
Not verified: no first-party Contentful source confirming "Canonical control" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.
Contentful's own guide assigns robots.txt and sitemap generation to the delivery layer, so the platform itself offers nothing to verify for this cell.
CMS-06
Not verified: no first-party Contentful source confirming "XML sitemap" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.
Contentful's own guide assigns robots.txt and sitemap generation to the delivery layer, so the platform itself offers nothing to verify for this cell.
CMS-07
Not verified: no first-party Contentful source confirming "Redirect control" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.
Contentful's own guide assigns robots.txt and sitemap generation to the delivery layer, so the platform itself offers nothing to verify for this cell.
CMS-08
Not verified: no first-party Contentful source confirming "URL control" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.
Contentful's own guide assigns robots.txt and sitemap generation to the delivery layer, so the platform itself offers nothing to verify for this cell.
CMS-09
Contentful's guide recommends modelling a noindex toggle and global verification fields as editorial content model fields, which the platform can host but not render.
These are modelling recommendations. Whether meta robots, titles or descriptions reach the delivered page depends entirely on the front-end implementation.
Technical SEO elements — Contentful SEO guide →CMS-10
Not verified: no first-party Contentful source confirming "Semantic HTML" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.
Contentful's own guide assigns robots.txt and sitemap generation to the delivery layer, so the platform itself offers nothing to verify for this cell.
CMS-11
Not verified: no first-party Contentful source confirming "Custom JSON-LD" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.
Contentful's own guide assigns robots.txt and sitemap generation to the delivery layer, so the platform itself offers nothing to verify for this cell.
CMS-12
Not verified: no first-party Contentful source confirming "Page-specific schema" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.
Contentful's own guide assigns robots.txt and sitemap generation to the delivery layer, so the platform itself offers nothing to verify for this cell.
CMS-13
Not verified: no first-party Contentful source confirming "Entity representation" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.
Contentful's own guide assigns robots.txt and sitemap generation to the delivery layer, so the platform itself offers nothing to verify for this cell.
CMS-14
Not verified: no first-party Contentful source confirming "Image semantics" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.
Contentful's own guide assigns robots.txt and sitemap generation to the delivery layer, so the platform itself offers nothing to verify for this cell.
CMS-15
Not verified: no first-party Contentful source confirming "Structured content" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.
Contentful's own guide assigns robots.txt and sitemap generation to the delivery layer, so the platform itself offers nothing to verify for this cell.
CMS-16
Not verified: no first-party Contentful source confirming "Internal linking" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.
Contentful's own guide assigns robots.txt and sitemap generation to the delivery layer, so the platform itself offers nothing to verify for this cell.
CMS-17
Not verified: no first-party Contentful source confirming "AI search crawler control" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.
Contentful's own guide assigns robots.txt and sitemap generation to the delivery layer, so the platform itself offers nothing to verify for this cell.
CMS-18
Not verified: no first-party Contentful source confirming "AI content extraction" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.
Contentful's own guide assigns robots.txt and sitemap generation to the delivery layer, so the platform itself offers nothing to verify for this cell.
CMS-19
Not verified: no first-party Contentful source confirming "Bot infrastructure access" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.
Contentful's own guide assigns robots.txt and sitemap generation to the delivery layer, so the platform itself offers nothing to verify for this cell.
CMS-20
Not verified: no first-party Contentful source confirming "Change verification" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.
Contentful's own guide assigns robots.txt and sitemap generation to the delivery layer, so the platform itself offers nothing to verify for this cell.
Research boundary
A documented control does not prove that a site will rank in Google or be cited by an AI system. It shows where a relevant technical control exists and what the platform's own documentation says about it.
See the full 15-platform benchmark →Compare CMS evidence
Growthract checks the site that is actually being delivered, not just what the CMS says it can support.