curious_
Junior Member
- Aug 26, 2020
- 169
- 40
An article on aged Medium account looks like this in SERP
- Dec 7, 2008
- 2,603
- 731
Just see if anything got accidentally changed in the article or your account settings. Ask Medium support for help if you're unsure.
curious_
Junior Member
- Aug 26, 2020
- 169
- 40
- Jun 16, 2019
- 6,487
- 7,221
take a look at the cached version of the page, probably some error occurred while google bots tried to fetch the page,
give it some time so they can recrawl it, using some indexing service or pbn can speed up the process,
make sure the page doesn't contain the noindex tag as well, it's very common with medium since a couple of years,
less likely to happen with an aged account with engagement, but still could be added in case of adding some suspicious links, thin/illegal/bh content, etc...
give it some time so they can recrawl it, using some indexing service or pbn can speed up the process,
make sure the page doesn't contain the noindex tag as well, it's very common with medium since a couple of years,
less likely to happen with an aged account with engagement, but still could be added in case of adding some suspicious links, thin/illegal/bh content, etc...
- Feb 16, 2018
- 1,161
- 882
Think Google did away with the cache, didn't they?
- Jun 16, 2019
- 6,487
- 7,221
works well on my end,
i believe they're just removing the buttons from the serps, isn't it the case?
- Feb 16, 2018
- 1,161
- 882
terrycody
Elite Member
- Sep 29, 2012
- 6,157
- 3,191
Soon not anymore too, cache funtion is going away...soon cache: instruct will not working.
ForgedBetaMaster
Newbie
- Feb 9, 2024
- 5
- 2
Usually this is observed when you directly check the indexing of a page with site: operator but that page or directory is blocked from robots.txt file. So once check robots.txt to make sure that the page you are checking indexing for is in a directory that is blocked in robots.txt.
curious_
Junior Member
- Aug 26, 2020
- 169
- 40
thanks for the comments and thoughts
1) the article is INDEX
2) here is how medium robots.txt looks like:
User-Agent: *
Disallow: /m/
Disallow: /me/
Disallow: /@me$
Disallow: /@me/
Disallow: /*/edit$
Disallow: /*/*/edit$
Disallow: /media/
Disallow: /p/*/share
Disallow: /r/
Disallow: /trending
Disallow: /search?q$
Disallow: /search?q=
Disallow: /*/search?q=
Disallow: /*/search/*?q=
Disallow: /*/*source=
Allow: /_/
Allow: /_/api/users/*/meta
Allow: /_/api/users/*/profile/stream
Allow: /_/api/posts/*/responses
Allow: /_/api/posts/*/responsesStream
Allow: /_/api/posts/*/related
Sitemap: https://medium.com/sitemap/sitemap.xml
User-Agent: GPTBot
Disallow: /
I don't see any signs of my URL being affected by this robots.txt, correct me if i'm wrong.
I'm not an expert in robots files, but from my understanding, if Medium would somehow mark or disallow URLs like mine in their Robots.txt, their file would be crazy long. So there is something else they did to my URL.
3) I re-indexed the URL a while ago using a proven method, but it didn't work.
A few of my questions now:
- Is there something else besides https://medium.com/robots.txt and INDEX/NOINDEX that Medium can do on their end to cause this type of issue in SERP?
- Can it be on Google side? Maybe that's how they ignore some URLs if the content is not helpful enough.
1) the article is INDEX
2) here is how medium robots.txt looks like:
User-Agent: *
Disallow: /m/
Disallow: /me/
Disallow: /@me$
Disallow: /@me/
Disallow: /*/edit$
Disallow: /*/*/edit$
Disallow: /media/
Disallow: /p/*/share
Disallow: /r/
Disallow: /trending
Disallow: /search?q$
Disallow: /search?q=
Disallow: /*/search?q=
Disallow: /*/search/*?q=
Disallow: /*/*source=
Allow: /_/
Allow: /_/api/users/*/meta
Allow: /_/api/users/*/profile/stream
Allow: /_/api/posts/*/responses
Allow: /_/api/posts/*/responsesStream
Allow: /_/api/posts/*/related
Sitemap: https://medium.com/sitemap/sitemap.xml
User-Agent: GPTBot
Disallow: /
I don't see any signs of my URL being affected by this robots.txt, correct me if i'm wrong.
I'm not an expert in robots files, but from my understanding, if Medium would somehow mark or disallow URLs like mine in their Robots.txt, their file would be crazy long. So there is something else they did to my URL.
3) I re-indexed the URL a while ago using a proven method, but it didn't work.
A few of my questions now:
- Is there something else besides https://medium.com/robots.txt and INDEX/NOINDEX that Medium can do on their end to cause this type of issue in SERP?
- Can it be on Google side? Maybe that's how they ignore some URLs if the content is not helpful enough.
- Feb 28, 2019
- 5,093
- 6,568
Google couldn't fetch the page content during crawl. If it didn't fix itself during the next crawl, then medium might be having a crawl budget.