SEO for Web Engineers

#1

Post by midef » Sat, Feb 09, 2019, 1:29 PM UTC

Re: SEO for Web Engineers

#2

Post by chiefalchemist » Sat, Feb 09, 2019, 2:36 PM UTC

A brisk but thorough checklist that fulfills the promise of the title.

My only objection would be this bit (below). Specifically, "demands." How many engineers are in a positiin to demand anything? The truth is, for the most part, it's not engineers who are ruining the internet with bloat and privacy infringements. It's designers and marketing. They're more likely to forget the end user and opt for so nasty excess.

> "Demand that someone take ownership of each tracking pixel and tag that's added to a page, then, make these stakeholders justify their tags every six months. If you don't, people will ask you to add junk to the page until your team gets blamed for a slow site."

Re: SEO for Web Engineers

#3

Post by lifeisstillgood » Sat, Feb 09, 2019, 2:39 PM UTC

The interesting one for me was measuring error rates (if your JS heavy web page calls the server 100 times, if two users try to load and one gets 500 that should be 50% error rate but it looks like So it feels like a piece of JS that says I have seen everything that should load load ok, then reports home with the page seems a good idea.

Probably quite doable - can JS see the network load like web developer tools ?

Re: SEO for Web Engineers

#4

Post by denniskane » Sat, Feb 09, 2019, 2:40 PM UTC

I dunno, I think I violate all those rules. I just try to write badass JS[1] purely for client-side rendering to make people's lives just work better.

[1] see an example at https://linuxontheweb.org/desk.os

Re: SEO for Web Engineers

#5

Post by caiocaiocaio » Sat, Feb 09, 2019, 2:49 PM UTC

chiefalchemist wrote: post #2

A brisk but thorough checklist that fulfills the promise of the title. My only objection would be this bit (below). Specifically, "demands." How many engineers are in a positiin to demand anything? The truth is, for the most part, it's not engineers who are ruining the internet with bloat and privacy infringements. It's designers and marketing. They're more likely to forget the end user and opt for so nasty excess. >…

My main objection is medium grey text on a white background.

Re: SEO for Web Engineers

#6

Post by sturgill » Sat, Feb 09, 2019, 3:03 PM UTC

lifeisstillgood wrote: post #3

The interesting one for me was measuring error rates (if your JS heavy web page calls the server 100 times, if two users try to load and one gets 500 that should be 50% error rate but it looks like So it feels like a piece of JS that says I have seen everything that should load load ok, then reports home with the page seems a good idea. Probably quite doable - can JS see the network load like web developer tools ?

There can’t be a generic solution to “am I done loading everything” (see the halting problem). And tightly coupling every request to a list feels awfully fragile. I think the real problem is making 100 api calls to load a page...

Re: SEO for Web Engineers

#7

Post by paulpauper » Sat, Feb 09, 2019, 3:14 PM UTC

The million dollar question is how to get good rankings for good keywords without having to spend too much money. This article does a good job describing how to keep a successful site optimized but actually getting the rankings is not covered much.

Never, ever, let marketers send newsletters and promotional e-mails from the same IPs that the websites are hosted on. A rogue employee who violates the CAN-SPAM act may result in the entire website being blacklisted.

But the problem is all someone needs to do is just get the IP for the website from the email link and blacklist that too, so a different IP will not help much. The best solution for blacklisting is cloud hosting which has many IPs , so the odds of all being blacklisted are slim. Amazon s3 servers have like 100+ ips

Re: SEO for Web Engineers

#8

Post by [deleted] » Sat, Feb 09, 2019, 3:27 PM UTC

chiefalchemist wrote: post #2

A brisk but thorough checklist that fulfills the promise of the title. My only objection would be this bit (below). Specifically, "demands." How many engineers are in a positiin to demand anything? The truth is, for the most part, it's not engineers who are ruining the internet with bloat and privacy infringements. It's designers and marketing. They're more likely to forget the end user and opt for so nasty excess. >…

[deleted]

Re: SEO for Web Engineers

#9

Post by papaman » Sat, Feb 09, 2019, 4:01 PM UTC

there is no such thing as "SEO". Also, everything on the list has nothing to do with Search Engine Optimization.

For example "SERVER STABILITY AND DOWNTIME".

How come taking case of your server stability is SEO???

Re: SEO for Web Engineers

#10

Post by mcny » Sat, Feb 09, 2019, 4:04 PM UTC

caiocaiocaio wrote: post #5

chiefalchemist wrote: post #2

A brisk but thorough checklist that fulfills the promise of the title. My only objection would be this bit (below). Specifically, "demands." How many engineers are in a positiin to demand anything? The truth is, for the most part, it's not engineers who are ruining the internet with bloat and privacy infringements. It's designers and marketing. They're more likely to forget the end user and opt for so nasty excess. >…

My main objection is medium grey text on a white background.

It is funny because your comment is slightly grey (I assume because a trusted community member downvoted you).