Ranking changes
Did important queries, pages or page ownership change in a way that explains the traffic movement? If ranking loss is confirmed, investigate the Google Ranking Drop.
Interweb Media · Organic traffic investigation
SEO traffic dropped. Find out what changed.
Organic traffic decline is a symptom, not a diagnosis. Interweb investigates the evidence to establish what changed before remediation begins.
No promise of recovery. A clearer account of what was lost, where it concentrated and what should happen next.
Symptom → investigation
ObservedOrganic traffic changed
QuestionWhat changed?
FocusWhere is the loss?
DecisionWhat next?
Traffic loss is a symptom
A decline tells you that something changed. It does not tell you what.
Organic search traffic can fall for different reasons, and more than one condition can overlap. The first task is to establish whether the change is real, when it began, which search surfaces moved and which parts of the website were affected.
Interweb does not begin by assuming a technical issue, an algorithm update, a content problem or a penalty. It begins by narrowing the evidence.
First questions
What was lost?Clicks, impressions, pages, queries or a particular search journey?
When did it move?One day, a release window, a seasonal shift or a gradual change?
Where is it concentrated?Templates, directories, markets, devices, queries or landing pages?
What else changed?The site, search results, competitors, demand or measurement?
Diagnostic directions
The evidence determines which direction matters.
These are possible lines of investigation, not a checklist that every traffic decline must pass through. The work follows the shape of the loss.
Indexation and technical evidence
Is there evidence of changed access, indexation, redirects, canonicals, rendering or other technical constraints?
Website changes
Did a release, redesign, template change, content edit or structural decision alter the search journey? If the change was a redesign, investigate what changed after the redesign. If it was a migration, see the SEO Migration Audit.
Search demand
Did the audience, season, market or query demand shift independently of the website?
Search result behaviour
Did result features, intent, devices or the competitive shape of the search page change?
Competitor movement
Did competing pages or businesses change the context in which the affected pages are evaluated?
Measurement
Is the reported decline consistent across analytics, Search Console and the underlying collection setup?
Timeline reconstruction
- BEFOREBaselineWhat was normal for the affected pages and search journeys?
- CHANGEFirst movementWhen did the signal depart from its prior pattern?
- CONTEXTConcurrent eventsWhat changed in the site, market, result page or measurement?
- NOWCurrent conditionWhat remains affected and what evidence is still stable?
Build the timeline
The date of the decline is evidence, not an explanation.
A useful investigation reconstructs the period before and after the change. It compares the first movement with releases, content changes, search demand, ranking signals, competitor movement and measurement conditions.
The aim is to reduce coincidence and identify the sequence that deserves closer testing.
Find where the loss is concentrated
The shape of the decline often narrows the investigation.
Compare affected and unaffected pages, query groups, templates, directories, markets, devices and search surfaces. A site-wide impression is not the same as a site-wide cause.
Grouping the loss makes it possible to test a specific explanation rather than react to an aggregate number.
Evidence into diagnosis
The investigation explains the loss before it recommends the repair.
Once the affected area and timeline are clear, the evidence can be tested against the most plausible causes. Some investigations point toward technical constraints. Others point toward demand, search result behaviour, site changes, competitors or measurement.
If the evidence becomes specifically technical, the next step may be a Technical SEO Audit. A traffic drop does not automatically require one.
Forensic deliverable
Leave with a clearer account of what happened.
The output is a working decision record, not a recovery promise. It explains the evidence, the strongest diagnosis available, the uncertainty that remains and what should happen next.
Loss definition
What changed, measured against the right baseline and search surface.
Affected area
Which pages, queries, templates, markets or devices carry the signal.
Diagnosis
What the evidence supports, what it rules out and where confidence is limited.
Next decision
The most useful next action and the evidence required to verify it.
Remediation follows diagnosis
Do not repair the wrong explanation.
Traffic loss creates pressure to act quickly. The wrong action can add noise, introduce risk or consume time without addressing the condition that changed. Diagnosis creates the basis for choosing whether the next step is technical repair, content or structural work, measurement correction, further investigation or no immediate website change.
See how investigation connects to implementation and verification →
Decision sequence
01UnderstandDefine the loss and reconstruct the timeline.
02TestCompare the strongest explanations against the evidence.
03ChooseSelect the next action that matches the diagnosis.
04VerifyRecheck the signal after a change is made.
Evidence infrastructure
The Interweb platform keeps the investigation connected.
Search performance, ranking context, crawl evidence, affected page groups and implementation history can stay connected to the question that started the investigation.
Start with the evidence
Investigate my traffic drop.
Begin with the website and the change you have observed. The public diagnostic journey is the starting point for establishing what happened and what should happen next.