A Google rankings drop is worth investigating when the same pages lose visibility for the same searches over a sustained period. If a Riyadh maintenance company sees fewer enquiries on Monday morning, it has a reason to look. It still needs to find out whether customers stopped searching, Google stopped showing an important page, or the website stopped recording enquiries. Each problem has a different fix.Start with Google Search Console. Compare complete periods, narrow the report to the part of the business that lost visibility, and test a few important URLs before changing anything. This checklist takes you from the first alert to a decision about what to fix.
1 Confirm the Google rankings drop
Open the Search Console Performance report and select Web search. Compare the most recent 28 complete days with the previous 28. If the change started abruptly, compare shorter periods that include the same weekdays and keep the longer view open for context. Leave out incomplete days. Turn on clicks, impressions, click-through rate and average position so you can see which measures moved together.Check where the complaint started. If analytics shows fewer Google organic sessions while Search Console clicks stayed steady, investigate the analytics tag, cookie consent settings and channel filters before changing pages. If search clicks held up but enquiries fell, submit a test form and check whether someone receives it. A broken form can look like an SEO problem in a sales report.Average position is an aggregate. A website can start showing for many new searches at lower positions while its established searches hold steady. The sitewide average may worsen even though no important page lost ground. Filter to a priority page and one search it used to serve. Compare that pair before calling the change a rankings loss.
2 Find which pages and customers are affected
Select Saudi Arabia in the country filter if that is the market that matters. Search Console's standard country filter does not isolate Riyadh or Jeddah, so use city words in queries and actual city pages to investigate location-specific changes. A customer in Riyadh may search without typing the city, so a query filter is only a partial view of local demand.Use the Pages tab to find where the biggest losses occurred. Start with a service, category or product page that matters to the business. Click into the page and review Queries. Repeat the comparison for mobile and desktop if one device appears to account for most of the change. A problem that affects only Arabic category pages is a useful lead because the pages may share a template, language switcher or release date.Take a few notes before opening another report. Record the dates, URL, sample queries and change in clicks, impressions and position. Add an unaffected page of the same type as a comparison. If all mobile pages lost visibility but their desktop figures look steady, that comparison gives your developer a narrower problem to reproduce.
3 Read the pattern before choosing a fix
A traffic graph can tell you where to look. It rarely proves a cause by itself. Use the table to choose your first check, then use a specific page and query to confirm the pattern. Google's guide to debugging traffic drops explains how to investigate several of these signals.
A date alone can send you in the wrong direction. Suppose a Saudi dates shop loses impressions after a seasonal buying period. Its gift box page still appears at similar positions for its usual searches. A Saudi Arabia comparison in Google Trends, together with the shop's own prior sales and search history, can help test whether interest fell. If the buying period follows the Islamic calendar, compare equivalent weeks around the event instead of assuming the same Gregorian dates are comparable.
4 Check indexing and recent website changes
For a URL that lost most of its impressions, open URL Inspection. Record whether the indexed version is on Google, the last crawl date and the Google-selected canonical if one is shown. Use the live test to check the current page separately. The indexed record can reflect an older crawl, and a successful live test tells you about accessibility at test time. It does not show that the page has already been reindexed.Open the public URL while signed out and see what a customer gets. Look for an error, an unexpected redirect, a noindex directive or a canonical pointing to a different page. If an Arabic category was replaced by an English category in the canonical tag during a template update, check whether that was intentional. When both language pages are meant to be indexed separately, each should normally use the appropriate canonical for its own version.After a redesign, test old URLs that used to earn search clicks. A discontinued URL with a close replacement can redirect to that replacement. An old Riyadh installation page should go to the current Riyadh installation page when the offer is equivalent. Sending it to a generic homepage leaves the visitor without the answer they clicked for. Use the technical SEO checklist for Saudi websites to check the related sitemap and internal links.
5 Compare the page with what searchers see now
If the URL is indexed and loads normally, look at the results for its main searches. Use a relevant location and device where possible, and treat a manual search as a snapshot. Search Console shows what happened across recorded impressions; the results on your own phone can differ.Check what the results are trying to help people do. A page about the cost of commercial cleaning may have lost ground because the results now feature pages that let facilities managers compare service scopes and ask for quotes. Read your page alongside the alternatives. Does it explain which sites you serve, what the price depends on, and how a customer can get a useful estimate? Add details your business can confirm. The on-page SEO checklist can help you check whether the title, headings and main content describe the same offer.Also look for a second page on your own site gaining impressions for those queries. If the older page and the new one answer the same question in the same language, decide which should be the main destination. Make internal links point consistently to it, and only merge or redirect if it makes sense for readers. A guide about cleaning costs and a service page for booking a site visit may both deserve to stay.Check what the results are trying to help people do. A page about the cost of commercial cleaning may have lost ground because the results now feature pages that let facilities managers compare service scopes and ask for quotes.Read your page alongside the alternatives. Does it explain which sites you serve, what the price depends on, and how a customer can get a useful estimate? Add details your business can confirm. The on-page SEO checklist can help you check whether the title, headings and main content describe the same offer.
6 Check whether a Google update fits the evidence
Use the Google Search Status Dashboard to see whether a reported ranking update or search incident overlaps with the decline. For a core update, review the comparison after the rollout finishes and allow time for the reporting window to settle. Check the release log too. If the affected URLs share a template changed on the same day, the website change still deserves investigation.A small shift on a few terms is often a reason to watch, especially when clicks and useful enquiries have barely changed. A large, lasting drop across important pages calls for a closer review. Look for weak answers, old service details, difficult navigation or repeated pages that give readers no useful reason to choose one over another. Review the pages that lost the most useful traffic before commissioning a rewrite of the whole site.
7 Fix the clearest issue and track recovery
Put the strongest finding first. If priority pages return errors after a deployment, give the developer sample URLs and the date the problem began. If one category lost clicks while its impressions and position stayed close to normal, review the visible title and snippet before asking for technical changes. If demand fell, record it in the report and adjust the next comparison window.For example, imagine a Jeddah refrigeration supplier finds a sharp loss on six Arabic service pages. Their English equivalents are steady. URL Inspection shows an old indexed record, and a live check of two affected URLs finds a noindex directive added during a template update. Remove the directive from pages that should be public, verify the live pages and test other URLs that use the same template. Log the release date and check later whether those pages are being crawled and receiving impressions again.Keep the next review simple. Record what changed, who did it and what signal should move first. For a technical fix, access and crawl checks come before traffic. For an editorial fix, compare the same page and priority searches after enough impressions have accumulated. Where search clicks recover, confirm whether enquiries recover too. That last check tells you whether the fix helped the business as well as the chart.For example, imagine a Jeddah refrigeration supplier finds a sharp loss on six Arabic service pages. Their English equivalents are steady. URL Inspection shows an old indexed record, and a live check of two affected URLs finds a noindex directive added during a template update.Remove the directive from pages that should be public, verify the live pages and test other URLs that use the same template. Log the release date and check later whether those pages are being crawled and receiving impressions again.