Ranking in Saudi Arabia is not generic SEO translated to Arabic. It is Saudi dialect keyword research, correct hreflang for ar-SA, English-stable slugs, Arabic fonts that do not kill LCP, and FAQ schema that wins rich results.
This is the full checklist we use for Next.js sites that rank in Riyadh, Jeddah, and Dammam.
1. Keyword research in Saudi dialect
Tools show MSA volume but users search dialect. For mobile, Saudis search جوال and جوالات far more than هاتف محمول. For invoicing they search فاتورة الكترونية and فاتورة زاتكا rather than فوترة. Build your map from Google Suggest in Saudi location, Search Console queries filtered to Saudi, and 200 real sales calls and WhatsApp messages.
Structure is one intent per page. Do not mix buy, price, and guide intents. For example separate pages for سعر نظام فواتير, شرح فاتورة المرحلة الثانية, and افضل برنامج فواتير للمنشآت. Each needs distinct title, H1, and FAQ.
Titles in Arabic should be 50 to 60 characters, front-load the main term, mention SAR or city where relevant, and avoid English words inside Arabic titles. We fixed two titles with English beyond inside Arabic and saw CTR recover immediately.
2. Slugs, URLs, and site structure
Keep slugs in English like /articles/quantum-safe-migration-checklist. Arabic slugs cause encoding issues in WhatsApp shares, analytics splits, and backlink errors. Put Arabic in H1, title tag, and meta description. URL stays clean and stable when you reword the Arabic title later.
Structure is /ar/ for Arabic and /en/ for English with self-canonicals. Do not mix locales in one directory. Sitemaps split at /ar/sitemap.xml and /en/sitemap.xml submitted separately in Search Console with country targeting left unset but hreflang doing the work.
Hreflang on every page must list ar-SA, en-US, and x-default pointing to the correct absolute URLs. Validate with Search Console international targeting report. A single wrong hreflang can deindex the Arabic version.
3. On-page in Arabic that converts
H1 one per page in natural Saudi Arabic. First 100 words must contain the main term plus SAR price signal or city signal. Use H2s as questions users ask on sales calls. Answer each in 40 to 60 words for featured snippet capture.
Meta descriptions 150 to 160 characters in Arabic with verb plus benefit plus trust signal. Example pattern is احصل على نظام فواتير متوافق مع زاتكا مع دعم مدى وتدريب عربي. No keyword stuffing.
Images need Arabic alt, AVIF format, explicit dimensions, and lazy loading below the fold. Files in /blog/ with Arabic alt outperform generic stock names.
Internal links should use Arabic anchor text to related Saudi guides, not click here. Link new articles from three existing high-traffic Arabic pages to get them crawled in days not weeks.
4. Technical SEO for Next.js
Render critical content server-side. Do not hide H1 behind client tabs. Use ISR with 1-hour revalidate for articles, stale-while-revalidate for listings, and webhook purge on publish by lang plus slug.
Core Web Vitals in Saudi 4G is the real test. Subset Arabic fonts to Arabic plus Latin, self-host, font-display swap, preconnect. Defer third-party chat and analytics. Keep LCP under 2.5s, CLS under 0.1, INP under 200ms on Moto G class devices.
Schema must be in page language. Article schema with Arabic headline, FAQPage with Arabic questions from sales calls, LocalBusiness with Dammam address, SAR prices, and Arabic reviews. Test with Rich Results Test set to Arabic.
5. Content velocity that ranks
Publish two Arabic guides weekly for 12 weeks minimum. Each 900 plus words with custom screenshots from Saudi dashboards, SAR pricing tables, and FAQ of five questions. Update top 10 pages monthly with new prices, wave dates, and screenshots. Freshness wins in fintech and compliance niches.
Measure rankings by ar-SA queries, CTR by title, and leads by WhatsApp clicks, not just traffic. One Fatoora guide that ranks third but drives 30 qualified demos beats ten generic AI articles with traffic and zero pipeline.
Bottom line is treat Arabic SEO as its own product with dialect research, English slugs, fast RTL pages, and schema in Arabic. Do that consistently and you own Saudi intent while competitors auto-translate.
