Improve SEO for embedded layers

[rtblair]

As an interested citizen searching for one or more maps that are offered as layers within ZoLa, one would have a hard time finding the resource via Google if they used a search term other than "NYC ZoLa" or "NYC Zoning and Land Use". For example, Zola does not appear on the first page of "NYC Sidewalk Cafe Zoning" results, and it probably should since we are an authoritative source.

Obviously this would need a path analysis, but I'll just share the following suggestion so we have it in our notes.

I propose that we create a path for each of the layers, encoding the title of the layer in <h1> or <h2> tags, and include a verbose description for each layer that can be fodder for the search engines. When a user lands on that URL, that layer should be the only one selected. URLs representing these layers should be encoded in a sitemap.xml file at the website's root directory. In the universe of things that can be done to improve SEO, these steps would probably get us 80% of the improvement for 20% of the effort.

[allthesignals]

So to break this up into first steps:

1. (?) Create a path for each of the layers. Is this already handled by query params? for example: https://zola.planning.nyc.gov/l/lot/1/1443/11?layer-groups=%5B%22building-footprints%22%2C%22street-centerlines%22%2C%22subway%22%2C%22zoning-map-amendments%22%5D. Or are you imagining explicit routes?
2. Encode the title of the every layer in the menu in <h1> or <h2> tags
3. Include a verbose description for each layer that can be fodder for the search engines (there are tooltips for each layer that could be used here — maybe another hidden element could include an even more verbose description if that helps with SEO)
4. URLs representing layers should be encoded in a sitemap.xml file at the website's root directory (note: there is a sitemap script that generates sitemap links here)