The Pipeline Leak Taxonomy
Organic revenue does not fall for one reason. It falls for one of twelve, and the twelve are always the same. This is the list Rakesh Ranjan Samantaray diagnoses against, whether the engagement is a free diagnostic, a working session or a full quarter.
| Leak | What you would see | What it costs | Time to fix |
|---|---|---|---|
| 01. Crawl waste | Search engines spend your crawl budget on pages that cannot rank. Sitemaps and internal links point at parameter pages, faceted filters, session URLs and support archives that return no new content. | Every request a crawler makes on a page that cannot rank is one it does not make on a page that can. | 1 to 2 days |
| 02. Index exclusion | Your best pages are not in the index at all. A noindex left on a page after a migration, a robots rule that is too broad, a page that only ever existed as a draft, or a canonical pointing somewhere else. | The page that should be your best seller is invisible, and no amount of content on it will matter. | 1 to 3 days |
| 03. Render gap | The content exists in the browser but not for the crawler. Pricing, comparison tables and FAQ answers rendered by JavaScript after the first paint, especially inside tabbed interfaces. | A buyer searching a phrase you wrote the answer for never sees the answer, because the crawler never did. | 3 to 5 days |
| 04. Redirect chain | Your link equity is spread across a chain of hops. A legacy blog URL that points to a category page, which points to a redirect, which points at the real page. | Every hop dilutes the signal and adds a delay the buyer feels on mobile. | Half a day |
| 05. Canonical conflict | Two pages claim to be the same page and search engines pick the wrong one. A product page and a blog post about that product, both with self referencing canonicals, or one page canonicalising to a variant you do not want to rank. | Your best content is competing with itself and losing. | 1 to 2 days |
| 06. Template thinness | You have hundreds of pages that are almost the same page. Location pages, comparison pages and product pages generated from one template with three varying fields. | A page that is almost identical to a thousand others ranks for nothing and still costs crawl budget. | 2 to 4 weeks |
| 07. Intent gap | You rank for the wrong stage of the buyer's journey. Top of funnel keywords that generate traffic and newsletter signups, while the pages that answer the buying question are not written at all. | Traffic goes up. Pipeline does not, and the board asks why. | 1 to 2 weeks |
| 08. Entity ambiguity | Nobody, human or machine, can say reliably what your company is. No consistent entity across your own site, inconsistent category language, a company name that means five different things in five places. | If AI cannot tell what you sell, you cannot be recommended for anything. | 2 to 4 weeks |
| 09. Citation deficit | Your pages are read but never quoted. Content that argues rather than answers. No short, self-contained statements a retrieval system can lift on its own. | You are in the training data and not in the answers. | 1 to 2 weeks |
| 10. Category gap | Somebody else owns the category term you need. A competitor ranking for the commercial head term your buyers actually use, because they wrote the definitive version and you wrote a blog post. | Every buyer starts at the category term. If you do not own it, you rent access to your own demand. | 4 to 8 weeks |
| 11. Attribution gap | The pipeline exists and nobody can prove where it came from. No first touch or last touch discipline, self reported attribution in a dashboard, and no connection between the keyword that won and the deal that closed. | The work looks successful on the traffic report and invisible in the revenue report. | 1 to 3 days |
| 12. Decay | Pages that used to work are quietly not working any more. A cluster losing impressions quarter over quarter while competitors publish, and a refresh backlog nobody owns. | The loss is slow enough that nobody notices until the traffic is gone. | 1 to 2 weeks |
Why twelve, and why publish them
Most organic audits take a week because the consultant does not know what to look for. A fixed taxonomy removes the search. The diagnostic is not a checklist you have to interpret, it is twelve named things that are either broken or not.
If the framework is public, anyone can point at a finding and say the work does not follow it. That is the point. An engagement you cannot audit from the outside is one you should not sign.
Frequently asked questions
How many of these will a typical site have?
Most B2B SaaS sites have four to seven live at once. They are rarely independent, which is why the diagnostic ranks them by pipeline impact instead of listing them as equal findings.
Can I diagnose my own site with this list?
Yes, and you should. If you can find your own bottleneck you may not need a diagnostic, and the free diagnostic will tell you that too.
Does this replace a technical audit?
No. A technical audit inspects your site. The taxonomy is the list of twelve ways the inspection is allowed to find something wrong, and it is shared by both the audit and the diagnostic so the two never contradict each other.
Is the taxonomy the same as the 12 point diagnostic?
The taxonomy is the list of twelve leak types. The diagnostic is the process that checks each one. See the diagnostic page for the mapping.
Who else uses this framework?
It was written for this practice, but it is published so your engineers, your writers and your agency can use the same twelve names. Disagreements are easier to resolve when everyone is using the same list.
Find out which ones are live on your site
The 48 hour diagnostic tests all twelve leak types and returns them ranked by pipeline impact, with the fix and the owner for each.
Direct access with Rakesh Ranjan Samantaray. No agency account managers.