Technical SEO glossary: infrastructure terms for Wix developers and site owners

Technical SEO has its own specialised vocabulary that can be intimidating for new practitioners. This lesson defines every major technical SEO term with specific context for how each applies to Wix websites. Understanding these terms allows you to diagnose technical issues, communicate with developers, and make informed decisions about your Wix site's infrastructure. Each term includes practical Wix application steps, common mistakes, and related terms to guide further learning.

Canonical Tag

An HTML element (rel="canonical") that specifies the preferred version of a URL when multiple URLs display identical or similar content. Canonical tags tell search engines which version to index and credit with ranking authority, preventing duplicate content issues. Wix automatically generates canonical tags for most pages, but you should verify them in the page SEO settings and override them manually where needed for dynamic content pages.

Usage Context

Canonical tags are essential when Wix generates multiple URL variants for the same page, such as filtered product category pages, blog tag pages, or CMS collection views. Without canonical tags, Google may split ranking authority across duplicate URL variants.

How to Apply on Wix

Managing canonical tags on Wix

• In the Wix Editor, open a page and navigate to its SEO settings.
• Go to the Advanced SEO tab to find the canonical URL field.
• Verify the pre-filled canonical URL is the correct preferred URL for that page.
• For CMS or dynamic pages where Wix cannot set a canonical automatically, use Velo code to set canonical URLs programmatically via wix-seo.
• Check your canonical tags using a browser extension like SEO Meta in 1 Click or Screaming Frog crawl.
• If using URL parameters for filtering (e.g., /products?colour=red), ensure the canonical on parameter pages points to the root /products page.

Common Mistakes

• Leaving auto-generated canonical tags unchecked — Wix may occasionally generate incorrect canonicals
• Setting self-referencing canonicals incorrectly, causing confusion in large Wix eCommerce sites
• Using canonical tags as a substitute for proper 301 redirects when permanently moving pages

Related Terms

• Duplicate Content
• Redirect (301)
• URL Structure
• Index
• Dynamic Pages

Robots.txt

A plain text file at the root of a domain that instructs compliant search engine crawlers which pages or sections should not be crawled. Wix automatically generates a robots.txt file. You can view it by adding /robots.txt to your domain. Check that critical pages and folders are not accidentally disallowed, and use it to block low-value areas like internal search result pages from consuming crawl budget.

Usage Context

Robots.txt controls crawling but NOT indexing. A page disallowed in robots.txt can still be indexed if it has external links pointing to it. For pages you want excluded from the index, use a noindex meta tag rather than (or in addition to) robots.txt disallow.

How to Apply on Wix

Reviewing your Wix robots.txt

• Visit yourdomain.com/robots.txt in a browser to view your Wix-generated robots.txt file.
• Verify that important pages and sections are not accidentally listed under Disallow.
• Check that your sitemap URL is correctly listed in the robots.txt file (Wix usually includes this automatically).
• For advanced Wix sites using Velo, you can create custom HTTP functions to serve a modified robots.txt with additional rules.
• Do not disallow crawlers from your entire site or from any directory containing important content.

Common Mistakes

• Using robots.txt to try to hide sensitive pages — disallowed pages can still be indexed via external links
• Accidentally blocking Googlebot from crawling CSS or JavaScript files that are needed to render your Wix pages
• Confusing robots.txt disallow with noindex — they are different directives with different effects

Related Terms

• Noindex
• Crawl Budget
• Sitemap
• Canonical Tag
• Index

Sitemap (XML Sitemap)

An XML file that lists all the URLs on your website you want search engines to discover and index, along with metadata about each URL including last modification date, change frequency, and priority. Wix automatically generates and updates an XML sitemap at yourdomain.com/sitemap.xml. Submit it to Google Search Console to accelerate indexing of new and updated pages.

Usage Context

A sitemap does not guarantee indexing — it is a discovery aid. Google uses it to find pages faster, but the actual decision to index is still based on content quality. Sitemaps are most valuable for large Wix sites (hundreds of pages) and for sites that publish new content frequently.

How to Apply on Wix

Managing your Wix sitemap

• Visit yourdomain.com/sitemap.xml and verify it loads correctly and includes your most important pages.
• Submit the sitemap in Google Search Console: go to Sitemaps and enter your sitemap URL.
• After publishing new content, wait for Wix to update the sitemap automatically, then resubmit in GSC to prompt faster discovery.
• Check the sitemap in GSC periodically for errors — GSC will report if any sitemapped URLs have issues.
• Ensure that pages you want in the sitemap are not set to noindex in their Wix page SEO settings, as Wix may exclude noindex pages from the sitemap.

Common Mistakes

• Including noindex pages in your sitemap — this creates a contradictory signal
• Never resubmitting the sitemap in GSC after major content additions
• Assuming the sitemap guarantees all pages will be indexed quickly

Related Terms

• Index
• Robots.txt
• Crawl Budget
• Google Search Console
• Noindex

Core Web Vitals (LCP, INP, CLS)

Google's user experience ranking signals measuring loading performance (LCP - Largest Contentful Paint, target under 2.5s), interactivity (INP - Interaction to Next Paint, target under 200ms), and visual stability (CLS - Cumulative Layout Shift, target under 0.1). Wix has improved its Core Web Vitals performance significantly, and following the technical optimisation modules of this course will help your Wix site meet all three thresholds.

Usage Context

Core Web Vitals data appears in Google Search Console under Experience > Core Web Vitals. Google uses field data (real user measurements via Chrome User Experience Report) for ranking, not lab data from PageSpeed Insights. A page can show "Needs Improvement" in lab tests while having "Good" field data — field data is what counts.

How to Apply on Wix

Improving Core Web Vitals on your Wix site

• Check your Core Web Vitals in Google Search Console under Experience > Core Web Vitals.
• Use PageSpeed Insights (pagespeed.web.dev) to identify specific issues affecting LCP, INP, and CLS.
• For LCP: optimise your hero image — use WebP format, set it as the largest above-the-fold element, and ensure it is not lazy-loaded.
• For CLS: avoid adding content above existing elements and set explicit width/height dimensions on images in Wix.
• For INP: minimise third-party scripts — remove unused apps from Wix App Market that add JavaScript.
• Use Wix's built-in image compression and format conversion to improve loading performance.
• Test on mobile specifically — mobile Core Web Vitals thresholds are harder to meet on Wix.

Common Mistakes

• Optimising for desktop PageSpeed scores while ignoring mobile field data
• Adding too many third-party apps from the Wix App Market that degrade INP
• Using high-resolution images without compressing them — a common LCP killer on Wix sites

Related Terms

• Page Speed
• Mobile-First Indexing
• Lazy Loading
• JavaScript SEO
• Rendering

Crawl Budget

The number of pages Google will crawl on your website within a specific timeframe, determined by server capacity and page importance. For most Wix sites with under a few thousand pages, crawl budget is not a major concern. However, for larger Wix eCommerce sites with faceted navigation or extensive product catalogues, managing crawl budget by blocking low-value URLs becomes important.

Usage Context

Crawl budget matters most for Wix sites with hundreds of CMS-generated pages, large product catalogues, or URL parameters from filter menus. If Googlebot is crawling thousands of low-value filtered URLs, it may not have budget to crawl new high-value content pages quickly.

How to Apply on Wix

Managing crawl budget on large Wix sites

• Review the Crawl Stats report in Google Search Console (Settings > Crawl stats) to see how often Googlebot visits your site.
• Use URL Inspection to check crawl frequency of individual pages — infrequent crawls signal low perceived value.
• For Wix eCommerce sites, ensure filtered category URLs (with URL parameters) have canonical tags pointing to the main category page.
• Set noindex on thin or low-value pages: internal search results, utility pages, empty category pages.
• Build more internal links to important pages to signal their value and encourage more frequent crawling.

Common Mistakes

• Over-indexing internal search and filter pages on Wix eCommerce sites
• Creating hundreds of near-duplicate CMS pages that dilute crawl budget without adding unique value
• Ignoring crawl budget until a large Wix site experiences slow indexing of new content

Related Terms

• Robots.txt
• Noindex
• Sitemap
• Index
• Crawl Depth

Mobile-First Indexing

Google's approach of using the mobile version of a website as the primary basis for crawling, indexing, and ranking. Wix websites are responsive by design, meaning the mobile version is automatically maintained. However, you must ensure that all content, structured data, and metadata present on desktop is equally present on mobile. Check this using Google's URL Inspection tool in Search Console.

Usage Context

Mobile-first indexing means that if your Wix mobile version hides content (for aesthetic reasons), Google will not index that hidden content. The Wix Editor allows you to hide elements on mobile — anything hidden on mobile is effectively invisible to Google.

How to Apply on Wix

Ensuring mobile-first compliance on your Wix site

• Open the Wix Editor and switch to mobile view.
• Scroll through each important page and verify that all key content (headings, body text, CTAs) is visible and not hidden.
• Check that images have alt text in Wix settings — alt text is particularly important for mobile image SEO.
• Use Google's Mobile-Friendly Test (search.google.com/test/mobile-friendly) to check individual pages.
• Review the Mobile Usability report in Google Search Console for any flagged issues.
• Ensure structured data and meta tags are identical between mobile and desktop page versions.

Common Mistakes

• Hiding content on mobile using Wix's hide on mobile feature to achieve a cleaner design
• Not checking mobile usability after making desktop design changes — mobile can break when desktop layout changes
• Using font sizes too small for mobile users (under 14px) which affects both UX and mobile usability scores

Related Terms

• Core Web Vitals
• Page Speed
• Schema Markup
• URL Inspection Tool
• Google Search Console

Schema Markup and Structured Data

Standardised code (typically in JSON-LD format) added to web pages to help search engines understand the content and context of information. Schema markup enables rich results such as star ratings, FAQ accordions, product prices, event details, and recipe information in Google search results. Wix supports JSON-LD structured data through custom code blocks and some apps, enabling rich results that significantly improve click-through rates.

Usage Context

Schema markup is a technical SEO enhancement, not a ranking booster in itself. It makes your content eligible for rich results in Google Search, which improves CTR. However, eligibility does not guarantee Google will display the rich result — Google uses rich results selectively.

How to Apply on Wix

Implementing schema markup on Wix

• Go to your Wix Dashboard and navigate to Settings > Custom Code.
• Click Add Custom Code and select the Head placement.
• Paste your JSON-LD schema code inside a <script type="application/ld+json"> tag.
• Set the code to load on the specific page(s) where it applies (e.g., FAQ schema on the FAQ page).
• Validate your schema at search.google.com/test/rich-results after publishing.
• Monitor the Enhancements section in Google Search Console for schema errors and warnings.
• Common schema types for Wix sites: Organization, LocalBusiness, FAQPage, BreadcrumbList, Product, Event.

Common Mistakes

• Adding schema without validating it — invalid schema provides no benefit and may cause errors in GSC
• Marking up content that is not visible on the page — Google requires schema to reflect actual visible content
• Using duplicate schema blocks from multiple sources (Wix app + custom code) that conflict with each other

Related Terms

• JSON-LD
• Rich Results
• FAQPage Schema
• BreadcrumbList
• Google Search Console

Noindex

A directive instructing search engine crawlers not to include a specific page in the search index. In Wix, noindex is controlled per page in the SEO settings under "Prevent search engines from indexing this page." Use noindex for thank-you pages, duplicate content pages, admin pages, and any content that should not appear in search results.

Related Terms

• Robots.txt
• Index
• Crawl Budget
• Canonical Tag
• URL Inspection Tool

HTTPS

HyperText Transfer Protocol Secure, the encrypted version of HTTP. Google confirmed HTTPS as a ranking signal in 2014. All Wix websites are automatically served over HTTPS, so this is handled for you. However, when you connect a custom domain, verify that HTTP requests redirect correctly to HTTPS and that there are no mixed content warnings.

Related Terms

• Custom Domain
• Redirect (301)
• Security
• Core Web Vitals
• Ranking Factor

301 and 302 Redirects

Server instructions that automatically forward users and crawlers from one URL to another. A 301 redirect signals a permanent move and passes the majority of link equity to the new URL. A 302 redirect signals a temporary move. In Wix, you manage 301 redirects through Marketing & SEO > SEO Tools > URL Redirect Manager. Use 301 redirects whenever you change a page URL, delete a page, or restructure your site.

How to Apply on Wix

Setting up 301 redirects in Wix

• Go to Marketing & SEO > SEO Tools > URL Redirect Manager in your Wix Dashboard.
• Click Add Redirect and enter the old URL (the one you want to redirect from) and the new URL.
• Select Permanent (301) for any redirect that is a permanent URL change.
• Use Temporary (302) only when you plan to restore the original URL in the future.
• Verify the redirect is working by visiting the old URL in a browser and confirming it lands on the new URL.
• After a site migration or URL restructure, create a redirect map covering every changed URL before making the changes live.

Common Mistakes

• Using 302 (temporary) instead of 301 (permanent) redirects for permanent URL changes — 302s do not pass link equity
• Creating redirect chains (A redirects to B which redirects to C) — each hop loses some link equity
• Deleting pages without setting up redirects — causes 404 errors that lose both traffic and link equity

Related Terms

• 404 Error
• Link Equity
• URL Structure
• Site Migration
• Canonical Tag

JavaScript SEO

The discipline of ensuring JavaScript-rendered content is properly crawled and indexed. Wix relies heavily on JavaScript, but Google's crawler uses a headless Chromium-based renderer that processes JavaScript. However, there can be delays in rendering. Critical content like headings, product information, and internal links should be in the initial HTML response where possible, not dependent on JavaScript execution.

Related Terms

• Rendering
• Core Web Vitals
• Crawl Budget
• Velo by Wix
• Mobile-First Indexing

Hreflang

An HTML attribute specifying the language and regional targeting of a webpage, helping search engines serve the correct language version to users. Wix Multilingual automatically manages hreflang implementation when you enable multiple languages. Verify correct hreflang configuration using Google Search Console's International Targeting report and the hreflang Testing Tool.

Related Terms

• Wix Multilingual
• International SEO
• Google Search Console
• Canonical Tag
• URL Structure

404 and 410 Status Codes

404 (Not Found) indicates a page does not exist. 410 (Gone) indicates a page has been permanently removed. Wix shows a default 404 page for missing URLs. You can customise this page to improve user experience. Monitor 404 errors in Google Search Console and either restore the missing content or redirect the URL to the most relevant alternative page.

Related Terms

• Redirect (301)
• Crawl Error
• Link Building
• Google Search Console
• Site Migration