Open rnorigian opened 1 year ago
Here's the Google article that spawned this idea: https://developers.google.com/search/docs/advanced/guidelines/hidden-text-links
@rnorigian Thanks for adding this. We may need to clarify the bullet points under "Expected behavior" a bit:
At the OUC weekly yesterday Joel said that there are a number of other sites (besides Policy) that use DSF that don't have OUC's manual workaround (to get google to crawl) in place. When you're ready to test this, Joel can identify the sites we'd use for monitoring effectiveness.
OK. There are currently some issues with this that don't relate to getting the data, but relate to the way the dreact module itself works. Some early choices in the project are causing major headaches. Right now I'm trying to get around needing to completely nuke all of the key/value pairs across all sites in order to get it to reload properly.
To better equip Google's crawler to find DReact related content (like a list of links on the Policies site), modify the dreact module to inject a list of links into a
<noscript>
tag derived from the assigned endpoint (Drupal View) on the page that the DReact app is embedded.This injection should only happen when the DReact app is set as "search-filter" (DSF).
Example endpoint view value: https://dev.policy.brown.edu/dsf_combined
Expected behavior:
<noscript>
tag