Use Meshkee {id}/{fa-slug} detail URLs for products and blogs.

Resolve pages via by-id APIs, slugify Farsi titles for public paths, and redirect legacy slug-only URLs to the canonical form.

Co-authored-by: Cursor <cursoragent@cursor.com>

Ai-data/prompt-seo.txt

@@ -2,11 +2,15 @@
 - Do NOT ship public/sitemap.xml or public/robots.txt (nginx proxies both to Meshkee API).
 - Publish GET /meshkee/sitemap-config.json generated at build time from app routes.
 - Include public static routes automatically; exclude auth/checkout/cart/admin paths.
-- Omit templates unless this site uses non-default detail URLs.
+- Canonical detail URLs (Meshkee defaults — omit templates unless customized):
+  - Product: /products/{id}/{nameFaSlug} → GET /tenants/{domain}/products/by-id/{id}
+  - Blog: /blog/{id}/{titleSlug} → GET /tenants/{domain}/blogs/by-id/{id}
+  - Portfolio: /portfolios/{id}/{titleFaSlug} → GET /tenants/{domain}/portfolios/by-id/{id}
+- Slugify: Farsi letters kept, spaces → -, strip other punctuation. Do not use legacy DB slug in public URLs.
 - After deploy: business dashboard → Website → Settings → Sync sitemap config (optional for CMS URLs; needed for static pages).
 
 ### On-page SEO (every public page)
 - Unique <title> and meta description on every crawlable page
 - Exactly one H1; H2/H3 for real sections
 - All content images must have meaningful alt (CMS title when available)
-- Prefer CMS fields for titles/descriptions; never leave Next defaults
+- Prefer CMS fields for titles/descriptions; never leave Next defaults