Complete headless Wix SEO audit checklist

This final lesson provides the complete 60-point SEO audit checklist specifically designed for headless Wix implementations, along with a systematic pre-launch review process and a quarterly maintenance workflow. A headless Wix site introduces unique SEO risks that standard audit checklists do not cover: Wix backend URLs leaking into search indexes, ISR caching misconfiguration causing stale canonical tags, webhook integration failures leaving blog content uncrawled, and hreflang clusters breaking when translation content is removed from the CMS. Use this checklist at launch and quarterly to ensure your headless site not only achieves its SEO potential at launch but maintains that advantage as the site evolves.

Pre-Launch Audit Process

Before running through the 60-point checklist, execute a systematic pre-launch crawl comparison that establishes your baseline and catches structural issues that the checklist items might not surface. This process uses Screaming Frog or a similar crawler to inspect every URL on your headless frontend against what the Wix backend serves, identifying mismatches, missing pages, and incorrect status codes before Google discovers them.

Running the pre-launch headless Wix SEO audit

• Export a complete list of all URLs from your legacy Wix site using Screaming Frog's crawl mode — this is your baseline of what should be accessible on the headless frontend
• Crawl your headless staging environment with Screaming Frog configured to crawl JavaScript-rendered pages, and compare the URL inventory against the Wix baseline to identify any missing pages
• Check that all Wix backend URLs (*.wixsite.com and *.wix.com URLs) are either redirecting to the headless frontend or returning 404 — they should never return 200 with crawlable content
• Verify that your noindex meta tag on the Wix backend site is active and that Screaming Frog finds no indexable pages when crawling the wixsite.com domain
• Run a PageSpeed Insights test on your homepage, a representative blog post, a product page, and a category page — document the initial scores as your performance baseline
• Validate your XML sitemap by submitting it to the Screaming Frog sitemap checker and verifying all URLs return 200 status codes and match your intended URL structure
• Test your robots.txt by running it through Google's robots.txt testing tool in Search Console — verify it allows Googlebot to crawl all intended directories
• Check your structured data by running 5-10 representative pages through the Google Rich Results Test and documenting which rich result types are detected and any errors
• Test international routing if applicable: visit each locale URL (/fr/, /de/) and confirm the correct translated content appears with the correct hreflang tags in the page source
• Verify Wix webhook integration by publishing a test post in the Wix dashboard and confirming the headless frontend reflects the update within your target ISR window

Technical Foundation (15 Points)

• All public pages render complete HTML on the server via SSG, ISR, or SSR — confirm by viewing source and verifying content appears without JavaScript execution
• No critical content (main headings, product details, blog post body) is loaded via client-side JavaScript only — test by disabling JavaScript in browser DevTools and confirming content is visible
• Robots.txt properly configured at domain root, allowing Googlebot access to all indexable content and explicitly disallowing admin, API, and staging directories
• XML sitemap includes all indexable URLs with accurate lastmod dates reflecting the most recent content update from the Wix CMS
• Sitemap submitted to Google Search Console and Bing Webmaster Tools with no errors reported in the Sitemaps coverage report
• HTTPS enforced on all URLs with valid certificate, HSTS headers configured, and no HTTP-to-HTTPS redirect chains longer than a single hop
• Custom 404 page returns correct HTTP 404 status code — verify with curl -I your-site.com/nonexistent-page and confirm the response shows 404 not 200
• Canonical tags present and self-referencing on all pages — no page should have a canonical pointing to a different page unless it is an intentional duplicate content management decision
• Pagination implemented with proper rel="next" and rel="prev" link tags on blog archives and product category pages with more than one page
• Wix backend URLs (wixsite.com domain) are noindexed or permanently redirected to the headless frontend — no Wix backend pages should appear in Google's index
• No mixed content warnings: all resources (images, scripts, stylesheets) served via HTTPS — check Chrome DevTools Security panel for any HTTP resources on HTTPS pages
• Clean URL structure: primary content URLs contain no query parameters or session tokens — filter parameter handling configured in robots.txt or via canonical tags
• Trailing slash handling consistent across all URLs: either always include or never include trailing slashes, with 301 redirects from the non-preferred version
• No redirect chains: all redirects resolve in a single hop — test using Screaming Frog's redirect chain report and fix any chains of two or more redirects
• Server response codes correct for all page types: 200 for live pages, 301 for permanent redirects, 410 for intentionally removed content, 404 for missing content

Content and On-Page SEO (15 Points)

• Unique title tags on every page pulled from Wix CMS SEO fields — no two pages share the same title, and all titles are between 30 and 60 characters
• Meta descriptions present and unique for all indexable pages — written to encourage clicks, between 120 and 160 characters, sourced from Wix CMS SEO description fields
• H1 tags present and unique on every page — each page has exactly one H1 that matches or closely relates to the page's target keyword and title tag
• Heading hierarchy follows logical H1 > H2 > H3 structure with no heading levels skipped — H3 never appears on a page without a preceding H2
• Image alt text populated from Wix Media Manager descriptions or Wix CMS alt text fields — no images with empty alt attributes unless they are purely decorative
• Internal linking structure connects related content: blog posts link to related posts and relevant category pages, product pages link to related products and parent categories
• Breadcrumb navigation present on all non-homepage pages and matches the URL hierarchy — visual breadcrumbs match the BreadcrumbList schema
• All main page content renders above the fold without JavaScript — test by disabling JavaScript and measuring what content is visible in the first 100vh
• Open Graph tags present for social sharing: og:title, og:description, og:image, og:url, og:type on all indexable pages
• Twitter Card tags present: twitter:card, twitter:title, twitter:description, twitter:image configured for optimal social media preview appearance
• Wix blog rich text content renders as semantic HTML with proper heading tags, figure/figcaption for images, and clean paragraph structure — not as div soup
• Product content includes all details from Wix eCommerce API: full description, specifications, pricing, availability, and image gallery
• No duplicate content across paginated pages, filtered URLs, or product variant pages — canonical tags or noindex used appropriately to manage duplicate risks
• Reading time and publication dates displayed visibly on blog posts sourced from the Wix Blog API minutesToRead and publishedDate fields
• Author information including name, bio link or social profile included on article and blog post pages sourced from Wix Blog API author data

Structured Data (10 Points)

• Organization schema present on homepage with name, url, logo, sameAs links to all social media profiles, and contactPoint if applicable
• WebSite schema with SearchAction potentialAction on homepage for Google's sitelinks search box — include query-input and target URL template
• Product schema on all product pages with name, description, image, offers (price, priceCurrency, availability, url), brand, and SKU properties
• Article schema on all blog posts with headline (max 110 chars), author (Person with name and url), datePublished, dateModified, image, and publisher (Organization)
• BreadcrumbList schema on all pages with breadcrumb navigation — matches the visible breadcrumb navigation exactly in terms of text and URLs
• FAQ schema on FAQ pages and product pages with question-answer pairs — each Question entity has acceptedAnswer with the full answer text
• LocalBusiness schema if serving local customers: includes address, telephone, openingHoursSpecification, geo, and priceRange from Wix Business Info
• ItemList schema on category and collection pages: each listed item has an @id, url, name, and position number
• All schema validates in Google Rich Results Test with no errors — warnings about recommended properties are acceptable but all required properties must be present
• No schema errors or warnings reported in Google Search Console Enhancements reports — resolve any issues within one week of discovery

Performance (10 Points)

• LCP under 2.5 seconds on mobile PageSpeed Insights field data — if field data is not available, lab data LCP under 2.5s with throttled 4G simulation
• CLS under 0.1 on both mobile and desktop PageSpeed Insights — all images have explicit dimensions, no content injected above existing content after load
• INP under 200ms measured via real user data from web-vitals package or PageSpeed Insights field data section
• TTFB under 800ms from edge CDN locations — verify by running curl --write-out "%{time_starttransfer}" from multiple geographic locations
• All images served via Wix Media CDN in WebP or AVIF format with explicit width, height, and quality parameters in the CDN URL
• Hero image (LCP element) preloaded with fetchpriority="high" using Next.js Image component priority prop — verify the preload link tag appears in page source
• JavaScript bundle under 150KB gzipped for initial page load — verify with Next.js Bundle Analyzer and split large dependencies into dynamic imports
• Web fonts preloaded with rel="preload" as="font" and font-display: swap in @font-face declarations — no invisible text during font loading
• Third-party analytics, chat, and marketing scripts loaded with Next.js Script strategy="lazyOnload" or strategy="afterInteractive" to prevent main thread blocking
• Service worker or CDN edge caching configured so repeat visitors get instant page loads from cache rather than full network requests

International SEO (5 Points)

• Hreflang link tags present in the document head on all multilingual pages — each language version links to all other language versions bidirectionally
• X-default hreflang tag set pointing to your primary language version on all multilingual pages — handles users whose language is not specifically targeted
• Language-specific XML sitemaps generated and submitted, each containing only URLs in that language with the correct locale prefix in every URL
• Translated content is unique, human-reviewed by native speakers, and has language-appropriate meta titles and meta descriptions — not machine-translated copies
• All international URLs follow a consistent subdirectory pattern (/fr/, /de/) matching the Wix Multilingual URL structure with no mixing of subdirectory and subdomain approaches

Monitoring and Maintenance (5 Points)

• Google Search Console verified and monitored weekly — review Coverage, Performance, and Enhancements reports for new errors and ranking changes
• Core Web Vitals monitoring set up with real user metrics via the web-vitals package sending data to your analytics platform — review monthly for degradation
• Automated crawl set up with Screaming Frog or Ahrefs to run monthly and compare against the post-launch baseline — alerts configured for new 404s, broken redirects, or missing canonical tags
• Wix webhook integration verified to trigger ISR rebuilds within 5 minutes of content changes in the Wix dashboard — test monthly by updating a piece of content and timing the frontend update
• Monthly SEO reporting comparing headless performance metrics (rankings, organic traffic, CTR, Core Web Vitals) against the pre-migration baseline established before going headless

Quarterly Maintenance Workflow

Running the 60-point checklist quarterly is only valuable if you act on the findings and track your score over time. Create a scoring system where each item is worth 1 point, giving you a maximum score of 60. Document your score at each quarterly review and track the trend. A declining score indicates technical debt accumulating as new features are added — catch it early before it becomes a ranking problem.

Running the quarterly headless Wix SEO review

• Schedule a fixed date each quarter for the audit — add it to your team calendar as a recurring event so it is treated as a planned engineering task, not an ad hoc activity
• Run a full Screaming Frog crawl of your production headless site and export the results — compare the URL count, status code distribution, and page title uniqueness against the previous quarter's export
• Run PageSpeed Insights on the 5 most important pages (homepage, top-traffic blog post, top product page, category page, about page) and record the LCP, CLS, and INP scores
• Check Google Search Console for any new Coverage errors, Breadcrumb errors, Product errors, or Article errors that appeared since the last quarter
• Validate 10 representative pages through the Google Rich Results Test — one of each major template type — and note any schema errors that have appeared since the last validation
• Review the Performance report in Google Search Console for organic traffic trends, average position changes, and click-through rate movement quarter over quarter
• Test all international URL routing and hreflang implementations if your site is multilingual — verify at least 3 representative pages per language with the hreflang validation tools
• Check that all Wix webhook integrations are functioning by reviewing your webhook delivery logs in the Wix dashboard and confirming recent ISR rebuilds completed successfully
• Score each of the 60 checklist items as pass or fail, calculate your total score, and document any failed items as technical SEO tasks in your project management system
• Prioritise the failed items by SEO impact and assign owners for each remediation task with a target completion date before the next quarterly audit