Diese Präsentation wurde erfolgreich gemeldet.
Wir verwenden Ihre LinkedIn Profilangaben und Informationen zu Ihren Aktivitäten, um Anzeigen zu personalisieren und Ihnen relevantere Inhalte anzuzeigen. Sie können Ihre Anzeigeneinstellungen jederzeit ändern.

Large Scale SEO - Method to the madness

6.874 Aufrufe

Veröffentlicht am

In this presentation, given at SMX Munich 2016, Joost talks about the methods he uses to do SEO for large scale websites. He covers his SEO data strategy, optimization strategy and regular audits.

Veröffentlicht in: Internet

Large Scale SEO - Method to the madness

  1. 1. Method to the madness - Large Scale SEO
  2. 2. What’s the problem?
  3. 3. Homepage example.com/ Support portal kb.example.com Shop example.com/shop/ News section example.com/news/ A “modern” website: Community portal example.com/forums/
  4. 4. What could go wrong? • Support portal outranking the main website • An error in the shop software causing the entire site to stop being indexed • So much crawl budget being spent on community forums that shop doesn’t get crawled properly • KB linking to shop everywhere, shop changes URL structure • etc. etc. etc.
  5. 5. What’s the solution?
  6. 6. Modern websites cause a need for a different SEO approach.
  7. 7. Method • Build properly • Get all the needed data • Optimize constantly • Audit regularly • Teach others
  8. 8. Do you know what’s on your site?
  9. 9. Homepage example.com/ Support portal kb.example.com Shop example.com/shop/ News section example.com/news/ It can be as simple as this: Community portal example.com/forums/
  10. 10. Method • Build properly • Get all the needed data • Optimize constantly • Audit regularly • Teach others
  11. 11. A comprehensive SEO data strategy • Service Oriented Approach to main sources of information: • Analytics • Logs, specifically: • Spider logs • Error logs • Internal Search
  12. 12. Analytics
  13. 13. Analytics • Often the only thing that’s already centralized. • Far too often answers questions that you don’t need to answer.
  14. 14. Do you know what content on your site is the most engaging?
  15. 15. Facebook stats?
  16. 16. Twitter stats?
  17. 17. Pinterest?
  18. 18. Video?
  19. 19. This can be done.
  20. 20. Engagement metrics
  21. 21. Engagement metrics
  22. 22. Good analytics is an aggegration of loads of sources of data.
  23. 23. Logs & Search console
  24. 24. Googlebot stats before GSC tells you Do you need Google Search Console to tell you you’ve got errors on your site?
  25. 25. Logs Centralize all logs into one “stash”. My personal preference: Logstash on ElasticSearsch. Using Kibana, you can filter out and create specific dashboards for bot traffic and errors.
  26. 26. Googlebot stats that HELP
  27. 27. Some of my favorite views Top spidered URLs over the last 24 hours, by Google user agent. Average response time, slow loading pages, slow loading page types. Googlebot 4xx and 5xx errors over the last 24 hours.
  28. 28. Google Search Console errors Be honest, how many of you have “accepted” a “background noise” of thousands or even 100k+ errors?
  29. 29. User errors Is anybody at your company monitoring user “crashes”? Pages that 404 more than X times a day?
  30. 30. If engagement is king, errors are the hangman.
  31. 31. Internal Search Internal search
  32. 32. Internal search should tell you which content you have.
  33. 33. Internal Search monitoring • Is someone / something monitoring the missed keyword opportunities across your site? • This could flow back into ElasticSearch / Kibana too
  34. 34. URLs
  35. 35. Homepage example.com/ Support portal kb.example.com Shop example.com/shop/ News section example.com/news/ A link changes in your shop Community portal example.com/forums/
  36. 36. Homepage example.com/ Support portal kb.example.com Shop example.com/shop/ News section example.com/news/ What happens to the links pointing there? Community portal example.com/forums/
  37. 37. URLs and links across your site • In an ideal world, you never embed complete links. • You embed ID’s, which are translated to links based on one datasource.
  38. 38. Homepage example.com/ Support portal kb.example.com Shop example.com/shop/ News section example.com/news/ One database that has all the URLs for: Community portal example.com/forums/
  39. 39. All URLs • App deeplinks • hreflang relations • AMP URLs • etc. etc.
  40. 40. XML Sitemaps & hreflang
  41. 41. Homepage example.com/ Support portal kb.example.com Shop example.com/shop/ News section example.com/news/ You probably don’t have this: Community portal example.com/forums/
  42. 42. Homepage example.com/ Support portal kb.example.com Shop example.com/shop/ News section example.com/news/ Community portal example.com/forums/ Homepage example.com/ Support portal kb.example.com Shop example.com/shop/ News section example.com/news/ Community portal example.com/forums/ Homepage example.com/ Support portal kb.example.com Shop example.com/shop/ News section example.com/news/ Community portal example.com/forums/ Homepage example.com/ Support portal kb.example.com Shop example.com/shop/ News section example.com/news/ But this, in 4, 5, 8, 20 languages: Community portal example.com/forums/
  43. 43. Multiple Sitemap indexes • Don’t try to combine them!
  44. 44. Need to build XML sitemaps? • Base it off of your Internal Search API! • Use a smart naming scheme to help you dive into sections of your site easily.
  45. 45. Method • Build properly • Get all the needed data • Optimize constantly • Audit regularly • Teach others
  46. 46. Use your internal search API for related content.
  47. 47. Feed engagement and commercial metrics in.
  48. 48. Method • Build properly • Get all the needed data • Optimize constantly • Audit regularly • Teach others
  49. 49. Site changes? Embed SEO into CI • Who knows what CI is?
  50. 50. Create CI tests for important stuff • Check canonicals • Check hreflang • Check that URLs stay the same • Check HTTP header codes • etc.
  51. 51. Regular crawls to identify issues • Screaming Frog, OnPage.org, DeepCrawl, etc. • I don’t care which one you use, as long as you one.
  52. 52. Who am I kidding?
 Use OnPage.org ;)
  53. 53. Method • Build properly • Get all the needed data • Optimize constantly • Audit regularly • Teach others
  54. 54. Teach developers technical SEO.
  55. 55. Teach analytics people to look beyond your main analytics package.
  56. 56. Teach!
  57. 57. Questions? Follow along: • https://yoast.com/ • @jdevalk & @yoast on Twitter • facebook.com/yoast

×