Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Support blocking search engines (support custom <head> content?) #186

Closed
tsmacdonald opened this issue Jan 31, 2024 · 3 comments
Closed

Support blocking search engines (support custom <head> content?) #186

tsmacdonald opened this issue Jan 31, 2024 · 3 comments
Assignees
@tsmacdonald

Comments

@tsmacdonald
Copy link
Collaborator

My motivating case is wanting to add a <meta name="robots contents="noindex"> to the <head> to block search engines from indexing the docs, but as I think about it it'd probably be best to support poking arbitrary content in there (maybe for opengraph attributes?).
@tsmacdonald tsmacdonald self-assigned this Jan 31, 2024
@tsmacdonald tsmacdonald mentioned this issue Jan 31, 2024
Merged
@seancorfield
Copy link
Member

Can you explain why you wouldn't want search engines to index publicly available uberdocs?

Also, is this a case of wanting a control to enable this or a control to insert <head> content or...?

@seancorfield
Copy link
Member

It seems reasonable to add a :meta option to the :marginalia key in project.clj that could be a hash map of name/contents:

  :marginalia {:meta {:robots "noindex"}}

That would produce:

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

in the <head> tag -- but could be used to insert other <meta> tags.

@seancorfield
Copy link
Member

Marginalia 0.9.2 released with this (and many other) fixes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tsmacdonald tsmacdonald

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@seancorfield @tsmacdonald