A useful SEO strategy starts with a question: what prevents the right customer from finding and using this page? For a Saudi business with Arabic and English pages, the answer may differ by language. One service page may be indexed but receive few relevant impressions; its Arabic twin may never have been crawled. Publishing more articles addresses neither problem automatically.
This guide gives a working sequence for choosing the next improvement. It is a planning framework, not a promise of rankings or a fixed timetable.
1. Choose the pages that support a customer decision
Start with your main services, useful buying guides and enquiry routes. Write down the audience, question and intended next action for each page. A branding service page should help a buyer understand deliverables and scope; a guide should help them make a decision before contacting anyone. Keep these jobs distinct.
Create a small working sheet with: URL, language, purpose, indexing state, relevant queries, impressions, clicks, enquiries, observed problem, proposed change, owner and verification date. Mark missing data as unknown. A zero in an analytics dashboard can also mean tracking was never configured.
2. Separate discovery from indexing
Google’s technical requirements include accessible crawling, a successful HTTP response and indexable content. Meeting them makes a page eligible; it does not guarantee indexing. Inspect the exact URL in Search Console rather than judging every page from the homepage.
- Unknown or discovered but not indexed: check whether important pages link to it, whether it is in the sitemap, and whether Google can fetch it. Do not infer a content-quality diagnosis from an uncrawled page alone.
- Crawled but not indexed: check the fetched content, canonical and duplicate versions. Review whether the page adds something useful beyond pages already covering the subject. The status itself does not explain every possible cause.
- Indexed: move to query relevance, clicks and the visitor’s next action instead of repeatedly submitting the URL.
The Page indexing report explains these states. Keep the inspection date and last crawl date with your notes: Google’s stored result can predate a live fix.
3. Make both language journeys usable
Link to relevant pages with descriptive text and actual anchor links, as covered in Google’s link guidance. A language button that only runs JavaScript should not be the sole way to discover an Arabic page.
For equivalent Arabic and English pages, use separate URLs and consistent reciprocal hreflang annotations. Each version should identify itself as well as its alternate. Then follow the Arabic journey as a reader: does the guide lead to an Arabic service, resource and contact page? Language annotations cannot repair an incomplete experience.
4. Improve the snippet where search demand is visible
For an indexed page, look at its queries before rewriting the title. If impressions come from a suitable service query, explain the offer and location plainly. If the queries are unrelated, reconsider the page’s focus rather than chasing clicks from the wrong audience.
Use a descriptive title, a direct opening answer and a meta description that accurately previews the page. Google can generate different title links and snippets. A change to your HTML is not proof that the search listing has changed.
5. Give a weak article a useful job
Google’s helpful-content guidance asks whether a page adds value and helps readers achieve their goal. Review a generic article against a specific reader task. Can the reader choose an option, complete a checklist or identify what information they still need?
For example, replace a paragraph saying “Arabic SEO matters” with a language-route checklist the site owner can actually run. Use a clearly labelled illustrative example when real evidence is unavailable. Never invent results, customer quotes or credentials. If two articles answer the same question with little difference, consider improving one stronger resource rather than expanding both.
6. Treat AI-search visibility as eligibility, not a guarantee
Google’s guidance for AI features says existing SEO practices remain relevant and no special AI markup is required. A page must be indexed and eligible for a snippet to support those features, but inclusion is not guaranteed. Write clear answers with verifiable sources; a separate AI-readable file does not replace a useful public page.
A review cycle your team can maintain
- Record a baseline for the chosen URLs and their relevant queries.
- Choose the single bottleneck supported by evidence and make one coherent improvement.
- Check the deployed page, links and language versions. Record exactly what changed.
- Use a sitemap or an appropriate recrawl request after a real update. Repeating requests does not make Google crawl faster.
- Compare equivalent reporting periods after data becomes available. Note changes in query mix and seasonality, and check qualified enquiries as well as clicks.
A hypothetical Riyadh service business might fix an inaccessible Arabic service page before rewriting its English guide. Another might already be indexed and need clearer project scope on its landing page. The same checklist produces different priorities because the evidence differs.
If you need help reviewing the site and its customer journey, see Eclipse’s digital marketing services and web development services, or discuss your current SEO bottleneck.