Skip to main content


Why do so many web pages use something like this as their opening paragraph? Is this taught in SEO school or something?

"Hello, everyone! Today I’m going to talk about (SUBJECT), and whether or not you should (SUBJECT). It seems like a simple enough question, but the answer might not be as straightforward as you think. In this blog post, I’m going to explore the benefits and drawbacks of (SUBJECT), and provide some tips for deciding whether or not it’s the right choice for you."

It sounds like a desperate student trying to pad out their essay when they have no idea what they're talking about. πŸ˜†

#Web

#web
This entry was edited (6 days ago)
in reply to FediThing πŸ³οΈβ€πŸŒˆ

it might be good for SEO but it's also a considerate way to help readers decide whether they want to read on or not, no?
in reply to FediThing πŸ³οΈβ€πŸŒˆ

I think it is, there was a blog post I read last year about it, and enshittification.

Those paragraphs were needed to ensure the site placed high in google results. SEO is a cursed discipline and I'll have no part of it.

in reply to FediThing πŸ³οΈβ€πŸŒˆ

It’s SEO (see also why recipes now come with a thousand word introduction.)

It’s also a way to help detect AI-generated content because they can’t reason so you get nonsense things like β€œFor millennia scholars have asked what is the difference between shit and Shinola?”

in reply to FediThing πŸ³οΈβ€πŸŒˆ

Ooh, that's new to me! That'll get used. Thank you!

My recipe app (Paprika, which has shown zero enshitification tendencies over the years) does a great job of pulling recipes off pages full of fluff, but one has to actually find the recipe one wants before feeding it to Paprika's filters.

in reply to FediThing πŸ³οΈβ€πŸŒˆ

@troublewithwords if you insert β€œcooked.wiki/β€œ after the :// in a recipe URL, that site makes a de-fluffed version of any recipe page.
⇧