Direct answer
Which content management system gives a site the best foundation for search visibility and AI extraction?
This study does not name a best CMS, and it cannot yet. The features that decide search and AI readiness are not properties of the CMS itself — they are properties of what the CMS can output and what you configure. Only 30 of the 300 cells in this matrix are settled by a retrieved first-party source, and they are not distributed evenly across the 15 platforms, so any ranking drawn from them would measure our evidence coverage rather than the platforms. What the matrix does establish is the layer each capability lives in, which is the part you control before you pick a product.
01
Crawlability, renderability and indexability are properties of the output a platform produces and what you configure on top of it, which is why the benchmark separates the CMS layer from the delivery and infrastructure layers.
02
AI-crawler access is a separate policy decision from search-crawler access, because search crawlers and training crawlers are documented as distinct agents.
03
Page-specific structured data has to be authorable per page; a single site-wide JSON-LD block cannot describe every page.
The CMS is usually the wrong place to look for the answer
Most “which CMS ranks best” comparisons quietly break the evidence chain. They run a handful of live sites, score the output, and publish a league table. That measures the sites they chose, and it measures the version of the platform that was live on the day. It does not measure the thing buyers actually need to know, which is whether the platform they are about to adopt gives them the controls that search and AI systems depend on.
So this benchmark is built the other way around. It defines twenty technical checks, asks each of them against fifteen publishing platforms, and answers only from first-party documentation. Where a vendor’s own docs do not settle a question, the cell stays UNVERIFIED — and it is printed that way on this page rather than quietly filled with a plausible guess.
That gap matters more than it might sound. A published feature is not a configured feature, and a configured feature is not a working one. If you want to see the layer where a documented capability has to be turned on, our AI search readiness benchmark covers the same discipline from the crawl side.
The twenty checks
The twenty checks are grouped into three layers, because the layer determines who has to do the work. A CMS-layer check is a feature of the product. A delivery-layer check is a feature of the site that sits in front of it — the theme, the edge, the middleware. An infrastructure-layer check belongs to the host or the network. Blaming a CMS for an infrastructure decision is the most common error in this category.
CMS
- CMS-09SEO metadata
Can an editor control title, meta description and robots directives for a page?
Does not prove: It does not establish how any engine displayed the page in results.
- CMS-14Image semantics
Can an editor control image alt text and captions in the content model?
Does not prove: It does not establish that any image was described accurately by any system.
- CMS-15Structured content
Can content be modelled as typed fields rather than unstructured blobs?
Does not prove: It does not establish topical authority, coverage, or that any system read the structure.
DELIVERY LAYER
- CMS-03Indexability
Can an operator prevent a page from being indexed using a real noindex mechanism?
Does not prove: It does not establish that the page was indexed, de-indexed, or ranked.
- CMS-04Content rendering
Is primary content present in the server-rendered HTML?
Does not prove: It does not establish that any engine rendered, parsed, retrieved or cited that content.
- CMS-05Canonical control
Can an operator set a rel=canonical for a page?
Does not prove: It does not establish that duplicate pages were consolidated, or that a canonical was honoured.
- CMS-06XML sitemap
Is a valid XML sitemap generated and exposed to crawlers?
Does not prove: It does not establish that URLs were crawled or indexed because the sitemap listed them.
- CMS-07Redirect control
Can an operator configure permanent redirects for moved URLs?
Does not prove: It does not establish that link equity or authority was transferred.
- CMS-08URL control
Can an operator control the published URL of a page?
Does not prove: It does not establish that the chosen URL structure helps any engine.
- CMS-10Semantic HTML
Does the delivered markup use semantic elements for structure?
Does not prove: It does not establish that any engine used that structure to understand the page.
- CMS-11Custom JSON-LD
Can an operator ship custom JSON-LD structured data?
Does not prove: It does not establish a rich result, an enhanced appearance, or any AI understanding.
- CMS-12Page-specific schema
Can structured data be scoped to individual page types?
Does not prove: It does not establish that the markup was valid, error-free, or used by any consumer.
- CMS-13Entity representation
Can an organisation be described as a typed entity for machines?
Does not prove: It does not establish that any knowledge system recognised, resolved or trusted that entity.
- CMS-16Internal linking
Can editors control internal links and related content?
Does not prove: It does not establish that authority flowed, that paths were discovered, or that rankings changed.
- CMS-18AI content extraction
Is content structured so an answer engine could quote it without guessing?
Does not prove: It does not establish that any assistant retrieved, mentioned, cited or recommended the brand.
INFRASTRUCTURE
- CMS-01HTTP crawlability
Does the live site return a crawlable HTTP response for public pages?
Does not prove: It does not establish that a specific crawler was served, or that any page was indexed.
- CMS-02Search crawler access
Can an operator control search crawler access through robots.txt or an equivalent platform control?
Does not prove: It does not establish indexing. robots.txt governs crawling, not inclusion in results.
- CMS-17AI search crawler control
Can an operator allow or block individual AI crawler user agents independently of search crawlers?
Does not prove: It does not establish AI visibility. Blocking or allowing a crawler only affects open-web access, and advisory directives are not always obeyed.
- CMS-19Bot infrastructure access
Is rate limiting or bot management applied at the network layer?
Does not prove: It does not establish that legitimate crawlers were served, or that blocking worked.
- CMS-20Change verification
Can an operator compare two comparable observations of the same site over time?
Does not prove: It does not establish an outcome. A change in evidence is not a change in business results.
The full matrix
300 cells in total: 30 answered from first-party documentation, 2 of those recording that the platform does not manage the control at all, and 270 recorded as UNVERIFIED. Expand any platform to read its twenty rows, each with its observation, its provision level and a link to the source it was read from.
A high unverified count is not a negative verdict on a platform. It is a statement about what its vendor chooses to document, which is a real and useful signal in its own right — documentation you cannot find is documentation you cannot rely on.
What each status means
- Documented
- A retrieved first-party source states the control exists and how to reach it.
- Partly documented
- A first-party source confirms the control exists but reaches it only in part, or needs one more layer on top of it.
- Constrained
- Affirmative evidence of failure: a first-party source establishes that the control is not supported as tested. Absence of documentation is never enough to get here.
- Not applicable
- The vendor states the platform does not manage this control at all, so it is outside what the platform is for.
- Unverified
- No first-party source settled the question. This is an evidence gap, not a finding — the capability is neither confirmed nor absent, and the row is never filled with a guess.
These statuses describe documentation coverage, not platform quality. No platform scores higher than another, and no count on this page is a score, a percentage or a ranking.
WordPressThe dominant self-hosted CMS. Its SEO surface is largely plugin- and theme-mediated, so capability depends heavily on what is installed.1 of 20 answered
| Check | Status | Observation | Provision | Source |
|---|---|---|---|---|
| HTTP crawlabilityCMS-01 | Unverified | Not verified: no first-party WordPress source confirming "HTTP crawlability" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: WordPress core documentation retrieved for this pass covers its default robots.txt only; per-cell SEO capability depends on the installed theme and plugin set, which is site-specific. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
| Search crawler accessCMS-02 | Documented | WordPress publishes a default robots.txt that disallows /wp-admin/ and allows admin-ajax.php, load-scripts.php and load-styles.php. | nativebuilt in effort | robots.txt output — WordPress Developer Resources |
| IndexabilityCMS-03 | Unverified | Not verified: no first-party WordPress source confirming "Indexability" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: WordPress core documentation retrieved for this pass covers its default robots.txt only; per-cell SEO capability depends on the installed theme and plugin set, which is site-specific. | custom codedeveloper effortlayer estimate | No source retrieved |
| Content renderingCMS-04 | Unverified | Not verified: no first-party WordPress source confirming "Content rendering" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: WordPress core documentation retrieved for this pass covers its default robots.txt only; per-cell SEO capability depends on the installed theme and plugin set, which is site-specific. | custom codedeveloper effortlayer estimate | No source retrieved |
| Canonical controlCMS-05 | Unverified | Not verified: no first-party WordPress source confirming "Canonical control" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: WordPress core documentation retrieved for this pass covers its default robots.txt only; per-cell SEO capability depends on the installed theme and plugin set, which is site-specific. | custom codedeveloper effortlayer estimate | No source retrieved |
| XML sitemapCMS-06 | Unverified | Not verified: no first-party WordPress source confirming "XML sitemap" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: WordPress core documentation retrieved for this pass covers its default robots.txt only; per-cell SEO capability depends on the installed theme and plugin set, which is site-specific. | custom codedeveloper effortlayer estimate | No source retrieved |
| Redirect controlCMS-07 | Unverified | Not verified: no first-party WordPress source confirming "Redirect control" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: WordPress core documentation retrieved for this pass covers its default robots.txt only; per-cell SEO capability depends on the installed theme and plugin set, which is site-specific. | custom codedeveloper effortlayer estimate | No source retrieved |
| URL controlCMS-08 | Unverified | Not verified: no first-party WordPress source confirming "URL control" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: WordPress core documentation retrieved for this pass covers its default robots.txt only; per-cell SEO capability depends on the installed theme and plugin set, which is site-specific. | custom codedeveloper effortlayer estimate | No source retrieved |
| SEO metadataCMS-09 | Unverified | Not verified: no first-party WordPress source confirming "SEO metadata" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: WordPress core documentation retrieved for this pass covers its default robots.txt only; per-cell SEO capability depends on the installed theme and plugin set, which is site-specific. | configurationconfiguration effortlayer estimate | No source retrieved |
| Semantic HTMLCMS-10 | Unverified | Not verified: no first-party WordPress source confirming "Semantic HTML" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: WordPress core documentation retrieved for this pass covers its default robots.txt only; per-cell SEO capability depends on the installed theme and plugin set, which is site-specific. | custom codedeveloper effortlayer estimate | No source retrieved |
| Custom JSON-LDCMS-11 | Unverified | Not verified: no first-party WordPress source confirming "Custom JSON-LD" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: WordPress core documentation retrieved for this pass covers its default robots.txt only; per-cell SEO capability depends on the installed theme and plugin set, which is site-specific. | custom codedeveloper effortlayer estimate | No source retrieved |
| Page-specific schemaCMS-12 | Unverified | Not verified: no first-party WordPress source confirming "Page-specific schema" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: WordPress core documentation retrieved for this pass covers its default robots.txt only; per-cell SEO capability depends on the installed theme and plugin set, which is site-specific. | custom codedeveloper effortlayer estimate | No source retrieved |
| Entity representationCMS-13 | Unverified | Not verified: no first-party WordPress source confirming "Entity representation" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: WordPress core documentation retrieved for this pass covers its default robots.txt only; per-cell SEO capability depends on the installed theme and plugin set, which is site-specific. | custom codedeveloper effortlayer estimate | No source retrieved |
| Image semanticsCMS-14 | Unverified | Not verified: no first-party WordPress source confirming "Image semantics" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: WordPress core documentation retrieved for this pass covers its default robots.txt only; per-cell SEO capability depends on the installed theme and plugin set, which is site-specific. | configurationconfiguration effortlayer estimate | No source retrieved |
| Structured contentCMS-15 | Unverified | Not verified: no first-party WordPress source confirming "Structured content" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: WordPress core documentation retrieved for this pass covers its default robots.txt only; per-cell SEO capability depends on the installed theme and plugin set, which is site-specific. | configurationconfiguration effortlayer estimate | No source retrieved |
| Internal linkingCMS-16 | Unverified | Not verified: no first-party WordPress source confirming "Internal linking" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: WordPress core documentation retrieved for this pass covers its default robots.txt only; per-cell SEO capability depends on the installed theme and plugin set, which is site-specific. | custom codedeveloper effortlayer estimate | No source retrieved |
| AI search crawler controlCMS-17 | Unverified | Not verified: no first-party WordPress source confirming "AI search crawler control" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: WordPress core documentation retrieved for this pass covers its default robots.txt only; per-cell SEO capability depends on the installed theme and plugin set, which is site-specific. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
| AI content extractionCMS-18 | Unverified | Not verified: no first-party WordPress source confirming "AI content extraction" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: WordPress core documentation retrieved for this pass covers its default robots.txt only; per-cell SEO capability depends on the installed theme and plugin set, which is site-specific. | custom codedeveloper effortlayer estimate | No source retrieved |
| Bot infrastructure accessCMS-19 | Unverified | Not verified: no first-party WordPress source confirming "Bot infrastructure access" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: WordPress core documentation retrieved for this pass covers its default robots.txt only; per-cell SEO capability depends on the installed theme and plugin set, which is site-specific. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
| Change verificationCMS-20 | Unverified | Not verified: no first-party WordPress source confirming "Change verification" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: WordPress core documentation retrieved for this pass covers its default robots.txt only; per-cell SEO capability depends on the installed theme and plugin set, which is site-specific. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
WebflowA hosted visual builder with SEO controls surfaced directly in site settings, including per-crawler directives and a Content-Signal header.2 of 20 answered
| Check | Status | Observation | Provision | Source |
|---|---|---|---|---|
| HTTP crawlabilityCMS-01 | Unverified | Not verified: no first-party Webflow source confirming "HTTP crawlability" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Only Webflow's robots.txt help article was retrieved and confirmed in this pass. An earlier draft of this profile cited that same robots.txt page as evidence for canonical, sitemap, redirect and schema controls; those claims were withdrawn rather than kept, because a page about robots.txt directives does not establish that a separate control exists. Verifying them requires Webflow's own pages for each control. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
| Search crawler accessCMS-02 | Documented | Webflow exposes robots.txt rules in Site settings under SEO and Indexing, including per-user-agent allow and disallow entries, and links the sitemap in robots.txt by default. | configurationconfiguration effort | Set robots.txt rules — Webflow Help Center |
| IndexabilityCMS-03 | Unverified | Not verified: no first-party Webflow source confirming "Indexability" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Only Webflow's robots.txt help article was retrieved and confirmed in this pass. An earlier draft of this profile cited that same robots.txt page as evidence for canonical, sitemap, redirect and schema controls; those claims were withdrawn rather than kept, because a page about robots.txt directives does not establish that a separate control exists. Verifying them requires Webflow's own pages for each control. | custom codedeveloper effortlayer estimate | No source retrieved |
| Content renderingCMS-04 | Unverified | Not verified: no first-party Webflow source confirming "Content rendering" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Only Webflow's robots.txt help article was retrieved and confirmed in this pass. An earlier draft of this profile cited that same robots.txt page as evidence for canonical, sitemap, redirect and schema controls; those claims were withdrawn rather than kept, because a page about robots.txt directives does not establish that a separate control exists. Verifying them requires Webflow's own pages for each control. | custom codedeveloper effortlayer estimate | No source retrieved |
| Canonical controlCMS-05 | Unverified | Not verified: no first-party Webflow source confirming "Canonical control" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Only Webflow's robots.txt help article was retrieved and confirmed in this pass. An earlier draft of this profile cited that same robots.txt page as evidence for canonical, sitemap, redirect and schema controls; those claims were withdrawn rather than kept, because a page about robots.txt directives does not establish that a separate control exists. Verifying them requires Webflow's own pages for each control. | custom codedeveloper effortlayer estimate | No source retrieved |
| XML sitemapCMS-06 | Unverified | Not verified: no first-party Webflow source confirming "XML sitemap" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Only Webflow's robots.txt help article was retrieved and confirmed in this pass. An earlier draft of this profile cited that same robots.txt page as evidence for canonical, sitemap, redirect and schema controls; those claims were withdrawn rather than kept, because a page about robots.txt directives does not establish that a separate control exists. Verifying them requires Webflow's own pages for each control. | custom codedeveloper effortlayer estimate | No source retrieved |
| Redirect controlCMS-07 | Unverified | Not verified: no first-party Webflow source confirming "Redirect control" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Only Webflow's robots.txt help article was retrieved and confirmed in this pass. An earlier draft of this profile cited that same robots.txt page as evidence for canonical, sitemap, redirect and schema controls; those claims were withdrawn rather than kept, because a page about robots.txt directives does not establish that a separate control exists. Verifying them requires Webflow's own pages for each control. | custom codedeveloper effortlayer estimate | No source retrieved |
| URL controlCMS-08 | Unverified | Not verified: no first-party Webflow source confirming "URL control" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Only Webflow's robots.txt help article was retrieved and confirmed in this pass. An earlier draft of this profile cited that same robots.txt page as evidence for canonical, sitemap, redirect and schema controls; those claims were withdrawn rather than kept, because a page about robots.txt directives does not establish that a separate control exists. Verifying them requires Webflow's own pages for each control. | custom codedeveloper effortlayer estimate | No source retrieved |
| SEO metadataCMS-09 | Unverified | Not verified: no first-party Webflow source confirming "SEO metadata" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Only Webflow's robots.txt help article was retrieved and confirmed in this pass. An earlier draft of this profile cited that same robots.txt page as evidence for canonical, sitemap, redirect and schema controls; those claims were withdrawn rather than kept, because a page about robots.txt directives does not establish that a separate control exists. Verifying them requires Webflow's own pages for each control. | configurationconfiguration effortlayer estimate | No source retrieved |
| Semantic HTMLCMS-10 | Unverified | Not verified: no first-party Webflow source confirming "Semantic HTML" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Only Webflow's robots.txt help article was retrieved and confirmed in this pass. An earlier draft of this profile cited that same robots.txt page as evidence for canonical, sitemap, redirect and schema controls; those claims were withdrawn rather than kept, because a page about robots.txt directives does not establish that a separate control exists. Verifying them requires Webflow's own pages for each control. | custom codedeveloper effortlayer estimate | No source retrieved |
| Custom JSON-LDCMS-11 | Unverified | Not verified: no first-party Webflow source confirming "Custom JSON-LD" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Only Webflow's robots.txt help article was retrieved and confirmed in this pass. An earlier draft of this profile cited that same robots.txt page as evidence for canonical, sitemap, redirect and schema controls; those claims were withdrawn rather than kept, because a page about robots.txt directives does not establish that a separate control exists. Verifying them requires Webflow's own pages for each control. | custom codedeveloper effortlayer estimate | No source retrieved |
| Page-specific schemaCMS-12 | Unverified | Not verified: no first-party Webflow source confirming "Page-specific schema" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Only Webflow's robots.txt help article was retrieved and confirmed in this pass. An earlier draft of this profile cited that same robots.txt page as evidence for canonical, sitemap, redirect and schema controls; those claims were withdrawn rather than kept, because a page about robots.txt directives does not establish that a separate control exists. Verifying them requires Webflow's own pages for each control. | custom codedeveloper effortlayer estimate | No source retrieved |
| Entity representationCMS-13 | Unverified | Not verified: no first-party Webflow source confirming "Entity representation" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Only Webflow's robots.txt help article was retrieved and confirmed in this pass. An earlier draft of this profile cited that same robots.txt page as evidence for canonical, sitemap, redirect and schema controls; those claims were withdrawn rather than kept, because a page about robots.txt directives does not establish that a separate control exists. Verifying them requires Webflow's own pages for each control. | custom codedeveloper effortlayer estimate | No source retrieved |
| Image semanticsCMS-14 | Unverified | Not verified: no first-party Webflow source confirming "Image semantics" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Only Webflow's robots.txt help article was retrieved and confirmed in this pass. An earlier draft of this profile cited that same robots.txt page as evidence for canonical, sitemap, redirect and schema controls; those claims were withdrawn rather than kept, because a page about robots.txt directives does not establish that a separate control exists. Verifying them requires Webflow's own pages for each control. | configurationconfiguration effortlayer estimate | No source retrieved |
| Structured contentCMS-15 | Unverified | Not verified: no first-party Webflow source confirming "Structured content" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Only Webflow's robots.txt help article was retrieved and confirmed in this pass. An earlier draft of this profile cited that same robots.txt page as evidence for canonical, sitemap, redirect and schema controls; those claims were withdrawn rather than kept, because a page about robots.txt directives does not establish that a separate control exists. Verifying them requires Webflow's own pages for each control. | configurationconfiguration effortlayer estimate | No source retrieved |
| Internal linkingCMS-16 | Unverified | Not verified: no first-party Webflow source confirming "Internal linking" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Only Webflow's robots.txt help article was retrieved and confirmed in this pass. An earlier draft of this profile cited that same robots.txt page as evidence for canonical, sitemap, redirect and schema controls; those claims were withdrawn rather than kept, because a page about robots.txt directives does not establish that a separate control exists. Verifying them requires Webflow's own pages for each control. | custom codedeveloper effortlayer estimate | No source retrieved |
| AI search crawler controlCMS-17 | Documented | Webflow supports per-user-agent robots.txt rules, so individual AI crawler user agents can be allowed or blocked independently of search crawlers from the same control. | configurationconfiguration effort | Set robots.txt rules — Webflow Help Center |
| AI content extractionCMS-18 | Unverified | Not verified: no first-party Webflow source confirming "AI content extraction" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Only Webflow's robots.txt help article was retrieved and confirmed in this pass. An earlier draft of this profile cited that same robots.txt page as evidence for canonical, sitemap, redirect and schema controls; those claims were withdrawn rather than kept, because a page about robots.txt directives does not establish that a separate control exists. Verifying them requires Webflow's own pages for each control. | custom codedeveloper effortlayer estimate | No source retrieved |
| Bot infrastructure accessCMS-19 | Unverified | Not verified: no first-party Webflow source confirming "Bot infrastructure access" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Only Webflow's robots.txt help article was retrieved and confirmed in this pass. An earlier draft of this profile cited that same robots.txt page as evidence for canonical, sitemap, redirect and schema controls; those claims were withdrawn rather than kept, because a page about robots.txt directives does not establish that a separate control exists. Verifying them requires Webflow's own pages for each control. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
| Change verificationCMS-20 | Unverified | Not verified: no first-party Webflow source confirming "Change verification" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Only Webflow's robots.txt help article was retrieved and confirmed in this pass. An earlier draft of this profile cited that same robots.txt page as evidence for canonical, sitemap, redirect and schema controls; those claims were withdrawn rather than kept, because a page about robots.txt directives does not establish that a separate control exists. Verifying them requires Webflow's own pages for each control. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
HubSpot Content HubA marketing-suite CMS tightly coupled to HubSpot's CRM, analytics and hosting, so its SEO surface is bounded by that ecosystem.5 of 20 answered
| Check | Status | Observation | Provision | Source |
|---|---|---|---|---|
| HTTP crawlabilityCMS-01 | Unverified | Not verified: no first-party HubSpot Content Hub source confirming "HTTP crawlability" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Four HubSpot knowledge base articles were retrieved and confirmed, covering crawler access, indexability, canonical URLs, sitemaps and redirects. An earlier draft of this profile asserted conditional sitemap coverage as an inference; that is now confirmed from HubSpot's own sitemap article and recorded as partial. AI crawler control, URL control, custom JSON-LD and per-entity schema were not established by a retrieved page. HubSpot's developer blog describes JSON-LD as developer-authored template code rather than a native content control, but a blog post is weaker than its own reference documentation, so that cell stays unverified rather than being recorded on blog evidence. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
| Search crawler accessCMS-02 | Documented | HubSpot provides a robots.txt control on the SEO & Crawlers settings tab, with a default ruleset per domain that an operator can override, and applies a noindex directive to pages served from hs-sites subdomains. | configurationconfiguration effort | Prevent content from appearing in search results — HubSpot Knowledge Base |
| IndexabilityCMS-03 | Partly documented | HubSpot's documented way to keep a page out of results is to add a noindex meta tag to the page's Head HTML, after which the page must be published or updated and search engines given time to pick the change up. | custom codedeveloper effort | Prevent content from appearing in search results — HubSpot Knowledge Base |
| Content renderingCMS-04 | Unverified | Not verified: no first-party HubSpot Content Hub source confirming "Content rendering" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Four HubSpot knowledge base articles were retrieved and confirmed, covering crawler access, indexability, canonical URLs, sitemaps and redirects. An earlier draft of this profile asserted conditional sitemap coverage as an inference; that is now confirmed from HubSpot's own sitemap article and recorded as partial. AI crawler control, URL control, custom JSON-LD and per-entity schema were not established by a retrieved page. HubSpot's developer blog describes JSON-LD as developer-authored template code rather than a native content control, but a blog post is weaker than its own reference documentation, so that cell stays unverified rather than being recorded on blog evidence. | custom codedeveloper effortlayer estimate | No source retrieved |
| Canonical controlCMS-05 | Documented | HubSpot sets a default canonical URL for each page and blog post, documents editing it per page, and provides a site-wide default that pages can override or disable. | configurationconfiguration effort | Set canonical URLs for duplicate content — HubSpot Knowledge Base |
| XML sitemapCMS-06 | Partly documented | HubSpot exposes a sitemap index at /sitemap.xml that automatically includes live pages of a HubSpot-hosted website and its blog posts, while landing page templates must be added manually and HubDB dynamic child pages are included only conditionally. | nativeconfiguration effort | View and edit a HubSpot-hosted domain sitemap — HubSpot Knowledge Base |
| Redirect controlCMS-07 | Partly documented | HubSpot documents URL redirects with a permanent 301 as the default style, plus flexible pattern redirects, bulk CSV upload, priority ordering and protocol and trailing-slash handling. | configurationconfiguration effort | Create and manage URL redirects — HubSpot Knowledge Base |
| URL controlCMS-08 | Unverified | Not verified: no first-party HubSpot Content Hub source confirming "URL control" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Four HubSpot knowledge base articles were retrieved and confirmed, covering crawler access, indexability, canonical URLs, sitemaps and redirects. An earlier draft of this profile asserted conditional sitemap coverage as an inference; that is now confirmed from HubSpot's own sitemap article and recorded as partial. AI crawler control, URL control, custom JSON-LD and per-entity schema were not established by a retrieved page. HubSpot's developer blog describes JSON-LD as developer-authored template code rather than a native content control, but a blog post is weaker than its own reference documentation, so that cell stays unverified rather than being recorded on blog evidence. | custom codedeveloper effortlayer estimate | No source retrieved |
| SEO metadataCMS-09 | Unverified | Not verified: no first-party HubSpot Content Hub source confirming "SEO metadata" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Four HubSpot knowledge base articles were retrieved and confirmed, covering crawler access, indexability, canonical URLs, sitemaps and redirects. An earlier draft of this profile asserted conditional sitemap coverage as an inference; that is now confirmed from HubSpot's own sitemap article and recorded as partial. AI crawler control, URL control, custom JSON-LD and per-entity schema were not established by a retrieved page. HubSpot's developer blog describes JSON-LD as developer-authored template code rather than a native content control, but a blog post is weaker than its own reference documentation, so that cell stays unverified rather than being recorded on blog evidence. | configurationconfiguration effortlayer estimate | No source retrieved |
| Semantic HTMLCMS-10 | Unverified | Not verified: no first-party HubSpot Content Hub source confirming "Semantic HTML" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Four HubSpot knowledge base articles were retrieved and confirmed, covering crawler access, indexability, canonical URLs, sitemaps and redirects. An earlier draft of this profile asserted conditional sitemap coverage as an inference; that is now confirmed from HubSpot's own sitemap article and recorded as partial. AI crawler control, URL control, custom JSON-LD and per-entity schema were not established by a retrieved page. HubSpot's developer blog describes JSON-LD as developer-authored template code rather than a native content control, but a blog post is weaker than its own reference documentation, so that cell stays unverified rather than being recorded on blog evidence. | custom codedeveloper effortlayer estimate | No source retrieved |
| Custom JSON-LDCMS-11 | Unverified | Not verified: no first-party HubSpot Content Hub source confirming "Custom JSON-LD" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Four HubSpot knowledge base articles were retrieved and confirmed, covering crawler access, indexability, canonical URLs, sitemaps and redirects. An earlier draft of this profile asserted conditional sitemap coverage as an inference; that is now confirmed from HubSpot's own sitemap article and recorded as partial. AI crawler control, URL control, custom JSON-LD and per-entity schema were not established by a retrieved page. HubSpot's developer blog describes JSON-LD as developer-authored template code rather than a native content control, but a blog post is weaker than its own reference documentation, so that cell stays unverified rather than being recorded on blog evidence. | custom codedeveloper effortlayer estimate | No source retrieved |
| Page-specific schemaCMS-12 | Unverified | Not verified: no first-party HubSpot Content Hub source confirming "Page-specific schema" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Four HubSpot knowledge base articles were retrieved and confirmed, covering crawler access, indexability, canonical URLs, sitemaps and redirects. An earlier draft of this profile asserted conditional sitemap coverage as an inference; that is now confirmed from HubSpot's own sitemap article and recorded as partial. AI crawler control, URL control, custom JSON-LD and per-entity schema were not established by a retrieved page. HubSpot's developer blog describes JSON-LD as developer-authored template code rather than a native content control, but a blog post is weaker than its own reference documentation, so that cell stays unverified rather than being recorded on blog evidence. | custom codedeveloper effortlayer estimate | No source retrieved |
| Entity representationCMS-13 | Unverified | Not verified: no first-party HubSpot Content Hub source confirming "Entity representation" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Four HubSpot knowledge base articles were retrieved and confirmed, covering crawler access, indexability, canonical URLs, sitemaps and redirects. An earlier draft of this profile asserted conditional sitemap coverage as an inference; that is now confirmed from HubSpot's own sitemap article and recorded as partial. AI crawler control, URL control, custom JSON-LD and per-entity schema were not established by a retrieved page. HubSpot's developer blog describes JSON-LD as developer-authored template code rather than a native content control, but a blog post is weaker than its own reference documentation, so that cell stays unverified rather than being recorded on blog evidence. | custom codedeveloper effortlayer estimate | No source retrieved |
| Image semanticsCMS-14 | Unverified | Not verified: no first-party HubSpot Content Hub source confirming "Image semantics" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Four HubSpot knowledge base articles were retrieved and confirmed, covering crawler access, indexability, canonical URLs, sitemaps and redirects. An earlier draft of this profile asserted conditional sitemap coverage as an inference; that is now confirmed from HubSpot's own sitemap article and recorded as partial. AI crawler control, URL control, custom JSON-LD and per-entity schema were not established by a retrieved page. HubSpot's developer blog describes JSON-LD as developer-authored template code rather than a native content control, but a blog post is weaker than its own reference documentation, so that cell stays unverified rather than being recorded on blog evidence. | configurationconfiguration effortlayer estimate | No source retrieved |
| Structured contentCMS-15 | Unverified | Not verified: no first-party HubSpot Content Hub source confirming "Structured content" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Four HubSpot knowledge base articles were retrieved and confirmed, covering crawler access, indexability, canonical URLs, sitemaps and redirects. An earlier draft of this profile asserted conditional sitemap coverage as an inference; that is now confirmed from HubSpot's own sitemap article and recorded as partial. AI crawler control, URL control, custom JSON-LD and per-entity schema were not established by a retrieved page. HubSpot's developer blog describes JSON-LD as developer-authored template code rather than a native content control, but a blog post is weaker than its own reference documentation, so that cell stays unverified rather than being recorded on blog evidence. | configurationconfiguration effortlayer estimate | No source retrieved |
| Internal linkingCMS-16 | Unverified | Not verified: no first-party HubSpot Content Hub source confirming "Internal linking" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Four HubSpot knowledge base articles were retrieved and confirmed, covering crawler access, indexability, canonical URLs, sitemaps and redirects. An earlier draft of this profile asserted conditional sitemap coverage as an inference; that is now confirmed from HubSpot's own sitemap article and recorded as partial. AI crawler control, URL control, custom JSON-LD and per-entity schema were not established by a retrieved page. HubSpot's developer blog describes JSON-LD as developer-authored template code rather than a native content control, but a blog post is weaker than its own reference documentation, so that cell stays unverified rather than being recorded on blog evidence. | custom codedeveloper effortlayer estimate | No source retrieved |
| AI search crawler controlCMS-17 | Unverified | Not verified: no first-party HubSpot Content Hub source confirming "AI search crawler control" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Four HubSpot knowledge base articles were retrieved and confirmed, covering crawler access, indexability, canonical URLs, sitemaps and redirects. An earlier draft of this profile asserted conditional sitemap coverage as an inference; that is now confirmed from HubSpot's own sitemap article and recorded as partial. AI crawler control, URL control, custom JSON-LD and per-entity schema were not established by a retrieved page. HubSpot's developer blog describes JSON-LD as developer-authored template code rather than a native content control, but a blog post is weaker than its own reference documentation, so that cell stays unverified rather than being recorded on blog evidence. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
| AI content extractionCMS-18 | Unverified | Not verified: no first-party HubSpot Content Hub source confirming "AI content extraction" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Four HubSpot knowledge base articles were retrieved and confirmed, covering crawler access, indexability, canonical URLs, sitemaps and redirects. An earlier draft of this profile asserted conditional sitemap coverage as an inference; that is now confirmed from HubSpot's own sitemap article and recorded as partial. AI crawler control, URL control, custom JSON-LD and per-entity schema were not established by a retrieved page. HubSpot's developer blog describes JSON-LD as developer-authored template code rather than a native content control, but a blog post is weaker than its own reference documentation, so that cell stays unverified rather than being recorded on blog evidence. | custom codedeveloper effortlayer estimate | No source retrieved |
| Bot infrastructure accessCMS-19 | Unverified | Not verified: no first-party HubSpot Content Hub source confirming "Bot infrastructure access" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Four HubSpot knowledge base articles were retrieved and confirmed, covering crawler access, indexability, canonical URLs, sitemaps and redirects. An earlier draft of this profile asserted conditional sitemap coverage as an inference; that is now confirmed from HubSpot's own sitemap article and recorded as partial. AI crawler control, URL control, custom JSON-LD and per-entity schema were not established by a retrieved page. HubSpot's developer blog describes JSON-LD as developer-authored template code rather than a native content control, but a blog post is weaker than its own reference documentation, so that cell stays unverified rather than being recorded on blog evidence. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
| Change verificationCMS-20 | Unverified | Not verified: no first-party HubSpot Content Hub source confirming "Change verification" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Four HubSpot knowledge base articles were retrieved and confirmed, covering crawler access, indexability, canonical URLs, sitemaps and redirects. An earlier draft of this profile asserted conditional sitemap coverage as an inference; that is now confirmed from HubSpot's own sitemap article and recorded as partial. AI crawler control, URL control, custom JSON-LD and per-entity schema were not established by a retrieved page. HubSpot's developer blog describes JSON-LD as developer-authored template code rather than a native content control, but a blog post is weaker than its own reference documentation, so that cell stays unverified rather than being recorded on blog evidence. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
ContentfulA 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.2 of 20 answered
| Check | Status | Observation | Provision | Source |
|---|---|---|---|---|
| HTTP crawlabilityCMS-01 | Unverified | 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.Limitation: 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. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
| Search crawler accessCMS-02 | Not applicable | 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. | infrastructureinfrastructure effort | Technical SEO elements — Contentful SEO guide |
| IndexabilityCMS-03 | Unverified | 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.Limitation: 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. | custom codedeveloper effortlayer estimate | No source retrieved |
| Content renderingCMS-04 | Unverified | 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.Limitation: 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. | custom codedeveloper effortlayer estimate | No source retrieved |
| Canonical controlCMS-05 | Unverified | 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.Limitation: 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. | custom codedeveloper effortlayer estimate | No source retrieved |
| XML sitemapCMS-06 | Unverified | 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.Limitation: 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. | custom codedeveloper effortlayer estimate | No source retrieved |
| Redirect controlCMS-07 | Unverified | 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.Limitation: 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. | custom codedeveloper effortlayer estimate | No source retrieved |
| URL controlCMS-08 | Unverified | 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.Limitation: 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. | custom codedeveloper effortlayer estimate | No source retrieved |
| SEO metadataCMS-09 | Partly documented | 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. | configurationconfiguration effort | Technical SEO elements — Contentful SEO guide |
| Semantic HTMLCMS-10 | Unverified | 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.Limitation: 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. | custom codedeveloper effortlayer estimate | No source retrieved |
| Custom JSON-LDCMS-11 | Unverified | 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.Limitation: 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. | custom codedeveloper effortlayer estimate | No source retrieved |
| Page-specific schemaCMS-12 | Unverified | 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.Limitation: 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. | custom codedeveloper effortlayer estimate | No source retrieved |
| Entity representationCMS-13 | Unverified | 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.Limitation: 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. | custom codedeveloper effortlayer estimate | No source retrieved |
| Image semanticsCMS-14 | Unverified | 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.Limitation: 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. | configurationconfiguration effortlayer estimate | No source retrieved |
| Structured contentCMS-15 | Unverified | 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.Limitation: 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. | configurationconfiguration effortlayer estimate | No source retrieved |
| Internal linkingCMS-16 | Unverified | 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.Limitation: 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. | custom codedeveloper effortlayer estimate | No source retrieved |
| AI search crawler controlCMS-17 | Unverified | 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.Limitation: 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. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
| AI content extractionCMS-18 | Unverified | 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.Limitation: 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. | custom codedeveloper effortlayer estimate | No source retrieved |
| Bot infrastructure accessCMS-19 | Unverified | 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.Limitation: 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. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
| Change verificationCMS-20 | Unverified | 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.Limitation: 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. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
SanityA structured content platform with a schema-first Studio, delivered to the front end you build and host yourself.0 of 20 answered
| Check | Status | Observation | Provision | Source |
|---|---|---|---|---|
| HTTP crawlabilityCMS-01 | Unverified | Not verified: no first-party Sanity source confirming "HTTP crawlability" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: No cell-level first-party source for Sanity was retrieved in this pass. Confirming "HTTP crawlability" requires reading the vendor's own control documentation and, where the control is a runtime behaviour, observing a live site built on the platform. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
| Search crawler accessCMS-02 | Unverified | Not verified: no first-party Sanity source confirming "Search crawler access" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: No cell-level first-party source for Sanity was retrieved in this pass. Confirming "Search crawler access" requires reading the vendor's own control documentation and, where the control is a runtime behaviour, observing a live site built on the platform. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
| IndexabilityCMS-03 | Unverified | Not verified: no first-party Sanity source confirming "Indexability" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: No cell-level first-party source for Sanity was retrieved in this pass. Confirming "Indexability" requires reading the vendor's own control documentation and, where the control is a runtime behaviour, observing a live site built on the platform. | custom codedeveloper effortlayer estimate | No source retrieved |
| Content renderingCMS-04 | Unverified | Not verified: no first-party Sanity source confirming "Content rendering" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: No cell-level first-party source for Sanity was retrieved in this pass. Confirming "Content rendering" requires reading the vendor's own control documentation and, where the control is a runtime behaviour, observing a live site built on the platform. | custom codedeveloper effortlayer estimate | No source retrieved |
| Canonical controlCMS-05 | Unverified | Not verified: no first-party Sanity source confirming "Canonical control" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: No cell-level first-party source for Sanity was retrieved in this pass. Confirming "Canonical control" requires reading the vendor's own control documentation and, where the control is a runtime behaviour, observing a live site built on the platform. | custom codedeveloper effortlayer estimate | No source retrieved |
| XML sitemapCMS-06 | Unverified | Not verified: no first-party Sanity source confirming "XML sitemap" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: No cell-level first-party source for Sanity was retrieved in this pass. Confirming "XML sitemap" requires reading the vendor's own control documentation and, where the control is a runtime behaviour, observing a live site built on the platform. | custom codedeveloper effortlayer estimate | No source retrieved |
| Redirect controlCMS-07 | Unverified | Not verified: no first-party Sanity source confirming "Redirect control" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: No cell-level first-party source for Sanity was retrieved in this pass. Confirming "Redirect control" requires reading the vendor's own control documentation and, where the control is a runtime behaviour, observing a live site built on the platform. | custom codedeveloper effortlayer estimate | No source retrieved |
| URL controlCMS-08 | Unverified | Not verified: no first-party Sanity source confirming "URL control" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: No cell-level first-party source for Sanity was retrieved in this pass. Confirming "URL control" requires reading the vendor's own control documentation and, where the control is a runtime behaviour, observing a live site built on the platform. | custom codedeveloper effortlayer estimate | No source retrieved |
| SEO metadataCMS-09 | Unverified | Not verified: no first-party Sanity source confirming "SEO metadata" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: No cell-level first-party source for Sanity was retrieved in this pass. Confirming "SEO metadata" requires reading the vendor's own control documentation and, where the control is a runtime behaviour, observing a live site built on the platform. | configurationconfiguration effortlayer estimate | No source retrieved |
| Semantic HTMLCMS-10 | Unverified | Not verified: no first-party Sanity source confirming "Semantic HTML" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: No cell-level first-party source for Sanity was retrieved in this pass. Confirming "Semantic HTML" requires reading the vendor's own control documentation and, where the control is a runtime behaviour, observing a live site built on the platform. | custom codedeveloper effortlayer estimate | No source retrieved |
| Custom JSON-LDCMS-11 | Unverified | Not verified: no first-party Sanity source confirming "Custom JSON-LD" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: No cell-level first-party source for Sanity was retrieved in this pass. Confirming "Custom JSON-LD" requires reading the vendor's own control documentation and, where the control is a runtime behaviour, observing a live site built on the platform. | custom codedeveloper effortlayer estimate | No source retrieved |
| Page-specific schemaCMS-12 | Unverified | Not verified: no first-party Sanity source confirming "Page-specific schema" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: No cell-level first-party source for Sanity was retrieved in this pass. Confirming "Page-specific schema" requires reading the vendor's own control documentation and, where the control is a runtime behaviour, observing a live site built on the platform. | custom codedeveloper effortlayer estimate | No source retrieved |
| Entity representationCMS-13 | Unverified | Not verified: no first-party Sanity source confirming "Entity representation" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: No cell-level first-party source for Sanity was retrieved in this pass. Confirming "Entity representation" requires reading the vendor's own control documentation and, where the control is a runtime behaviour, observing a live site built on the platform. | custom codedeveloper effortlayer estimate | No source retrieved |
| Image semanticsCMS-14 | Unverified | Not verified: no first-party Sanity source confirming "Image semantics" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: No cell-level first-party source for Sanity was retrieved in this pass. Confirming "Image semantics" requires reading the vendor's own control documentation and, where the control is a runtime behaviour, observing a live site built on the platform. | configurationconfiguration effortlayer estimate | No source retrieved |
| Structured contentCMS-15 | Unverified | Not verified: no first-party Sanity source confirming "Structured content" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: No cell-level first-party source for Sanity was retrieved in this pass. Confirming "Structured content" requires reading the vendor's own control documentation and, where the control is a runtime behaviour, observing a live site built on the platform. | configurationconfiguration effortlayer estimate | No source retrieved |
| Internal linkingCMS-16 | Unverified | Not verified: no first-party Sanity source confirming "Internal linking" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: No cell-level first-party source for Sanity was retrieved in this pass. Confirming "Internal linking" requires reading the vendor's own control documentation and, where the control is a runtime behaviour, observing a live site built on the platform. | custom codedeveloper effortlayer estimate | No source retrieved |
| AI search crawler controlCMS-17 | Unverified | Not verified: no first-party Sanity source confirming "AI search crawler control" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: No cell-level first-party source for Sanity was retrieved in this pass. Confirming "AI search crawler control" requires reading the vendor's own control documentation and, where the control is a runtime behaviour, observing a live site built on the platform. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
| AI content extractionCMS-18 | Unverified | Not verified: no first-party Sanity source confirming "AI content extraction" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: No cell-level first-party source for Sanity was retrieved in this pass. Confirming "AI content extraction" requires reading the vendor's own control documentation and, where the control is a runtime behaviour, observing a live site built on the platform. | custom codedeveloper effortlayer estimate | No source retrieved |
| Bot infrastructure accessCMS-19 | Unverified | Not verified: no first-party Sanity source confirming "Bot infrastructure access" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: No cell-level first-party source for Sanity was retrieved in this pass. Confirming "Bot infrastructure access" requires reading the vendor's own control documentation and, where the control is a runtime behaviour, observing a live site built on the platform. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
| Change verificationCMS-20 | Unverified | Not verified: no first-party Sanity source confirming "Change verification" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: No cell-level first-party source for Sanity was retrieved in this pass. Confirming "Change verification" requires reading the vendor's own control documentation and, where the control is a runtime behaviour, observing a live site built on the platform. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
StrapiAn open-source headless CMS. Delivery, routing and crawl controls belong to the front-end application and its host.0 of 20 answered
| Check | Status | Observation | Provision | Source |
|---|---|---|---|---|
| HTTP crawlabilityCMS-01 | Unverified | Not verified: no first-party Strapi source confirming "HTTP crawlability" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: No cell-level first-party source for Strapi was retrieved in this pass. Confirming "HTTP crawlability" requires reading the vendor's own control documentation and, where the control is a runtime behaviour, observing a live site built on the platform. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
| Search crawler accessCMS-02 | Unverified | Not verified: no first-party Strapi source confirming "Search crawler access" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: No cell-level first-party source for Strapi was retrieved in this pass. Confirming "Search crawler access" requires reading the vendor's own control documentation and, where the control is a runtime behaviour, observing a live site built on the platform. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
| IndexabilityCMS-03 | Unverified | Not verified: no first-party Strapi source confirming "Indexability" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: No cell-level first-party source for Strapi was retrieved in this pass. Confirming "Indexability" requires reading the vendor's own control documentation and, where the control is a runtime behaviour, observing a live site built on the platform. | custom codedeveloper effortlayer estimate | No source retrieved |
| Content renderingCMS-04 | Unverified | Not verified: no first-party Strapi source confirming "Content rendering" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: No cell-level first-party source for Strapi was retrieved in this pass. Confirming "Content rendering" requires reading the vendor's own control documentation and, where the control is a runtime behaviour, observing a live site built on the platform. | custom codedeveloper effortlayer estimate | No source retrieved |
| Canonical controlCMS-05 | Unverified | Not verified: no first-party Strapi source confirming "Canonical control" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: No cell-level first-party source for Strapi was retrieved in this pass. Confirming "Canonical control" requires reading the vendor's own control documentation and, where the control is a runtime behaviour, observing a live site built on the platform. | custom codedeveloper effortlayer estimate | No source retrieved |
| XML sitemapCMS-06 | Unverified | Not verified: no first-party Strapi source confirming "XML sitemap" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: No cell-level first-party source for Strapi was retrieved in this pass. Confirming "XML sitemap" requires reading the vendor's own control documentation and, where the control is a runtime behaviour, observing a live site built on the platform. | custom codedeveloper effortlayer estimate | No source retrieved |
| Redirect controlCMS-07 | Unverified | Not verified: no first-party Strapi source confirming "Redirect control" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: No cell-level first-party source for Strapi was retrieved in this pass. Confirming "Redirect control" requires reading the vendor's own control documentation and, where the control is a runtime behaviour, observing a live site built on the platform. | custom codedeveloper effortlayer estimate | No source retrieved |
| URL controlCMS-08 | Unverified | Not verified: no first-party Strapi source confirming "URL control" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: No cell-level first-party source for Strapi was retrieved in this pass. Confirming "URL control" requires reading the vendor's own control documentation and, where the control is a runtime behaviour, observing a live site built on the platform. | custom codedeveloper effortlayer estimate | No source retrieved |
| SEO metadataCMS-09 | Unverified | Not verified: no first-party Strapi source confirming "SEO metadata" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: No cell-level first-party source for Strapi was retrieved in this pass. Confirming "SEO metadata" requires reading the vendor's own control documentation and, where the control is a runtime behaviour, observing a live site built on the platform. | configurationconfiguration effortlayer estimate | No source retrieved |
| Semantic HTMLCMS-10 | Unverified | Not verified: no first-party Strapi source confirming "Semantic HTML" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: No cell-level first-party source for Strapi was retrieved in this pass. Confirming "Semantic HTML" requires reading the vendor's own control documentation and, where the control is a runtime behaviour, observing a live site built on the platform. | custom codedeveloper effortlayer estimate | No source retrieved |
| Custom JSON-LDCMS-11 | Unverified | Not verified: no first-party Strapi source confirming "Custom JSON-LD" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: No cell-level first-party source for Strapi was retrieved in this pass. Confirming "Custom JSON-LD" requires reading the vendor's own control documentation and, where the control is a runtime behaviour, observing a live site built on the platform. | custom codedeveloper effortlayer estimate | No source retrieved |
| Page-specific schemaCMS-12 | Unverified | Not verified: no first-party Strapi source confirming "Page-specific schema" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: No cell-level first-party source for Strapi was retrieved in this pass. Confirming "Page-specific schema" requires reading the vendor's own control documentation and, where the control is a runtime behaviour, observing a live site built on the platform. | custom codedeveloper effortlayer estimate | No source retrieved |
| Entity representationCMS-13 | Unverified | Not verified: no first-party Strapi source confirming "Entity representation" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: No cell-level first-party source for Strapi was retrieved in this pass. Confirming "Entity representation" requires reading the vendor's own control documentation and, where the control is a runtime behaviour, observing a live site built on the platform. | custom codedeveloper effortlayer estimate | No source retrieved |
| Image semanticsCMS-14 | Unverified | Not verified: no first-party Strapi source confirming "Image semantics" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: No cell-level first-party source for Strapi was retrieved in this pass. Confirming "Image semantics" requires reading the vendor's own control documentation and, where the control is a runtime behaviour, observing a live site built on the platform. | configurationconfiguration effortlayer estimate | No source retrieved |
| Structured contentCMS-15 | Unverified | Not verified: no first-party Strapi source confirming "Structured content" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: No cell-level first-party source for Strapi was retrieved in this pass. Confirming "Structured content" requires reading the vendor's own control documentation and, where the control is a runtime behaviour, observing a live site built on the platform. | configurationconfiguration effortlayer estimate | No source retrieved |
| Internal linkingCMS-16 | Unverified | Not verified: no first-party Strapi source confirming "Internal linking" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: No cell-level first-party source for Strapi was retrieved in this pass. Confirming "Internal linking" requires reading the vendor's own control documentation and, where the control is a runtime behaviour, observing a live site built on the platform. | custom codedeveloper effortlayer estimate | No source retrieved |
| AI search crawler controlCMS-17 | Unverified | Not verified: no first-party Strapi source confirming "AI search crawler control" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: No cell-level first-party source for Strapi was retrieved in this pass. Confirming "AI search crawler control" requires reading the vendor's own control documentation and, where the control is a runtime behaviour, observing a live site built on the platform. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
| AI content extractionCMS-18 | Unverified | Not verified: no first-party Strapi source confirming "AI content extraction" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: No cell-level first-party source for Strapi was retrieved in this pass. Confirming "AI content extraction" requires reading the vendor's own control documentation and, where the control is a runtime behaviour, observing a live site built on the platform. | custom codedeveloper effortlayer estimate | No source retrieved |
| Bot infrastructure accessCMS-19 | Unverified | Not verified: no first-party Strapi source confirming "Bot infrastructure access" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: No cell-level first-party source for Strapi was retrieved in this pass. Confirming "Bot infrastructure access" requires reading the vendor's own control documentation and, where the control is a runtime behaviour, observing a live site built on the platform. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
| Change verificationCMS-20 | Unverified | Not verified: no first-party Strapi source confirming "Change verification" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: No cell-level first-party source for Strapi was retrieved in this pass. Confirming "Change verification" requires reading the vendor's own control documentation and, where the control is a runtime behaviour, observing a live site built on the platform. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
StoryblokA component-based headless CMS with a visual editor, where rendered markup is produced by the framework layer.1 of 20 answered
| Check | Status | Observation | Provision | Source |
|---|---|---|---|---|
| HTTP crawlabilityCMS-01 | Unverified | Not verified: no first-party Storyblok source confirming "HTTP crawlability" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Storyblok's own headless/SEO FAQ was retrieved and confirmed. It documents the delivery boundary rather than a set of platform controls, so most page-level checks belong to the customer's frontend and were not verified as Storyblok capabilities. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
| Search crawler accessCMS-02 | Unverified | Not verified: no first-party Storyblok source confirming "Search crawler access" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Storyblok's own headless/SEO FAQ was retrieved and confirmed. It documents the delivery boundary rather than a set of platform controls, so most page-level checks belong to the customer's frontend and were not verified as Storyblok capabilities. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
| IndexabilityCMS-03 | Unverified | Not verified: no first-party Storyblok source confirming "Indexability" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Storyblok's own headless/SEO FAQ was retrieved and confirmed. It documents the delivery boundary rather than a set of platform controls, so most page-level checks belong to the customer's frontend and were not verified as Storyblok capabilities. | custom codedeveloper effortlayer estimate | No source retrieved |
| Content renderingCMS-04 | Not applicable | Not a Storyblok capability: Storyblok's FAQ states it delivers content to any frontend as JSON and that the customer's own frontend is responsible for a fast, crawlable site, which places server-rendered HTML with the frontend the customer chose. | custom codedeveloper effort | Storyblok Headless CMS and SEO — Storyblok FAQ |
| Canonical controlCMS-05 | Unverified | Not verified: no first-party Storyblok source confirming "Canonical control" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Storyblok's own headless/SEO FAQ was retrieved and confirmed. It documents the delivery boundary rather than a set of platform controls, so most page-level checks belong to the customer's frontend and were not verified as Storyblok capabilities. | custom codedeveloper effortlayer estimate | No source retrieved |
| XML sitemapCMS-06 | Unverified | Not verified: no first-party Storyblok source confirming "XML sitemap" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Storyblok's own headless/SEO FAQ was retrieved and confirmed. It documents the delivery boundary rather than a set of platform controls, so most page-level checks belong to the customer's frontend and were not verified as Storyblok capabilities. | custom codedeveloper effortlayer estimate | No source retrieved |
| Redirect controlCMS-07 | Unverified | Not verified: no first-party Storyblok source confirming "Redirect control" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Storyblok's own headless/SEO FAQ was retrieved and confirmed. It documents the delivery boundary rather than a set of platform controls, so most page-level checks belong to the customer's frontend and were not verified as Storyblok capabilities. | custom codedeveloper effortlayer estimate | No source retrieved |
| URL controlCMS-08 | Unverified | Not verified: no first-party Storyblok source confirming "URL control" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Storyblok's own headless/SEO FAQ was retrieved and confirmed. It documents the delivery boundary rather than a set of platform controls, so most page-level checks belong to the customer's frontend and were not verified as Storyblok capabilities. | custom codedeveloper effortlayer estimate | No source retrieved |
| SEO metadataCMS-09 | Unverified | Not verified: no first-party Storyblok source confirming "SEO metadata" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Storyblok's own headless/SEO FAQ was retrieved and confirmed. It documents the delivery boundary rather than a set of platform controls, so most page-level checks belong to the customer's frontend and were not verified as Storyblok capabilities. | configurationconfiguration effortlayer estimate | No source retrieved |
| Semantic HTMLCMS-10 | Unverified | Not verified: no first-party Storyblok source confirming "Semantic HTML" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Storyblok's own headless/SEO FAQ was retrieved and confirmed. It documents the delivery boundary rather than a set of platform controls, so most page-level checks belong to the customer's frontend and were not verified as Storyblok capabilities. | custom codedeveloper effortlayer estimate | No source retrieved |
| Custom JSON-LDCMS-11 | Unverified | Not verified: no first-party Storyblok source confirming "Custom JSON-LD" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Storyblok's own headless/SEO FAQ was retrieved and confirmed. It documents the delivery boundary rather than a set of platform controls, so most page-level checks belong to the customer's frontend and were not verified as Storyblok capabilities. | custom codedeveloper effortlayer estimate | No source retrieved |
| Page-specific schemaCMS-12 | Unverified | Not verified: no first-party Storyblok source confirming "Page-specific schema" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Storyblok's own headless/SEO FAQ was retrieved and confirmed. It documents the delivery boundary rather than a set of platform controls, so most page-level checks belong to the customer's frontend and were not verified as Storyblok capabilities. | custom codedeveloper effortlayer estimate | No source retrieved |
| Entity representationCMS-13 | Unverified | Not verified: no first-party Storyblok source confirming "Entity representation" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Storyblok's own headless/SEO FAQ was retrieved and confirmed. It documents the delivery boundary rather than a set of platform controls, so most page-level checks belong to the customer's frontend and were not verified as Storyblok capabilities. | custom codedeveloper effortlayer estimate | No source retrieved |
| Image semanticsCMS-14 | Unverified | Not verified: no first-party Storyblok source confirming "Image semantics" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Storyblok's own headless/SEO FAQ was retrieved and confirmed. It documents the delivery boundary rather than a set of platform controls, so most page-level checks belong to the customer's frontend and were not verified as Storyblok capabilities. | configurationconfiguration effortlayer estimate | No source retrieved |
| Structured contentCMS-15 | Unverified | Not verified: no first-party Storyblok source confirming "Structured content" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Storyblok's own headless/SEO FAQ was retrieved and confirmed. It documents the delivery boundary rather than a set of platform controls, so most page-level checks belong to the customer's frontend and were not verified as Storyblok capabilities. | configurationconfiguration effortlayer estimate | No source retrieved |
| Internal linkingCMS-16 | Unverified | Not verified: no first-party Storyblok source confirming "Internal linking" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Storyblok's own headless/SEO FAQ was retrieved and confirmed. It documents the delivery boundary rather than a set of platform controls, so most page-level checks belong to the customer's frontend and were not verified as Storyblok capabilities. | custom codedeveloper effortlayer estimate | No source retrieved |
| AI search crawler controlCMS-17 | Unverified | Not verified: no first-party Storyblok source confirming "AI search crawler control" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Storyblok's own headless/SEO FAQ was retrieved and confirmed. It documents the delivery boundary rather than a set of platform controls, so most page-level checks belong to the customer's frontend and were not verified as Storyblok capabilities. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
| AI content extractionCMS-18 | Unverified | Not verified: no first-party Storyblok source confirming "AI content extraction" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Storyblok's own headless/SEO FAQ was retrieved and confirmed. It documents the delivery boundary rather than a set of platform controls, so most page-level checks belong to the customer's frontend and were not verified as Storyblok capabilities. | custom codedeveloper effortlayer estimate | No source retrieved |
| Bot infrastructure accessCMS-19 | Unverified | Not verified: no first-party Storyblok source confirming "Bot infrastructure access" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Storyblok's own headless/SEO FAQ was retrieved and confirmed. It documents the delivery boundary rather than a set of platform controls, so most page-level checks belong to the customer's frontend and were not verified as Storyblok capabilities. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
| Change verificationCMS-20 | Unverified | Not verified: no first-party Storyblok source confirming "Change verification" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Storyblok's own headless/SEO FAQ was retrieved and confirmed. It documents the delivery boundary rather than a set of platform controls, so most page-level checks belong to the customer's frontend and were not verified as Storyblok capabilities. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
GhostA hosted publishing platform with a built-in membership and newsletter model, oriented to editorial output rather than enterprise web properties.4 of 20 answered
| Check | Status | Observation | Provision | Source |
|---|---|---|---|---|
| HTTP crawlabilityCMS-01 | Unverified | Not verified: no first-party Ghost source confirming "HTTP crawlability" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Two first-party Ghost pages were retrieved and confirmed (the documentation introduction and the robots.txt help article). An earlier draft of this profile used those two pages to claim custom JSON-LD and per-user-agent AI crawler control. Both were withdrawn: the introduction documents markup Ghost emits automatically rather than schema an operator supplies, and the robots article documents a default file and a theme replacement but does not describe per-user-agent or AI crawler targeting. Indexability, redirects and entity markup need their own Ghost page, or observation of a live Ghost site. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
| Search crawler accessCMS-02 | Partly documented | Ghost documents a default robots.txt and provides a theme-level robots.txt.liquid file, so search crawler access is adjustable by editing the theme rather than from the admin UI. | configurationconfiguration effort | Modifying robots.txt — Ghost Help Center |
| IndexabilityCMS-03 | Unverified | Not verified: no first-party Ghost source confirming "Indexability" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Two first-party Ghost pages were retrieved and confirmed (the documentation introduction and the robots.txt help article). An earlier draft of this profile used those two pages to claim custom JSON-LD and per-user-agent AI crawler control. Both were withdrawn: the introduction documents markup Ghost emits automatically rather than schema an operator supplies, and the robots article documents a default file and a theme replacement but does not describe per-user-agent or AI crawler targeting. Indexability, redirects and entity markup need their own Ghost page, or observation of a live Ghost site. | custom codedeveloper effortlayer estimate | No source retrieved |
| Content renderingCMS-04 | Unverified | Not verified: no first-party Ghost source confirming "Content rendering" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Two first-party Ghost pages were retrieved and confirmed (the documentation introduction and the robots.txt help article). An earlier draft of this profile used those two pages to claim custom JSON-LD and per-user-agent AI crawler control. Both were withdrawn: the introduction documents markup Ghost emits automatically rather than schema an operator supplies, and the robots article documents a default file and a theme replacement but does not describe per-user-agent or AI crawler targeting. Indexability, redirects and entity markup need their own Ghost page, or observation of a live Ghost site. | custom codedeveloper effortlayer estimate | No source retrieved |
| Canonical controlCMS-05 | Partly documented | Ghost's introduction states that a canonical URL is added automatically to each post and page. The check asks whether an operator can set one, and the retrieved page documents no control for choosing or overriding that value. | nativebuilt in effort | Introduction — Ghost Documentation |
| XML sitemapCMS-06 | Documented | Ghost's documentation introduction states that a Google sitemap is generated automatically for publication. | nativebuilt in effort | Introduction — Ghost Documentation |
| Redirect controlCMS-07 | Unverified | Not verified: no first-party Ghost source confirming "Redirect control" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Two first-party Ghost pages were retrieved and confirmed (the documentation introduction and the robots.txt help article). An earlier draft of this profile used those two pages to claim custom JSON-LD and per-user-agent AI crawler control. Both were withdrawn: the introduction documents markup Ghost emits automatically rather than schema an operator supplies, and the robots article documents a default file and a theme replacement but does not describe per-user-agent or AI crawler targeting. Indexability, redirects and entity markup need their own Ghost page, or observation of a live Ghost site. | custom codedeveloper effortlayer estimate | No source retrieved |
| URL controlCMS-08 | Documented | Ghost's introduction states that routing is configurable, so an operator chooses the published URL structure and a post's permalink slug through the publishing interface. | configurationconfiguration effort | Introduction — Ghost Documentation |
| SEO metadataCMS-09 | Unverified | Not verified: no first-party Ghost source confirming "SEO metadata" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Two first-party Ghost pages were retrieved and confirmed (the documentation introduction and the robots.txt help article). An earlier draft of this profile used those two pages to claim custom JSON-LD and per-user-agent AI crawler control. Both were withdrawn: the introduction documents markup Ghost emits automatically rather than schema an operator supplies, and the robots article documents a default file and a theme replacement but does not describe per-user-agent or AI crawler targeting. Indexability, redirects and entity markup need their own Ghost page, or observation of a live Ghost site. | configurationconfiguration effortlayer estimate | No source retrieved |
| Semantic HTMLCMS-10 | Unverified | Not verified: no first-party Ghost source confirming "Semantic HTML" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Two first-party Ghost pages were retrieved and confirmed (the documentation introduction and the robots.txt help article). An earlier draft of this profile used those two pages to claim custom JSON-LD and per-user-agent AI crawler control. Both were withdrawn: the introduction documents markup Ghost emits automatically rather than schema an operator supplies, and the robots article documents a default file and a theme replacement but does not describe per-user-agent or AI crawler targeting. Indexability, redirects and entity markup need their own Ghost page, or observation of a live Ghost site. | custom codedeveloper effortlayer estimate | No source retrieved |
| Custom JSON-LDCMS-11 | Unverified | Not verified: no first-party Ghost source confirming "Custom JSON-LD" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Two first-party Ghost pages were retrieved and confirmed (the documentation introduction and the robots.txt help article). An earlier draft of this profile used those two pages to claim custom JSON-LD and per-user-agent AI crawler control. Both were withdrawn: the introduction documents markup Ghost emits automatically rather than schema an operator supplies, and the robots article documents a default file and a theme replacement but does not describe per-user-agent or AI crawler targeting. Indexability, redirects and entity markup need their own Ghost page, or observation of a live Ghost site. | custom codedeveloper effortlayer estimate | No source retrieved |
| Page-specific schemaCMS-12 | Unverified | Not verified: no first-party Ghost source confirming "Page-specific schema" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Two first-party Ghost pages were retrieved and confirmed (the documentation introduction and the robots.txt help article). An earlier draft of this profile used those two pages to claim custom JSON-LD and per-user-agent AI crawler control. Both were withdrawn: the introduction documents markup Ghost emits automatically rather than schema an operator supplies, and the robots article documents a default file and a theme replacement but does not describe per-user-agent or AI crawler targeting. Indexability, redirects and entity markup need their own Ghost page, or observation of a live Ghost site. | custom codedeveloper effortlayer estimate | No source retrieved |
| Entity representationCMS-13 | Unverified | Not verified: no first-party Ghost source confirming "Entity representation" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Two first-party Ghost pages were retrieved and confirmed (the documentation introduction and the robots.txt help article). An earlier draft of this profile used those two pages to claim custom JSON-LD and per-user-agent AI crawler control. Both were withdrawn: the introduction documents markup Ghost emits automatically rather than schema an operator supplies, and the robots article documents a default file and a theme replacement but does not describe per-user-agent or AI crawler targeting. Indexability, redirects and entity markup need their own Ghost page, or observation of a live Ghost site. | custom codedeveloper effortlayer estimate | No source retrieved |
| Image semanticsCMS-14 | Unverified | Not verified: no first-party Ghost source confirming "Image semantics" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Two first-party Ghost pages were retrieved and confirmed (the documentation introduction and the robots.txt help article). An earlier draft of this profile used those two pages to claim custom JSON-LD and per-user-agent AI crawler control. Both were withdrawn: the introduction documents markup Ghost emits automatically rather than schema an operator supplies, and the robots article documents a default file and a theme replacement but does not describe per-user-agent or AI crawler targeting. Indexability, redirects and entity markup need their own Ghost page, or observation of a live Ghost site. | configurationconfiguration effortlayer estimate | No source retrieved |
| Structured contentCMS-15 | Unverified | Not verified: no first-party Ghost source confirming "Structured content" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Two first-party Ghost pages were retrieved and confirmed (the documentation introduction and the robots.txt help article). An earlier draft of this profile used those two pages to claim custom JSON-LD and per-user-agent AI crawler control. Both were withdrawn: the introduction documents markup Ghost emits automatically rather than schema an operator supplies, and the robots article documents a default file and a theme replacement but does not describe per-user-agent or AI crawler targeting. Indexability, redirects and entity markup need their own Ghost page, or observation of a live Ghost site. | configurationconfiguration effortlayer estimate | No source retrieved |
| Internal linkingCMS-16 | Unverified | Not verified: no first-party Ghost source confirming "Internal linking" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Two first-party Ghost pages were retrieved and confirmed (the documentation introduction and the robots.txt help article). An earlier draft of this profile used those two pages to claim custom JSON-LD and per-user-agent AI crawler control. Both were withdrawn: the introduction documents markup Ghost emits automatically rather than schema an operator supplies, and the robots article documents a default file and a theme replacement but does not describe per-user-agent or AI crawler targeting. Indexability, redirects and entity markup need their own Ghost page, or observation of a live Ghost site. | custom codedeveloper effortlayer estimate | No source retrieved |
| AI search crawler controlCMS-17 | Unverified | Not verified: no first-party Ghost source confirming "AI search crawler control" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Two first-party Ghost pages were retrieved and confirmed (the documentation introduction and the robots.txt help article). An earlier draft of this profile used those two pages to claim custom JSON-LD and per-user-agent AI crawler control. Both were withdrawn: the introduction documents markup Ghost emits automatically rather than schema an operator supplies, and the robots article documents a default file and a theme replacement but does not describe per-user-agent or AI crawler targeting. Indexability, redirects and entity markup need their own Ghost page, or observation of a live Ghost site. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
| AI content extractionCMS-18 | Unverified | Not verified: no first-party Ghost source confirming "AI content extraction" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Two first-party Ghost pages were retrieved and confirmed (the documentation introduction and the robots.txt help article). An earlier draft of this profile used those two pages to claim custom JSON-LD and per-user-agent AI crawler control. Both were withdrawn: the introduction documents markup Ghost emits automatically rather than schema an operator supplies, and the robots article documents a default file and a theme replacement but does not describe per-user-agent or AI crawler targeting. Indexability, redirects and entity markup need their own Ghost page, or observation of a live Ghost site. | custom codedeveloper effortlayer estimate | No source retrieved |
| Bot infrastructure accessCMS-19 | Unverified | Not verified: no first-party Ghost source confirming "Bot infrastructure access" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Two first-party Ghost pages were retrieved and confirmed (the documentation introduction and the robots.txt help article). An earlier draft of this profile used those two pages to claim custom JSON-LD and per-user-agent AI crawler control. Both were withdrawn: the introduction documents markup Ghost emits automatically rather than schema an operator supplies, and the robots article documents a default file and a theme replacement but does not describe per-user-agent or AI crawler targeting. Indexability, redirects and entity markup need their own Ghost page, or observation of a live Ghost site. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
| Change verificationCMS-20 | Unverified | Not verified: no first-party Ghost source confirming "Change verification" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Two first-party Ghost pages were retrieved and confirmed (the documentation introduction and the robots.txt help article). An earlier draft of this profile used those two pages to claim custom JSON-LD and per-user-agent AI crawler control. Both were withdrawn: the introduction documents markup Ghost emits automatically rather than schema an operator supplies, and the robots article documents a default file and a theme replacement but does not describe per-user-agent or AI crawler targeting. Indexability, redirects and entity markup need their own Ghost page, or observation of a live Ghost site. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
DrupalAn enterprise open-source CMS with deep URL, redirect and metadata control, at the cost of significant implementation effort.1 of 20 answered
| Check | Status | Observation | Provision | Source |
|---|---|---|---|---|
| HTTP crawlabilityCMS-01 | Unverified | Not verified: no first-party Drupal source confirming "HTTP crawlability" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Drupal's web properties returned a bot challenge rather than readable article text in this pass, so only Drupal core's own robots.txt scaffold was read and confirmed. It is the one file in core that establishes a real, shipped control; the sitemap, redirect, metadata and schema capabilities visible in search results come from contributed community modules and Drupal CMS recipes rather than core, and those pages could not be retrieved here, so they are not encoded. Verifying them requires reading the module or recipe pages in a readable session, and any such cell should be recorded as an extension or configuration dependency rather than a core capability. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
| Search crawler accessCMS-02 | Partly documented | Drupal core ships a robots.txt scaffold containing a single User-agent: * group that allows core and profile asset paths and disallows /core/, /profiles/, /admin/, search, user and oembed paths. The file is a static scaffold on disk rather than an administrative control. | infrastructureinfrastructure effort | robots.txt scaffold file — Drupal core |
| IndexabilityCMS-03 | Unverified | Not verified: no first-party Drupal source confirming "Indexability" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Drupal's web properties returned a bot challenge rather than readable article text in this pass, so only Drupal core's own robots.txt scaffold was read and confirmed. It is the one file in core that establishes a real, shipped control; the sitemap, redirect, metadata and schema capabilities visible in search results come from contributed community modules and Drupal CMS recipes rather than core, and those pages could not be retrieved here, so they are not encoded. Verifying them requires reading the module or recipe pages in a readable session, and any such cell should be recorded as an extension or configuration dependency rather than a core capability. | custom codedeveloper effortlayer estimate | No source retrieved |
| Content renderingCMS-04 | Unverified | Not verified: no first-party Drupal source confirming "Content rendering" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Drupal's web properties returned a bot challenge rather than readable article text in this pass, so only Drupal core's own robots.txt scaffold was read and confirmed. It is the one file in core that establishes a real, shipped control; the sitemap, redirect, metadata and schema capabilities visible in search results come from contributed community modules and Drupal CMS recipes rather than core, and those pages could not be retrieved here, so they are not encoded. Verifying them requires reading the module or recipe pages in a readable session, and any such cell should be recorded as an extension or configuration dependency rather than a core capability. | custom codedeveloper effortlayer estimate | No source retrieved |
| Canonical controlCMS-05 | Unverified | Not verified: no first-party Drupal source confirming "Canonical control" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Drupal's web properties returned a bot challenge rather than readable article text in this pass, so only Drupal core's own robots.txt scaffold was read and confirmed. It is the one file in core that establishes a real, shipped control; the sitemap, redirect, metadata and schema capabilities visible in search results come from contributed community modules and Drupal CMS recipes rather than core, and those pages could not be retrieved here, so they are not encoded. Verifying them requires reading the module or recipe pages in a readable session, and any such cell should be recorded as an extension or configuration dependency rather than a core capability. | custom codedeveloper effortlayer estimate | No source retrieved |
| XML sitemapCMS-06 | Unverified | Not verified: no first-party Drupal source confirming "XML sitemap" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Drupal's web properties returned a bot challenge rather than readable article text in this pass, so only Drupal core's own robots.txt scaffold was read and confirmed. It is the one file in core that establishes a real, shipped control; the sitemap, redirect, metadata and schema capabilities visible in search results come from contributed community modules and Drupal CMS recipes rather than core, and those pages could not be retrieved here, so they are not encoded. Verifying them requires reading the module or recipe pages in a readable session, and any such cell should be recorded as an extension or configuration dependency rather than a core capability. | custom codedeveloper effortlayer estimate | No source retrieved |
| Redirect controlCMS-07 | Unverified | Not verified: no first-party Drupal source confirming "Redirect control" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Drupal's web properties returned a bot challenge rather than readable article text in this pass, so only Drupal core's own robots.txt scaffold was read and confirmed. It is the one file in core that establishes a real, shipped control; the sitemap, redirect, metadata and schema capabilities visible in search results come from contributed community modules and Drupal CMS recipes rather than core, and those pages could not be retrieved here, so they are not encoded. Verifying them requires reading the module or recipe pages in a readable session, and any such cell should be recorded as an extension or configuration dependency rather than a core capability. | custom codedeveloper effortlayer estimate | No source retrieved |
| URL controlCMS-08 | Unverified | Not verified: no first-party Drupal source confirming "URL control" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Drupal's web properties returned a bot challenge rather than readable article text in this pass, so only Drupal core's own robots.txt scaffold was read and confirmed. It is the one file in core that establishes a real, shipped control; the sitemap, redirect, metadata and schema capabilities visible in search results come from contributed community modules and Drupal CMS recipes rather than core, and those pages could not be retrieved here, so they are not encoded. Verifying them requires reading the module or recipe pages in a readable session, and any such cell should be recorded as an extension or configuration dependency rather than a core capability. | custom codedeveloper effortlayer estimate | No source retrieved |
| SEO metadataCMS-09 | Unverified | Not verified: no first-party Drupal source confirming "SEO metadata" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Drupal's web properties returned a bot challenge rather than readable article text in this pass, so only Drupal core's own robots.txt scaffold was read and confirmed. It is the one file in core that establishes a real, shipped control; the sitemap, redirect, metadata and schema capabilities visible in search results come from contributed community modules and Drupal CMS recipes rather than core, and those pages could not be retrieved here, so they are not encoded. Verifying them requires reading the module or recipe pages in a readable session, and any such cell should be recorded as an extension or configuration dependency rather than a core capability. | configurationconfiguration effortlayer estimate | No source retrieved |
| Semantic HTMLCMS-10 | Unverified | Not verified: no first-party Drupal source confirming "Semantic HTML" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Drupal's web properties returned a bot challenge rather than readable article text in this pass, so only Drupal core's own robots.txt scaffold was read and confirmed. It is the one file in core that establishes a real, shipped control; the sitemap, redirect, metadata and schema capabilities visible in search results come from contributed community modules and Drupal CMS recipes rather than core, and those pages could not be retrieved here, so they are not encoded. Verifying them requires reading the module or recipe pages in a readable session, and any such cell should be recorded as an extension or configuration dependency rather than a core capability. | custom codedeveloper effortlayer estimate | No source retrieved |
| Custom JSON-LDCMS-11 | Unverified | Not verified: no first-party Drupal source confirming "Custom JSON-LD" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Drupal's web properties returned a bot challenge rather than readable article text in this pass, so only Drupal core's own robots.txt scaffold was read and confirmed. It is the one file in core that establishes a real, shipped control; the sitemap, redirect, metadata and schema capabilities visible in search results come from contributed community modules and Drupal CMS recipes rather than core, and those pages could not be retrieved here, so they are not encoded. Verifying them requires reading the module or recipe pages in a readable session, and any such cell should be recorded as an extension or configuration dependency rather than a core capability. | custom codedeveloper effortlayer estimate | No source retrieved |
| Page-specific schemaCMS-12 | Unverified | Not verified: no first-party Drupal source confirming "Page-specific schema" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Drupal's web properties returned a bot challenge rather than readable article text in this pass, so only Drupal core's own robots.txt scaffold was read and confirmed. It is the one file in core that establishes a real, shipped control; the sitemap, redirect, metadata and schema capabilities visible in search results come from contributed community modules and Drupal CMS recipes rather than core, and those pages could not be retrieved here, so they are not encoded. Verifying them requires reading the module or recipe pages in a readable session, and any such cell should be recorded as an extension or configuration dependency rather than a core capability. | custom codedeveloper effortlayer estimate | No source retrieved |
| Entity representationCMS-13 | Unverified | Not verified: no first-party Drupal source confirming "Entity representation" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Drupal's web properties returned a bot challenge rather than readable article text in this pass, so only Drupal core's own robots.txt scaffold was read and confirmed. It is the one file in core that establishes a real, shipped control; the sitemap, redirect, metadata and schema capabilities visible in search results come from contributed community modules and Drupal CMS recipes rather than core, and those pages could not be retrieved here, so they are not encoded. Verifying them requires reading the module or recipe pages in a readable session, and any such cell should be recorded as an extension or configuration dependency rather than a core capability. | custom codedeveloper effortlayer estimate | No source retrieved |
| Image semanticsCMS-14 | Unverified | Not verified: no first-party Drupal source confirming "Image semantics" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Drupal's web properties returned a bot challenge rather than readable article text in this pass, so only Drupal core's own robots.txt scaffold was read and confirmed. It is the one file in core that establishes a real, shipped control; the sitemap, redirect, metadata and schema capabilities visible in search results come from contributed community modules and Drupal CMS recipes rather than core, and those pages could not be retrieved here, so they are not encoded. Verifying them requires reading the module or recipe pages in a readable session, and any such cell should be recorded as an extension or configuration dependency rather than a core capability. | configurationconfiguration effortlayer estimate | No source retrieved |
| Structured contentCMS-15 | Unverified | Not verified: no first-party Drupal source confirming "Structured content" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Drupal's web properties returned a bot challenge rather than readable article text in this pass, so only Drupal core's own robots.txt scaffold was read and confirmed. It is the one file in core that establishes a real, shipped control; the sitemap, redirect, metadata and schema capabilities visible in search results come from contributed community modules and Drupal CMS recipes rather than core, and those pages could not be retrieved here, so they are not encoded. Verifying them requires reading the module or recipe pages in a readable session, and any such cell should be recorded as an extension or configuration dependency rather than a core capability. | configurationconfiguration effortlayer estimate | No source retrieved |
| Internal linkingCMS-16 | Unverified | Not verified: no first-party Drupal source confirming "Internal linking" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Drupal's web properties returned a bot challenge rather than readable article text in this pass, so only Drupal core's own robots.txt scaffold was read and confirmed. It is the one file in core that establishes a real, shipped control; the sitemap, redirect, metadata and schema capabilities visible in search results come from contributed community modules and Drupal CMS recipes rather than core, and those pages could not be retrieved here, so they are not encoded. Verifying them requires reading the module or recipe pages in a readable session, and any such cell should be recorded as an extension or configuration dependency rather than a core capability. | custom codedeveloper effortlayer estimate | No source retrieved |
| AI search crawler controlCMS-17 | Unverified | Not verified: no first-party Drupal source confirming "AI search crawler control" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Drupal's web properties returned a bot challenge rather than readable article text in this pass, so only Drupal core's own robots.txt scaffold was read and confirmed. It is the one file in core that establishes a real, shipped control; the sitemap, redirect, metadata and schema capabilities visible in search results come from contributed community modules and Drupal CMS recipes rather than core, and those pages could not be retrieved here, so they are not encoded. Verifying them requires reading the module or recipe pages in a readable session, and any such cell should be recorded as an extension or configuration dependency rather than a core capability. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
| AI content extractionCMS-18 | Unverified | Not verified: no first-party Drupal source confirming "AI content extraction" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Drupal's web properties returned a bot challenge rather than readable article text in this pass, so only Drupal core's own robots.txt scaffold was read and confirmed. It is the one file in core that establishes a real, shipped control; the sitemap, redirect, metadata and schema capabilities visible in search results come from contributed community modules and Drupal CMS recipes rather than core, and those pages could not be retrieved here, so they are not encoded. Verifying them requires reading the module or recipe pages in a readable session, and any such cell should be recorded as an extension or configuration dependency rather than a core capability. | custom codedeveloper effortlayer estimate | No source retrieved |
| Bot infrastructure accessCMS-19 | Unverified | Not verified: no first-party Drupal source confirming "Bot infrastructure access" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Drupal's web properties returned a bot challenge rather than readable article text in this pass, so only Drupal core's own robots.txt scaffold was read and confirmed. It is the one file in core that establishes a real, shipped control; the sitemap, redirect, metadata and schema capabilities visible in search results come from contributed community modules and Drupal CMS recipes rather than core, and those pages could not be retrieved here, so they are not encoded. Verifying them requires reading the module or recipe pages in a readable session, and any such cell should be recorded as an extension or configuration dependency rather than a core capability. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
| Change verificationCMS-20 | Unverified | Not verified: no first-party Drupal source confirming "Change verification" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Drupal's web properties returned a bot challenge rather than readable article text in this pass, so only Drupal core's own robots.txt scaffold was read and confirmed. It is the one file in core that establishes a real, shipped control; the sitemap, redirect, metadata and schema capabilities visible in search results come from contributed community modules and Drupal CMS recipes rather than core, and those pages could not be retrieved here, so they are not encoded. Verifying them requires reading the module or recipe pages in a readable session, and any such cell should be recorded as an extension or configuration dependency rather than a core capability. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
ShopifyA hosted commerce platform. Its documentation is unusually explicit about crawler layers, and it states that network-level bot management is handled for stores on the platform.4 of 20 answered
| Check | Status | Observation | Provision | Source |
|---|---|---|---|---|
| HTTP crawlabilityCMS-01 | Unverified | Not verified: no first-party Shopify source confirming "HTTP crawlability" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Shopify's help centre documents crawler behaviour but does not publish per-tier control matrices, so this cell rests on unconfirmed inference about the hosted runtime. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
| Search crawler accessCMS-02 | Documented | Every store is served a default robots.txt described by Shopify as optimal for SEO, and customisation is available by adding a robots.txt.liquid template. | configurationconfiguration effort | Editing robots.txt.liquid — Shopify Help Center |
| IndexabilityCMS-03 | Unverified | Not verified: no first-party Shopify source confirming "Indexability" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Shopify's help centre documents crawler behaviour but does not publish per-tier control matrices, so this cell rests on unconfirmed inference about the hosted runtime. | custom codedeveloper effortlayer estimate | No source retrieved |
| Content renderingCMS-04 | Unverified | Not verified: no first-party Shopify source confirming "Content rendering" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Shopify's help centre documents crawler behaviour but does not publish per-tier control matrices, so this cell rests on unconfirmed inference about the hosted runtime. | custom codedeveloper effortlayer estimate | No source retrieved |
| Canonical controlCMS-05 | Unverified | Not verified: no first-party Shopify source confirming "Canonical control" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Shopify's help centre documents crawler behaviour but does not publish per-tier control matrices, so this cell rests on unconfirmed inference about the hosted runtime. | custom codedeveloper effortlayer estimate | No source retrieved |
| XML sitemapCMS-06 | Documented | Shopify states that all stores automatically generate a sitemap.xml containing products, primary product images, pages, collections and blog posts, and that files update as content is added. | nativebuilt in effort | Finding and submitting your sitemap — Shopify Help Center |
| Redirect controlCMS-07 | Unverified | Not verified: no first-party Shopify source confirming "Redirect control" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Shopify's help centre documents crawler behaviour but does not publish per-tier control matrices, so this cell rests on unconfirmed inference about the hosted runtime. | custom codedeveloper effortlayer estimate | No source retrieved |
| URL controlCMS-08 | Unverified | Not verified: no first-party Shopify source confirming "URL control" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Shopify's help centre documents crawler behaviour but does not publish per-tier control matrices, so this cell rests on unconfirmed inference about the hosted runtime. | custom codedeveloper effortlayer estimate | No source retrieved |
| SEO metadataCMS-09 | Unverified | Not verified: no first-party Shopify source confirming "SEO metadata" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Shopify's help centre documents crawler behaviour but does not publish per-tier control matrices, so this cell rests on unconfirmed inference about the hosted runtime. | configurationconfiguration effortlayer estimate | No source retrieved |
| Semantic HTMLCMS-10 | Unverified | Not verified: no first-party Shopify source confirming "Semantic HTML" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Shopify's help centre documents crawler behaviour but does not publish per-tier control matrices, so this cell rests on unconfirmed inference about the hosted runtime. | custom codedeveloper effortlayer estimate | No source retrieved |
| Custom JSON-LDCMS-11 | Unverified | Not verified: no first-party Shopify source confirming "Custom JSON-LD" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Shopify's help centre documents crawler behaviour but does not publish per-tier control matrices, so this cell rests on unconfirmed inference about the hosted runtime. | custom codedeveloper effortlayer estimate | No source retrieved |
| Page-specific schemaCMS-12 | Unverified | Not verified: no first-party Shopify source confirming "Page-specific schema" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Shopify's help centre documents crawler behaviour but does not publish per-tier control matrices, so this cell rests on unconfirmed inference about the hosted runtime. | custom codedeveloper effortlayer estimate | No source retrieved |
| Entity representationCMS-13 | Unverified | Not verified: no first-party Shopify source confirming "Entity representation" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Shopify's help centre documents crawler behaviour but does not publish per-tier control matrices, so this cell rests on unconfirmed inference about the hosted runtime. | custom codedeveloper effortlayer estimate | No source retrieved |
| Image semanticsCMS-14 | Unverified | Not verified: no first-party Shopify source confirming "Image semantics" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Shopify's help centre documents crawler behaviour but does not publish per-tier control matrices, so this cell rests on unconfirmed inference about the hosted runtime. | configurationconfiguration effortlayer estimate | No source retrieved |
| Structured contentCMS-15 | Unverified | Not verified: no first-party Shopify source confirming "Structured content" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Shopify's help centre documents crawler behaviour but does not publish per-tier control matrices, so this cell rests on unconfirmed inference about the hosted runtime. | configurationconfiguration effortlayer estimate | No source retrieved |
| Internal linkingCMS-16 | Unverified | Not verified: no first-party Shopify source confirming "Internal linking" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Shopify's help centre documents crawler behaviour but does not publish per-tier control matrices, so this cell rests on unconfirmed inference about the hosted runtime. | custom codedeveloper effortlayer estimate | No source retrieved |
| AI search crawler controlCMS-17 | Documented | Shopify documents controlling AI crawler access at two layers, including allowing or blocking specific user-agent crawlers through robots.txt.liquid, and states that these rules are directional and advisory. | configurationconfiguration effort | Editing robots.txt.liquid — Shopify Help Center |
| AI content extractionCMS-18 | Partly documented | Shopify publishes guidance for making product detail pages legible to AI systems and offers a first-party Knowledge Base app for curating the FAQs AI shopping agents use. | extensionextension effort | Optimizing your store for AI — Shopify Help Center |
| Bot infrastructure accessCMS-19 | Unverified | Not verified: no first-party Shopify source confirming "Bot infrastructure access" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Shopify's help centre documents crawler behaviour but does not publish per-tier control matrices, so this cell rests on unconfirmed inference about the hosted runtime. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
| Change verificationCMS-20 | Unverified | Not verified: no first-party Shopify source confirming "Change verification" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Shopify's help centre documents crawler behaviour but does not publish per-tier control matrices, so this cell rests on unconfirmed inference about the hosted runtime. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
WixA hosted website builder whose SEO surface is largely fixed, with editing constrained to what the platform exposes.4 of 20 answered
| Check | Status | Observation | Provision | Source |
|---|---|---|---|---|
| HTTP crawlabilityCMS-01 | Unverified | Not verified: no first-party Wix source confirming "HTTP crawlability" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Wix's Advanced SEO and sitemap help articles were retrieved and confirmed. An earlier draft cited Advanced SEO for per-page title and meta description fields; that claim was withdrawn, because the page documents default SEO and social meta tags rather than title, description and robots directive controls. Indexability directives, URL control and custom entity markup need their own Wix page. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
| Search crawler accessCMS-02 | Unverified | Not verified: no first-party Wix source confirming "Search crawler access" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Wix's Advanced SEO and sitemap help articles were retrieved and confirmed. An earlier draft cited Advanced SEO for per-page title and meta description fields; that claim was withdrawn, because the page documents default SEO and social meta tags rather than title, description and robots directive controls. Indexability directives, URL control and custom entity markup need their own Wix page. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
| IndexabilityCMS-03 | Unverified | Not verified: no first-party Wix source confirming "Indexability" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Wix's Advanced SEO and sitemap help articles were retrieved and confirmed. An earlier draft cited Advanced SEO for per-page title and meta description fields; that claim was withdrawn, because the page documents default SEO and social meta tags rather than title, description and robots directive controls. Indexability directives, URL control and custom entity markup need their own Wix page. | custom codedeveloper effortlayer estimate | No source retrieved |
| Content renderingCMS-04 | Unverified | Not verified: no first-party Wix source confirming "Content rendering" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Wix's Advanced SEO and sitemap help articles were retrieved and confirmed. An earlier draft cited Advanced SEO for per-page title and meta description fields; that claim was withdrawn, because the page documents default SEO and social meta tags rather than title, description and robots directive controls. Indexability directives, URL control and custom entity markup need their own Wix page. | custom codedeveloper effortlayer estimate | No source retrieved |
| Canonical controlCMS-05 | Documented | Wix documents a canonical URL field per page in Advanced SEO settings, defaulting to the page URL and editable where a different canonical is required. | configurationconfiguration effort | SEO Settings: Advanced SEO — Wix Help Center |
| XML sitemapCMS-06 | Documented | Wix states that a sitemap is generated automatically, is kept updated as site content changes, and is submitted to search engines on the site's behalf. | nativebuilt in effort | Understanding your site's sitemap file — Wix Help Center |
| Redirect controlCMS-07 | Unverified | Not verified: no first-party Wix source confirming "Redirect control" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Wix's Advanced SEO and sitemap help articles were retrieved and confirmed. An earlier draft cited Advanced SEO for per-page title and meta description fields; that claim was withdrawn, because the page documents default SEO and social meta tags rather than title, description and robots directive controls. Indexability directives, URL control and custom entity markup need their own Wix page. | custom codedeveloper effortlayer estimate | No source retrieved |
| URL controlCMS-08 | Unverified | Not verified: no first-party Wix source confirming "URL control" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Wix's Advanced SEO and sitemap help articles were retrieved and confirmed. An earlier draft cited Advanced SEO for per-page title and meta description fields; that claim was withdrawn, because the page documents default SEO and social meta tags rather than title, description and robots directive controls. Indexability directives, URL control and custom entity markup need their own Wix page. | custom codedeveloper effortlayer estimate | No source retrieved |
| SEO metadataCMS-09 | Unverified | Not verified: no first-party Wix source confirming "SEO metadata" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Wix's Advanced SEO and sitemap help articles were retrieved and confirmed. An earlier draft cited Advanced SEO for per-page title and meta description fields; that claim was withdrawn, because the page documents default SEO and social meta tags rather than title, description and robots directive controls. Indexability directives, URL control and custom entity markup need their own Wix page. | configurationconfiguration effortlayer estimate | No source retrieved |
| Semantic HTMLCMS-10 | Unverified | Not verified: no first-party Wix source confirming "Semantic HTML" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Wix's Advanced SEO and sitemap help articles were retrieved and confirmed. An earlier draft cited Advanced SEO for per-page title and meta description fields; that claim was withdrawn, because the page documents default SEO and social meta tags rather than title, description and robots directive controls. Indexability directives, URL control and custom entity markup need their own Wix page. | custom codedeveloper effortlayer estimate | No source retrieved |
| Custom JSON-LDCMS-11 | Partly documented | Wix offers predefined structured data presets in Advanced SEO and allows custom JSON-LD to be pasted per page, documented as limited to five markups per page and 7,000 characters. | configurationconfiguration effort | SEO Settings: Advanced SEO — Wix Help Center |
| Page-specific schemaCMS-12 | Documented | Wix documents structured data scoped to page type, with separate presets for store product and category pages, booking pages, blog posts and event pages. | configurationconfiguration effort | SEO Settings: Advanced SEO — Wix Help Center |
| Entity representationCMS-13 | Unverified | Not verified: no first-party Wix source confirming "Entity representation" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Wix's Advanced SEO and sitemap help articles were retrieved and confirmed. An earlier draft cited Advanced SEO for per-page title and meta description fields; that claim was withdrawn, because the page documents default SEO and social meta tags rather than title, description and robots directive controls. Indexability directives, URL control and custom entity markup need their own Wix page. | custom codedeveloper effortlayer estimate | No source retrieved |
| Image semanticsCMS-14 | Unverified | Not verified: no first-party Wix source confirming "Image semantics" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Wix's Advanced SEO and sitemap help articles were retrieved and confirmed. An earlier draft cited Advanced SEO for per-page title and meta description fields; that claim was withdrawn, because the page documents default SEO and social meta tags rather than title, description and robots directive controls. Indexability directives, URL control and custom entity markup need their own Wix page. | configurationconfiguration effortlayer estimate | No source retrieved |
| Structured contentCMS-15 | Unverified | Not verified: no first-party Wix source confirming "Structured content" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Wix's Advanced SEO and sitemap help articles were retrieved and confirmed. An earlier draft cited Advanced SEO for per-page title and meta description fields; that claim was withdrawn, because the page documents default SEO and social meta tags rather than title, description and robots directive controls. Indexability directives, URL control and custom entity markup need their own Wix page. | configurationconfiguration effortlayer estimate | No source retrieved |
| Internal linkingCMS-16 | Unverified | Not verified: no first-party Wix source confirming "Internal linking" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Wix's Advanced SEO and sitemap help articles were retrieved and confirmed. An earlier draft cited Advanced SEO for per-page title and meta description fields; that claim was withdrawn, because the page documents default SEO and social meta tags rather than title, description and robots directive controls. Indexability directives, URL control and custom entity markup need their own Wix page. | custom codedeveloper effortlayer estimate | No source retrieved |
| AI search crawler controlCMS-17 | Unverified | Not verified: no first-party Wix source confirming "AI search crawler control" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Wix's Advanced SEO and sitemap help articles were retrieved and confirmed. An earlier draft cited Advanced SEO for per-page title and meta description fields; that claim was withdrawn, because the page documents default SEO and social meta tags rather than title, description and robots directive controls. Indexability directives, URL control and custom entity markup need their own Wix page. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
| AI content extractionCMS-18 | Unverified | Not verified: no first-party Wix source confirming "AI content extraction" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Wix's Advanced SEO and sitemap help articles were retrieved and confirmed. An earlier draft cited Advanced SEO for per-page title and meta description fields; that claim was withdrawn, because the page documents default SEO and social meta tags rather than title, description and robots directive controls. Indexability directives, URL control and custom entity markup need their own Wix page. | custom codedeveloper effortlayer estimate | No source retrieved |
| Bot infrastructure accessCMS-19 | Unverified | Not verified: no first-party Wix source confirming "Bot infrastructure access" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Wix's Advanced SEO and sitemap help articles were retrieved and confirmed. An earlier draft cited Advanced SEO for per-page title and meta description fields; that claim was withdrawn, because the page documents default SEO and social meta tags rather than title, description and robots directive controls. Indexability directives, URL control and custom entity markup need their own Wix page. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
| Change verificationCMS-20 | Unverified | Not verified: no first-party Wix source confirming "Change verification" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Wix's Advanced SEO and sitemap help articles were retrieved and confirmed. An earlier draft cited Advanced SEO for per-page title and meta description fields; that claim was withdrawn, because the page documents default SEO and social meta tags rather than title, description and robots directive controls. Indexability directives, URL control and custom entity markup need their own Wix page. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
SquarespaceA hosted site builder with a deliberately limited SEO surface, favouring a working default over operator control.0 of 20 answered
| Check | Status | Observation | Provision | Source |
|---|---|---|---|---|
| HTTP crawlabilityCMS-01 | Unverified | Not verified: no first-party Squarespace source confirming "HTTP crawlability" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Retrieval was attempted and did not produce readable first-party text. Squarespace's AI-crawler help article was requested directly and returned a sign-in-required page shell with no article body, so nothing from it could be quoted or confirmed. Search snippets were not accepted as a substitute. Verifying any Squarespace cell requires reading the vendor page in a readable session. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
| Search crawler accessCMS-02 | Unverified | Not verified: no first-party Squarespace source confirming "Search crawler access" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Retrieval was attempted and did not produce readable first-party text. Squarespace's AI-crawler help article was requested directly and returned a sign-in-required page shell with no article body, so nothing from it could be quoted or confirmed. Search snippets were not accepted as a substitute. Verifying any Squarespace cell requires reading the vendor page in a readable session. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
| IndexabilityCMS-03 | Unverified | Not verified: no first-party Squarespace source confirming "Indexability" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Retrieval was attempted and did not produce readable first-party text. Squarespace's AI-crawler help article was requested directly and returned a sign-in-required page shell with no article body, so nothing from it could be quoted or confirmed. Search snippets were not accepted as a substitute. Verifying any Squarespace cell requires reading the vendor page in a readable session. | custom codedeveloper effortlayer estimate | No source retrieved |
| Content renderingCMS-04 | Unverified | Not verified: no first-party Squarespace source confirming "Content rendering" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Retrieval was attempted and did not produce readable first-party text. Squarespace's AI-crawler help article was requested directly and returned a sign-in-required page shell with no article body, so nothing from it could be quoted or confirmed. Search snippets were not accepted as a substitute. Verifying any Squarespace cell requires reading the vendor page in a readable session. | custom codedeveloper effortlayer estimate | No source retrieved |
| Canonical controlCMS-05 | Unverified | Not verified: no first-party Squarespace source confirming "Canonical control" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Retrieval was attempted and did not produce readable first-party text. Squarespace's AI-crawler help article was requested directly and returned a sign-in-required page shell with no article body, so nothing from it could be quoted or confirmed. Search snippets were not accepted as a substitute. Verifying any Squarespace cell requires reading the vendor page in a readable session. | custom codedeveloper effortlayer estimate | No source retrieved |
| XML sitemapCMS-06 | Unverified | Not verified: no first-party Squarespace source confirming "XML sitemap" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Retrieval was attempted and did not produce readable first-party text. Squarespace's AI-crawler help article was requested directly and returned a sign-in-required page shell with no article body, so nothing from it could be quoted or confirmed. Search snippets were not accepted as a substitute. Verifying any Squarespace cell requires reading the vendor page in a readable session. | custom codedeveloper effortlayer estimate | No source retrieved |
| Redirect controlCMS-07 | Unverified | Not verified: no first-party Squarespace source confirming "Redirect control" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Retrieval was attempted and did not produce readable first-party text. Squarespace's AI-crawler help article was requested directly and returned a sign-in-required page shell with no article body, so nothing from it could be quoted or confirmed. Search snippets were not accepted as a substitute. Verifying any Squarespace cell requires reading the vendor page in a readable session. | custom codedeveloper effortlayer estimate | No source retrieved |
| URL controlCMS-08 | Unverified | Not verified: no first-party Squarespace source confirming "URL control" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Retrieval was attempted and did not produce readable first-party text. Squarespace's AI-crawler help article was requested directly and returned a sign-in-required page shell with no article body, so nothing from it could be quoted or confirmed. Search snippets were not accepted as a substitute. Verifying any Squarespace cell requires reading the vendor page in a readable session. | custom codedeveloper effortlayer estimate | No source retrieved |
| SEO metadataCMS-09 | Unverified | Not verified: no first-party Squarespace source confirming "SEO metadata" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Retrieval was attempted and did not produce readable first-party text. Squarespace's AI-crawler help article was requested directly and returned a sign-in-required page shell with no article body, so nothing from it could be quoted or confirmed. Search snippets were not accepted as a substitute. Verifying any Squarespace cell requires reading the vendor page in a readable session. | configurationconfiguration effortlayer estimate | No source retrieved |
| Semantic HTMLCMS-10 | Unverified | Not verified: no first-party Squarespace source confirming "Semantic HTML" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Retrieval was attempted and did not produce readable first-party text. Squarespace's AI-crawler help article was requested directly and returned a sign-in-required page shell with no article body, so nothing from it could be quoted or confirmed. Search snippets were not accepted as a substitute. Verifying any Squarespace cell requires reading the vendor page in a readable session. | custom codedeveloper effortlayer estimate | No source retrieved |
| Custom JSON-LDCMS-11 | Unverified | Not verified: no first-party Squarespace source confirming "Custom JSON-LD" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Retrieval was attempted and did not produce readable first-party text. Squarespace's AI-crawler help article was requested directly and returned a sign-in-required page shell with no article body, so nothing from it could be quoted or confirmed. Search snippets were not accepted as a substitute. Verifying any Squarespace cell requires reading the vendor page in a readable session. | custom codedeveloper effortlayer estimate | No source retrieved |
| Page-specific schemaCMS-12 | Unverified | Not verified: no first-party Squarespace source confirming "Page-specific schema" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Retrieval was attempted and did not produce readable first-party text. Squarespace's AI-crawler help article was requested directly and returned a sign-in-required page shell with no article body, so nothing from it could be quoted or confirmed. Search snippets were not accepted as a substitute. Verifying any Squarespace cell requires reading the vendor page in a readable session. | custom codedeveloper effortlayer estimate | No source retrieved |
| Entity representationCMS-13 | Unverified | Not verified: no first-party Squarespace source confirming "Entity representation" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Retrieval was attempted and did not produce readable first-party text. Squarespace's AI-crawler help article was requested directly and returned a sign-in-required page shell with no article body, so nothing from it could be quoted or confirmed. Search snippets were not accepted as a substitute. Verifying any Squarespace cell requires reading the vendor page in a readable session. | custom codedeveloper effortlayer estimate | No source retrieved |
| Image semanticsCMS-14 | Unverified | Not verified: no first-party Squarespace source confirming "Image semantics" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Retrieval was attempted and did not produce readable first-party text. Squarespace's AI-crawler help article was requested directly and returned a sign-in-required page shell with no article body, so nothing from it could be quoted or confirmed. Search snippets were not accepted as a substitute. Verifying any Squarespace cell requires reading the vendor page in a readable session. | configurationconfiguration effortlayer estimate | No source retrieved |
| Structured contentCMS-15 | Unverified | Not verified: no first-party Squarespace source confirming "Structured content" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Retrieval was attempted and did not produce readable first-party text. Squarespace's AI-crawler help article was requested directly and returned a sign-in-required page shell with no article body, so nothing from it could be quoted or confirmed. Search snippets were not accepted as a substitute. Verifying any Squarespace cell requires reading the vendor page in a readable session. | configurationconfiguration effortlayer estimate | No source retrieved |
| Internal linkingCMS-16 | Unverified | Not verified: no first-party Squarespace source confirming "Internal linking" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Retrieval was attempted and did not produce readable first-party text. Squarespace's AI-crawler help article was requested directly and returned a sign-in-required page shell with no article body, so nothing from it could be quoted or confirmed. Search snippets were not accepted as a substitute. Verifying any Squarespace cell requires reading the vendor page in a readable session. | custom codedeveloper effortlayer estimate | No source retrieved |
| AI search crawler controlCMS-17 | Unverified | Not verified: no first-party Squarespace source confirming "AI search crawler control" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Retrieval was attempted and did not produce readable first-party text. Squarespace's AI-crawler help article was requested directly and returned a sign-in-required page shell with no article body, so nothing from it could be quoted or confirmed. Search snippets were not accepted as a substitute. Verifying any Squarespace cell requires reading the vendor page in a readable session. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
| AI content extractionCMS-18 | Unverified | Not verified: no first-party Squarespace source confirming "AI content extraction" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Retrieval was attempted and did not produce readable first-party text. Squarespace's AI-crawler help article was requested directly and returned a sign-in-required page shell with no article body, so nothing from it could be quoted or confirmed. Search snippets were not accepted as a substitute. Verifying any Squarespace cell requires reading the vendor page in a readable session. | custom codedeveloper effortlayer estimate | No source retrieved |
| Bot infrastructure accessCMS-19 | Unverified | Not verified: no first-party Squarespace source confirming "Bot infrastructure access" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Retrieval was attempted and did not produce readable first-party text. Squarespace's AI-crawler help article was requested directly and returned a sign-in-required page shell with no article body, so nothing from it could be quoted or confirmed. Search snippets were not accepted as a substitute. Verifying any Squarespace cell requires reading the vendor page in a readable session. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
| Change verificationCMS-20 | Unverified | Not verified: no first-party Squarespace source confirming "Change verification" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Retrieval was attempted and did not produce readable first-party text. Squarespace's AI-crawler help article was requested directly and returned a sign-in-required page shell with no article body, so nothing from it could be quoted or confirmed. Search snippets were not accepted as a substitute. Verifying any Squarespace cell requires reading the vendor page in a readable session. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
Adobe Experience ManagerAn enterprise content platform with deep authored, structured content, typically delivered on a managed infrastructure stack.3 of 20 answered
| Check | Status | Observation | Provision | Source |
|---|---|---|---|---|
| HTTP crawlabilityCMS-01 | Unverified | Not verified: no first-party Adobe Experience Manager source confirming "HTTP crawlability" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Adobe's AEM SEO and URL management best-practices page was retrieved and confirmed. It describes implementation responsibilities an author or implementer carries at page level, not controls AEM applies automatically, so these cells are recorded as partial rather than as native features. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
| Search crawler accessCMS-02 | Unverified | Not verified: no first-party Adobe Experience Manager source confirming "Search crawler access" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Adobe's AEM SEO and URL management best-practices page was retrieved and confirmed. It describes implementation responsibilities an author or implementer carries at page level, not controls AEM applies automatically, so these cells are recorded as partial rather than as native features. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
| IndexabilityCMS-03 | Partly documented | Adobe's AEM best-practices page describes indexability as something managed through robots directives and page-level configuration, treating it as an implementer responsibility rather than an automatic platform behaviour. | configurationconfiguration effort | SEO and URL Management Best Practices — Adobe Experience Manager |
| Content renderingCMS-04 | Unverified | Not verified: no first-party Adobe Experience Manager source confirming "Content rendering" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Adobe's AEM SEO and URL management best-practices page was retrieved and confirmed. It describes implementation responsibilities an author or implementer carries at page level, not controls AEM applies automatically, so these cells are recorded as partial rather than as native features. | custom codedeveloper effortlayer estimate | No source retrieved |
| Canonical controlCMS-05 | Partly documented | The same AEM page treats canonical tags as a page-level implementation decision the site author or implementer must make, rather than a value AEM derives automatically. | configurationconfiguration effort | SEO and URL Management Best Practices — Adobe Experience Manager |
| XML sitemapCMS-06 | Unverified | Not verified: no first-party Adobe Experience Manager source confirming "XML sitemap" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Adobe's AEM SEO and URL management best-practices page was retrieved and confirmed. It describes implementation responsibilities an author or implementer carries at page level, not controls AEM applies automatically, so these cells are recorded as partial rather than as native features. | custom codedeveloper effortlayer estimate | No source retrieved |
| Redirect controlCMS-07 | Unverified | Not verified: no first-party Adobe Experience Manager source confirming "Redirect control" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Adobe's AEM SEO and URL management best-practices page was retrieved and confirmed. It describes implementation responsibilities an author or implementer carries at page level, not controls AEM applies automatically, so these cells are recorded as partial rather than as native features. | custom codedeveloper effortlayer estimate | No source retrieved |
| URL controlCMS-08 | Unverified | Not verified: no first-party Adobe Experience Manager source confirming "URL control" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Adobe's AEM SEO and URL management best-practices page was retrieved and confirmed. It describes implementation responsibilities an author or implementer carries at page level, not controls AEM applies automatically, so these cells are recorded as partial rather than as native features. | custom codedeveloper effortlayer estimate | No source retrieved |
| SEO metadataCMS-09 | Partly documented | Adobe's page places title and description metadata under the same page-level implementation responsibility, configurable on the content component or template. | configurationconfiguration effort | SEO and URL Management Best Practices — Adobe Experience Manager |
| Semantic HTMLCMS-10 | Unverified | Not verified: no first-party Adobe Experience Manager source confirming "Semantic HTML" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Adobe's AEM SEO and URL management best-practices page was retrieved and confirmed. It describes implementation responsibilities an author or implementer carries at page level, not controls AEM applies automatically, so these cells are recorded as partial rather than as native features. | custom codedeveloper effortlayer estimate | No source retrieved |
| Custom JSON-LDCMS-11 | Unverified | Not verified: no first-party Adobe Experience Manager source confirming "Custom JSON-LD" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Adobe's AEM SEO and URL management best-practices page was retrieved and confirmed. It describes implementation responsibilities an author or implementer carries at page level, not controls AEM applies automatically, so these cells are recorded as partial rather than as native features. | custom codedeveloper effortlayer estimate | No source retrieved |
| Page-specific schemaCMS-12 | Unverified | Not verified: no first-party Adobe Experience Manager source confirming "Page-specific schema" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Adobe's AEM SEO and URL management best-practices page was retrieved and confirmed. It describes implementation responsibilities an author or implementer carries at page level, not controls AEM applies automatically, so these cells are recorded as partial rather than as native features. | custom codedeveloper effortlayer estimate | No source retrieved |
| Entity representationCMS-13 | Unverified | Not verified: no first-party Adobe Experience Manager source confirming "Entity representation" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Adobe's AEM SEO and URL management best-practices page was retrieved and confirmed. It describes implementation responsibilities an author or implementer carries at page level, not controls AEM applies automatically, so these cells are recorded as partial rather than as native features. | custom codedeveloper effortlayer estimate | No source retrieved |
| Image semanticsCMS-14 | Unverified | Not verified: no first-party Adobe Experience Manager source confirming "Image semantics" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Adobe's AEM SEO and URL management best-practices page was retrieved and confirmed. It describes implementation responsibilities an author or implementer carries at page level, not controls AEM applies automatically, so these cells are recorded as partial rather than as native features. | configurationconfiguration effortlayer estimate | No source retrieved |
| Structured contentCMS-15 | Unverified | Not verified: no first-party Adobe Experience Manager source confirming "Structured content" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Adobe's AEM SEO and URL management best-practices page was retrieved and confirmed. It describes implementation responsibilities an author or implementer carries at page level, not controls AEM applies automatically, so these cells are recorded as partial rather than as native features. | configurationconfiguration effortlayer estimate | No source retrieved |
| Internal linkingCMS-16 | Unverified | Not verified: no first-party Adobe Experience Manager source confirming "Internal linking" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Adobe's AEM SEO and URL management best-practices page was retrieved and confirmed. It describes implementation responsibilities an author or implementer carries at page level, not controls AEM applies automatically, so these cells are recorded as partial rather than as native features. | custom codedeveloper effortlayer estimate | No source retrieved |
| AI search crawler controlCMS-17 | Unverified | Not verified: no first-party Adobe Experience Manager source confirming "AI search crawler control" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Adobe's AEM SEO and URL management best-practices page was retrieved and confirmed. It describes implementation responsibilities an author or implementer carries at page level, not controls AEM applies automatically, so these cells are recorded as partial rather than as native features. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
| AI content extractionCMS-18 | Unverified | Not verified: no first-party Adobe Experience Manager source confirming "AI content extraction" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Adobe's AEM SEO and URL management best-practices page was retrieved and confirmed. It describes implementation responsibilities an author or implementer carries at page level, not controls AEM applies automatically, so these cells are recorded as partial rather than as native features. | custom codedeveloper effortlayer estimate | No source retrieved |
| Bot infrastructure accessCMS-19 | Unverified | Not verified: no first-party Adobe Experience Manager source confirming "Bot infrastructure access" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Adobe's AEM SEO and URL management best-practices page was retrieved and confirmed. It describes implementation responsibilities an author or implementer carries at page level, not controls AEM applies automatically, so these cells are recorded as partial rather than as native features. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
| Change verificationCMS-20 | Unverified | Not verified: no first-party Adobe Experience Manager source confirming "Change verification" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Adobe's AEM SEO and URL management best-practices page was retrieved and confirmed. It describes implementation responsibilities an author or implementer carries at page level, not controls AEM applies automatically, so these cells are recorded as partial rather than as native features. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
SitecoreAn enterprise experience platform, usually paired with infrastructure and bot-management products that the CMS itself does not provide.1 of 20 answered
| Check | Status | Observation | Provision | Source |
|---|---|---|---|---|
| HTTP crawlabilityCMS-01 | Unverified | Not verified: no first-party Sitecore source confirming "HTTP crawlability" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Sitecore's robots.txt configuration page was retrieved and confirmed. It documents one infrastructure control only; sitemap generation, canonical, indexability and markup controls need their own Sitecore pages. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
| Search crawler accessCMS-02 | Partly documented | Sitecore documents editing robots.txt rules per site in Site Settings, and states that an empty rule set produces a robots.txt of User-agent: * with Disallow: /, meaning an unconfigured site asks crawlers to stay away entirely. | configurationconfiguration effort | Configure the robots.txt file — Sitecore Documentation |
| IndexabilityCMS-03 | Unverified | Not verified: no first-party Sitecore source confirming "Indexability" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Sitecore's robots.txt configuration page was retrieved and confirmed. It documents one infrastructure control only; sitemap generation, canonical, indexability and markup controls need their own Sitecore pages. | custom codedeveloper effortlayer estimate | No source retrieved |
| Content renderingCMS-04 | Unverified | Not verified: no first-party Sitecore source confirming "Content rendering" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Sitecore's robots.txt configuration page was retrieved and confirmed. It documents one infrastructure control only; sitemap generation, canonical, indexability and markup controls need their own Sitecore pages. | custom codedeveloper effortlayer estimate | No source retrieved |
| Canonical controlCMS-05 | Unverified | Not verified: no first-party Sitecore source confirming "Canonical control" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Sitecore's robots.txt configuration page was retrieved and confirmed. It documents one infrastructure control only; sitemap generation, canonical, indexability and markup controls need their own Sitecore pages. | custom codedeveloper effortlayer estimate | No source retrieved |
| XML sitemapCMS-06 | Unverified | Not verified: no first-party Sitecore source confirming "XML sitemap" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Sitecore's robots.txt configuration page was retrieved and confirmed. It documents one infrastructure control only; sitemap generation, canonical, indexability and markup controls need their own Sitecore pages. | custom codedeveloper effortlayer estimate | No source retrieved |
| Redirect controlCMS-07 | Unverified | Not verified: no first-party Sitecore source confirming "Redirect control" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Sitecore's robots.txt configuration page was retrieved and confirmed. It documents one infrastructure control only; sitemap generation, canonical, indexability and markup controls need their own Sitecore pages. | custom codedeveloper effortlayer estimate | No source retrieved |
| URL controlCMS-08 | Unverified | Not verified: no first-party Sitecore source confirming "URL control" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Sitecore's robots.txt configuration page was retrieved and confirmed. It documents one infrastructure control only; sitemap generation, canonical, indexability and markup controls need their own Sitecore pages. | custom codedeveloper effortlayer estimate | No source retrieved |
| SEO metadataCMS-09 | Unverified | Not verified: no first-party Sitecore source confirming "SEO metadata" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Sitecore's robots.txt configuration page was retrieved and confirmed. It documents one infrastructure control only; sitemap generation, canonical, indexability and markup controls need their own Sitecore pages. | configurationconfiguration effortlayer estimate | No source retrieved |
| Semantic HTMLCMS-10 | Unverified | Not verified: no first-party Sitecore source confirming "Semantic HTML" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Sitecore's robots.txt configuration page was retrieved and confirmed. It documents one infrastructure control only; sitemap generation, canonical, indexability and markup controls need their own Sitecore pages. | custom codedeveloper effortlayer estimate | No source retrieved |
| Custom JSON-LDCMS-11 | Unverified | Not verified: no first-party Sitecore source confirming "Custom JSON-LD" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Sitecore's robots.txt configuration page was retrieved and confirmed. It documents one infrastructure control only; sitemap generation, canonical, indexability and markup controls need their own Sitecore pages. | custom codedeveloper effortlayer estimate | No source retrieved |
| Page-specific schemaCMS-12 | Unverified | Not verified: no first-party Sitecore source confirming "Page-specific schema" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Sitecore's robots.txt configuration page was retrieved and confirmed. It documents one infrastructure control only; sitemap generation, canonical, indexability and markup controls need their own Sitecore pages. | custom codedeveloper effortlayer estimate | No source retrieved |
| Entity representationCMS-13 | Unverified | Not verified: no first-party Sitecore source confirming "Entity representation" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Sitecore's robots.txt configuration page was retrieved and confirmed. It documents one infrastructure control only; sitemap generation, canonical, indexability and markup controls need their own Sitecore pages. | custom codedeveloper effortlayer estimate | No source retrieved |
| Image semanticsCMS-14 | Unverified | Not verified: no first-party Sitecore source confirming "Image semantics" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Sitecore's robots.txt configuration page was retrieved and confirmed. It documents one infrastructure control only; sitemap generation, canonical, indexability and markup controls need their own Sitecore pages. | configurationconfiguration effortlayer estimate | No source retrieved |
| Structured contentCMS-15 | Unverified | Not verified: no first-party Sitecore source confirming "Structured content" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Sitecore's robots.txt configuration page was retrieved and confirmed. It documents one infrastructure control only; sitemap generation, canonical, indexability and markup controls need their own Sitecore pages. | configurationconfiguration effortlayer estimate | No source retrieved |
| Internal linkingCMS-16 | Unverified | Not verified: no first-party Sitecore source confirming "Internal linking" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Sitecore's robots.txt configuration page was retrieved and confirmed. It documents one infrastructure control only; sitemap generation, canonical, indexability and markup controls need their own Sitecore pages. | custom codedeveloper effortlayer estimate | No source retrieved |
| AI search crawler controlCMS-17 | Unverified | Not verified: no first-party Sitecore source confirming "AI search crawler control" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Sitecore's robots.txt configuration page was retrieved and confirmed. It documents one infrastructure control only; sitemap generation, canonical, indexability and markup controls need their own Sitecore pages. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
| AI content extractionCMS-18 | Unverified | Not verified: no first-party Sitecore source confirming "AI content extraction" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Sitecore's robots.txt configuration page was retrieved and confirmed. It documents one infrastructure control only; sitemap generation, canonical, indexability and markup controls need their own Sitecore pages. | custom codedeveloper effortlayer estimate | No source retrieved |
| Bot infrastructure accessCMS-19 | Unverified | Not verified: no first-party Sitecore source confirming "Bot infrastructure access" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Sitecore's robots.txt configuration page was retrieved and confirmed. It documents one infrastructure control only; sitemap generation, canonical, indexability and markup controls need their own Sitecore pages. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
| Change verificationCMS-20 | Unverified | Not verified: no first-party Sitecore source confirming "Change verification" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Sitecore's robots.txt configuration page was retrieved and confirmed. It documents one infrastructure control only; sitemap generation, canonical, indexability and markup controls need their own Sitecore pages. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
Next.jsA framework rather than a CMS. It ships first-class file conventions for metadata, robots and sitemaps, but every control is yours to implement.2 of 20 answered
| Check | Status | Observation | Provision | Source |
|---|---|---|---|---|
| HTTP crawlabilityCMS-01 | Unverified | Not verified: no first-party Next.js source confirming "HTTP crawlability" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Next.js ships conventions rather than executed controls, so every cell depends on what the implementing team actually built. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
| Search crawler accessCMS-02 | Documented | This repository implements a per-user-agent robots control in app/robots.ts using the framework's robots file convention, allowing named AI agents while disallowing /api/, and pointing crawlers at the sitemap. | nativebuilt in effort | robots file convention — Next.js documentation |
| IndexabilityCMS-03 | Unverified | Not verified: no first-party Next.js source confirming "Indexability" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Next.js ships conventions rather than executed controls, so every cell depends on what the implementing team actually built. | custom codedeveloper effortlayer estimate | No source retrieved |
| Content renderingCMS-04 | Unverified | Not verified: no first-party Next.js source confirming "Content rendering" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Next.js ships conventions rather than executed controls, so every cell depends on what the implementing team actually built. | custom codedeveloper effortlayer estimate | No source retrieved |
| Canonical controlCMS-05 | Unverified | Not verified: no first-party Next.js source confirming "Canonical control" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Next.js ships conventions rather than executed controls, so every cell depends on what the implementing team actually built. | custom codedeveloper effortlayer estimate | No source retrieved |
| XML sitemapCMS-06 | Documented | This repository implements app/sitemap.ts returning a typed sitemap of static routes plus every published blog and case study, with source-backed last-modified dates only on editorial content. | nativebuilt in effort | sitemap file convention — Next.js documentation |
| Redirect controlCMS-07 | Unverified | Not verified: no first-party Next.js source confirming "Redirect control" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Next.js ships conventions rather than executed controls, so every cell depends on what the implementing team actually built. | custom codedeveloper effortlayer estimate | No source retrieved |
| URL controlCMS-08 | Unverified | Not verified: no first-party Next.js source confirming "URL control" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Next.js ships conventions rather than executed controls, so every cell depends on what the implementing team actually built. | custom codedeveloper effortlayer estimate | No source retrieved |
| SEO metadataCMS-09 | Unverified | Not verified: no first-party Next.js source confirming "SEO metadata" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Next.js ships conventions rather than executed controls, so every cell depends on what the implementing team actually built. | configurationconfiguration effortlayer estimate | No source retrieved |
| Semantic HTMLCMS-10 | Unverified | Not verified: no first-party Next.js source confirming "Semantic HTML" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Next.js ships conventions rather than executed controls, so every cell depends on what the implementing team actually built. | custom codedeveloper effortlayer estimate | No source retrieved |
| Custom JSON-LDCMS-11 | Unverified | Not verified: no first-party Next.js source confirming "Custom JSON-LD" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Next.js ships conventions rather than executed controls, so every cell depends on what the implementing team actually built. | custom codedeveloper effortlayer estimate | No source retrieved |
| Page-specific schemaCMS-12 | Unverified | Not verified: no first-party Next.js source confirming "Page-specific schema" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Next.js ships conventions rather than executed controls, so every cell depends on what the implementing team actually built. | custom codedeveloper effortlayer estimate | No source retrieved |
| Entity representationCMS-13 | Unverified | Not verified: no first-party Next.js source confirming "Entity representation" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Next.js ships conventions rather than executed controls, so every cell depends on what the implementing team actually built. | custom codedeveloper effortlayer estimate | No source retrieved |
| Image semanticsCMS-14 | Unverified | Not verified: no first-party Next.js source confirming "Image semantics" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Next.js ships conventions rather than executed controls, so every cell depends on what the implementing team actually built. | configurationconfiguration effortlayer estimate | No source retrieved |
| Structured contentCMS-15 | Unverified | Not verified: no first-party Next.js source confirming "Structured content" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Next.js ships conventions rather than executed controls, so every cell depends on what the implementing team actually built. | configurationconfiguration effortlayer estimate | No source retrieved |
| Internal linkingCMS-16 | Unverified | Not verified: no first-party Next.js source confirming "Internal linking" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Next.js ships conventions rather than executed controls, so every cell depends on what the implementing team actually built. | custom codedeveloper effortlayer estimate | No source retrieved |
| AI search crawler controlCMS-17 | Unverified | Not verified: no first-party Next.js source confirming "AI search crawler control" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Next.js ships conventions rather than executed controls, so every cell depends on what the implementing team actually built. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
| AI content extractionCMS-18 | Unverified | Not verified: no first-party Next.js source confirming "AI content extraction" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Next.js ships conventions rather than executed controls, so every cell depends on what the implementing team actually built. | custom codedeveloper effortlayer estimate | No source retrieved |
| Bot infrastructure accessCMS-19 | Unverified | Not verified: no first-party Next.js source confirming "Bot infrastructure access" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Next.js ships conventions rather than executed controls, so every cell depends on what the implementing team actually built. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
| Change verificationCMS-20 | Unverified | Not verified: no first-party Next.js source confirming "Change verification" was retrieved and confirmed during this research pass. Neither capability nor absence of capability is being claimed.Limitation: Next.js ships conventions rather than executed controls, so every cell depends on what the implementing team actually built. | infrastructureinfrastructure effortlayer estimate | No source retrieved |
Where the work actually lands
Coverage is not the useful axis. Effort is. Across all 300 cells, the work falls into 7 built-in defaults that need nothing from you, 61 that are reachable from a settings screen, 1 that need a plugin or app, 165 that need engineering time, and 66 that sit below the CMS entirely.
Read those numbers as a shape, not a finding about any vendor: 270 of them describe cells no source has answered yet, so they are planning estimates derived from the layer, not documentation. Effort is reported separately from status precisely so a projected effort never reads as a measured capability.
That shape is the part of this study you can act on without relying on our documentation coverage. Buying a platform with more built-in capability does not help much if the layer where your actual blockers live is infrastructure, because no product choice reaches it. The practical move is to run the twenty checks against your own site, sort what you find by which layer owns it, and only then decide whether the platform is the constraint. The matrix above is a reference for what to ask a vendor; it is not a substitute for checking your own URLs, and it does not record a single failing check for any platform. If you want that done on a real site rather than reasoned about in the abstract, the AI visibility audit and the AI search visibility checker both read your own pages and tell you which layer each problem is in.
What this benchmark does not establish
The largest honest caveat is the one we can state most simply: this is a documentation study. It is not a live test rig. No customer site was crawled, no deployment was inspected, and no rendering was observed. If you need those answers, this is the wrong artifact and the audit tools linked above are the right one.
- It does not predict rankings, citations, or AI-assistant mentions for any platform.
- It does not confirm that a documented capability is switched on in your specific configuration.
- It does not compare platforms against each other with a weighted figure, and it publishes no ranking verdict of its own.
- It does not treat a documented crawler allowance as an AI-visibility advantage. A crawler being permitted is not the same thing as a system retrieving or citing the page, which is the distinction we unpack in llms.txt for SEO and AI search.
Choosing by use case
With no winner to crown, the matrix is more useful as a filter. Match the row that looks like your situation to the layer that actually owns your problem.
- You cannot change the CMS. Stop evaluating platforms. Most checks are answerable at the delivery or infrastructure layer regardless of what publishes the content.
- You are choosing a CMS now. Weight the CMS-layer checks and the provision column heavily, because those are the only ones your choice will actually move.
- Your content is fully headless. Rendering and per-page schema move into the frontend. The CMS contributes structured content and nothing else, which is a narrower but more honest scope than most comparisons imply.
- AI assistants matter to you. Crawler policy, extractable content structure and entity clarity are the checks to read closely, in that order.
Methodology
Every cell in the matrix was filled from one of three source classes. Vendor documentation is used for capability claims, search-engine documentation is used for requirements, and this repository's own published robots and sitemap implementations are used for the custom stack row. A cell is only recorded as answered when one of those sources settles the question directly.
Provision, dependency and effort are reported as separate columns because they are different things. Provision is how a capability is delivered — built in, configured, extended, hand-built, or owned by infrastructure. Dependency is how much of it is unavoidable. Effort is what it costs to get from default to working. For answered cells these come from the source. For UNVERIFIED cells they are layer-derived planning estimates and are labelled as such, so they are never mistaken for measured findings.
Sources were retrieved on 26 September 2026. Vendor documentation changes without notice, so re-verify any cell before you rely on it in a decision.
Sources
- Publishers and developers FAQ — OpenAI
OpenAI documents OAI-SearchBot as the search crawler and GPTBot as a training crawler, so blocking one is not equivalent to blocking the other.
- Introduction to robots.txt — Google Search Central
Google states that robots.txt governs crawling rather than indexing, that a disallowed URL can still appear in results, and that a CMS may not let you edit robots.txt directly.
- Build and submit a sitemap — Google Search Central
Google's requirements for sitemaps, including listing all indexable canonical URLs.
- Editing robots.txt — Shopify Help Center
Shopify documents the default robots.txt it generates and where merchants can edit its directives.
- Find your sitemap — Shopify Help Center
Shopify documents its generated sitemap, its URL inclusion rules, and its structured-data handling.
- Optimizing your online store for AI — Shopify Help Center
Shopify's own guidance on content structure and metadata for AI discovery, distinct from crawler access.
- Set robots.txt rules — Webflow Help Center
Webflow documents robots.txt directives including per-user-agent allow and disallow rules, and that not all bots obey them. It is cited only for crawler-access cells, not for canonical, sitemap, redirect or schema controls.
- Technical SEO guide — Contentful
Contentful states that robots.txt is not managed within Contentful, placing crawler control in the delivery layer, and recommends modelling indexability and metadata fields in the content model.
- robots.txt — WordPress Developer Resources
WordPress core documents how it generates and filters robots.txt, and states that major optimizers can disable it.
- sitemap file convention — Next.js
Next.js documents generating sitemap.xml programmatically from route metadata.
- robots.txt file convention — Next.js
Next.js documents generating robots.txt programmatically, including per-user-agent rules.
- Introduction — Ghost Documentation
Ghost states that a canonical URL is added automatically to each post and page, that a Google sitemap is generated automatically, and that routing is configurable. It documents automatic emission rather than an operator-set canonical, and is not cited for custom schema.
- Modifying robots.txt — Ghost Help Center
Ghost documents a default robots.txt and a theme-level robots.txt.liquid file. It describes replacing the file rather than per-user-agent or AI crawler targeting, and is cited only for the crawler access cell.
- SEO Settings: Advanced SEO — Wix Help Center
Wix documents a per-page canonical URL field, structured data presets scoped to page type, and a custom JSON-LD field limited to five markups and 7,000 characters per page. The page documents default SEO and social meta tags rather than title, description and robots directive controls.
- Understanding your site's sitemap file — Wix Help Center
Wix states a sitemap is generated automatically, kept updated with content changes, and submitted to search engines on the site's behalf.
- Storyblok Headless CMS and SEO — Storyblok FAQ
Storyblok states it delivers content to any frontend as JSON and that the customer's own frontend is responsible for a fast, crawlable site, which is what places rendering with the customer rather than the platform.
- Configure the robots.txt file — Sitecore Documentation
Sitecore documents per-site robots.txt rules in Site Settings, that an empty rule set serves Disallow: /, and that changes require a publish or republish.
- SEO and URL Management Best Practices — Adobe Experience Manager
Adobe treats indexability, canonical tags and metadata as page-level implementation responsibilities in AEM rather than automatic platform behaviour.
- Prevent content from appearing in search results — HubSpot Knowledge Base
HubSpot documents a robots.txt control in SEO & Crawlers settings with a per-domain default and an operator override, and separately a noindex meta tag added to a page's Head HTML that takes effect only after publishing.
- Set canonical URLs for duplicate content — HubSpot Knowledge Base
HubSpot documents a default canonical URL per page and blog post, per-page overrides, a site-wide default that can be disabled, and that blog listing pages have no default canonical.
- View and edit a HubSpot-hosted domain sitemap — HubSpot Knowledge Base
HubSpot documents an automatically maintained sitemap index at /sitemap.xml covering live hosted pages and blog posts, with landing pages added manually and HubDB dynamic child pages included only conditionally.
- Create and manage URL redirects — HubSpot Knowledge Base
HubSpot documents standard and flexible URL redirects with permanent 301 as the default style, bulk CSV upload and priority ordering, gated by subscription and limited to domains hosted in HubSpot.
- robots.txt scaffold file — Drupal core
Drupal core ships a robots.txt scaffold with a single User-agent: * group that allows core and profile assets and disallows admin, search, user and oembed paths. It is a static file on disk, not an administrative control, and declares no per-user-agent or AI crawler targeting.
Continue exploring
Related insights
Also relevantExplore Growthract’s SEO + AEO approach
Case study
An illustrative strategy showing how a B2B software company could make core documentation publicly accessible, improve machine readability and reach Google AI Overview inclusion across 17 of 20 tracked query groups.
See the case study →
Insight
Original research across 100 B2B SaaS websites on llms.txt adoption, AI crawler access, JSON-LD, schema markup, canonicals, and technical readiness.
Read the insight →
Insight
The 15 technical checks worth adding to a standard SEO audit now that ChatGPT, Perplexity and Google's AI Overviews are reading — and sometimes citing — your website.
Read the insight →