Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • pleroma pleroma
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 647
    • Issues 647
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 88
    • Merge requests 88
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • PleromaPleroma
  • pleromapleroma
  • Issues
  • #1601
Closed
Open
Issue created Mar 05, 2020 by SilverWolf@SilverWolf

Remote accounts are exposed to search engine indexing regardless of their "disable search engine indexing" preference on the host instance

When Pleroma pulls remote account metadata, it stores it locally and exposes it to search engines. This wouldn't be a problem if it were restricted to accounts that wanted that – but it's not.

According to https://marf.space/objects/71bcb26a-b934-45f6-807f-69bb417d8509, crawlers can start at the federated timeline and end up at our local copy of the profile.

https://marf.space/objects/7d46a7bd-1053-4712-9aca-35529b0e98c0 explains that Mastodon's feature to tell search engines to not index profiles is done through a meta tag:

<meta content="noindex, noarchive" name="robots">

I've looked on my Pleroma alt instance's copy of my Mastodon main's profile and this meta tag is not there. Could we respect it and add the same meta tag to our local copies of remote accounts?

#1206 (closed) is also relevant here, and looks like it would also solve the problem of exposing remote users to search engines in a different way.

Edited Mar 05, 2020 by SilverWolf
Assignee
Assign to
Time tracking