Find out why your search traffic dropped and fix the causes on your site
Search traffic can fall after a release that changed templates or redirects, a theme or plugin update, a migration or a Google ranking update. Pages that say too little or repeat each other can lose ground as well. Sometimes the drop exists only in the reports, because the tracking changed. We date the drop, list the pages and searches that lost visibility, and compare that period with everything that changed on the site and in search. The report states what the evidence shows and how certain each finding is, and the fixes follow once you approve them.
Norml investigates why an existing website lost search traffic and fixes the causes on the site. The work can include a dated diagnosis, a test of a known site problem against the search data, a review of thin or repeated pages, a written report, the approved fixes and a comparison with the period before the drop.
What a traffic drop diagnosis covers
The work starts with the date the drop began and the pages that lost visibility. Each check either explains part of the drop or rules a cause out, and both results go into the report.
The drop dated and confirmedSearch Console and analytics show when clicks and impressions fell, on which pages and for which searches. Tracking is checked first, because a removed tag or a changed analytics setup can look like lost traffic. Where the data goes back far enough, the same months of earlier years show whether demand is seasonal.
01
Site changes and Google updates on one timelineReleases, theme and plugin updates, migrations, redirect and URL changes, and robots or indexing settings are listed with their dates and set against the drop, together with Google's published ranking updates. Where release records are missing, archived copies of pages, crawl history and server logs help date the changes.
02
Technical checks on the pages that fellFor the affected pages we check index status, status codes, redirects, canonical tags, robots rules, internal links and what search engines receive when they render the page. Each problem is reported with the addresses it affects, so it can be checked again after the fix.
03
Thin, generic and repeated pagesPages that say little, read as filler or compete with each other for the same searches are reviewed one by one. Each gets a decision: rewritten around facts you supply, merged into a stronger page, or removed with a redirect. Pages that were started and never finished get the same decision, and the XML sitemap then lists only the pages that remain.
04
A known problem tested against the dataWhen a specific defect is already known, we establish when it was live and compare clicks, impressions, indexing and rankings for the affected pages before, during and after it. Other site changes and Google updates in the same period are weighed as alternative explanations. Where the data allows, the report estimates the clicks lost and shows how that figure was reached.
05
A written diagnosisEach finding comes with its evidence, how certain it is and the explanations that were ruled out. Fixes are listed in the order we would make them, with the pages each one affects.
06
Fixes made and checkedThe fixes you approve are made on a staging copy where the site has one, then checked on the live pages. Pages that still bring traffic keep their addresses, titles and other settings unless a fix needs to change them.
Shows our technical SEO on an older WordPress codebase: a New York co-working brand's site had accumulated a decade of changes without refactoring, and we fixed technical issues that had been suppressing its rankings for years.
Shows how we check traffic and tracking during site changes: a nutrition platform moved off Elementor onto a custom WordPress theme one part at a time, each stage monitored against the old version, and years of accumulated Tag Manager tags were reduced.
Shows our local search work for a law firm with two offices: a page for each practice area, written around how people in its region search, and local SEO set up across directories with citation building alongside the new website.
Search data from before the dropUser access to Search Console for the domain and to your analytics account, with all the history they hold. Data from before the drop matters most.
01
What changed and whenThe date you first noticed the drop and anything that changed around it: releases, redesigns, migrations, theme or plugin updates, a hosting move, new tracking, or work by another team on the site.
02
Site access and change recordsAdmin or developer access to the website, plus any history that exists: version control, release notes, hosting or server logs, backups and earlier SEO reports.
03
Someone who knows the businessA person who can confirm changes outside the website that affect demand, such as a dropped service, a price change or a busy season, and who approves the fixes.
04
How a traffic drop diagnosis runs
[Collect access and history]
Access to the search data, the site and its change records is set up first, along with the dates you already know.
Step 01
[Find the cause]
We work through the timeline, the technical checks and the content review, comparing the pages that fell with pages that held their traffic.
Step 02
[Report and choose the fixes]
You receive the written diagnosis and decide which fixes go ahead, and in what order.
Step 03
[Release the fixes]
Approved fixes go out in the agreed order, with a dated record of each release for the comparison that follows.
Step 04
[Compare with the period before the drop]
Once search engines have processed the changes, the affected pages are compared with the period before the drop. Changes Google has not yet picked up are reported as pending.
No account layer between you and them. These are the Norml specialists this work runs through.
Let's chat
“I've spent 10 years working across development and marketing. I started as a developer, but design, SEO and advertising were already part of the job. That taught me to treat a website as one system: the business, the content, the design and the code have to work together. At Norml, I lead the architecture behind our work and stay involved wherever strategy, design, development and search meet.”
Often, though not always. When the change records, Search Console data and crawl data line up, the report names the cause and the evidence for it. When several things changed in the same weeks or records are missing, it ranks the likely causes and says what further data would separate them.
Will our rankings come back after the fixes?
No one can promise that. The fixes remove the causes found on the site, and Google reassesses the pages in its own time. A loss that comes from outside the site, such as a Google update or lower demand, may not reverse, and the report says when that is the likely explanation.
Can the report be used in a dispute or legal case?
The report documents what changed on the site and what the search data shows, with the sources and method behind each finding, so another specialist can check the work. We do not act as expert witnesses or give legal opinions. If your case needs expert evidence, your legal team decides who provides it.
Can pages be rewritten without undoing their SEO setup?
Yes. Before a rewrite we record each page's address, title tag, meta description, canonical tag, structured data and tracking tags. The new copy goes onto the same address, and those settings stay as they are unless a change is agreed for that page. After publishing, the same list is checked on the live page, along with the internal links that point to it.
What if Search Console was never set up?
The diagnosis then relies on analytics, crawl data, page archives and third-party ranking estimates. They show less, so the report marks which conclusions they support and which stay open. We set up Search Console during the work, so the comparison after the fixes uses Google's own data.
Our drop is in local searches. Do you check our business listings?
Yes, as part of the diagnosis. The business name, address, phone number and opening hours on your Google Business Profile and directory listings are compared with the website, and any mismatch goes into the report. Mismatches on the website are fixed with the other approved fixes. Corrections to the profile and the listings themselves are part of our local SEO work and are agreed separately.
Does the site have to run on WordPress?
No. The diagnosis reads search data, analytics and the site's change history, whatever the platform. On WordPress we also make the fixes in the theme, plugins and content. On another platform, who makes each fix is agreed before the work starts.
Will you change anything before the diagnosis is finished?
Only problems that keep doing damage while they stay, such as pages blocked from search by mistake, and only after you approve. Everything else waits for the report, so each change can be traced to a finding and the comparison afterwards stays clean.
Can we order only part of this work?
Yes. A test of one known problem can end with the written report. A review and rewrite of thin or generic pages can also run on its own, without a drop to diagnose, starting from the pages you choose.
What if the cause needs more than these fixes?
If the drop started with spam pages, redirects to other sites or a security warning, the site is cleaned up first as a hack recovery. A redesign, a migration, new content plans, link building, ongoing SEO and a technical audit of pages unrelated to the drop are scoped separately.
Read our search and tracking case studies
Read how we handled technical search problems, tracking and local search on client websites.