SEO Optimizer

Paid pluginsize Mplanned, not built

Indicative price, not an offer: €29/mo; meta optimization, schema markup, sitemap, redirect management

Generated from docs/plan/paid/seo-optimizer/PLAN.md in the AstroBaaS repository. Nothing described below is implemented — it is the written plan for it.

SEO Optimizer helps merchants improve search rankings by managing meta tags, structured schema markup, XML sitemaps, canonical URLs, and redirect chains. Merchants get audit reports showing which products lack meta descriptions or schema markup, recommendations for keyword optimization, and automated bulk fixes. This is a paid plugin requiring SEO expertise (support commitment) and search-rank tracking (ongoing monitoring SLA).

The problem

Products rank nowhere on Google; merchants have no meta tags, no schema markup, no sitemap. Learning SEO is complex; merchants don’t know where to start. Competitors with better SEO dominate search results, and merchants lose customers to organic search.

What it does

• Meta tag management: auto-generate or manual edit meta title, meta description, meta keywords
• Schema markup: auto-generate JSON-LD for Product, BreadcrumbList, Organization, FAQPage
• Structured data validator: validate schema against schema.org spec, show errors
• XML sitemap: auto-generate sitemap.xml, include all products, categories, blog posts
• Canonical URL: auto-set or manual override for syndicated/duplicate content
• Redirect management: create 301 redirects from old URLs to new (e.g., after product rename)
• Bulk audit: scan all products, report missing meta titles, short descriptions, missing schema
• Keyword analyzer: suggest primary keyword for each product based on name, description, category
• Bulk fix: apply recommended meta title/description template to 500 products in one action
• Search-rank tracking: monthly snapshot of top 100 keywords, ranking positions (via third-party API)
• Audit log: all meta changes tracked with timestamp and staff member

What it deliberately does NOT do

Each boundary carries its reason. A boundary without a reason gets crossed by the next person who reads this.

• Paid search (Google Ads, Bing Ads) — scope is organic SEO only; paid ads are separate channel
• Content rewriting (restructure paragraphs for keyword density) — scope is meta markup only; content strategy is merchant responsibility
• Backlink analysis or competitor monitoring — scope is on-page SEO only; external link analysis requires third-party data

Data model

Extend core product schema: add seoMetadata = { metaTitle, metaDescription, metaKeywords, canonicalURL, schema_json }. New plugin-owned collection: SEOAudit (id, timestamp, productCount, missingMetaTitles, missingSchemaMarkup, recommendations[]). No breaking migration if using extension.

API

• GET /api/seo/audit — scan all products, return audit report
• PATCH /api/products/:id/seo — set meta title, description, canonical URL
• POST /api/seo/bulk-fix — apply template to 500 products (meta title = ‘{name} | Buy Online’)
• GET /api/seo/sitemap.xml — generate sitemap
• POST /api/seo/redirects — create 301 redirect
• GET /api/seo/keywords/:id — suggest primary keyword for product
• GET /api/seo/schema/:id — return JSON-LD schema markup for product

Every route added here must also appear in src/pages/openapi.json.ts — a test fails the build if it does not.

Admin

SEO Dashboard: audit score (e.g., 62/100), breakdown (40% products have meta title, 15% have schema). Audit report lists products missing meta data, grouped by issue type. Bulk fix form: select template (e.g., ‘{name} | Premium {category}’), apply to products matching filter (missing meta title). Redirect manager: old URL → new URL, bulk import from CSV. Keyword analyzer shows suggested keyword for each product. Schema markup preview shows JSON-LD for selected product. Monthly search-rank report shows top 20 keywords and ranking positions.

The seam — why this is paid

Paid plugin owns: audit logic, SEO recommendations, schema.org validation, search-rank tracking (via third-party API integration), bulk-fix templates, support SLA. Core owns: product metadata storage, sitemap generation, canonical URL setting.

Support commitment: SEO audit accuracy, search-rank tracking, optimization SLA

Dependencies

• core-audit-log (meta changes tracked)
• rich-text-editor (description used in SEO recommendations)

Acceptance checks

Each of these must be able to fail. Before claiming this is done, break the code deliberately and watch each one go red.

• Audit scan of 500 products complete in <1 minute; report shows 42% missing meta title, 18% missing schema
• Bulk fix applies template ‘{name} | Shop Now’ to 210 products missing meta title
• Schema validator shows ‘Valid Product schema’ or lists specific schema.org errors (e.g., missing price field)
• XML sitemap includes all 500 products, 20 categories, 45 blog posts with lastmod date
• 301 redirect: old URL /products/shoe → new URL /products/running-shoe works for storefront
• Keyword analyzer suggests ‘waterproof hiking boots’ as primary keyword for product ‘KEEN Targhee III’
• Monthly search-rank report shows ‘hiking boots’ at position 23 (up from 31 last month)

Risks

Schema validation doesn’t catch soft errors (missing price or image); valid JSON-LD but incomplete markup. Bulk-fix template applied to wrong products if filter logic inverted (applies to products THAT HAVE meta title, not missing). Redirect chain (A→B→C) not flattened causes rank decay. Search-rank tracking API rate limit breaks monthly report if too many keywords. Canonical URL misconfiguration (points to wrong domain) breaks SEO signal.

Commercial context

The anchor is what the nearest equivalent charges on Shopify or Magento today. It is context for a pricing decision, not the decision.

---

Generated from the commerce plan. See docs/COMMERCE-PLAN.md for the full catalogue and ../../AI-GUIDE.md for how to work on this repository.