TL;DR Summary
Find declining SaaS pages in Google Search Console, diagnose what changed, and decide which pages deserve a refresh using a simple worksheet.
A SaaS comparison page loses 160 Google clicks in a month. Before I assign a rewrite, I open the page’s Queries report. If the clicks came from buyers comparing two tools, the page may deserve a refresh this week. If they came from an unrelated definition the page briefly ranked for, I have a different problem.
Content decay is a gradual drop in a page’s organic performance. An outdated example or a change in what buyers are looking for can contribute to it. A broken canonical, weaker demand, or a change in how Google displays results can produce a similar chart. Treat the drop as a list of pages to investigate.
Start with the pages that lost the most clicks
Open Performance → Search results in Google Search Console. Compare the latest 28 complete days with the previous 28 as a starting point. If your market has seasonal patterns, compare the same period last year as well. Keep the search type consistent. If a page targets a specific country or device, inspect that segment on its own.
Export the Pages table. Start with absolute click loss. A URL that fell from 400 clicks to 240 needs a closer look than one that fell from 20 to 5, even though the second page lost a larger share of its traffic. Open the page filter for each candidate and switch to Queries. Check which query group moved and whether those searches still match the page’s purpose. Google explains how to read clicks, impressions, CTR, and position when comparing the two periods.
- Clicks and impressions fell for the same query group. Compare search interest and check whether the page still appears for those queries. Review its indexing if visibility dropped abruptly.
- Impressions and position look similar, but clicks fell. Check the individual queries and devices behind the average. Look at the live results, including the title Google displays and any new result features.
- Visibility fell and positions worsened for the core query group. Inspect what now ranks. Look for a shift in format or intent, such as comparison pages replacing broad guides.
- Several unrelated pages fell at once. Check the deployment timeline, indexing, and sitewide changes before opening multiple content briefs.
Google’s search traffic drop guide covers indexing problems, ranking changes, and seasonality. If a release coincides with a wider drop, use the Maroon Pixel SEO checklist to work through canonicals, redirects, and crawlability.
Put a business decision next to each URL
I’d keep one row per page: URL, lost clicks, affected query group, current buyer intent, suspected cause, action, and review date. If signup tracking is reliable, add the number of organic landing sessions that produced a signup. Keep that metric at the page level. Search Console reports search performance and GA4 measures site behavior, so you cannot assign a GA4 signup to a specific Search Console query from these reports.
Say a comparison page loses 160 monthly clicks and an introductory glossary page loses 400. If the comparison page brings qualified trial starts and people still search for that comparison, refresh it first. If the comparison query now favors a different use case, revisit the brief before rewriting the introduction. The SaaS SEO strategy explains how to group pages by buyer intent. For a page that has to help buyers choose between two products, start with the comparison page structure.
Fill one worksheet row before opening a brief
Here’s a worked example with sample data. The clicks are for the entire page. The query group is the slice of the loss I would investigate first.
- Page and period. Product comparison page, latest 28 complete days versus the preceding 28.
- Change. 400 to 240 clicks, down 160 or 40%.
- Query group. The two product names plus words such as “vs,” “pricing,” and “alternative.”
Growth mechanics, zero fluff.
Join SaaS founders and operators getting weekly notes and tear-downs on organic acquisition and churn reduction.
- What the results now answer. In this example, several current results explain which plan includes the reporting feature.
- What our page lacks. The plan table lists the feature but leaves buyers to check who can use it.
- First change. Verify the current plan restrictions and replace the generic feature row with the buyer’s reporting workflow.
- What to check afterward. Visibility for the same queries and whether visits to the page still lead to qualified trials.
If two URLs appear for the same priority query, filter the query and open the Pages tab. Check which URL gets the impressions in each period. Read both pages and decide which one better answers the query before changing links or merging pages. A switching URL is a lead to investigate. It can also reflect changes in the mix of searches.
Fix the thing you can point to
If the table has stale plan details, recheck the vendor pages and update the table. If searchers now want a migration checklist, add the steps and constraints they would need to act. If the page is indexing the wrong URL, work with engineering on the canonical or redirect first. Change the URL only when the underlying site structure calls for it.
Record the change and its date. Review the same page, query group, country, and device after a few weeks, allowing for recrawl and enough data. Track whether those clicks come back and whether the page sends visitors to the next step. If clicks recover while qualified actions stay flat, check whether the traffic is returning for the queries the page was written to serve.





