fmaury/seirdy.one
1
0
Fork 0
mirror of https://git.sr.ht/~seirdy/seirdy.one synced 2024-11-10 00:12:09 +00:00
Code Issues Projects Releases Wiki Activity

New note: JS-enabled engines

Browse source
This commit is contained in:
Rohan Kumar 2022-06-02 18:32:30 -07:00
parent f271291f49
commit 74842ce644
No known key found for this signature in database
GPG key ID: 1E892DB2A5F84479
1 changed files with 14 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
content/notes/JS-enabled-engines.md Normal file
View file

@ -0,0 +1,14 @@
---
title: "JS-enabled engines"
date: 2022-06-02T18:30:30-07:00
replyURI: "https://mk.nixnet.social/notes/911asmc9rn"
replyTitle: "if search engine crawlers didn't run JavaScript the Web would be better"
replyType: "SocialMediaPosting"
replyAuthor: "Alexandra"
replyAuthorURI: "https://www.alm.website/me"
---
The only engines I know of that run JavaScript are Google, Bing, and maybe Petal. None of the other engines in my list appear to support it. I don't even think Yandex does.
It's common practice for sites to give a JavaScript-lite version to search engines, though if the content differs heavily you run the risk of hitting a manual action. I'd imagine that search-crawler-exclusive editions would become the norm if crawlers stopped handling JavaScript.
Marginalia actually seems to penalize its use.