Wix Velo SEO automation: backend functions and scheduled tasks

Wix Velo unlocks the most powerful SEO automation capabilities on the Wix platform. Backend functions can run server-side code on a schedule, query external APIs, process CMS data, and trigger actions without user interaction. Scheduled tasks (jobs) can run daily, weekly, or at custom intervals. This lesson covers how to use Wix Velo backend functions and scheduled tasks to build custom SEO automations that no off-the-shelf tool provides.

Wix Velo Backend Capabilities for SEO

• Scheduled jobs: run functions at specific times (daily at 6am, weekly on Mondays, etc.)
• HTTP functions: create API endpoints on your Wix site that external tools can call
• Data hooks: trigger functions automatically when CMS items are created, updated, or deleted
• External API calls: query Google Search Console API, PageSpeed API, or any REST API
• Email sending: send automated reports and alerts via Wix email capabilities
• CMS data processing: bulk update meta tags, generate sitemaps, or audit content fields

Setting Up Your First Velo Scheduled SEO Job

Create a daily CMS content quality check using Velo

• Step 1: Enable Velo Dev Mode on your Wix site (Settings > Advanced > Developer Tools).
• Step 2: In the Velo sidebar, navigate to Backend and create a new file called "seoJobs.js".
• Step 3: Import wix-data at the top of the file: import wixData from "wix-data";
• Step 4: Create a function that queries your main CMS collection and checks for SEO issues: missing meta descriptions, short titles, missing alt text fields.
• Step 5: For each item with issues, compile a report object with the item title, URL, and specific issues found.
• Step 6: Use wix-email or a connected email service to send the report to your email address.
• Step 7: Create a jobs.config file in the Backend section. Define a scheduled job that runs your function daily at 7am.
• Step 8: The jobs.config format is: { "jobs": [{ "functionLocation": "/seoJobs.js", "functionName": "dailySeoCheck", "description": "Daily SEO content quality check", "executionConfig": { "cronExpression": "0 7 * * *" } }] }
• Step 9: Publish the site to activate the scheduled job.
• Step 10: Wait 24 hours and verify the email report arrives. Check the Wix logs (Site Monitoring) for any errors.

Data Hooks for Automatic SEO Validation

Wix Velo data hooks run automatically when CMS data changes. A beforeInsert hook can validate SEO fields before a new item is published. An afterInsert hook can trigger indexing requests or update related pages. This is the most powerful way to enforce SEO quality standards on Wix because it catches issues at the point of content creation.

Querying External SEO APIs from Velo

Wix Velo backend functions can call external APIs using the fetch function. This enables you to query the Google PageSpeed Insights API to check page performance, the Google Search Console API to monitor indexation, or third-party SEO APIs for ranking data. API responses can be stored in CMS collections for reporting or trigger alerts when values exceed thresholds.

Complete How-To Guide: Building an Automated SEO Dashboard with Wix Velo

Create an automated SEO monitoring dashboard on your Wix site

• Step 1: Create a CMS collection called "SEO Metrics" with fields: Page URL (text), Check Date (date), Page Speed Score (number), Mobile Score (number), Indexed Status (boolean), Issues Found (rich text).
• Step 2: In Velo Backend, create a file called "seoMetricsCollector.js".
• Step 3: Write a function that fetches your important page URLs from a "Monitored Pages" CMS collection.
• Step 4: For each URL, call the Google PageSpeed Insights API (free, no key required for limited use): fetch("https://www.googleapis.com/pagespeedonline/v5/runPagespeed?url=" + pageUrl)
• Step 5: Extract the performance score from the API response and save it to the SEO Metrics collection.
• Step 6: Schedule this function to run weekly using jobs.config.
• Step 7: Create a dynamic page on your Wix site that displays the SEO Metrics collection as a dashboard with charts showing scores over time.
• Step 8: Add conditional formatting: green for scores above 90, yellow for 50-89, red for below 50.
• Step 9: Add an alert trigger: if any page score drops below 50, send an email notification.
• Step 10: Expand the dashboard over time: add indexation checks, keyword ranking data, and broken link counts as you build more automation.

Automate safely: guardrails for scheduled SEO jobs

Automation is powerful here, which is exactly why it needs guardrails, because a scheduled job that changes live SEO settings on its own can do damage faster than any manual mistake. The safe default is that jobs monitor and alert, they do not act. Have a scheduled job flag pages with missing meta descriptions or dropped rankings and email you, rather than letting it rewrite titles automatically, because an automated meta rewrite that goes wrong can pull rankings across a whole collection before you notice. If you do automate a change, gate it: write the proposed change to a review field in the CMS first and apply it only after a person approves, and always log what changed and when so you can undo it. Two more practical limits. External APIs have quotas, so the Google PageSpeed Insights and Search Console calls in your jobs will fail if you run them too often, which means spacing runs sensibly and caching results rather than re-fetching. And wrap every scheduled function in error handling that alerts you when it fails, because the worst automation is the one you assume is running and that stopped weeks ago. For the wider picture of what backend Velo unlocks, see <a href="/the-complete-wix-seo-course/lessons/wix-velo-seo-what-dev-mode-unlocks">what Dev Mode unlocks</a>, and for a monitoring job worth building first, see <a href="/the-complete-wix-seo-course/lessons/ranking-drop-detection-automated-keyword-monitoring-wix-sites">automated ranking-drop detection</a>.