When organic traffic falls, identify which visitors disappeared and whether the business lost useful inquiries before commissioning a rewrite. A reporting change, seasonal slowdown, broken page, and weaker search visibility need different responses. A clear diagnosis protects your budget and the pages that still work.
Reconstructed archive: April 2024. Written in November 2026 using contemporary historical sources. The archive date organizes this series; this text is not a recovered original.
The April 2024 documentation update
Google’s April 26, 2024 documentation changelog recorded expanded guidance on diagnosing traffic drops, including algorithmic changes and spam issues. This was an explanatory documentation update, not an announcement that every site experienced a new ranking event that day.
Current practical expansion: The following checklist was added in November 2026 and uses current documentation. It is not presented as advice originally published in April 2024.
Write down the decline you are actually investigating
“Traffic is down” is too broad to become a useful work order. Record the affected website, report, date range, comparison period, and business consequence. Specify whether the number represents Google Search clicks, analytics sessions from organic search, all website visits, or inquiries. Those measures describe different parts of the customer journey.
Use a short incident statement: “Google Search clicks to our installation pages declined over the last four complete weeks compared with the previous four. Qualified installation inquiries also fell. Maintenance pages appear stable.” That is a hypothetical example, not a Guardian client result. It creates a testable scope without claiming a cause.
Preserve the original report and filters. Keep incomplete recent days out of the initial comparison, check comparable weekdays, and add a year-over-year view where the business is seasonal and suitable history exists. A holiday week compared with an ordinary week can create an alarming but misleading picture.
Separate a measurement problem from a search problem
Compare independent evidence rather than expecting every platform to match. Search Console describes activity in Google Search. Website analytics measures what its implementation can observe on the site. Your inquiry log records another step, and may have its own gaps.
Google’s Performance report documentation explains clicks, impressions, click-through rate, average position, and the available dimensions. Review the same page group and dates, then split by device and country if the totals hide different patterns. Preserve the search-type filter. A property-wide average can conceal a problem affecting only one service.
- Analytics falls while Search Console stays broadly steady: investigate collection, consent behavior, channel definitions, and recent analytics changes before treating the decline as lost rankings.
- Search clicks and inquiries both fall: investigate which landing pages and services changed, while still checking that contact routes work.
- Visits fall while qualified inquiries hold: determine whether the lost traffic had commercial value before making recovery your highest priority.
- Inquiries fall without a similar traffic decline: test forms, phone links, availability, and the offer. Traffic recovery may not be the immediate job.
These are investigation paths, not automatic diagnoses. Two systems moving together strengthens a question worth asking; it does not establish why the change happened.
Find the pages and searches behind the total
Build a short list of the pages responsible for the largest absolute decline. A page losing two visits from a starting point of four has a dramatic percentage change, but may matter less than a core service page losing a substantial source of qualified demand. Record both the absolute difference and percentage when the starting volume supports a meaningful comparison.
Separate branded searches, service searches, and informational topics where the data allows. Then ask whether the decline affects a few former high-volume articles, an entire service section, or the whole website. Keep missing or unavailable query information visible rather than pretending the exported rows describe every visitor.
For each important page, capture its current purpose, whether the service is still offered, recent edits, and the next action a customer can take. This connects a technical investigation to the work the business wants to win.
Check recent changes and technical failures before rewriting
Request a dated change log from whoever manages the website. Look for deployment dates, hosting changes, security rules, URL edits, deleted pages, navigation changes, and analytics releases. “Nothing changed” should mean the relevant people checked, rather than nobody remembers.
Have the appropriate specialist inspect affected URLs for availability, unintended redirects, indexing restrictions, canonical selection, and internal links. Test representative pages, including a page that did not decline, so a sitewide assumption can be challenged. A working home page does not establish that every service URL works.
If a page was intentionally retired, decide whether it has a genuinely relevant replacement. Avoid redirecting every missing URL to the home page. If a release introduced an obvious technical defect, fix that defect and verify the result before launching a wholesale content project.
Google’s traffic-drop guidance identifies several possible causes, including technical issues, demand changes, ranking changes, and reporting anomalies. It also cautions against radical changes for small ranking fluctuations. An update occurring near the decline is context to investigate, not proof that it caused your loss.
Distinguish demand, visibility, and click choice
After ruling out urgent breakages, ask three separate questions. Are fewer people looking for this service? Is the site appearing less often or in less useful positions for comparable searches? Are people choosing other results even when the site appears?
Use relevant market context and comparable search groups rather than one overall average. Changes in the mix of searches can move averages without every individual page getting worse. A seasonal service, a discontinued offering, and an article that briefly attracted attention should not be assessed against identical expectations.
Inspect current results for a small set of important searches and record the date, location context, device, and result type. Treat this as a sample. Ask whether the page still answers the customer’s task, whether its title accurately describes the offer, and whether competing results expose a genuine information gap. Do not assume a longer article is automatically a better answer.
Ask for a diagnosis with decisions, not a list of possible causes
A useful engagement should produce a written handover you can act on. Request:
- Scope: the affected services, pages, periods, and business outcomes.
- Evidence: saved comparisons and tests, with the report settings included.
- Findings: confirmed defects separated from plausible explanations and unresolved questions.
- Priorities: what needs immediate repair, what needs more evidence, and what should remain unchanged.
- Ownership: who implements each fix and who checks it afterward.
- Review plan: the measurements and timing used to assess the next stage, without a guaranteed recovery date.
For a hypothetical installation-page decline, the recommendation might be to repair an unintended redirect first, verify the destination, and observe the affected page group before changing copy. Another investigation might find no defect and recommend improving outdated service information. The deliverable should explain why the selected response fits the evidence.
Decide whether you need a repair project or ongoing SEO
A single confirmed fault can justify a bounded repair. Repeated content gaps, unresolved technical work, and weak reporting ownership may justify an ongoing program. Ask how the proposed SEO work will convert the diagnosis into completed changes and reviewable decisions.
Our local SEO proposal checklist can help you compare scope and responsibilities. Avoid buying a fixed quantity of new articles simply because the traffic line moved down.
Contact Guardian Solutions to discuss the decline, the pages affected, and the evidence available. Bring the dates and change history so the conversation can start with the problem rather than a guessed solution.
Historical source retained from the reconstructed archive: Google documentation changelog, April 26, 2024 entry.