You publish an Arabic article, share it, and then wait for it to appear in Google. Most of the anxiety in that wait comes from not knowing what happens in between, so this guide walks through the three stages Google itself describes: crawling, indexing and serving, and shows you where to watch each one for your own site.
The problem: guessing instead of checking
When a new page does not show up in search, people tend to reach for random fixes: rewriting the title, buying a “fast indexing” service, or resubmitting the same URL every day. Almost all of that guessing disappears once you know which stage the page is stuck in. A page that Google never found needs a different fix from a page that Google found and chose not to index.
Two ground rules from Google’s documentation set expectations before we start. First, Google says it does not accept payment to crawl a site more often or to rank it higher. Second, Google does not guarantee that it will crawl, index or serve any page, even one that follows Google Search Essentials. What caught my attention when I first read that page is how plainly it says this. Anyone promising guaranteed indexing is promising something Google does not.
The three stages, explained
Crawling. Google discovers URLs mainly by following links from pages it already knows and by reading sitemaps. Its crawler, Googlebot, then decides what to fetch. In Google’s words, “Googlebot uses an algorithmic process to determine which sites to crawl, how often, and how many pages to fetch from each site.” There is no fixed schedule you can count on, and a new site should expect this to take its own time.
Rendering. During the crawl, Google renders the page and runs the JavaScript it finds using a recent version of Chrome. For Arabic sites built on modern themes or JavaScript frameworks, this matters: if your article text only appears after a reader taps a tab or a “read more” button, Googlebot may never see it. Primary content should load without any user action.
Indexing. Google analyses the page and stores it. Part of this step is duplicate handling: Google groups pages with similar content and picks the one it considers most representative as the canonical. If your Arabic and English pages are near copies, or the same article lives at several URLs, Google will choose among them. Google also states clearly that indexing is not guaranteed, and that not every page it processes will be indexed.
Serving. When someone searches, Google returns the results it considers most relevant. Google describes relevancy as being determined by hundreds of factors, which could include the user’s location, language and device. For an Arabic site, that means the same page can appear differently for a reader in Rabat searching in Arabic and a reader in London searching in English.
Step by step: watch each stage for your site
- Verify your site in Google Search Console. Google’s getting started page for Search Console is the right entry point. Without it you are working blind.
- Submit your sitemap. Most CMS platforms generate one. Submitting it helps discovery, though it does not force indexing.
- Inspect a single URL. Use the URL Inspection tool on a new article. It tells you whether Google knows the URL, when it last crawled it, and whether it is indexed.
- View the rendered page. Inside URL Inspection, check the tested page to confirm your Arabic body text is actually present in what Google rendered.
- Read the Page indexing report. It groups URLs by status. Some “not indexed” reasons are normal, such as duplicates Google folded into a canonical.
- Check serving in the Performance report. Once pages are indexed, look at queries, countries and devices to see how and where they appear.
A bilingual example
Imagine a small Amman bakery with a site at example.com/ar/ and example.com/en/. The Arabic menu page and the English menu page carry the same prices and photos but real translated text. That is fine: they are different languages, not duplicates. The problem appears when the English page is only the Arabic page with a translated header, leaving the body in Arabic. Google may then treat the two as near duplicates and pick one. The fix is editorial: translate the full content or keep a single version, and make that choice deliberately rather than letting templates decide.
Checklist for a newly launched Arabic site
| Check | How | Tool |
|---|---|---|
| Site is verified | Add a property and complete verification | Google Search Console |
| Sitemap is known to Google | Submit the sitemap URL | Search Console Sitemaps report |
| New pages are discoverable | Link every new article from a category or home page | Your CMS menus and internal links |
| Arabic text renders | Compare rendered HTML with the live page | URL Inspection |
| Indexing status is clear | Review reasons listed for excluded URLs | Page indexing report |
| Duplicates are intentional | Decide which version of overlapping pages is primary | Page indexing report and your CMS |
| Pages are being served | Filter by query, country and device | Performance report |
Common mistakes
- Assuming every published page gets indexed. Google says indexing is not guaranteed. Check the status instead of assuming.
- Hiding Arabic content behind clicks or scripts. Tabs, accordions and “load more” buttons that fetch text only on interaction can keep your main content out of what Google processes.
- Paying for faster crawling or better ranking. Google states it does not accept payment for either. A service that claims otherwise is selling something Google does not offer.
- Publishing near identical Arabic and English pages without a decision. If two pages overlap heavily, decide which one is primary where that makes sense, or make them genuinely distinct.
In my view, the most useful habit here is the least exciting one: open URL Inspection on every important new page for the first few weeks. It replaces guessing with a clear answer about which stage you are in.
Sources
- Google Search Central, in-depth guide to how Google Search works, documentation page consulted 23 September 2025, https://developers.google.com/search/docs/fundamentals/how-search-works
- Google Search Central, Google Search Essentials, documentation page consulted 23 September 2025, https://developers.google.com/search/docs/essentials
- Google Search Central, getting started with Search Console, documentation page consulted 23 September 2025, https://developers.google.com/search/docs/monitor-debug/search-console-start