WordPress makes it easy to launch an Arabic site in an afternoon, and just as easy to launch one with duplicate URLs, two competing sitemaps and a staging copy sitting in Google’s index. None of this needs a developer to fix, but it does need one pass through the settings that control crawling, indexing and speed. This is the pass I would run on any Arabic WordPress site, with Google’s documentation as the reference.
Why an Arabic WordPress site needs a technical pass
The problems are rarely dramatic. They build up quietly: a theme adds its own canonical tags, an SEO plugin adds another; a multilingual plugin creates /ar/ and /en/ versions but the language switcher points at the wrong pages; a heavy page builder loads four Arabic font weights before the text appears.
Two points from Google set the tone. First, you probably already have a sitemap: “If you’re using a CMS such as WordPress, Wix, or Blogger, it’s likely that your CMS has already made a sitemap available to search engines.” Second, Google points WordPress owners to one specific tool: “If your site is on WordPress, you can view both Google Analytics and Search Console data in a single dashboard within WordPress.” That tool is Site Kit, which describes itself as “Google’s official WordPress plugin”. Useful for monitoring, but don’t expect it to change your rankings; its job is showing you data.
The setup, step by step
- Set the site language and theme. Choose Arabic as the site language and use a theme with proper RTL support, so text direction, menus and breadcrumbs flow correctly.
- Choose permalinks once. Pick a readable structure before you publish much. Changing it later means redirects for every old URL.
- Keep one sitemap source. Check whether WordPress core or your SEO plugin produces the sitemap, disable the other, and submit the remaining one in Search Console.
- Decide on thin archives. Tag pages, author archives and date archives often add little. Whether to noindex them is your editorial call, not a Google rule. If you do, use noindex, because robots.txt does not do that job. Google says: “To keep a web page out of Google, block indexing with noindex or password-protect the page.”
- Check canonicals. Google describes rel=”canonical” as “A strong signal that the specified URL should become canonical.” Make sure exactly one plugin outputs it, that it uses absolute URLs, and that you are not trying to canonicalize with robots.txt, which Google advises against.
- Verify hreflang from your multilingual plugin. Open an Arabic post and its English sibling. Each should list itself and the other version, and the links must point both ways.
- Trim performance weight. Load one Arabic font family in the weights you actually use, compress images, and turn on caching.
- Never lazy-load the first screen. A web.dev analysis of 2022 data found “84% of sites that use browser-level image lazy loading use WordPress”, and it advises to “avoid lazy loading above-the-fold elements”. Your featured image at the top of a post should load right away.
- Connect Site Kit to see Search Console and Analytics data in the dashboard.
- Password-protect staging. A staging copy blocked only by robots.txt can still end up in results. Put it behind a password.
Example: the canonical on an Arabic post
Here is what the canonical tag should look like in the head of an Arabic post. It uses an absolute path, as Google recommends (“Use absolute paths rather than relative paths with the rel=”canonical” link element.”), and the Arabic slug is percent-encoded:
<link rel="canonical" href="https://example.com/ar/%D9%88%D9%88%D8%B1%D8%AF%D8%A8%D8%B1%D9%8A%D8%B3-%D8%AA%D9%82%D9%86%D9%8A/">
What caught my attention in audits is how often an Arabic post ends up with the raw Arabic URL in one tag and the encoded version in another, or with comment and pagination variants each declaring themselves canonical. View the page source, search for “canonical”, and count. The answer should be one.
On a bilingual setup, the English sibling at /en/ has its own canonical pointing to itself. Hreflang links connect the two versions; the canonical does not.
Technical checklist
| Check | How | Tool |
|---|---|---|
| Site is visible to search engines | Confirm the “Discourage search engines” option is unchecked | WordPress Settings, Reading |
| One sitemap only | Open the sitemap URLs from core and plugin; keep one | Browser and Search Console Sitemaps report |
| One canonical per page | View source and search for “canonical” | Browser view source |
| Canonicals are absolute | Read the href value | Browser view source |
| Hreflang is reciprocal | Compare tags on the Arabic and English versions | Browser view source |
| First-screen image not lazy | Check the featured image for a lazy loading attribute | Browser developer tools |
| Staging is private | Open the staging URL in a private window | Browser |
| Indexing status of key pages | Inspect each important URL | URL Inspection in Search Console |
| Data in the dashboard | Confirm Search Console and Analytics are connected | Site Kit |
Common mistakes
- “Discourage search engines” left on after launch. It is easy to miss in a rushed launch. Check it on day one.
- Two plugins generating competing sitemaps or canonicals. Theme, SEO plugin and multilingual plugin can all try to do the same job. Pick one owner for each function.
- Public staging copies indexed. robots.txt is not a lock. Use a password.
- Heavy page builders and many font weights. They slow loading and responsiveness, and phones feel it first. Measure after every theme change.
- Changing the permalink structure without redirects. Every old link, share and bookmark breaks. If you must change it, redirect each old URL to its new one.
In my view, the best technical SEO plugin for a WordPress site is the one you configured deliberately. No plugin is required by Google, and none can replace a clear decision about what each part of the site should do.
Sources
- Google Search Central, build and submit a sitemap, documentation page consulted 21 July 2026, https://developers.google.com/search/docs/crawling-indexing/sitemaps/build-sitemap
- Google Search Central, how to specify a canonical URL, documentation page consulted 21 July 2026, https://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls
- Google Search Central, robots.txt introduction and guide, documentation page consulted 21 July 2026, https://developers.google.com/search/docs/crawling-indexing/robots/intro
- Google Search Central, tell Google about localized versions of your page, documentation page consulted 21 July 2026, https://developers.google.com/search/docs/specialty/international/localized-versions
- Google Search Central, using Google Analytics and Search Console together, documentation page consulted 21 July 2026, https://developers.google.com/search/docs/monitor-debug/google-analytics-search-console
- Site Kit by Google, official WordPress plugin page, consulted 21 July 2026, https://sitekit.withgoogle.com/
- web.dev, article on lazy loading and Largest Contentful Paint (2022 data), consulted 21 July 2026, https://web.dev/articles/lcp-lazy-loading