DomainLens

Guías

Wix SEO Checklist: Audit What Google Actually Receives

Wix handles much of the infrastructure, but it cannot choose your canonical strategy, remove duplicate content, or prove that Google indexed the right pages. This checklist verifies the published output.

Revisa tu sitio antes de corregir

Ejecuta una auditoría nueva en DomainLens y usa el informe como lista de prioridades.

Ejecutar auditoría SEO gratis

Start with the published site, not the Wix editor

A green checkbox in Wix confirms that a setting exists; it does not confirm that the live URL returns the intended HTML or that Google selected it for indexing. Audit the custom-domain URL after publishing, including its response code, rendered title, robots directive, canonical, headings, content, and crawlable links.

Use Wix’s SEO Setup Checklist for initial configuration, then verify every important template independently. The home page, service pages, product pages, blog posts, and CMS dynamic pages can produce different output.

Confirm Wix allows the pages to be indexed

If Search Console says “Crawled – currently not indexed,” do not toggle indexing off and on. Use the indexability debugging workflow to separate a directive problem from weak, duplicated, or poorly linked content.

  1. 1Open SEO & GEO in the Wix dashboard and confirm site-wide search indexing is enabled.
  2. 2For each sample page, open Page settings → SEO basics and verify that search engines are allowed to index it.
  3. 3Fetch the published URL and confirm HTTP 200. Redirects, soft 404s, password protection, and unpublished dynamic items require different fixes.
  4. 4Inspect the rendered head for a single indexable robots directive and a single canonical pointing to the preferred custom-domain URL.
  5. 5Run URL Inspection in Search Console. Compare the user-declared canonical with Google-selected canonical and inspect the rendered HTML.

Audit page-level SEO without copying one pattern everywhere

CMS collection patterns need special attention. A title pattern such as “Item name | Brand” is useful only when every item name is descriptive. Empty fields, repeated city pages, and near-identical service variants can generate hundreds of formally valid but low-value URLs.

ElementWix locationPublished-page check
Title and descriptionPage settings → SEO basicsUnique, intent-specific, and present in rendered head
URL slugPage settings → URL slugReadable, stable, and redirected if changed
CanonicalAdvanced SEOOne absolute URL matching the preferred live page
H1Editor text elementOne descriptive page heading, not merely the logo
Image alt textImage settingsDescribes informative images; decorative images remain empty
Structured dataAdvanced SEO → Structured data markupMatches visible content and passes Rich Results Test

Find Wix duplication and discovery problems

  • Check both the Wix subdomain and custom domain. The custom domain should be the only internally linked and canonical version.
  • Search for old URL slugs after a restructure and confirm they redirect once to the closest replacement.
  • Inspect tag, category, filter, search, member, and dynamic collection URLs. Keep only versions with a distinct search purpose indexable.
  • Open sitemap.xml and compare it with the set of pages you intentionally want indexed. A sitemap is an inventory, not a guarantee.
  • Crawl navigation and in-content links. Important landing pages should not depend on JavaScript-only interactions or site search for discovery.

Performance checks that are actionable on Wix

Wix controls hosting and core delivery, but page composition still matters. Test a representative template on mobile. Oversized hero media, background video, animation, many app widgets, consent tools, chat, and marketing tags can delay LCP or occupy the main thread.

If LCP is slow, identify the LCP element before compressing every image. If INP is poor, test the interaction that users perform and isolate third-party code. If CLS is poor, look for galleries, embeds, banners, and late font or app content that changes dimensions.

Use DomainLens as the publication check

Run DomainLens against each sample URL after Wix is published. Read status code, robots, canonical, headings, structured data, internal links, mobile/desktop Core Web Vitals, and Lighthouse diagnostics together. A pass in the editor is not enough if the public response disagrees.

Record findings by template: affected URLs, evidence, recommended Wix setting, and validation method. Fix a shared collection template before isolated page copy, republish, rerun the same URLs, and only then request indexing.

Recursos relacionados