July 14, 2015 | Sarah Danks


Ian Lurie’s 2015 MnSearch Summit Presentation:

Technical Issues for SEO — Most Important/Most Ignored

Ian was one of the presenter’s at the 2nd annual MnSearch Summit, held in St. Paul at the Rivercentre on June 26, 2015. CEO of Portent, Ian regularly speaks, blogs, Tweets, eats/sleeps/breathes SEO. He connected with fellow SEO nerds in his presentation about technical issues that affect SEO.

So where DO rankings come from?

DFP = Distance From Perfect

ian-mnsearch-distance-from-perfect

You see someone outranking you — obviously they’re spamming.

ian-mnsearch-outranked

Wait, they’ve got lots of content. So YOU write lots of content. Wheeeee! You rise in the SERPS to #2…

…and your competitor is #1. @!#%*$

Paid / Earned / Owned

Content — Analytics — Infrastructure

ian-mnsearch-infrastructure

You’re at the content creation stage — hoping to wend your way upwards in the SERPS. But really you need to start with your infrastructure.

Infrastructure drives distance from perfect

The 5 DFP Creators

    • Debris
    • Obfuscation
    • Duplication
    • Misdirection
    • Divorce

#1: DEBRIS

AKA: busted links.

What’s bad? Broken links on your own site. What’s worse? Broken links from another site.

How to detect debris: don’t trust Google (or Bing). How, then?

Get the log files. Learn grep.

For those of you who aren’t technical — as I’m not:

“grep is a command-line utility for searching plain-text data sets for lines matching a regular expression.”

~ Wikipedia

ian-mnsearch-grep

ian-mnsearch-grep-2

ian-mnsearch-grep-3

Beware of lost authority!

ian-mnsearch-lost-authority

Fixing Debris

Ask nicely — “please could I have my link back?” If they refuse, you’ll have to put the old page back, or 301 redirect the old to the new.

Easiest link building ever? Fixing broken links.

#2: OBFUSCATION

What we see:
ian-mnsearch-radar-map

What’s really there:

ian-mnsearch-radar-map-no-images

Detecting Obfuscation

ian-mnsearch-web-dev-toolbar

ian-mnsearch-curl

ian-mnsearch-curl-code

Fixing Obfuscation

Use javascript to drive interaction and apps; but do NOT use javascript to deliver content.

Snapshots / Graceful degradation / Don’t trust Google / Distance from Perfect

#3: DUPLICATION & THIN CONTENT

ian-mnsearch-dupe

ian-mnsearch-dupe-2

Lost crawl budget:

ian-mnsearch-dupe-3

If you make Google spend too much time worrying which URL to crawl, Google’s gonna get bored and bounce (see what I did there???).

Lost authority:

ian-mnsearch-dupe-links

If you’ve got duplicate content across multiple URLs, but links pointing to each version — how does Google know what’s what?

You’re going to lose page authority by spreading your “link love” too thin:

ian-mnsearch-lost-authority-2

Detecting Duplication & Thin Content

Screaming Frog shows duplicate content:

ian-mnsearch-screaming-frog-dupe

And it also shows word count, which can be an indication of thin content:

ian-mnsearch-screaming-frog-thin-content

Fixing Duplicate/Thin Content

So, how do you fix dupe/thin content?

a) JUST FIX IT.

  • Good — logical
  • Bad — too logical, difficult, too logical

b) 301s

  • Good — easy
  • Bad — decaying authority, screwed up, redirect chains

3) Boilerplate

  • Good — logical
  • Bad — resistance, legal issues, brand issues

4) robots.txt disallow / robots tag

  • Good — easy, one file
  • Bad — fails all the time, gets crawled, burns crawl budget

5) Rel canonical

  • Good — easy
  • Bad — easy to screw up, burns crawl budget

Did you forget? Don’t trust Google.

#4: MISDIRECTION

Server Response Codes

  • 200 = all is well (page crawled + indexed)
  • 301 = this page is gone and won’t be back (destination crawled + indexed)
  • 302 = this page is gone and will be back (???)
  • 404 = this page is gone (page dropped?)
  • 500 = this server is gone (site dropped?)

ian-mnsearch-302-bad

ian-mnsearch-200-worse

Lost Crawl Budget

  • Thin pages
  • Duplication
  • Panda

Detecting Misdirection

ian-mnsearch-curl-2

Fixing Misdirection

“Fix your @#$ server”

~ Ian Lurie

#5: DIVORCED CONTENT

ian-mnsearch-divorced-content

Fixing Divorced Content

(Take it to counseling?)

1) Scrape and republish…

ian-mnsearch-scrape

…or

2) Write your own.

  • Good — easy-peasy (lemon-squeezy)
  • Bad — not real-time, can be slow, lots of moving parts

3) Reverse Proxy

ian-mnsearch-reverse-proxy

  • Good — flexible, fast, nerd cred
  • Bad — difficult, security (if ecom), aneurysms

ian-mnsearch-dfp-creators

Bonus round: screwing plagiarists!

Most plagiarism is lazy scraping.

ian-mnsearch-plagiarism

ian-mnsearch-plagiarism-2

ian-mnsearch-plagiarism-3

ian-mnsearch-plagiarism-4

ian-mnsearch-plagiarism-5

TIP: Replace it on the server with another image

ian-mnsearch-plagiarism-6

And that’s it!

 

Want to see the entire presentation? Check out Ian’s full deck here.

 

 

 

 

 

 

 

 

 


Categories


Archives


Subscribe To Our Newsletter

Our newsletter includes industry news, tips, and upcoming events!