Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Collection

SEO Troubleshooting

Each page in this section starts from an SEO symptom you can see in Search Console, a traffic report or the results page, lists the plausible causes in a diagnosis table, and gives a check, a fix, a verification step and a prevention habit for each. The mechanics behind every cause are explained in an SEO guide elsewhere on the site, and each page links to it.

Looking for how to use this library? Read the guide below the list.

All 20 pages in this collection

Find the page for your symptom

What you seeGo toWhy that page
Search Console says "Crawled - currently not indexed"Crawled, currently not indexedGoogle fetched the page and declined to keep it
Search Console says "Discovered - currently not indexed"Discovered, currently not indexedGoogle knows the URL but has not fetched it yet
Search Console says "Duplicate without user-selected canonical"Duplicate without user-selected canonicalGoogle folded the URL into another version you never named
Search Console says "Indexed, though blocked by robots.txt"Indexed, though blocked by robots.txtGoogle kept URLs it is not allowed to fetch, usually because they are linked
Valid-looking pages are labelled as soft not-found errorsSoft errors in Search ConsoleThe server says success but the page looks missing
Rankings fell suddenly with no site moveRankings dropped suddenlySeparates technical blocks, updates, links, edits, intent and reporting
Organic traffic fell after a redesign, replatform or domain changeTraffic drop after a migrationStarts from the launch and checks redirects, directives, content and tagging
The Core Web Vitals report flags a slow largest contentful paintLCP too slowIsolates the element and the phase of loading that is slow
The Core Web Vitals report flags layout shiftCLS issue: layout shifts on loadFinds the element that arrives without reserved space
The Core Web Vitals report flags slow interactionsINP issue: slow interactionsSplits the slow tap into input delay, processing and presentation
Structured data looks fine but no stars, prices or events appearRich results not showingSorts errors, eligibility and Google's discretion
Searchers in one market see another country's pageWrong country version rankingFinds the locale signal that points the wrong way
Google shows a different headline from your title tagGoogle rewriting title tagsIdentifies which source Google used instead and why
A new page is indexed but never climbs for its target queryNew content not rankingChecks intent, cannibalisation, substance, internal links and topic depth
The site does not appear on Google at all, not even for its own nameWebsite not showing on GoogleChecks discovery, blocking rules, access and the property before anything else
The site is on Google, but other results come up when people search for its nameNot ranking for your own brand nameChecks the home page, how plainly the pages state the name, a shared name and mismatched listings
Search Console reports server errors on pages that load for youServer errors in Search ConsoleFinds when and where the server failed the crawler
Not-found errors climb after a reorganisation or a releaseNot-found errors in Search ConsoleSeparates pages that should stay gone from links, sitemaps and pages that broke
The "Page with redirect" count keeps growingPage with redirect in Search ConsoleSeparates planned redirects from sitemaps, canonicals and links that still name old addresses
The wrong page on your site ranks for a queryWrong page ranking for a keywordFinds the links, titles and overlaps that point the engine at the other page

How these pages work

Every page opens by asking whether the symptom is what it seems. A ranking "drop" may be a tracker that changed its settings, a traffic loss may be a missing analytics tag, and an indexing status may sit on URLs nobody wants indexed. Only after that check does a page give its diagnosis table: the symptom as you would see it, the check that confirms or rules out a cause, the cause, and the fix. Each cause then has its own short section covering the fix, how to verify it worked, and how to keep it from coming back, followed by a prevention routine and an invented worked example.

The pages deliberately stop short of teaching the underlying subject. How crawling, rendering and canonicalisation work is explained in crawling and indexing; the mechanics of templates, redirects, structured data and speed live in the technical SEO section. Each troubleshooting page links to the guide that owns a cause at the moment you confirm it, so you can go deeper on the one thing that is actually wrong.

Reading Search Console statuses before acting

Many of these problems start in Search Console (GSC), and its wording is precise. "Discovered" means Google has not crawled the URL; "crawled" means it has, and chose not to index it. "Duplicate without user-selected canonical" means the site declared no Canonical Tag and Google chose another URL; "Google chose different canonical than user" means it overrode the one you declared. Treat each label as a pointer to a stage of Google's process, not as an error to be cleared. Before changing anything, export the examples, group them by template or URL pattern, and inspect a few with the live test. A status affecting thousands of filter URLs is often a sign of wasted Crawl Budget rather than lost pages, and the fix is to produce fewer URLs, not to force more into the index. The Search Console guide explains each report these pages refer to.

When to run a technical audit instead

A troubleshooting page answers one question quickly. If several symptoms appear together, if the site has just been rebuilt, or if nobody can say when it was last reviewed, a structured technical SEO audit is the better tool. It works through crawling, indexing, architecture, rendering, speed and markup in a fixed order and prioritises what it finds, instead of chasing whichever symptom is loudest. Many teams run the audit once, then use these pages for the individual problems that surface between audits.