Find the page for your symptom
| What you see | Go to | Why that page |
|---|---|---|
| Search Console says "Crawled - currently not indexed" | Crawled, currently not indexed | Google fetched the page and declined to keep it |
| Search Console says "Discovered - currently not indexed" | Discovered, currently not indexed | Google knows the URL but has not fetched it yet |
| Search Console says "Duplicate without user-selected canonical" | Duplicate without user-selected canonical | Google folded the URL into another version you never named |
| Search Console says "Indexed, though blocked by robots.txt" | Indexed, though blocked by robots.txt | Google kept URLs it is not allowed to fetch, usually because they are linked |
| Valid-looking pages are labelled as soft not-found errors | Soft errors in Search Console | The server says success but the page looks missing |
| Rankings fell suddenly with no site move | Rankings dropped suddenly | Separates technical blocks, updates, links, edits, intent and reporting |
| Organic traffic fell after a redesign, replatform or domain change | Traffic drop after a migration | Starts from the launch and checks redirects, directives, content and tagging |
| The Core Web Vitals report flags a slow largest contentful paint | LCP too slow | Isolates the element and the phase of loading that is slow |
| The Core Web Vitals report flags layout shift | CLS issue: layout shifts on load | Finds the element that arrives without reserved space |
| The Core Web Vitals report flags slow interactions | INP issue: slow interactions | Splits the slow tap into input delay, processing and presentation |
| Structured data looks fine but no stars, prices or events appear | Rich results not showing | Sorts errors, eligibility and Google's discretion |
| Searchers in one market see another country's page | Wrong country version ranking | Finds the locale signal that points the wrong way |
| Google shows a different headline from your title tag | Google rewriting title tags | Identifies which source Google used instead and why |
| A new page is indexed but never climbs for its target query | New content not ranking | Checks intent, cannibalisation, substance, internal links and topic depth |
| The site does not appear on Google at all, not even for its own name | Website not showing on Google | Checks 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 name | Not ranking for your own brand name | Checks 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 you | Server errors in Search Console | Finds when and where the server failed the crawler |
| Not-found errors climb after a reorganisation or a release | Not-found errors in Search Console | Separates pages that should stay gone from links, sitemaps and pages that broke |
| The "Page with redirect" count keeps growing | Page with redirect in Search Console | Separates planned redirects from sitemaps, canonicals and links that still name old addresses |
| The wrong page on your site ranks for a query | Wrong page ranking for a keyword | Finds 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 (GSCGoogle's search performance and indexing tool.), 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 TagTells search engines the preferred URL. 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 BudgetHow much a search engine crawls a site. 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.
