Platform SEO
SEO considerations by platform and CMS — what each system does for you automatically, what it locks down, and the quirks that matter. Hub for CMS SEO, website builders, headless CMS, JavaScript frameworks, and ecommerce platforms.
Every platform makes SEO decisions for you — some good, some limiting. Traditional CMS platforms like WordPress give you the most control; hosted builders like Wix and Squarespace handle the basics automatically but restrict what you can customize; headless and JS frameworks put you in full control but require you to build what plugins used to handle. This hub points to the platform-specific deep dives: CMS, website builders, headless CMS, JavaScript frameworks, and ecommerce platforms.
Evidence for this claim The article's described platform-seo capabilities must be evaluated against the platform's current documentation rather than assumed to be search-engine behavior. Scope: Platform-specific capability documentation. Confidence: high · Verified: Google: SEO Starter Guide Evidence for this claim Regardless of platform, Google needs crawlable URLs, accessible rendered content, descriptive metadata, and valid search directives. Scope: Google requirements independent of platform. Confidence: high · Verified: Google Search Central: SEO Starter GuideTL;DR — The platform you build your site on shapes your SEO options before you write a single word. Some platforms do a lot for you automatically; others give you full control but leave more for you to configure. The difference matters most for technical SEOTechnical SEO is the practice of making a site easy for search engines to crawl, render, index, and (now) be eligible for AI answers. It's the foundation that lets your content and links rank — not a ranking trick of its own. — titles, canonicals, sitemapsA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing., structured dataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding., robots.txtA plain-text file at the root of a host that tells crawlers which URLs they may and may not request. It controls crawling, not indexing — a blocked URL can still be indexed if it's linked from elsewhere., and renderingTurning HTML, CSS, and JavaScript into the final visual page and DOM..
Why platform choice affects SEO
Most SEO advice treats a website as a blank canvas. In reality, your CMSA content management system (CMS) is software that lets users create, manage, and publish digital content — like blog posts and pages — without writing raw code. WordPress, Drupal, and Joomla are the most common open-source CMS platforms. or
website builder has already made dozens of SEO decisions for you — the URL
structure, how sitemapsA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing. are generated, whether you can edit robots.txt, how
metadata is handled, and what structured data gets injected automatically.
The good news: most major platforms cover the basics well. The differences show up when you need to do something non-standard, fix a specific technical issue, or scale to tens of thousands of pages.
The five categories
Traditional CMS platforms (WordPress, Drupal, Joomla, HubSpot CMS, Umbraco, Sitecore) install on your own server (or a managed host) and give you deep control over every technical SEOTechnical SEO is the practice of making a site easy for search engines to crawl, render, index, and (now) be eligible for AI answers. It's the foundation that lets your content and links rank — not a ranking trick of its own. setting. WordPress in particular has a rich plugin ecosystem — Yoast, Rank Math, and others handle most technical SEO automatically once configured.
Visual and SaaS website buildersHosted visual tools — Wix, Squarespace, Webflow, Framer, and others — that let users build and publish websites without writing code. They manage hosting, SSL, and rendering but vary significantly in the SEO controls they expose. (Wix, Squarespace, Webflow, FramerFramer SEO is the set of built-in and configurable search optimization features in Framer, a design-first website builder. Framer publishes pre-rendered static HTML, so pages are crawlable without JavaScript execution, and it exposes per-page metadata, automatic sitemaps and robots.txt, redirects, canonical tags, and custom <head> code injection., and
others) host your site and manage the infrastructure. They handle HTTPSHTTPS is the encrypted version of HTTP — it uses TLS to authenticate the server and protect data in transit between a browser and a website. Google announced it as a lightweight ranking signal in 2014 and today conditionally prefers HTTPS pages as canonical; Chrome marks plain HTTP pages 'Not Secure.', CDN,
sitemaps, and basic metadata automatically, but most restrict server-side
configuration and URL structureURL structure is how the parts of a web address — scheme, domain, path, query string, and fragment — are organized and formatted. It mostly affects crawling, usability, and how engines understand a page, not rankings directly.. robots.txt access varies by builder — Wix and
Squarespace lock it down, while Webflow exposes it directly under Settings → SEO.
Great for most sites; limiting for edge cases.
Headless CMSA headless CMS decouples content storage and editing (the backend) from how that content is rendered and delivered (the frontend), serving content over an API instead of a built-in templated 'head'. Its SEO outcomes come almost entirely from how the separate frontend renders pages. (Contentful, Strapi, Sanity, Storyblok, Ghost) separates where you write content from how it gets rendered. SEO is entirely determined by the frontend renderer you choose — SSG and SSR are safe; CSR requires care. Everything WordPress plugins handle automatically (metadata, sitemaps, canonicals) you now build explicitly.
JavaScript frameworksJavaScript frameworks — React, Vue, Angular, Next.js, Nuxt, Svelte, Astro — are libraries or meta-frameworks for building web UIs. Their SEO impact depends on rendering mode: SSR and SSG deliver pre-rendered HTML; CSR-only apps require Googlebot to execute JavaScript before it can index content. (React, Next.js, Vue, Nuxt, Angular, Astro, Svelte) are frontend renderingTurning HTML, CSS, and JavaScript into the final visual page and DOM. environments, not content management systems. Each has its own SEO implications based on how it renders pages — server-side, statically at build time, or in the browser. Next.js and Nuxt (meta-frameworks) have the most built-in SEO support.
Ecommerce platforms (Shopify, WooCommerce, Magento, BigCommerce) layer ecommerce-specific SEO concerns on top: product structured data, faceted navigationFaceted navigation (faceted search, product filtering) lets visitors refine a list of products or content by attribute — price, color, size, brand, rating. The SEO problem: each filter combination can spawn a distinct crawlable URL, turning a small catalog into millions of near-duplicate pages that waste crawl budget and dilute ranking signals., paginationPagination splits a large set of content — product listings, blog archives, search results — across multiple sequentially numbered URLs. For SEO, each paginated page should be crawlable, indexable, and self-canonical; Google no longer uses rel=prev/next, but Bing still does., duplicate URLs from variants and collections, and platform-locked URL structures.
How to use this section
Start with the hub for your platform category, then drill into the specific platform article. Each covers what the platform handles automatically, what it restricts, and the platform-specific quirks that trip people up.
Evidence for this claim The article's described platform-seo capabilities must be evaluated against the platform's current documentation rather than assumed to be search-engine behavior. Scope: Platform-specific capability documentation. Confidence: high · Verified: Google: SEO Starter Guide Evidence for this claim Regardless of platform, Google needs crawlable URLs, accessible rendered content, descriptive metadata, and valid search directives. Scope: Google requirements independent of platform. Confidence: high · Verified: Google Search Central: SEO Starter GuideTL;DR — Platform SEOPlatform SEO covers the SEO considerations specific to the technology a site is built on — CMS, website builder, headless stack, or JavaScript framework. Each platform has different defaults, constraints, and required configurations that affect crawling, indexing, and ranking. is really about constraints and defaults: what does your platform decide before you touch it, and which of those decisions can you override? The gaps that matter are renderingTurning HTML, CSS, and JavaScript into the final visual page and DOM. architecture (CSR vs SSR vs SSG),
robots.txteditability, structured dataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding. injection, URL structureURL structure is how the parts of a web address — scheme, domain, path, query string, and fragment — are organized and formatted. It mostly affects crawling, usability, and how engines understand a page, not rankings directly. flexibility, and sitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing. coverage. The rest is mostly configurable with the right plugin or build setup.
Evaluating platforms for SEO
When assessing a platform for SEO, the questions that matter at scale:
RenderingTurning HTML, CSS, and JavaScript into the final visual page and DOM. architecture — Does the platform serve pre-rendered HTML or does the browser build the page with JavaScript? Static HTML is the safe default. CSR introduces rendering delays and can cause GooglebotGooglebot is Google's web crawler — the software that fetches pages so Google can index and rank them. It comes in two variants, Googlebot Smartphone (primary, under mobile-first indexing) and Googlebot Desktop, and runs an evergreen Chromium renderer. to miss content if it fails to execute scripts. SSR and ISR (incremental static regeneration) sit in between — SSR is reliably crawlable; ISR can serve stale versions to crawlersA crawler — also called a spider or bot — is an automated program that fetches web pages, extracts their links, and queues new URLs to visit. Search engines use crawlers to discover and download content for their index. if the revalidation window is too long.
Metadata control — Can you set unique <title>, <meta description>, Open
Graph, and canonical tagsA rel=\"canonical\" annotation — in the HTML <head> or an HTTP Link header — that tells search engines which URL is the preferred version of duplicate or near-duplicate content. per page programmatically? Most modern platforms can.
The constraint usually shows up with large catalogs: can you template metadata at
scale without custom development?
Structured data — Does the platform inject schema automatically, or is it manual? Shopify’s product schemaProduct schema (schema.org/Product) is structured data that tells search engines a page's product name, price, availability, and reviews so it can appear in Shopping-style rich results. It's separate from a Google Merchant Center feed, though Google reconciles the two. is theme-dependent. WordPress needs a plugin. Headless setups require explicit implementation.
robots.txt and crawl control — Can you edit robots.txt directly? Most
platforms let you: Shopify supports customization on any plan through a
robots.txt.liquid theme template, and Webflow exposes it natively under
Settings → SEO. Wix and Squarespace are the more locked-down exception. For most
sites it doesn’t matter; for complex sites the differences in how much you can
override still matter.
URL structureURL structure is how the parts of a web address — scheme, domain, path, query string, and fragment — are organized and formatted. It mostly affects crawling, usability, and how engines understand a page, not rankings directly. — Can you customize the path, or is it platform-enforced?
Shopify’s /products/ prefix is fixed. Most traditional CMSA content management system (CMS) is software that lets users create, manage, and publish digital content — like blog posts and pages — without writing raw code. WordPress, Drupal, and Joomla are the most common open-source CMS platforms. platforms give you
full control.
SitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing. — Auto-generated, manually maintained, or via plugin? What gets included — can you exclude specific pages or post types?
Migration risk — Changing platforms mid-life means URL changes and the risk of broken redirectsA redirect sends browsers and crawlers from a requested URL to a different one. An HTTP redirect specifically is a 3xx status code paired with a Location header; meta refresh and JavaScript redirects achieve a similar navigation without being a 3xx response themselves. Permanent redirects (301/308) are Google's signal the target should be canonical; temporary ones (302/303/307) aren't.. Budget for a redirect map and a full post-migration crawl regardless of platform.
Platform SEO comparison by constraint
| Concern | Traditional CMS | SaaS Builder | Headless | JS Framework | Ecommerce |
|---|---|---|---|---|---|
| Rendering | PHP/server-side | Hosted static/SSR | Depends on frontend | Depends on framework | Hosted, usually SSR |
| Robots.txtA plain-text file at the root of a host that tells crawlers which URLs they may and may not request. It controls crawling, not indexing — a blocked URL can still be indexed if it's linked from elsewhere. | Full control | Varies (Webflow: full edit; Wix/Squarespace: locked down) | Full control | Full control | Customizable via template (Shopify: any plan via Liquid); varies elsewhere |
| URL structure | Flexible | Semi-flexible | Full control | Full control | Often fixed |
| Structured data | Plugin or manual | Basic, auto | Manual | Manual | Auto (varies by theme) |
| Sitemap | Plugin or auto | Auto | Manual or plugin | Manual | Auto |
| Metadata at scale | Plugin-driven | Limited | Full control | Full control | Theme-dependent |
Platform SEOPlatform SEO covers the SEO considerations specific to the technology a site is built on — CMS, website builder, headless stack, or JavaScript framework. Each platform has different defaults, constraints, and required configurations that affect crawling, indexing, and ranking. is about understanding what your CMSA content management system (CMS) is software that lets users create, manage, and publish digital content — like blog posts and pages — without writing raw code. WordPress, Drupal, and Joomla are the most common open-source CMS platforms. or website builder does for you
automatically versus what you have to configure manually. Every platform makes
technical SEOTechnical SEO is the practice of making a site easy for search engines to crawl, render, index, and (now) be eligible for AI answers. It's the foundation that lets your content and links rank — not a ranking trick of its own. decisions before you touch it — renderingTurning HTML, CSS, and JavaScript into the final visual page and DOM. method, URL structureURL structure is how the parts of a web address — scheme, domain, path, query string, and fragment — are organized and formatted. It mostly affects crawling, usability, and how engines understand a page, not rankings directly.,
sitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing. generation, metadata handling, and robots.txt control.
Traditional CMS (WordPress, Drupal, Joomla, HubSpot CMS, Umbraco, Sitecore): Full control over all SEO settings. WordPress has the richest plugin ecosystem for SEO automationSEO automation is the use of scripts, APIs, scheduled jobs, and no-code tools to run repetitive or data-heavy SEO tasks — monitoring, crawling, reporting, alerting, and content prep — without a human repeating the steps by hand. It sits on a spectrum from fully hands-off jobs to human-in-the-loop work a person reviews before anything ships.. Heavier to maintain but most flexible.
SaaS website buildersHosted visual tools — Wix, Squarespace, Webflow, Framer, and others — that let users build and publish websites without writing code. They manage hosting, SSL, and rendering but vary significantly in the SEO controls they expose. (Wix, Squarespace, Webflow, FramerFramer SEO is the set of built-in and configurable search optimization features in Framer, a design-first website builder. Framer publishes pre-rendered static HTML, so pages are crawlable without JavaScript execution, and it exposes per-page metadata, automatic sitemaps and robots.txt, redirects, canonical tags, and custom <head> code injection., Weebly, Duda):
Handle HTTPSHTTPS is the encrypted version of HTTP — it uses TLS to authenticate the server and protect data in transit between a browser and a website. Google announced it as a lightweight ranking signal in 2014 and today conditionally prefers HTTPS pages as canonical; Chrome marks plain HTTP pages 'Not Secure.', CDN, basic sitemapsA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing., and metadata automatically. Most restrict URL
structure and server configuration; robots.txt access varies (Webflow: full
edit; Wix/Squarespace: locked down). Suitable for most sites.
Headless CMSA headless CMS decouples content storage and editing (the backend) from how that content is rendered and delivered (the frontend), serving content over an API instead of a built-in templated 'head'. Its SEO outcomes come almost entirely from how the separate frontend renders pages. (Contentful, Strapi, Sanity, Storyblok, Ghost): SEO depends entirely on the frontend framework chosen. Use SSG or SSR; avoid CSR. All plugin-handled SEO (sitemaps, canonicals, metadata) must be built explicitly.
JavaScript frameworksJavaScript frameworks — React, Vue, Angular, Next.js, Nuxt, Svelte, Astro — are libraries or meta-frameworks for building web UIs. Their SEO impact depends on rendering mode: SSR and SSG deliver pre-rendered HTML; CSR-only apps require Googlebot to execute JavaScript before it can index content. (React, Next.js, Vue, Nuxt, Angular, Astro, Svelte): SEO varies by renderingTurning HTML, CSS, and JavaScript into the final visual page and DOM. mode. Next.js and Nuxt have strong built-in SSR/SSG support. Pure React/Vue in CSR mode requires prerendering or SSR for reliable indexation.
Ecommerce platforms (Shopify, WooCommerce, Magento, BigCommerce): Add ecommerce-specific concerns — product schemaProduct schema (schema.org/Product) is structured data that tells search engines a page's product name, price, availability, and reviews so it can appear in Shopping-style rich results. It's separate from a Google Merchant Center feed, though Google reconciles the two., faceted navigationFaceted navigation (faceted search, product filtering) lets visitors refine a list of products or content by attribute — price, color, size, brand, rating. The SEO problem: each filter combination can spawn a distinct crawlable URL, turning a small catalog into millions of near-duplicate pages that waste crawl budget and dilute ranking signals., duplicate URLs from collections and variants, paginationPagination splits a large set of content — product listings, blog archives, search results — across multiple sequentially numbered URLs. For SEO, each paginated page should be crawlable, indexable, and self-canonical; Google no longer uses rel=prev/next, but Bing still does., and platform-locked URL structuresURL structure is how the parts of a web address — scheme, domain, path, query string, and fragment — are organized and formatted. It mostly affects crawling, usability, and how engines understand a page, not rankings directly..
Platform selection framework for SEO
Step 1 — Identify your renderingTurning HTML, CSS, and JavaScript into the final visual page and DOM. constraint
- Content that must rank → needs SSR or SSG (static HTML delivered to crawlersA crawler — also called a spider or bot — is an automated program that fetches web pages, extracts their links, and queues new URLs to visit. Search engines use crawlers to discover and download content for their index.)
- CSR-only → pre-render critical pages or switch to SSR/SSG
- ISR → set short revalidation windows for content that changes frequently
Step 2 — Audit the platform’s defaults
- What does the platform auto-generate? (sitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing., canonicals, structured dataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding.)
- What is locked/unconfigurable? (robots.txtA plain-text file at the root of a host that tells crawlers which URLs they may and may not request. It controls crawling, not indexing — a blocked URL can still be indexed if it's linked from elsewhere., URL structureURL structure is how the parts of a web address — scheme, domain, path, query string, and fragment — are organized and formatted. It mostly affects crawling, usability, and how engines understand a page, not rankings directly.,
<head>access) - What requires a plugin or custom code?
Step 3 — Map your SEO requirements to platform capabilities
- Metadata templating at scale?
- Custom structured data types?
- Faceted navigationFaceted navigation (faceted search, product filtering) lets visitors refine a list of products or content by attribute — price, color, size, brand, rating. The SEO problem: each filter combination can spawn a distinct crawlable URL, turning a small catalog into millions of near-duplicate pages that waste crawl budget and dilute ranking signals. / parameter handling?
- HreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others. for international?
- Log file access for crawl analysis?
Step 4 — Evaluate migration cost
- Current URL structureURL structure is how the parts of a web address — scheme, domain, path, query string, and fragment — are organized and formatted. It mostly affects crawling, usability, and how engines understand a page, not rankings directly. → can you preserve it or need redirectsA redirect sends browsers and crawlers from a requested URL to a different one. An HTTP redirect specifically is a 3xx status code paired with a Location header; meta refresh and JavaScript redirects achieve a similar navigation without being a 3xx response themselves. Permanent redirects (301/308) are Google's signal the target should be canonical; temporary ones (302/303/307) aren't.?
- Redirect infrastructure on new platform?
- Post-migration monitoring plan?
Platform migration checklist
- Export all current URLs (crawl or sitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing.)
- Map old → new URLs; flag any that change
- Implement 301 redirectsA 301 redirect is the HTTP status code for a permanent move: it tells browsers and search engines a URL has moved for good, and it's the strongest signal for consolidating a page's ranking signals onto the new URL. Google says permanent redirects don't cause a loss in PageRank. for every changed URL
- Set canonical tagsA rel=\"canonical\" annotation — in the HTML <head> or an HTTP Link header — that tells search engines which URL is the preferred version of duplicate or near-duplicate content. before launch
- Submit new sitemap in Search ConsoleGoogle's free tool for monitoring crawling, indexing, and search performance.
- Crawl staging to verify renderingTurning HTML, CSS, and JavaScript into the final visual page and DOM., titles, meta, canonicals
- Monitor crawl errors and index coverage for 4–6 weeks post-launch
- Check Core Web VitalsGoogle's three real-user UX metrics — LCP (loading), INP (responsiveness), and CLS (visual stability) — used by Google's ranking systems, with no official weight attached, measured on field data. on new platform (CDN, image handling often differ)
Platform-specific deep dives
- WordPress SEOWordPress SEO is the process of configuring, optimizing, and maintaining a WordPress site so search engines can efficiently crawl, index, and rank it. WordPress gives you a solid foundation, but its defaults — ?p=123 permalinks, attachment pages, thin archives — need cleanup before a site is actually well-optimized.
- Shopify SEOShopify SEO is the practice of optimizing a Shopify store to rank in organic search. Shopify handles a lot for you automatically — canonical tags, an XML sitemap, SSL, a fast CDN — but it also imposes a fixed URL structure (/products/, /collections/, /pages/, /blogs/) and creates a duplicate URL for every product reachable through a collection, which the platform canonicalizes for you.
- Webflow SEOWebflow SEO is the set of technical controls, on-page settings, and CMS features built into the Webflow visual platform that affect how Webflow-built sites are crawled, indexed, and ranked. Its core advantage is that Webflow publishes static HTML at publish time, so crawlers get fully-rendered content without running JavaScript.
- Headless CMS SEOA headless CMS decouples content storage and editing (the backend) from how that content is rendered and delivered (the frontend), serving content over an API instead of a built-in templated 'head'. Its SEO outcomes come almost entirely from how the separate frontend renders pages.
- Next.js SEONext.js SEO is the set of practices and built-in features that make a Next.js site crawlable, indexable, and rankable — rendering mode (SSG/SSR/ISR/Server Components), the App Router Metadata API, sitemap.ts/robots.ts conventions, next/image, and next/link.
Platform SEO
Platform SEO covers the SEO considerations specific to the technology a site is built on — CMS, website builder, headless stack, or JavaScript framework. Each platform has different defaults, constraints, and required configurations that affect crawling, indexing, and ranking.
Related: CMS, JavaScript SEO, Headless CMS
Platform SEO
Platform SEO refers to the SEO decisions and constraints that arise from the specific technology stack a website is built on, rather than from content or link strategy. Every platform — WordPress, Wix, Shopify, Next.js, Contentful + Astro — has different defaults for URLs, sitemapsA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing., metadata, robots.txtA plain-text file at the root of a host that tells crawlers which URLs they may and may not request. It controls crawling, not indexing — a blocked URL can still be indexed if it's linked from elsewhere., renderingTurning HTML, CSS, and JavaScript into the final visual page and DOM., and structured dataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding..
Key questions for any platform:
- Does it generate clean, configurable URLs?
- Can you edit robots.txtA plain-text file at the root of a host that tells crawlers which URLs they may and may not request. It controls crawling, not indexing — a blocked URL can still be indexed if it's linked from elsewhere. and inject custom meta tagsMeta tags are HTML elements in a page's head that pass metadata about the page to search engines and browsers. For SEO only a few matter — the title element, the meta description, and the robots meta tag — while meta keywords and most others are ignored.?
- Does it render HTML server-side, or does it rely on client-side JavaScript?
- What’s the plugin/module ecosystem for SEO tooling?
- What is locked down and can’t be changed?
Platform choice rarely determines SEO success on its own, but the wrong platform — or a misconfigured one — creates technical ceilings that content and links alone can’t overcome.
Related: CMS, JavaScript SEO, Headless CMS
Build-time retrieval analysis plus live signals for this exact article. The automatic chunk report includes a deterministic readiness score and is ready without a model download.
Search Console
sampleGA4 traffic (28d)
sampleCloudflare traffic (7d)
sampledCrUX field data (28d, phone)
sampleGoogle NLP entities
localChangelog
Updated Jul 19, 2026.
Editorial summary and recorded change details.Summary
Cross-checked this hub against same-day fact corrections made to its five linked child articles (wordpress-seo, shopify-seo, webflow-seo, headless-cms-seo, next-seo). Found and fixed one contradiction: the hub repeated the now-corrected false claim that Shopify restricts robots.txt editing to non-standard plans, and separately implied Webflow restricts robots.txt like Wix/Squarespace does. WordPress version facts, Webflow CMS caps/redirects, and the Shopify Hydrogen/React-Router migration are not mentioned in this hub, so no change was needed for those.
Change details
- Before
Shopify (standard plans) and some hosted builders don't allow this [editing robots.txt directly].AfterShopify supports robots.txt customization on any plan through a robots.txt.liquid theme template, and Webflow exposes robots.txt natively under Settings → SEO; Wix and Squarespace are the more locked-down exception — corrected to match shopify-seo.mdx's and webflow-seo.mdx's verified corrections. - Before
restrict what you can customize — especially robots.txt, URL structure, and server-side configuration [SaaS builders, Beginner and AI-Summary lenses]Afterrobots.txt access varies by builder — Wix and Squarespace lock it down, while Webflow exposes it directly under Settings → SEO. - Before
Robots.txt | Full control | Restricted | Full control | Full control | Restricted (varies) [comparison table]AfterRobots.txt | Full control | Varies (Webflow: full edit; Wix/Squarespace: locked down) | Full control | Full control | Customizable via template (Shopify: any plan via Liquid); varies elsewhere
Full comparison unavailable — no prior snapshot was archived for this revision.