Checklists · 15 mistakes

15 SEO mistakes that kill rankings

The recurring, high-cost mistakes we see again and again, most of them silent, most introduced by a deploy or migration. Here's what each one does to your rankings and how to catch it before it costs you.

Check my site freeFree SEO tools

Why are these mistakes so dangerous?

The worst SEO mistakes are silent. The page still loads, nothing looks broken, and the traffic drop arrives days later once search engines re-crawl, by which point the cause is buried. That delay is exactly why these need monitoring, not just a manual glance.

Every item below maps to a real, mechanically detectable check, not a rule of thumb. That matters because it means each one has an unambiguous pass/fail state: either the tag is there or it isn't, either the status code is 301 or it's 302, either the target returns 200 or it doesn't. Nothing on this list requires a judgment call, which is exactly why it's worth automating rather than re-checking by eye after every release.

The deindexing mistakes (most damaging)

These remove pages from search entirely.

1

A stray noindex on a template

A staging noindex or CMS toggle that ships to production deindexes every page using that template at once. The single most common SEO disaster. How to catch it →

2

A canonical pointing to the wrong URL

Canonicalising to a redirect, a 404, or every page to page 1 tells Google to index a different (or dead) URL, removing your real page. Canonical mistakes →

3

Blocking pages in robots.txt to "hide" them

robots.txt doesn't deindex, it just stops Google seeing your noindex, leaving pages in the index with no description. The robots.txt trap →

4

Pages returning 4XX/5XX after a migration

Important URLs that started erroring drop out of the index. A single template or config change can turn a whole section into 404s or 500s at once, which is why the audit checks status codes across every crawled page on every run, not just spot-checks. Always re-check status codes after a move.

These four share one property: they don't just hurt one page, they can silently remove an entire section of your site from search results while every page still loads fine in a browser. That's what makes them the most damaging category, and the first thing to rule out whenever traffic drops for no visible reason.

The authority-leaking mistakes

These waste the ranking strength you've already earned.

5

Broken internal links

Links to 404s waste crawl budget and leak link equity into dead ends. Why broken links hurt →

6

Orphan pages

Pages nothing links to are barely discovered and starved of authority. Orphan pages →

7

Redirect chains and loops

Multi-hop redirects waste crawl budget and risk equity loss; loops take a page offline entirely. Redirect chains →

8

Using a 302 for a permanent move

A temporary redirect keeps the old URL indexed and stalls the transfer of authority to the new one. 301 vs 302 →

9

Internal links pointing to redirects

Linking to a URL that redirects wastes a hop on every crawl and click. Link to the final URL directly.

10

"Click here" anchor text

Generic anchors waste the topical signal a link could pass. Describe the destination. Anchor text →

None of these six stop a page ranking outright the way the deindexing mistakes do. What they do is waste the authority you've already earned through backlinks and internal linking, spreading it thinner across dead ends, redirect hops and unclear anchors instead of concentrating it on the pages you actually want to win.

The clarity & experience mistakes

These muddy how pages are understood or felt.

11

Duplicate titles and meta descriptions

Repeated tags across pages dilute clarity and signal templated content. Fix titles & descriptions →

12

A sitemap full of junk URLs

Redirects, 404s, and noindex pages in the sitemap send contradictory signals to crawlers. Sitemap best practices →

13

Slow Core Web Vitals on mobile

Failing LCP, CLS, or INP on mobile costs both a ranking signal and real conversions. Core Web Vitals →

14

Broken or missing hreflang

On multilingual sites, missing return tags and invalid codes serve the wrong-language page or cause versions to compete. hreflang guide →

15

Invalid structured data

JSON-LD errors throw warnings in Search Console and block rich results. Common failures the audit checks for: a duration field that isn't valid ISO 8601, a language code that doesn't validate, a date that doesn't parse, and FAQ schema whose answer text is hidden from visible readers, that mismatch between what's marked up and what's shown gets treated as an attempt to game rich results. Validate any schema you ship, and don't invent properties that aren't in the schema.org vocabulary.

This group is about clarity rather than visibility: none of these five stop a page from being crawled or indexed, but each one makes the page harder for search engines, and often users, to understand correctly. A duplicate title looks fine to a human skimming the page and still confuses the algorithm deciding which of your pages should rank for a given query.

Where to read the full explanation

Every category, one click away

This list is a summary, not the full explanation. For the detailed reasoning and fixes behind each mistake, go to the category it belongs to: crawlability, indexability, links, redirects, sitemaps, content, performance, security, and localization.

Or work from the other checklist: the 20-point technical SEO checklist covers the same ground in the order to actually run it in, rather than ranked by how damaging a mistake is.

Mistake questions, answered

What is the single most damaging SEO mistake?

A stray noindex tag shipped on a shared template. Because templates are reused across many pages, one flag in one place deindexes every page built from it at once, and because the page still loads normally, nobody notices until organic traffic has already dropped.

How do I know if one of these mistakes has already happened to my site?

Run a full-site crawl rather than checking pages by eye. Most of these are invisible on a normal page view and only show up when something reads the actual HTTP response and meta tags. Search Console's Pages report will also show a sudden change in indexed page count, usually the first external signal.

Why do these mistakes usually happen right after a deploy or migration?

Because most of them are side effects of changing infrastructure rather than deliberate choices: a staging noindex left in a template, a framework defaulting new redirects to 302, a migration that doesn't carry canonicals and hreflang over. None of these look like errors in a code review.

Can one of these mistakes tank my whole site, or just one page?

It depends on where it lives. A bug on an individual page affects only that page. The same bug baked into a shared template or CMS default affects every page using it, which is why template-level and site-wide mistakes rank higher on this list than page-level ones.

How often should I check for these mistakes?

After every deploy that touches templates, redirects, the sitemap, or canonical logic, since that's when almost all of them are introduced. Run a full pass at least monthly too, to catch the slower-moving ones like link rot and orphaned pages that accumulate over time.

Catch these before they cost you

Free to start. Audit your site for every mistake on this list and get alerted when a new one ships.

Start my free audit