Every WooCommerce REST API fix we catalog
SEOLZ catalogs 3 fixes for WooCommerce REST API across 2 areas — SEO, answer-engine readiness, accessibility, security and site-health. Each lists the exact steps for WooCommerce REST API, with a link to the official docs.
Accessibility (WCAG) · 1 fixes
Document titleQuick win
Add a descriptive, non-empty `<title>` element to every page so browsers, screen readers, and search engines can identify it.
On WooCommerce REST API
- When creating or updating products via the REST API, include the 'yoast_head_json' or use the Yoast SEO REST endpoint PATCH /wp-json/yoast/v1/indexable to set the title.
- Alternatively, update the post's native title (which Yoast uses as fallback) via PATCH /wp-json/wc/v3/products/{id} with { 'name': 'Your Product Title' } — this populates the SEO title template automatically.
- Verify by fetching the page HTML and confirming a non-empty <title> tag is present.
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Women's Running Shoes – Acme Sports</title>
</head>
<body>
<!-- page content -->
</body>
</html>Place this inside the <head> section of every HTML page. Replace the text with the actual page and store name.
Security (OWASP) · 2 fixes
Https not availableQuick win
Enable HTTPS by installing a valid SSL/TLS certificate and redirecting all HTTP traffic to the secure HTTPS version of your store.
On WooCommerce REST API
- The REST API inherits the SSL status of the WordPress/WooCommerce installation.
- Ensure HTTPS is active and enforced on the WordPress site first (see WooCommerce steps above).
- WooCommerce REST API requires HTTPS by default for all authenticated endpoints — if your site is HTTP-only, API calls using OAuth or Application Passwords will fail or be insecure.
- After enabling HTTPS, update any API client configurations or webhooks to use the https:// base URL.
Missing spfQuick win
Add a DNS TXT record containing a valid SPF policy to your domain so that email receivers can verify which servers are authorised to send mail on your behalf.
On WooCommerce REST API
- This is a headless WooCommerce setup; email is still sent by the WordPress/WooCommerce backend via your SMTP configuration.
- Identify your SMTP provider in your SMTP plugin settings (e.g. WP Mail SMTP → Settings) and add its SPF include: tag to a TXT record at '@' in your DNS provider.
- Verify propagation.
v=spf1 include:_spf.google.com include:sendgrid.net include:spf.mailgun.org -allAdd this as a DNS TXT record at your domain apex ('@'). Replace the include: values with the exact hostnames from each of your email providers' SPF documentation. Only one SPF TXT record is allowed per domain — combine all providers into one record.