A technical guide to SEO
ma.ttias.be
A technical guide to SEO
1–10 of 29 posts
Re: A technical guide to SEO
#2Re: A technical guide to SEO
#3Re: A technical guide to SEO
#4Re: A technical guide to SEO
#5Re: A technical guide to SEO
#6Google plays go (learnt yesterday), develops self driving cars and robots. And it still cant understand which piece of text on simple website is the header. Without SEO. Right?
Nobody's claiming Google can't figure out the visual structure of a page or determine the canonical page within a set of duplicates, but evidence[0][1] has shown that making it easier for Google to do those things has a positive effect.
[0] Search Engine Ranking Factors 2015: https://moz.com/search-ranking-factors
[1] Anecdotal evidence: Just two weeks ago one of my clients' sites had a temporary issue with 301-redirects, causing some old URLs to return 404 instead of redirecting to new URLs, and the www version of every page not redirect to the non-www version. Search traffic nearly halved the following week (this past week). I patched up those issues and we're already seeing things resume back to normal.
Re: A technical guide to SEO
#7Re: A technical guide to SEO
#8Actually, what do you recommend for ongoing monitoring of the things flagged by wget scripts? I could assign it to my programmer. I also think Moz or similar services handle that automatically. It might be more effective just to outsource it to them?
My current solution has been to avoid monitoring it, which isn't optimal.
Re: A technical guide to SEO
#9I think AdSense used to warn of possibly lower earnings when switching to HTTPS, because somehow less ads are available over HTTPS. Is that still the case?