\n When publishing documents and images on the web, you may unintentionally publish information
\n beyond what is immediately visible to the human eye. In particular, information that you might
\n not see, or that was intended to be redacted, might be included in some document formats and
\n visible to search engines.\n <\/p>\n
Because search engines index public material on the web, including images, content that is
\n not completely redacted can potentially be findable in search engines. Assistive technologies
\n like screen readers can make this seemingly “hidden” content more easily accessible, and
\n common image understanding techniques like optical character recognition (OCR) similarly make
\n it possible to search for this content.\n <\/p>\n
Even though putting text in a tiny font, using a font color that’s the same as the background
\n the text is on, or covering text with an image may make something invisible to the human eye,
\n these methods don’t actually redact material in a way that prevents search engines from
\n indexing it and making it findable.\n <\/p>\n
\n Similarly, some document types include information in various ways that aren’t immediately
\n visible. They might include the document’s change history, allowing users to see text that has
\n been redacted or altered. They might retain the full versions of images that contain cropped
\n or redacted information. There might also be metadata that’s included in a file, which is not
\n immediately visible, that may list the names of people who accessed or edited the file.\n <\/p>\n
\n All of this information can remain even when a document is exported or converted from one
\n format to another. If you need to remove information from a file, it’s critical that the
\n information is removed completely from the file before that file is made public.\n <\/p>\n
\n Here are some best practices for how to appropriately redact information from documents that
\n you don’t want to be indexed and made discoverable via Google Search.\n <\/p>\n
\n Google Search lists images that it finds across the web, both those that are on web pages or
\n those that are embedded into various document formats. Embedded images are sometimes edited
\n using only the containing document’s editing tools. This can cause this redaction to fail when
\n an image is indexed apart from the document. That is why it’s best to edit images before
\n embedding them into a document, not after. In particular:\n <\/p>\n
\n After following the suggestions in this document, export or save the updated images as non-vector or
\n flattened image file formats such as PNG or WEBP. This prevents those parts of the images from
\n being inadvertently included in a public document.\n <\/p>\n
\n Before you generate the public document, remove any text that you don’t want displayed in the
\n final version of the file. Move to a public format that does not keep your previous change
\n history. Here are more specific tips:\n <\/p>\n
noindex<\/code> robots<\/span> meta<\/code> tag<\/a>
\n to block indexing.\n <\/li>\n- \n When publishing, make sure that the website is
\n verified in Google Search Console<\/a>.
\n This allows quick removal action, if needed.\n <\/li>\n<\/ul>\nWhat to do if unredacted or improperly redacted documents are indexed in Search<\/h2>\n\n- \n Remove the live document from the website or location where you published it.\n <\/li>\n
- \n Use the Removals tool<\/a>
\n for the verified site to remove the documents in question from Search. Use a URL prefix if
\n you need to remove many documents. For verified sites, a URL removal generally takes less
\n than a day. This prevents the document in question from appearing for any searches for
\n redacted content.\n <\/li>\n- \n Host the properly redacted document under a different URL. This makes sure that any newly
\n indexed version is of the new document, and not an older version of the document (since
\n recrawling of URLs and updating them in a search index can take a bit of time). Update any
\n links to those documents.\n <\/li>\n - \n Contact any other site that may also be hosting the improperly redacted documents and ask
\n them to take them down as well. Ask them to use the Removals tool in their Search Console
\n account, or you can use the
\n Outdated Content tool<\/a>
\n to ask Google’s systems to update the search results.\n <\/li>\n- \n Allow the URL removal requests to expire (this happens after the URLs were either updated in
\n the Google Search index, or after about 6 months).\n <\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"Learn best practices for how to redact information from documents that you don’t want to be indexed and made discoverable via Google Search.<\/p>\n","protected":false},"menu_order":49,"template":"","meta":{"footnotes":""},"ar_kb_kategori":[688],"ar_kb_etiket":[],"class_list":["post-25563","ar_kb","type-ar_kb","status-publish","has-post-thumbnail","hentry","ar_kb_kategori-removals-crawling-and-indexing"],"_links":{"self":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb\/25563","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb"}],"about":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/types\/ar_kb"}],"version-history":[{"count":0,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb\/25563\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/media\/27583"}],"wp:attachment":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/media?parent=25563"}],"wp:term":[{"taxonomy":"ar_kb_kategori","embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb_kategori?post=25563"},{"taxonomy":"ar_kb_etiket","embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb_etiket?post=25563"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}