Live data from Hacker News

A technical guide to SEO

ma.ttias.be

11–20 of 29 posts

Re: A technical guide to SEO

#11
post #9
post #7

I 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?

I've switched a handful of sites from http to https over the past 7 months and the drop of adsense earnings has been negligible.

Thanks, that sounds encouraging!

Re: A technical guide to SEO

#15
> Content is, as always, still king. It doesn't matter how technically OK your site is, if the content isn't up to snuff, it won't do you much good.

Shameless plug: friends of mine have been building Webtexttool [1], a tool aimed at helping content writers (who often are unaware of SEO technicalities) write optimized content. They are still adding features but it already works quite well.

[1] http://www.webtexttool.com/

Re: A technical guide to SEO

#16
post #9
post #7

I 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?

I've switched a handful of sites from http to https over the past 7 months and the drop of adsense earnings has been negligible.

Same scenario here (author of the original post): moving from HTTP to HTTPs did hurt my revenue for the first couple of months (I switched 2 years ago), but advertisers seem to have caught up.

For tech-oriented sites, I don't see a difference in revenue for HTTP vs HTTPs sites anymore. In fashion or other markets, that may still be a different deal.

Re: A technical guide to SEO

#17
post #16
post #9

Earlier quoted context omitted.

I've switched a handful of sites from http to https over the past 7 months and the drop of adsense earnings has been negligible.

Same scenario here (author of the original post): moving from HTTP to HTTPs did hurt my revenue for the first couple of months (I switched 2 years ago), but advertisers seem to have caught up. For tech-oriented sites, I don't see a difference in revenue for HTTP vs HTTPs sites anymore. In fashion or other markets, that may still be a different deal.

Despite being 2016, Bing can't read a ssl sitemap served on HTTPS sni. Supposed to be fixed soon I guess...

Re: A technical guide to SEO

#18
Note that forcing HTTPS will reduce your ad revenue. Google itself warns about it:

"Some important things to know about the SSL-compatible ad code: HTTPS-enabled sites require that all content on the page, including the ads, be SSL-compliant. As such, AdSense will remove all non-SSL compliant ads from competing in the auction on these pages. If you do decide to convert your HTTP site to HTTPS, please be aware that because we remove non-SSL compliant ads from the auction, thereby reducing auction pressure, ads on your HTTPS pages might earn less than those on your HTTP pages."

Re: A technical guide to SEO

#19
Solid resource but ultimately this kind of stuff plays a very small part in rankings. Targeting the correct keywords and building backlinks are what it's all about. This article came out not long ago, thought it was really good.

http://www.siegemedia.com/strategy/increase-website-traffic

Re: A technical guide to SEO

#20
post #8

Great overview, thank you. This gave me several things to fix I hadn't been aware of, and my site generally already does well with on-site SEO. Actually, 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 b…

Maybe it's not what you're looking for, but it would be easy to just write a cron job that runs wget and emails you if the error output is non-empty.
Post reply on HN