Most “SEO for [platform]” guides are the same generic advice with a brand name swapped into the title, and that’s why they don’t help you. The truth is that about 80% of a good platform seo checklist is identical no matter what you build on — a bot still has to crawl, render, and understand your pages the same way whether they’re served by WordPress, Shopify, Wix, Webflow, Squarespace, or a hand-rolled Next.js app. The remaining 20% is where platforms genuinely diverge, and that’s the part worth knowing cold, because it’s where each one quietly sabotages you by default.
This checklist is organized around exactly that split: the invariant fundamentals that apply everywhere, then the specific default you have to override on each major platform. Treat this platform seo checklist as a sequence: work it top to bottom before you blame Google for slow rankings.
Start by Separating “Platform-Invariant” from “Platform-Specific”
The single most useful mental model here is that search engines don’t care what generated your HTML. Googlebot fetches a URL, follows redirects, renders JavaScript if it has to, reads the DOM, and decides what the page is about and whether it deserves to rank. Every item in the first half of this platform seo checklist is a property of the final rendered page, not the tool that produced it. A slow, uncrawlable, thin page loses on any stack.
What changes per platform is the default behavior and the ceiling: how easily you can control the title tag, whether URLs are forced into a fixed structure, how the platform handles duplicate content, and how much JavaScript stands between the bot and your words. Knowing that division stops you from wasting a week fighting a “Shopify SEO problem” that’s really just a missing internal link.
Crawlability and Indexation: The Non-Negotiable Base
Nothing ranks that Google can’t crawl and index, so this is where any platform seo audit starts. Confirm your robots.txt isn’t blocking CSS, JS, or whole sections you actually want indexed — a surprising number of staging-to-production launches ship with a site-wide disallow still in place. Verify an XML sitemap exists, is referenced in robots.txt, and lists only canonical, indexable URLs (not tag pages, filtered facets, or thank-you pages).
- Check Google Search Console’s Pages report for the reasons URLs are excluded — “Crawled, currently not indexed” usually means thin or duplicative content, not a technical block.
- Make sure important pages aren’t buried more than three clicks from the homepage.
- Confirm there are no accidental
noindextags left over from development, and no orphan pages with zero internal links pointing at them.
URL Structure, Canonicals, and Duplicate Content
Clean, stable, descriptive URLs are a fundamental — but this is also the first place platforms impose their will. The universal rules: use lowercase, hyphen-separated, keyword-relevant slugs; avoid parameter soup where you can; and never change a ranking URL without a 301 redirect. Then set a self-referencing canonical tag on every page so filtered, sorted, and session-parameter versions of a URL consolidate their signals onto one address.
Duplicate content is rarely a “penalty” — it’s a dilution problem. When ten near-identical URLs compete, Google picks one and your link equity scatters. Canonicals and consistent internal linking fix it. This matters more on some platforms than others, which we’ll get to.
On-Page Signals: Titles, Meta, Headings, and Structured Data
Every platform lets you control these; most bury the controls somewhere different. Your working list: one unique, ~50–60-character title tag per page with the primary term near the front; a compelling 150–160-character meta description (it won’t rank you, but it wins the click); exactly one H1 that matches search intent; and a logical H2/H3 hierarchy that a screen reader and a crawler can both follow. Add schema markup where it fits — Product, Article, FAQ, Breadcrumb, LocalBusiness — because it’s how you earn rich results and feed AI answer engines clean, machine-readable facts.
Core Web Vitals and Rendering Reality
Speed is a genuine ranking input, but the version that matters is field data — real users’ Largest Contentful Paint, Interaction to Next Paint, and Cumulative Layout Shift as reported in the Core Web Vitals report, not a one-off lab score. The universal fixes are the same everywhere: compress and lazy-load images, serve modern formats like WebP, defer non-critical JavaScript, and cut third-party scripts.
Rendering is the sharper platform divider. If your primary content only appears after client-side JavaScript executes, you’re betting on Google’s render budget every crawl. Server-rendered HTML is always the safer bet, which is why the JavaScript-heavy builders demand extra scrutiny here.
The Platform-Specific Layer: Where Each One Trips You Up
This is the 20% that generic guides skip, and it’s what turns a generic checklist into a real platform seo checklist. Here’s the current default you have to work around on each major platform.
WordPress
The most flexible platform, which is also the risk — nothing is optimized until you configure it. Install one SEO plugin (Yoast or Rank Math), set permalinks to the “Post name” structure immediately (the default ?p=123 is terrible), and disable indexing of author and tag archives if they create thin duplicate pages. WordPress’s real SEO tax is speed: bloated themes and stacked plugins are the usual Core Web Vitals killers, so audit your theme and caching before adding anything.
Shopify
Shopify forces /products/ and /collections/ into your URLs and you can’t remove them. Worse, the same product reachable through a collection generates a duplicate URL — Shopify sets canonicals to the primary product URL by default, so verify that’s still true after theme edits. You cannot edit robots.txt.liquid as freely as on WordPress, and blog URLs are locked to /blogs/. Focus your energy where you do have control: title/meta fields, image alt text, and internal linking from collection pages.
Wix
Wix earned its bad reputation years ago for JavaScript-heavy rendering, and it has largely fixed that — Wix sites can and do rank. Its SEO settings panel (Wix SEO Setup Checklist and the per-page SEO tab) exposes titles, meta, canonical, and structured data. The real constraints today are less control over server-level details and heavier page weight, so lean hard on the image and script hygiene items above.
Webflow
Webflow ships clean, semantic, server-rendered HTML — a genuine SEO strength. The gotcha is CMS Collection routing: your dynamic URLs inherit the Collection’s slug pattern, so plan that structure before you publish and set canonical/meta fields on the Collection template, not page by page. Don’t forget to disable the free .webflow.io subdomain from indexing once you connect a custom domain.
Squarespace
Squarespace is fine for smaller content and commerce sites but gives you the least low-level control. Titles, descriptions, and clean URLs are editable; deep technical tweaks (custom robots directives, granular redirects at scale) are limited. Use its built-in redirect manager religiously when you change slugs.
Next.js and Headless Builds
Custom stacks give you total control and total responsibility. The decision that dominates everything is rendering: use static generation (SSG) or server rendering (SSR)/incremental static regeneration for any page that must rank, not client-only rendering. Use the framework’s metadata API to emit unique titles, descriptions, canonicals, and Open Graph tags per route, generate a sitemap programmatically, and confirm your rendered HTML contains the actual content when you view source — not an empty <div id="root">.
The One Checklist Item Everyone Skips: Internal Linking
Whatever platform you’re on, the highest-leverage move after the technical base is deliberate internal linking. It distributes authority, tells Google which pages matter, and defines your topical structure. Most CMS themes generate zero contextual internal links automatically — every one you place is manual. A single strong internal link from an established page to a new one often does more for indexing speed than a week of technical tinkering.
Turning the Checklist into an Actual Audit
A checklist is only useful if you run it against real pages, and doing that manually across a whole site is where people give up. This is the workflow SEO Rocket is built to compress: its real-crawler site audit fetches your pages the way a search engine does and surfaces the exact issues on this list — missing canonicals, broken redirects, thin pages, orphaned URLs, and slow templates — regardless of which platform generated them. Because it’s a platform-agnostic SEO layer rather than a page builder, the same audit and rank tracking work whether the site is Shopify, Webflow, or a custom Next.js app.
From there the loop continues in one place: AI keyword research on real Ahrefs data to decide what each page should target, a validation-gated AI writer to produce the on-page content at scale without shipping thin drafts, and rank tracking plus a client dashboard to prove the checklist worked. It runs around $50/month with a free tier — and it exists because this exact playbook, refined across 1,000,000+ ranking pages, comes down to doing every unglamorous checklist item consistently while competitors skip half of them.
Frequently Asked Questions
Is a CMS SEO checklist different from a website builder SEO checklist?
The fundamentals are identical — crawlability, URLs, on-page tags, speed, and internal links apply to both. The difference is control. A CMS SEO checklist like WordPress’s assumes you can edit almost anything (robots.txt, redirects, schema). A website builder SEO checklist for Wix or Squarespace has to account for locked defaults and fewer server-level levers, so it leans harder on the settings the platform does expose.
Which platform is best for SEO?
There’s no single winner, and any platform that claims to be “best for SEO” is marketing. WordPress and Webflow give the most control; Shopify is strong for commerce despite its forced URL structure; Wix and Squarespace are perfectly capable for smaller sites. The determining factor is how well you execute the checklist, not the logo. A well-run Wix site beats a neglected WordPress one every time.
How often should I run a platform SEO audit?
Run a full platform seo audit at launch, after any theme or template migration, and roughly quarterly thereafter. Check crawl and indexation data in Search Console monthly, since that’s where new problems (like an accidental noindex or a redirect chain) show up first. Continuous rank tracking catches issues between formal audits.
