Wanderization #13

Closed
opened 2022-08-28 12:30:23 +02:00 by kreyren · 13 comments
Owner

To increase the reach and awareness of the project

Website expected to be implemented in GNU Guile.

To increase the reach and awareness of the project Website expected to be implemented in GNU Guile.
kreyren added this to the Gold milestone 2022-08-28 12:31:25 +02:00

I think you are actually generating a bad name for your project by putting the url out there before it's reachable. all indexers are going to index and keep for a while are "not resolved" of all of your "soon to come" domains...

just my two cents.

I think you are actually generating a bad name for your project by putting the url out there before it's reachable. all indexers are going to index and keep for a while are "not resolved" of all of your "soon to come" domains... just my two cents.
Author
Owner

@wanderer hmm in my testing the indexers were just not using the URL if it's 404 though?

@wanderer hmm in my testing the indexers were just not using the URL if it's 404 though?

if it's 404 though?

that's not what your urls are..

they are literally not being resolved because they are either not even registered or no server is set up for them anyway...which might do bad wonders for your future SEO..

> if it's 404 though? that's not what your urls are.. they are literally not being resolved because they are either not even registered or no server is set up for them anyway...which might do bad wonders for your future SEO..
Author
Owner

Seems like the same scenario with the indexers just not using the URL.. lets wait few hours and check what happens~

Seems like the same scenario with the indexers just not using the URL.. lets wait few hours and check what happens~

Seems like the same scenario with the indexers just not using the URL.. lets wait few hours and check what happens~

of course they are not using it, that's not the point.

the point is your projects (or even this site's) potential negative credit (internal to the indexers) gained through usage of broken links.

> Seems like the same scenario with the indexers just not using the URL.. lets wait few hours and check what happens~ of course they are not using it, that's not the point. the point is your projects (or even this site's) potential negative credit (internal to the indexers) gained through usage of broken links.
Author
Owner

Hmm looking at SEO analyzers for git.dotya.ml I don't think that I anything that would make it worse 🤔

either way the indexing takes at least a day so lets wait for the bots to check the website and then decide based on available data?

Hmm looking at SEO analyzers for git.dotya.ml I don't think that I anything that would make it worse 🤔 either way the indexing takes at least a day so lets wait for the bots to check the website and then decide based on available data?

Hmm looking at SEO analyzers for git.dotya.ml I don't think that I anything that would make it worse 🤔

:D

any proof?

either way the indexing takes at least a day so lets wait

again, it's not something you'll see indexed, but might nevertheless affect the results..

still..don't mind me..

> Hmm looking at SEO analyzers for git.dotya.ml I don't think that I anything that would make it worse 🤔 :D any proof? > either way the indexing takes at least a day so lets wait again, it's not something you'll see indexed, but might nevertheless affect the results.. still..don't mind me..
Author
Owner

any proof?

Ok you did this to yourself to unleash my SEO skills

Because the SEO tools are not open-source we have to assume that they can be just a snake oil spilling out a random values in order to sell their marketing BS so to mitigate this multiple analyses have to be checked and common issues then assumed as valid:

Sources:

Where the highlighted issues are:

  1. The website is using git.dotya.ml with website dotya.ml which harms SEO as subdomains are bound to the main domain and these two have conflicting wording resulting in the SEO flagging it as unspecified to determine the search results

dotya search

compared to:

codeberg search

  1. the landing page of git.dotya.ml is understandable to humans but not to bots because you are using icons that are important to the context and use inefficient wording so the landing page should have git

so to improve the SEO it should be reworked to have an elaborated title instead of just A Gitea instance by dotya.ml provided for fun as a hobby, with passion and love (generally at least 250 words seems to be important

  1. Majority of the analyzers complain abotu H1 Header tag Usage with the recommendation:

Your page has more than one H1 Tag. It is generally recommended to only use one H1 Tag on a page.
The H1 Header Tag is an important way of signaling to search engines what your content is about, and subsequently the keywords it should rank for.

  1. There is also an inconsistency in keywords where things like bloat gets indexed:

git dotya keywords

which gets associated with negative search results like complains about other things being bloated:

gotya bloat

beyond that things like 1ms, 0ms, back, etc.. gets also indexed

  1. The name dotya is too generic and gets you associated with DotA 2 (the game) so any kind of indexing makes is very steep hill to climb to differenciate from the game same as rust had issues with marketing from the survival game

dotya google search

Recommendation: Figure out a unique name that is easier to index

  1. The analyzers also complain about content on the website where the phrase word count 138 gets repeated across platforms suggesting that the landing page needs more content to be more SEO efficient

  2. There are also complains about not using canonical tags with the best explanation that i can find being:

The Canonical Tag tells Search Engines the primary URL of a page. URLs can have multiple versions due to things like parameters being passed or www and non-www versions resulting in potential duplicate content. Google recommends all pages specify a Canonical.

  1. There is a page that has public GPG that gets processed in the search which might confuses the search engine because it's bunch of random characters -> Add exclusion of it it in robots.txt

/assets/0DD13DBC6B5433D3.asc

gpg dotya associated

  1. Web.dev complains about "missing source maps for large first party javascript".. google is usually very sensitive for these kinds of things so that should be addresssed

  2. web.dev complains about the theme not having a sufficient contrast ration inbetween background and foreground which lowers the SEO score -> Improve the contrast ration

  3. majority of the analyzers complain about lack of social media widgets so it may be a good idea to add a fake widgets to fool the bots while avoiding tracking by bigtech (dunno the impact of it)

  4. Add FLOSS analysis tool - the analyzers complain about not finding an analysis tools which may harm the SEO score

  5. The 'google's pagespeed insights - mobile' seems to be mentioned a lot as well where it seems that it has issues with the mobile version of the website that should be investigated

  6. Sizing of buttons seems to be a common complaint as well where the recommendation is to increase the size of them slightly

  7. Seemingly dotya is using 'Facebook Open Graph Tags' might be a privacy issue

  8. Unwanted child pages get indexed:

  • /user/login?redirect_to=%2f
  • /user/oauth2/GitHub
  • /api/swagger
  • /assets/0DD13DBC6B5433D3.asc
> any proof? Ok you did this to yourself to unleash my SEO skills Because the SEO tools are not open-source we have to assume that they can be just a snake oil spilling out a random values in order to sell their marketing BS so to mitigate this multiple analyses have to be checked and common issues then assumed as valid: Sources: * https://rankmath.com/tools/seo-analyzer/ * https://web.dev/measure/?url=https%3A%2F%2Fgit.dotya.ml (Google's SEO tool) * https://seositecheckup.com/analysis * https://suite.seotesteronline.com/seo-checker/aHR0cDovL2dpdC5kb3R5YS5tbA==/ * https://www.seoptimer.com/git.dotya.ml Where the highlighted issues are: 1. The website is using `git.dotya.ml` with website `dotya.ml` which harms SEO as subdomains are bound to the main domain and these two have conflicting wording resulting in the SEO flagging it as unspecified to determine the search results ![dotya search](https://git.dotya.ml/attachments/6a156a4d-6416-40c2-824b-d650a3569143) compared to: ![codeberg search](https://git.dotya.ml/attachments/d473e38a-d777-4d55-a142-1c09bf647396) 2. the landing page of `git.dotya.ml` is understandable to humans but not to bots because you are using icons that are important to the context and use inefficient wording so the landing page should have git so to improve the SEO it should be reworked to have an elaborated title instead of just `A Gitea instance by dotya.ml provided for fun as a hobby, with passion and love` (generally at least 250 words seems to be important 3. Majority of the analyzers complain abotu `H1 Header tag Usage` with the recommendation: > Your page has more than one H1 Tag. It is generally recommended to only use one H1 Tag on a page. > The H1 Header Tag is an important way of signaling to search engines what your content is about, and subsequently the keywords it should rank for. 4. There is also an inconsistency in keywords where things like `bloat` gets indexed: ![git dotya keywords](https://git.dotya.ml/attachments/7af3ed11-c393-425b-afc2-a1a3b7aeb37a) which gets associated with negative search results like complains about other things being bloated: ![gotya bloat](https://git.dotya.ml/attachments/59f4e936-c9ec-4c44-8445-2ab824c0671c) beyond that things like `1ms`, `0ms`, `back`, etc.. gets also indexed 5. The name dotya is too generic and gets you associated with DotA 2 (the game) so any kind of indexing makes is very steep hill to climb to differenciate from the game same as rust had issues with marketing from the survival game ![dotya google search](https://git.dotya.ml/attachments/cd2526b1-9a23-4937-84dd-877cad5e4b52) Recommendation: Figure out a unique name that is easier to index 6. The analyzers also complain about content on the website where the phrase `word count 138` gets repeated across platforms suggesting that the landing page needs more content to be more SEO efficient 7. There are also complains about not using canonical tags with the best explanation that i can find being: > The Canonical Tag tells Search Engines the primary URL of a page. URLs can have multiple versions due to things like parameters being passed or www and non-www versions resulting in potential duplicate content. Google recommends all pages specify a Canonical. 8. There is a page that has public GPG that gets processed in the search which might confuses the search engine because it's bunch of random characters -> Add exclusion of it it in robots.txt /assets/0DD13DBC6B5433D3.asc ![gpg dotya associated](https://git.dotya.ml/attachments/06de0f95-804e-4b08-9b3d-b83d019c1ac5) 9. Web.dev complains about "missing source maps for large first party javascript".. google is usually very sensitive for these kinds of things so that should be addresssed 10. web.dev complains about the theme not having a sufficient contrast ration inbetween background and foreground which lowers the SEO score -> Improve the contrast ration 11. majority of the analyzers complain about lack of social media widgets so it may be a good idea to add a fake widgets to fool the bots while avoiding tracking by bigtech (dunno the impact of it) 12. Add FLOSS analysis tool - the analyzers complain about not finding an analysis tools which may harm the SEO score 13. The 'google's pagespeed insights - mobile' seems to be mentioned a lot as well where it seems that it has issues with the mobile version of the website that should be investigated 14. Sizing of buttons seems to be a common complaint as well where the recommendation is to increase the size of them slightly 15. Seemingly dotya is using 'Facebook Open Graph Tags' might be a privacy issue 16. Unwanted child pages get indexed: * /user/login?redirect_to=%2f * /user/oauth2/GitHub * /api/swagger * /assets/0DD13DBC6B5433D3.asc
Author
Owner

again, it's not something you'll see indexed, but might nevertheless affect the results..

Nah you can always see those :p just need to know where and how to look to understand the search behavior :p

> again, it's not something you'll see indexed, but might nevertheless affect the results.. Nah you can always see those :p just need to know where and how to look to understand the search behavior :p
Author
Owner

@wanderer transfer in dotya.ml issue tracker i will make a new tracking for my issue

@wanderer transfer in dotya.ml issue tracker i will make a new tracking for my issue

@wanderer transfer in dotya.ml issue tracker i will make a new tracking for my issue

will do, thanks for the write-up.

> @wanderer transfer in dotya.ml issue tracker i will make a new tracking for my issue will do, thanks for the write-up.
kreyren changed title from Make promotional website for the project on https://pman.rxt.eco to Wanderization 2022-08-30 14:38:29 +02:00
Author
Owner

Btw. the pman.rxt.eco is so far not indexed anywhere but i will keep an eye out for it (thanks for mentioning it :p)

Btw. the pman.rxt.eco is so far not indexed anywhere but i will keep an eye out for it (thanks for mentioning it :p)

Btw. the pman.rxt.eco is so far not indexed anywhere but i will keep an eye out for it (thanks for mentioning it :p)

no worries. it is not present in the public indices, but I am pretty sure the crawlers have been here and saved it as a broken link. still..you'll sort it out once relevant.

> Btw. the pman.rxt.eco is so far not indexed anywhere but i will keep an eye out for it (thanks for mentioning it :p) no worries. it is not present in the public indices, but I am pretty sure the crawlers have been here and saved it as a broken link. still..you'll sort it out once relevant.
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: kreyren/pman#13
No description provided.