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.

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

Feature: inject metadata into head section #655

Closed
AnneB-SEO opened this issue Feb 27, 2019 · 3 comments
Closed

Feature: inject metadata into head section #655

AnneB-SEO opened this issue Feb 27, 2019 · 3 comments
Assignees

Comments

@AnneB-SEO
Copy link

Per our meeting today (2/27/2019) with: @debadair @nik9000 @nrichers @sylvie777 @liztauscher

We'd like a feature that will enable the Docs Team to inject a robots meta tag into the docs HTML head section for pages that will be removed. This will allow us to remove content from the Google search index, which cannot be done once the page is deleted.

Related document: How to Remove Content from the Google Search

@AnneB-SEO
Copy link
Author

Hi @nik9000 - Any update on this ticket?

@nik9000
Copy link
Member

nik9000 commented Apr 11, 2019

I haven't started and probably won't until I finish with the Asciidoctor conversion which is a few months out I think.

@debadair
Copy link
Contributor

debadair commented May 1, 2020

With the Asciidoctor migration complete, it is now possible to use the keywords and description attributes to inject metadata for a page. We can also inject custom attributes such as the robots meta tag using docinfo files:

  1. Create a docinfo.html file that contains the meta tag:

    <meta name="robots" content="noindex,nofollow”/>

  2. Add the docinfo attribute to the page. For example:

    :docinfo: shared
    ["appendix",role="exclude",id="redirects"]
     = Deleted pages```
    

I was not able to get per-page "private" doc info files to work, but setting the docinfodir attribute worked & could be used to differentiate between the shared robots tags and other uses of docinfo.

Closing this feature issue as complete, but this relates to #1820.

@debadair debadair closed this as completed May 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants